After an update of windows 10 my VM stopped working
After an update of windows 10 my VM stopped working
The error is this
The virtual machine 'Windows 10' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\dell\VirtualBox VMs\Windows 10\Logs\VBoxHardening.log'.
Código de Resultado:
E_FAIL (0x80004005)
Componente:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
I already reinstalled the virtualbox, I imported the appliance, .. but I did not succeed.
Anyone have any idea what needs to be done to solve this problem?
The log is attached
The virtual machine 'Windows 10' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\dell\VirtualBox VMs\Windows 10\Logs\VBoxHardening.log'.
Código de Resultado:
E_FAIL (0x80004005)
Componente:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
I already reinstalled the virtualbox, I imported the appliance, .. but I did not succeed.
Anyone have any idea what needs to be done to solve this problem?
The log is attached
- Attachments
-
VBoxHardeningPart.Log- (16.81 KiB) Downloaded 108 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: After an update of windows 10 my VM stopped working
Partial logs do not help. Please ZIP and attach the whole log.fjr wrote:The log is attachedVBoxHardeningPart.Log
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: After an update of windows 10 my VM stopped working
Sorry, follow full log
- Attachments
-
- VBoxHardening.zip
- (13.59 KiB) Downloaded 117 times
-
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: After an update of windows 10 my VM stopped working
The log shows a security error on "opengl32.dll" and the presence of "Kaspersky Anti-Virus" and "System Interceptors" programs.
On my Windows 10 PC there is an opengl32.dll from Microsoft. Maybe yours has been hacked? Try running "sfc /scannow" in an elevated command prompt. Then try Virtualbox.
If the above doesn't fix things, try uninstalling Kaspersky and Interceptors (uninstall, not just disable). Then try Virtualbox again.
On my Windows 10 PC there is an opengl32.dll from Microsoft. Maybe yours has been hacked? Try running "sfc /scannow" in an elevated command prompt. Then try Virtualbox.
If the above doesn't fix things, try uninstalling Kaspersky and Interceptors (uninstall, not just disable). Then try Virtualbox again.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: After an update of windows 10 my VM stopped working
I think, more likely it has been replaced by a manufacturers own version which redirects OpenGL API calls to hardware accelerated implementations. That's ok, but the DLL needs to be signed. Perhaps a graphics driver update will fix this.scottgus1 wrote:The log shows a security error on "opengl32.dll" ... Maybe [this] has been hacked?
Re: After an update of windows 10 my VM stopped working
I ran "sfc / scannow", updated NVIDIA Driver, removed Kaspersky but nothing worked ...
It's very strange, I have the same VirtualBox, with the same VM installed in another notebook, with the same features and works normally. The only difference between them is that what is working the VM is Windows 10 PRO and the one that is not running Windows 10 Home Single Language.
It must be some restriction that Windows 10 HOME has, do not you think?
It's very strange, I have the same VirtualBox, with the same VM installed in another notebook, with the same features and works normally. The only difference between them is that what is working the VM is Windows 10 PRO and the one that is not running Windows 10 Home Single Language.
It must be some restriction that Windows 10 HOME has, do not you think?
-
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: After an update of windows 10 my VM stopped working
Post an updated VBoxHardening.log.fjr wrote:I ran "sfc / scannow", updated NVIDIA Driver, removed Kaspersky but nothing worked ...
No.fjr wrote:It must be some restriction that Windows 10 HOME has, do not you think?
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.
-
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: After an update of windows 10 my VM stopped working
Careful, "sfc / scannow" isn't "sfc /scannow" - notice no space between the / and the scannow. What did this command say when you ran it?fjr wrote:I ran "sfc / scannow",
Re: After an update of windows 10 my VM stopped working
Thanks for listening ...
"Sfc / scannow" was run correctly and ended with the message "Windows Resource Protection found corrupted files and can not fix some of them" ... generated the log "CBS.Log" which for being very large I did not send attached ...
The error of running the VM is this:
The virtual machine 'Windows 10' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C: \ Users \ dell \ VirtualBox VMs \ Windows 10 \ Logs \ VBoxHardening.log'.
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Attached is VBoxHardening.log.
"Sfc / scannow" was run correctly and ended with the message "Windows Resource Protection found corrupted files and can not fix some of them" ... generated the log "CBS.Log" which for being very large I did not send attached ...
The error of running the VM is this:
The virtual machine 'Windows 10' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C: \ Users \ dell \ VirtualBox VMs \ Windows 10 \ Logs \ VBoxHardening.log'.
Result Code:
E_FAIL (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Attached is VBoxHardening.log.
- Attachments
-
- VBoxHardening.zip
- (11.46 KiB) Downloaded 105 times
-
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: After an update of windows 10 my VM stopped working
Still having opengl32.dll problems. If you zip the cbs log is it attachable?
Also try updating your graphics drivers.
Also try updating your graphics drivers.
Re: After an update of windows 10 my VM stopped working
CBS.LOG is too big to attach!
NVIDIA (GeForce) is with the last update ok.
Should I be doing something wrong to fix the opengl32.dll problem
Can you tell me the steps to fix the opengl32.dll problem?
Thank you !
NVIDIA (GeForce) is with the last update ok.
Should I be doing something wrong to fix the opengl32.dll problem
Can you tell me the steps to fix the opengl32.dll problem?
Thank you !
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: After an update of windows 10 my VM stopped working
scottgus1 wrote:If you zip the cbs log is it attachable?
Re: After an update of windows 10 my VM stopped working
it is not
Compressed, occupies 839Kb
Compressed, occupies 839Kb
-
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: After an update of windows 10 my VM stopped working
Ok, that is too big. Can you post it to a Dropbox-like service and post the link here? That log should tell what issues your sfc /scannow couldn't fix. Or you could open the log file and see what the problem was? Interpreting the cbs.log is a Windows thing, not a Virtualbox thing, so you should be able to google for how to find the problem.
-
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: After an update of windows 10 my VM stopped working
Or, in other words, to add to what Scott said, your host is messed up. Big time. VirtualBox was only so sensitive as to show you that there is a problem.scottgus1 wrote:Interpreting the cbs.log is a Windows thing, not a Virtualbox thing, so you should be able to google for how to find the problem.
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.