Friday, 18 January 2019

Fix issues with VirtualBox v6 and VMUB (fix --startvm error)

The new version 6 of Oracle VirtualBox has changed executables and so it has (deliberately!) broken backwards compatibility with all earlier scripts, shortcuts and applications which call VirtualBox.

This includes DavidB's VMUB application. To make VMUB work with the new VBox 6 version:

Workaround for VBox v6 (fix for --startvm error)

I recommend changing the executable path to VirtualBoxVM.exe.
However the 'Manage' button in VMUB will not work. If you want to run Virtual Box Manager then set up an Administrator Desktop shortcut if you want to run the Manager.

The fix below does NOT lock the USB drive and can cause boot failures.

1. In VMUB - Options - VirtualBox - change Exe Path to C:\Program Files\Oracle\VirtualBox\VMUB.cmd

2. Run an Admin cmd shell (use WinKey+X - Powershell (as Admin) - and then type cmd to get a cmd shell).

3. Type

cd "\Program Files\Oracle\VirtualBox"

4. To create a new file in the \Program Files\Oracle\VirtualBox folder called VMUB.cmd

Type on the command line:

Notepad VMUB.cmd

5. Type and save the following text:

@echo off
if "%1"=="" start VirtualBox.exe
if not "%1"=="" start VirtualBoxVM.exe %*

Note: This fix does not work correctly because the .cmd file causes the USB drive to be re-mounted by Windows. This means that booting to WinPE, etc. from VMUB may not work.

No comments:

Post a Comment