Unable to boot VM after upgrade of Extension Pack

[Brad123]

Upgraded to VirtualBox 6.1.34 with the latest extension pack 6.1.34 from Windows 10(64bit) HOST, and now cannot launch the Windows 10(64bit) guest.

1. I upgraded the extension pack and then I wasn't able to boot my virtual machine - it came up with an error.
2. So I downgraded the extension pack back:

VirtualBoxExtensionPack1.PNG (19.25 KiB) Viewed 3457 times

3. It came up with an error where the extension pack seemed to have failed to install:

VirtualBoxExtensionPack2.PNG (66.76 KiB) Viewed 3447 times

4. I still can't boot my virtual machine. When attempting to install the old one back (I chose the 'Downgrade to the 6.0.24 version), it says the extension pack is already installed, and I can't reinstall it.
So when I go to install it (by clicking the downloaded 6.0.24 version installer) I get message to reinstall it:

VirtualBoxExtensionPack3.PNG (65.58 KiB) Viewed 3447 times

5. But when I continue to reinstall it, I get 'Failed to load main module' error: [VirtualBoxExtensionPack4]
6. When I do a File->Update, it says I am already running the current version of VirtualBox. But then it says: "I'm running an old version (6.0.24) of the extension pack - shall I download the latest one (6.1.34) ?" I said yes and it said it was installed successfully.
7. But when I go to launch my virtual machine, it gives the error: "Make sure the Kernel Module has been loaded successfully":
[VirtualBoxExtensionPack4]
[VirtualBoxExtensionPack5]
[VirtualBoxExtensionPack6]
8. Looking at the VBoxHardening.log it says: "Driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help."
I tried to query the vboxdrv, but it doesn't look like it is installed: [VirtualBoxExtensionPack7]
9. I tried to launch it via command prompt, but the same kernel error occurs: [VirtualBoxExtensionPack8]
10. I tried to pause/resume/poweroff it via command prompt, but is said it is not currently running (fair enough!). I tried to discard the state, but it says it's not in a saved state (the machine is currently powered off)
11. I restarted my HOST OS and I can confirm my Virtual Box version is 6.1.34, and looked at File->Preferences=>Extensions and can also confirm the Extension Pack is 6.1.34.

Do i need a process running prior to launching the VirtualBox gui? Do i need to 'reboot' the VM somehow even though it is already switched off?
Please, please can any one suggest what to do?? Thank-you for your much-needed help.

[mpack]

The first dialog shows you downgrading to extension pack 6.0.24.

The remaining dialogs show the 6.0.24 extpack failing to load because it's the wrong version. It has to match the host version.

I see nothing unexpected here.

[scottgus1]

One other thing, on Windows hosts, Virtualbox has to Run As Administrator to install the Extension Pack. Normally Virtualbox asks for this permission, but sometimes the permission doesn't come through.

Reboot the host so no Virtualbox processes are running.
Right-click Virtualbox and Run As Administrator.
Uninstall whatever Extension Pack is shown now, and install the Extension Pack that matches the Virtualbox version you have installed. As Mpack points out above, the EP and Virtualbox versions must match exactly.
After the EP installs, close Virtualbox.
Log off your account, then log on again.
Virtualbox should now have the proper EP installed.

The final log-off & on is to be sure Run As Administrator is cleared from Virtualbox, which does not need and should not have Admin permissions when running normal VMs.

Note that if the EP installs correctly and you still cannot run the VMs, please report he exact error you get, as you did above, but don't do anything about it until we advise.

[Brad123]

Hi,

mpack thanks for the response. Yes, I understand what you are saying, but in my point 6 I did actually upgrade it to the same version number, and it said the installation of the service pack was successful.
And then in my point 11, I rebooted the HOST and checked the version number of VirtualBox (Help->About), and the version number of the extension pack (File->Preferences->Extensions->), and it showed the same (v6.1.34 r150636)

Hi scottgus1 thank-you as well. I have followed your steps and note I do have full admin access (I'm an administrator) on the Host.

1. I rebooted the HOST (restarted my windows 10 machine)
2. Right-clicked Virtualbox and selected Run As Administrator
3. Uninstalled the extension pack in File->Preferences->Extensions (it was v6.1.34 r150636)
4. Installed the Extension Pack that matches the Virtualbox version you have installed. (Went to the Virtualbox Wiki Downloads and downloaded the 6.1.34 Extension Pack and clicked on it to run. It installed successfully)
5. Closed VirtualBox
6. Restarted the machine (I have no feature to log off as I have set windows to auto log me on)
7. Confirmed VirtualBox and Extension Pack have same version number v6.1.34 r150636
8. Then when trying to launch, I get the error 'STATUS_OBJECT_NAME_NOT_FOUND - Make sure the kernel module has been loaded successfully.'

ErrorMsg1.PNG (64.2 KiB) Viewed 3354 times

9. Then when clicking OK, I get 'Failed to open a session for the virtual machine...'.

ErrorMsg2.PNG (74.18 KiB) Viewed 3354 times

[Brad123]

Hi again,
I have the logs available if needed? Did you manage to get a chance to look into the error?
(It also seems my Ubuntu VM is having the same problem, but this is not important - i really need the Windows Guest to work)
I even tried to create another Windows VM, but the same error occurs when i boot it up (before I can even install the OS)

Should I roll-back to a previous version of VirtualBox (and the related Service Pack) maybe?

Please can you assist at all?
Thank-you so much, Brad.