| 12 | | Like I mentioned in the OP, you need to use vboxmanage (their CLI tool), not the GUI. The GUI works fine, but this is a blocker '''(100% "blocker", not a "major bug")''' for any Windows 10 user solely using scripting for VirtualBox use (for example, use with headless VMs). Do the exact same steps you just did, only via the CLI "vboxmanage.exe", and that is how I reproduced this on multiple computers. |
| | 12 | Like I mentioned in the OP, you need to use vboxmanage (their CLI tool), not the GUI. The GUI works fine, but this is a blocker '''(100% "blocker", not a "major bug")''' for any Windows 10 user solely using scripting for VirtualBox use (for example, use with headless VMs). Do the exact same steps you just did, only via the CLI "vboxmanage.exe", and that is how I reproduced this on multiple computers: |
| | 13 | |
| | 14 | |
| | 15 | {{{ |
| | 16 | vboxmanage.exe import "path/to/myvm.ova" |
| | 17 | }}} |
| | 18 | Will show success, but not show in listvm, will not show in GUI, and you can't manage it. BUT it generates a .vbox file @ VirtualBox VMs/myvm.vbox |
| | 19 | |
| | 20 | {{{ |
| | 21 | vboxmanage.exe list vms |
| | 22 | }}} |
| | 23 | Will show 0 vm's (unless added by GUI or manually opened the .vbox file itself). BUT, it will show your VM in elevated cmd prompt (documentation shows elevation isn't necessary, so this is strange). BUT #2, you can't do anything with it, even if listed elevated -- it will still say not found if you try any other cmd, even using the uid itself. Strange behavior. |
| | 24 | |
| | 25 | {{{ |
| | 26 | vboxmanage.exe modifyvm myvm <anything> |
| | 27 | }}} |
| | 28 | Will show cannot find VM, whether elevated or not. Unless you opened the .vbox file manually. |
| | 29 | |
| | 30 | {{{ |
| | 31 | vboxmanage.exe startvm myvm <whatever params, or blank> |
| | 32 | }}} |
| | 33 | Will show launch failed, can't find VM -- in ALL situations -- even if elevated, even if added to GUI via double clicking the .vbox file |
| | 34 | |
| | 35 | It WILL launch normally if double clicked from GUI *IF* you manually opened the .vbox file, but again, things work ONLY if you use the GUI and does NOT work if you use CLI. |