VMs stopped working on Win7 host

Discussions related to using VirtualBox on Windows hosts.
Post Reply
aleksashka
Posts: 2
Joined: 1. Dec 2022, 06:14
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Win7, CentOS, Rocky

VMs stopped working on Win7 host

Post by aleksashka »

Hello,

TLDR; VBoxHardening.log is attached. The last line of it is:

Code: Select all

248.1cec: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x40000015 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 2969 ms, the end);
First this happened on my PC (Win7 host) about a month or so ago - I could not start any VM (Win7, WinXP, CentOS7, Rocky8). I tried to Google the solution, updated VBox, rebooted the host, etc. Then I moved one of the VMs to my laptop (same Win7 host), VM started fine and I decided that may be some software is getting in the way of VBox, but few days ago I received the same error on my laptop as well...

I have not updated Win7 on PC or laptop, so just in case here is a list of recently updated software from Control Panel -> Uninstall a program (sorted by install date) from my laptop, which I use right now:
Microsoft Edge WebView2 Runtime (version 107.0.1218.62, installed on 2022-12-01, I presume Chrome installed this :?)
Google Chrome (version 107.0.5304.123, installed on 2022-12-01)
Oracle VM VirtualBox 7.0.4 (version 7.0.4, installed on 2022-11-30)
Telegram Desktop (version 4.3.3, installed on 2022-11-26)

I haven't tried to uninstall Chrome (it's kind of a headache to tie all my Google accounts back) or Telegram (for no particular reason :D), but I do remember uninstalling WebView on my PC and it didn't help (rebooted host after removing). Neither helped reinstalling VBox.

I threw many threatening glances at the log-file, but no secrets were revealed (my VBox-Log-interrogation skills suck :?). Hopefully someone with a great level of VBox-Log-reading-power could help me :).

Thank you.

Update:
Forgot to show the message from VBox while starting VM:

Code: Select all

---------------------------
VirtualBox - Error In supR3HardenedWinReSpawn
---------------------------
<html><b>Error relaunching VirtualBox VM process: 5<br>Command line: '60eaff78-4bdd-042d-2e72-669728efd737-suplib-3rdchild --comment VM_01 --startvm 3cab6bb2-cd26-4aed-b67b-0e2e19243719 --no-startvm-errormsgbox --sup-hardening-log=D:\vms\VM_01\Logs\VBoxHardening.log' (rc=-104)</b><br/><br/>Please try reinstalling VirtualBox.<br><br><!--EOM-->where: supR3HardenedWinReSpawn
what:  5
VERR_INVALID_NAME (-104) - Invalid (malformed) file/path name.
</html>
---------------------------
OK   
---------------------------
Message from notification center:

Code: Select all

VM Name: VM_01

The virtual machine 'VM_01' has terminated unexpectedly during startup with exit code 1073741845 (0x40000015). More details may be available in 'D:\vms\VM_01\Logs\VBoxHardening.log'.
Result Code:
E_FAIL (0X80004005)
Component:
MachineWrap
Interface:
IMachine {300763af-5d6b-46e6-aa96-273eac15538a}
Starting VM from command line doesn't show anything in CMD:

Code: Select all

C:\Program Files\Oracle\VirtualBox>VirtualBoxVM --startvm "VM_01"

C:\Program Files\Oracle\VirtualBox>
Attachments
VBoxHardening.zip
Win7 guest, normal start
(15.62 KiB) Downloaded 70 times
aleksashka
Posts: 2
Joined: 1. Dec 2022, 06:14
Primary OS: MS Windows 7
VBox Version: PUEL
Guest OSses: Win7, CentOS, Rocky

Re: VMs stopped working on Win7 host

Post by aleksashka »

Is it too bad?
mpack
Site Moderator
Posts: 39156
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: VMs stopped working on Win7 host

Post by mpack »

VirtualBox stopped supporting Win7 hosts a considerable time ago, so yes, it is what it is.
Post Reply