I use VirtualBox 7.0.6 on Windows 11 22H2. Yesterday I rebooted the host OS, but I forgot to power off a running VirtualBox VM first. After the host restarted, I found all VMs cannot be started, with error messages like this:
VM Name: Windows 11 x64
The virtual machine 'Windows 11 x64' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\w_ou\VirtualBox VMs\Windows 11 x64\Logs\VBoxHardening.log'.
Result Code:
E_FAIL (0X80004005)
Component:
MachineWrap
Interface:
IMachine {300763af-5d6b-46e6-aa96-273eac15538a}
Furthermore, I found the VirtualBox host-only network adapter doesn't exist in the network adapter list of Windows 11. I tried to uninstal and reinstall VirtualBox, the problem still exists. The progress bar of the installer suspends for several minutes at about 70%. I guess the installer tried to create the virtual network adapter and failed at that time. When I start the VirtualBox Manager, enter the Network Manager and try to create the host-only network interface manually, the progress bar suspends several minutes and fails. The error message is:
Name: TBD
Querying NetCfgInstanceId failed (ERROR_FILE_NOT_FOUND).
Result Code:
E_FAIL (0X80004005)
Component:
HostNetworkInterfaceWrap
Interface:
IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}
How to solve this problem?
All VMs failed to start (with exit code 1) after host OS rebooted
All VMs failed to start (with exit code 1) after host OS rebooted
- Attachments
-
- VBoxHardening.zip
- VM start failure log
- (14.11 KiB) Downloaded 5 times
Re: All VMs failed to start (with exit code 1) after host OS rebooted
I forgot to mention another error message: After I reinstalled VirtualBox, when I run VirtualBox Manager soon after I reboot the host Windows 11 every time, the UAC dialog will pop up and ask "Do you want to allow this app to make changes to your device?" After I click "yes", the Manager app suspends for at least 2 min, then the main window becomes visible with the following error message:
Failed to acquire host parameter.
Callee RC:
E_ACCESSDENIED (0X80070005)
Failed to acquire host parameter.
Callee RC:
E_ACCESSDENIED (0X80070005)
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: All VMs failed to start (with exit code 1) after host OS rebooted
There's probably something really wrong with the Virtualbox installation.
- 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.
Re: All VMs failed to start (with exit code 1) after host OS rebooted
Unfortunately the problem still exists. The installer suspends at least 2 min when the progress bar at about 70%. After installation when I run VirtualBox Manager, the app suspends for 2 min and show the main window with the error message I mentioned above: "Failed to acquire host parameter. Callee RC: E_ACCESSDENIED (0X80070005)".scottgus1 wrote:There's probably something really wrong with the Virtualbox installation.
- 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.
Maybe the host OS itself has some problem?
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: All VMs failed to start (with exit code 1) after host OS rebooted
Could be. Or over-aggressive 3rd-party AV?merced wrote:Maybe the host OS itself has some problem?
The Virtualbox installer is really a Microsoft program that works with the Windows MSI installer database.
Please try this:
Make a new folder on your C drive to put the installer and the log it will make:
C:\VBinstall
Put the installer in the new folder. Open a Run-As-Admin command prompt. Drag-n-drop the installer on the Command Prompt window, then finish typing this in the command line:
"C:\VBinstall\VirtualBox-X.Y.Z-######-Win.exe"{space}--logging{space}--msi-log-file{space}"C:\VBinstall\textfile.txt"
So, as an example, for 6.1.36 it should've read:
"C:\VBinstall\VirtualBox-6.1.36-152435-Win.exe" --logging --msi-log-file "C:\VBinstall\msilog.txt"
Your version's numbers will be different, but you shold follow the same pattern.
Also find this file:
C:\Windows\INF\setupapi.dev.log
Zip and post both logs using the forum's Upload Attachment tab.
Re: All VMs failed to start (with exit code 1) after host OS rebooted
Actually some errors found in those 2 log files.scottgus1 wrote:Please try this:
Make a new folder on your C drive to put the installer and the log it will make:
C:\VBinstall
Put the installer in the new folder. Open a Run-As-Admin command prompt. Drag-n-drop the installer on the Command Prompt window, then finish typing this in the command line:
"C:\VBinstall\VirtualBox-X.Y.Z-######-Win.exe"{space}--logging{space}--msi-log-file{space}"C:\VBinstall\textfile.txt"
So, as an example, for 6.1.36 it should've read:
"C:\VBinstall\VirtualBox-6.1.36-152435-Win.exe" --logging --msi-log-file "C:\VBinstall\msilog.txt"
Your version's numbers will be different, but you shold follow the same pattern.
Also find this file:
C:\Windows\INF\setupapi.dev.log
Zip and post both logs using the forum's Upload Attachment tab.
Thanks a lot!
- Attachments
-
- VBInstall.zip
- (232.18 KiB) Downloaded 4 times
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: All VMs failed to start (with exit code 1) after host OS rebooted
I'm not too good at interpreting these logs, but maybe a forum guru might see what's up.
I see the Host-Only system not installing for some reason./
I also see some Chinese (I think) in the log. I wonder if you could change your computer language to English, if the install would work. There could be a bug in the installer.
I see the Host-Only system not installing for some reason./
I also see some Chinese (I think) in the log. I wonder if you could change your computer language to English, if the install would work. There could be a bug in the installer.
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: All VMs failed to start (with exit code 1) after host OS rebooted
I don't know how to solve them correctly, but here are some issues found:
This pattern occurs several times. VBoxNetLwf.inf gets installed as oem24.inf, and Windows doesn't accept the contents. This prevents the VBoxNetLwf.sys driver from installing. Compare the two INF files. If they're not identical, get rid of oem24.inf somehow.setupapi.dev.log wrote:>>> [SetupCopyOEMInf - C:\Program Files\Oracle\VirtualBox\drivers\network\netlwf\VBoxNetLwf.inf] >>> Section start 2023/03/21 00:04:20.045 cmd: C:\Windows\System32\MsiExec.exe -Embedding 6348F14615358CF46428335F39D2B512 E Global\MSI0000 inf: Copy style: 0x00000000 ! inf: Driver package is already in driver store sto: {Setup Import Driver Package: C:\Program Files\Oracle\VirtualBox\drivers\network\netlwf\VBoxNetLwf.inf} 00:04:20.049 sto: Driver package already imported as 'oem24.inf'. sto: {Setup Import Driver Package - exit (0x00000000)} 00:04:20.056 inf: Driver Store Path: C:\Windows\System32\DriverStore\FileRepository\vboxnetlwf.inf_amd64_40a3826078769700\vboxnetlwf.inf inf: Published Inf Path: C:\Windows\INF\oem24.inf <<< Section end 2023/03/21 00:04:20.059 <<< [Exit status: SUCCESS] >>> [Install network driver - oracle_VBoxNetLwf] >>> Section start 2023/03/21 00:04:20.060 [...] dvi: Selected driver: dvi: INF path C:\Windows\INF\oem24.inf dvi: INF section VBoxNetLwf.ndi dvi: INF version 7.0.6.5176 ! inf: Unable to load INF: 'C:\Windows\INF\oem24.inf'(e0000003) ! inf: Error 0xe0000003: The syntax of the INF is invalid. <<< Section end 2023/03/21 00:04:20.278 <<< [Exit status: FAILURE(0xe0000003)]
This pattern also occurs several times. Here it looks like vboxnetadp6.inf_amd64_37b41c46e926407a is damaged, which is an INF file copy of vboxnetadp6.inf inside Windows. Perhaps also something to get rid of somehow.setupapi.dev.log wrote:>>> [Configure Driver Package - c:\windows\system32\driverstore\filerepository\vboxnetadp6.inf_amd64_37b41c46e926407a\vboxnetadp6.inf] >>> Section start 2023/03/21 00:32:04.175 cmd: "C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe" /Helper VirtualBox\SVCHelper\{eecbd6d5-bd95-4eb0-aacd-24326713dd04} sto: Source Filter = VBoxNetAdp6.ndi sto: Target Filter = ROOT\NET\0000 inf: Class GUID = {4d36e972-e325-11ce-bfc1-08002be10318} inf: Class Options = Configurable !!! idb: Failed to open driver package object 'vboxnetadp6.inf_amd64_37b41c46e926407a'. Error = 0x00000005 <<< Section end 2023/03/21 00:32:04.182 <<< [Exit status: FAILURE(0x00000005)]
Re: All VMs failed to start (with exit code 1) after host OS rebooted
To scottgus1 & fth0:
I carried out the following procedure just now:
1) Uninstall VB.
2) Open 'C:\Windows\INF' directory and DELETE 'oem24.inf' and 'oem24.pnf'.
3) Open 'C:\Windows\System32\DriverStore\FileRepository' directory, change the owner of 'vboxnetadp6.inf_amd64_*', 'vboxnetlwf.inf_amd64_*' and all files in them from 'SYSTEM' to my own account, and add Full Control rights for my account to these subdirectories and files. Finally DELETE these 2 subdirectories.
4) Reboot and reinstall VB.
The installation completed very smoothly, then I found the host-only network adapter created successfully! I tested the VB Manager and found that all VMs in it started successfully and worked normally!
Thank you very much!
I carried out the following procedure just now:
1) Uninstall VB.
2) Open 'C:\Windows\INF' directory and DELETE 'oem24.inf' and 'oem24.pnf'.
3) Open 'C:\Windows\System32\DriverStore\FileRepository' directory, change the owner of 'vboxnetadp6.inf_amd64_*', 'vboxnetlwf.inf_amd64_*' and all files in them from 'SYSTEM' to my own account, and add Full Control rights for my account to these subdirectories and files. Finally DELETE these 2 subdirectories.
4) Reboot and reinstall VB.
The installation completed very smoothly, then I found the host-only network adapter created successfully! I tested the VB Manager and found that all VMs in it started successfully and worked normally!
Thank you very much!
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: All VMs failed to start (with exit code 1) after host OS rebooted
Thanks for reporting back!