virtualbox.org

I just upgraded VirtualBox on my Windows 10 PC to version 6.1.36 r152435 (Qt5.6.2).

I opened VB and tried to launch my VM, but there was an error and it wouldn't launch. Attached is a screenshot of the error, and the file VBHardening.log which was mentioned in the error message. The text of the error that was copied to the clipboard when I clicked "Copy" is:
=======
Failed to open a session for the virtual machine RHEL first.
The virtual machine 'RHEL first' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\paulc\VirtualBox VMs\RHEL first\Logs\VBoxHardening.log'.
Result Code: E_FAIL (0x80004005)
Component: MachineWrap
Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
======
The log file suggested to run a command, I ran the command and got this output:
------
C:\Users\paulc\VirtualBox VMs\RHEL first\Logs>sc.exe query vboxdrv
[SC] EnumQueryServicesStatus:OpenService FAILED 1060:

The specified service does not exist as an installed service.
------
I'm using a Dell XPS 8930 tower PC running Windows 10. The VM is RHEL. Help debugging this would be much appreciated.

Uninstall Virtualbox and reboot.
Go to "C:\Windows\System32\drivers", look for any files called 'Vbox*.sys' (there could be up to 5) and delete them.
Reboot again.
If you have any 3rd-party security or anti-malware software, disable the living daylights out of it for a moment.
Reinstall Virtualbox using right-click-Run-As-Administrator.

thanks that worked

If I follow scottgus1's advice

(Uninstall Virtualbox and reboot etc)

If I do this do I lose all my VMs

A reply would be apperciated

Thanks

Is this a question?

Because uninstalling software never causes your data to be deleted. VMs are data as far as the host is concerned.

Many thanks for that

same problem here. It worked for me. Thanks for sharing.

I just deleted a repeated thanks from Mazda323f, I guess he didn't notice it was repeated. But anyway no more thanks in this topic please - those are technically off topic chatter unless they come from the OP.

Reinstalling Virtualbox did not get rid of the error for me.

Workaround for me now was exporting as ova and importing in VMware Workstation. I would guess that exporting again to Virtualbox would then be possible, but I haven't tried that. At least this lets me boot the VMs again.

JM-Lemmi wrote:Workaround for me now was exporting as ova and importing in VMware Workstation.

More like a work-away. But at least you got your VM running somewhere. If & when you want to troubleshoot Virtualbox again, please start your own topic.
Do not hijack other threads, create your own. Choose your title carefully.
Minimum Info Needed for Assistance