VirtualBox v6.1.34 shows "Make sure the kernel module has been loaded successfully" and VM wont start

[Syl20]

VM no longer starts after:

• a VirtualBox upgrade
• then a Windows Update

• had VirtualBox-6.1.32-149290-Win.exe installed since 01/31/2022
• On 05/09/2022, I upgraded it with VirtualBox-6.1.34-150636-Win.exe
• VM working perfectly. Saved, or closed and reopened...
• on 05/12/2022, I rebooted windows, and a Windows Update took place.
• Then, VM no longer starts with message:

VirtualBox - Error In supR1HardenedWinReSpawn
NtCreateFile(\Device\VBoxDrvStub) failed: 0xc0000034
STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)

Make sure the kernel module has been loaded successfully.

where: supR3HardenedWinReSpawn what: 3 VERR_OPEN_FAILED (-101) - File/ Device open failed. driver is probably stuck stopping/starting. Try 'sc.exe query vboxdrv' to get more information about its state. Rebooting may actually help.

I rebooted windows. Same issue.

• I just discovered that downgrading fixed the problem.

I looked in windows update history and saw:

• on 05/11/2022, (one day before my "Update and restart" though this one ​http://support.microsoft.com/kb/890830. Others are too old

Also, working on a professional laptop, with windows administration by our IT team, I saw this notification after the "update and restart" of windows (did not have time to screenshot it), it was saying something like "an administrator has changed the rights on some path..." Don't know if it helps.

Hardware: Intel(R) Core(TM) i7-10750H CPU @ 2.60Ghz 64Go Windows 11 professional Version 21H2 Build 22000.675 Experience 1000.22000 675.0

[Syl20]

1st error after trying to run an Ubuntu VM

[Syl20]

2nd error after closing the first one

[Khun_Doug]

I am seeing the same error, but only after upgrading my 6.1.34 build to beta 6.1.35 r151573. It is the same error message as highlighted in the original post. I do have the hardening.log file if needed.

[Vort]

Try installing VirtualBox\drivers\vboxsup\VBoxSup.inf driver manually and then starting it manually too: sc.exe start vboxsup (with admin rights).