[Solved] Unable to start VMs on Windows 10 User 1903 after update

Discussions related to using VirtualBox on Windows hosts.
Post Reply
lmb02
Posts: 3
Joined: 23. Jun 2019, 04:31

[Solved] Unable to start VMs on Windows 10 User 1903 after update

Post by lmb02 »

Hello,

I was running fine before upgrading to 1903 HOME edition. After upgrade I created a restore point then tried to install the Windows Sandbox. It didn't work (I know, it's only supposed to run on Pro but I tried the fix to run it on Home Edition). I then rolled back.
When I tried to launch VirtualBox it blew up with the following error:
NtCreateFile(\Device\VboxDrvStub) failed: 0xc0000034
STATUS_OBJECT_NAME_NOT_FOUND (0 retries) (rc=-101)

Make sure the kernal 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 might actually help.
When I issue the sc command I get:
E_NAME: vboxdrv
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 31  (0x1f)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
After about a minute a popup appears saying it is trying to create a process for the VM.

At one point I got a message saying Windows thought the digital signature was not recognised (I can't reproduce the condition that caused that message to be displayed, to my annoyance).

The various suggestions I found when searching the forum appear to be for 1903 Pro edition and different from what I've encountered. I've uninstalled and reinstalled and rebooted several times, using 5.2.28, 6.0.8, and 6.0.9(beta).

Any assistance will be greatly appreciated.
lmb02
Posts: 3
Joined: 23. Jun 2019, 04:31

Re: Unable to start VMs on Windows 10 User 1903 after update

Post by lmb02 »

Read the topic about hardening and tried a few of the suggestions.

1) Ran without AV to see if that was the problem because of the certificate message. Made no difference.

2) Ran sfc /scannow. No integrity violations.

Attaching hardening log.

Again, any assistance will be welcome.
Attachments
VBoxHardening.zip
(2.62 KiB) Downloaded 27 times
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Unable to start VMs on Windows 10 User 1903 after update

Post by socratis »

  1. Uninstall VirtualBox. Your VMs are going to be untouched. Reboot.
  2. You may want to clean up your registry and/or filesystem at this point. CCleaner is a freeware utility that could help you. Mind the installation, it comes with "offers" from 3rd parties, known as "bundleware". Also, check out Device Cleanup program that helps you to remove any unused devices from your computer, mainly multiple "Host-Only Adapter #n".
  3. Download (if you haven't already) the latest VirtualBox and its matching ExtPack. Store them in a common location, i.e. not on "Desktop", or "Documents", but to "Public/Downloads" for example.
  4. Uninstall (don't simply disable) all 3rd party antivirus. If you're afraid about your computer being vulnerable, pull the Ethernet plug, disconnect your WiFi, don't go browsing around.
  5. Locate the downloaded file in Windows Explorer. Right-click on the installer and select "Run-as-Administrator", even if you are the administrator. At the end of the installation, choose to "Start Oracle VM VirtualBox". Do not worry if your VMs do not show up.
  6. If you're going to install the ExtPack, go to File » Preferences » Extensions. Click on the icon with the orange, down-pointing arrow on the right. Select the ExtPack from the previous steps.
  7. Quit VirtualBox. Re-start VirtualBox as you would normally, i.e. from the Desktop shortcut or the Start menu.
  8. Update the Guest Additions (GAs) in your guest(s), if the GAs are available for a specific guest.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
lmb02
Posts: 3
Joined: 23. Jun 2019, 04:31

Re: Unable to start VMs on Windows 10 User 1903 after update

Post by lmb02 »

Thank you. Followed your instructions and everything running again.

Many thanks!!
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Unable to start VMs on Windows 10 User 1903 after update

Post by socratis »

Glad you got it going. Marking as [Solved].
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
POuria25
Posts: 11
Joined: 12. Jun 2020, 11:58

Re: [Solved] Unable to start VMs on Windows 10 User 1903 after update

Post by POuria25 »

hello,

I have a similar problem in which my PC ran into a problem (Blue screen) after upgrading VM from 6.0.20 to 6.1.10 and I have followed your instruction but it doesn't work!


Please help me
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: [Solved] Unable to start VMs on Windows 10 User 1903 after update

Post by scottgus1 »

POuria25, your other post viewtopic.php?f=6&t=98590 has a response. Please continue there.
Post Reply