Hello
The computer :
Virtualbox : last version
Windows 7 x64 clean and up to date. No virus, no malware.
Antivirus AVAST : clean and up to date
Video: NVIDIA Geforce GTS 250 x2 SLI with last driver.
Sfc /scannow = OK
Some important file controlled with signtool and are OK .
Detail error message:
Login failed for w10 virtual machine.
The virtual machine 'w10' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\***\VirtualBox VMs\w10\Logs\VBoxHardening.log'.
Code d'erreur : E_FAIL (0x80004005)
Composant : MachineWrap
Interface : IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
Procedure during the report:
After installing Virtualbox, I was able to create a VM and launch it without any problem. After the reboot of the computer, it is no longer possible to launch the VM. There is attached in the ZP file, the LOG traces before the reboot (It is possible to launch the VM) and LOG traces after the reboot (impossible to start the VM). It is therefore possible to compare the two LOGs in order to track the problem.
I cannot find the solution. Can you give me the solution to solve this problem?
Note:
The first fault written in the LOG file is : "NtOpenDirectoryObject failed on \Driver: 0xc0000022"
Thanks
Error Virtualbox 5.2.18 E_FAIL (0x80004005)
Error Virtualbox 5.2.18 E_FAIL (0x80004005)
- Attachments
-
- vboxhardening-kog.zip
- 2 LOG ( before and after )
- (35.77 KiB) Downloaded 18 times
Re: Error Virtualbox 5.2.18 E_FAIL (0x80004005)
Hi
I scanned all .dll found in LOG file and I don't found problem with signature. ( controled with sigcheck.exe)
Could you help me about this?
Regards
I scanned all .dll found in LOG file and I don't found problem with signature. ( controled with sigcheck.exe)
Could you help me about this?
Regards
- Attachments
-
- 2018-09-15 12_46_45-Indésirables - Dossiers locaux - Mozilla Thunderbird.png (38.76 KiB) Viewed 2677 times
-
- 2018-09-15 12_47_18-VirtualBox - Error In supR3HardenedWinReSpawn.png (16.06 KiB) Viewed 2677 times
Re: Error Virtualbox 5.2.18 E_FAIL (0x80004005)
next
- Attachments
-
- 2018-09-15 12_46_45-Indésirables - Dossiers locaux - Mozilla Thunderbird.png (38.76 KiB) Viewed 2677 times
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Error Virtualbox 5.2.18 E_FAIL (0x80004005)
Please read really carefully the following FAQ: Diagnosing VirtualBox Hardening Issues for some generic guidelines/ideas. Remember, these are guidelines, not the exact solution, you have to use your judgement as to which program might be responsible...
Try to completely uninstall Avast. If that works, then re-install Avast, but add an exception for VirtualBox.LML77 wrote:Antivirus AVAST : clean and up to date
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.
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.
Re: Error Virtualbox 5.2.18 E_FAIL (0x80004005)
Have you tried creating a new vm with the previous media & running vbox as administrator? If it works then permission or configuration problem may exists.
Also make a blank vm, and try to boot to get "fatal..." msg.
Also make a blank vm, and try to boot to get "fatal..." msg.
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Error Virtualbox 5.2.18 E_FAIL (0x80004005)
When you have a hardening error, you can't run any VM. VirtualBox refuses to run. "Lean_geek", read the Hardening FAQ please...Lean_geek wrote:Have you tried creating a new vm with the previous media
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.
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.
Re: Error Virtualbox 5.2.18 E_FAIL (0x80004005)
I read the document, and I tried to find the reason based on the information contained.
I controled intégrity with sfc /scannow = clean
I tried, with and without AVAST = same problem
I create exceptions in AVAST for all modules = same
I deleted some program not used = same
I controled certifacate validity for .DLL = clean
I up to date the OS = clean
I cleaning all registry and kill old key. = same
virtualbox is started with administrator elevation = same
So, could you tell me the procedure to found that's wrong ?
Here with , the processus image memory for the process when there is the Herdened error.
( I will try to uninstall the Video driver and reinstall it.
Note: just after installing Virtualbox, everything works, but after the reboot of the computer, the hardened error appears.)
I controled intégrity with sfc /scannow = clean
I tried, with and without AVAST = same problem
I create exceptions in AVAST for all modules = same
I deleted some program not used = same
I controled certifacate validity for .DLL = clean
I up to date the OS = clean
I cleaning all registry and kill old key. = same
virtualbox is started with administrator elevation = same
So, could you tell me the procedure to found that's wrong ?
Here with , the processus image memory for the process when there is the Herdened error.
( I will try to uninstall the Video driver and reinstall it.
Note: just after installing Virtualbox, everything works, but after the reboot of the computer, the hardened error appears.)
- Attachments
-
- VBoxSVC.exe.txt
- (6.72 KiB) Downloaded 14 times
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Error Virtualbox 5.2.18 E_FAIL (0x80004005)
Uninstall Avast that we know for sure is causing problems. Then post a new VBoxHardening.log.
And I'm not sure what you attached there in the VBoxSVC.exe.txt, but it doesn't do anything to help you figure out what the problem is.
And I'm not sure what you attached there in the VBoxSVC.exe.txt, but it doesn't do anything to help you figure out what the problem is.
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.
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.
Re: Error Virtualbox 5.2.18 E_FAIL (0x80004005)
Done:
AVAST uninstalled
Cleaning registry
reboot
Re install Virtualbox
Test
>>> The problem is same, unfortunatly it's not AVAST
Here are the LOG file
AVAST uninstalled
Cleaning registry
reboot
Re install Virtualbox
Test
>>> The problem is same, unfortunatly it's not AVAST
Here are the LOG file
- Attachments
-
- VBoxHardening.zip
- (10.79 KiB) Downloaded 17 times
-
- Site Moderator
- Posts: 27330
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Error Virtualbox 5.2.18 E_FAIL (0x80004005)
Follow the instructions on the Microsoft article System file check (SFC) Scan and Repair System Files & DISM to fix things SFC cannot. Pay special attention to the command "dism.exe /online /Cleanup-Image /RestoreHealth".
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.
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.