Hello,
I Have a Windows 10 Enterprise 64bit (version 1803, build 17134.48), and Virtualbox 5.2.10 r122046 (Qt. 5.6.2).
I don't know if some one has experienced the same thing, but after the last windows update (to my current version), everytime I start a virtual machine (that were previously working well), the OS freezes and I need to restart my laptop with a cold reboot.
I haven't experienced other issues in any other application, except for Virtualbox.
Has any one a sugestion for me to try?
Many thanks in advance,
António Carvalho
[Resolved] Windows 10 (1803) stop working after starting a virtualmachine
-
António Carvalho
- Posts: 5
- Joined: 10. May 2018, 10:48
[Resolved] Windows 10 (1803) stop working after starting a virtualmachine
Last edited by socratis on 11. May 2018, 21:52, edited 2 times in total.
Reason: Marked as [Resolved].
Reason: Marked as [Resolved].
-
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: Windows 10 (1803) stop working after staring a virtualmachine
Uninstall VirutalBox. Reboot. Re-install VirtualBox.António Carvalho wrote:Has any one a sugestion for me to try?
Your VMs and your preferences are going to be unharmed, don't worry.
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.
-
António Carvalho
- Posts: 5
- Joined: 10. May 2018, 10:48
Re: Windows 10 (1803) stop working after starting a virtualmachine
«Uninstall VirutalBox. Reboot. Re-install VirtualBox.»
I have done all those, in that exact order. Still not working. It crashes as soon as I start the virtual machine...
I have done all those, in that exact order. Still not working. It crashes as soon as I start the virtual machine...
-
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: Windows 10 (1803) stop working after staring a virtualmachine
- Can you try with 5.2.12 that was just released?
- I wish I could easily identify what's installed on your system and see what might be conflicting. Can you try both of those commands from PowerShell?
Code: Select all
Get-WmiObject -Class Win32_Product | Select-Object -Property Name Get-ItemProperty HKLM:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion, Publisher, InstallDate | Format-Table –AutoSize
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.
-
António Carvalho
- Posts: 5
- Joined: 10. May 2018, 10:48
Re: Windows 10 (1803) stop working after starting a virtualmachine
«I wish I could easily identify what's installed on your system and see what might be conflicting. Can you try both of those commands from PowerShell?»
Please check the files that I have attached: Out1.txt for the first command, and out2.txt for the second one (I had to zip them).
«Can you try with 5.2.12 that was just released?»
I have not tried it. As soon as I try, I'll post the result.
Please check the files that I have attached: Out1.txt for the first command, and out2.txt for the second one (I had to zip them).
«Can you try with 5.2.12 that was just released?»
I have not tried it. As soon as I try, I'll post the result.
- Attachments
-
- out.zip
- (13.57 KiB) Downloaded 30 times
-
António Carvalho
- Posts: 5
- Joined: 10. May 2018, 10:48
Re: Windows 10 (1803) stop working after starting a virtualmachine
«Can you try with 5.2.12 that was just released?»
Just tried it. I have uninstalled the 5.2.10, rebooted, installed the 5.2.12, reboot again, and the same behaviour. Full SO stop!
Just tried it. I have uninstalled the 5.2.10, rebooted, installed the 5.2.12, reboot again, and the same behaviour. Full SO stop!
-
António Carvalho
- Posts: 5
- Joined: 10. May 2018, 10:48
Re: Windows 10 (1803) stop working after starting a virtualmachine
Hello,
I've found the solution, and I'm sharing it now!
It seems to be related to "Credential Guard and Virtualization Based Security", as I've found in this post on stackoverflow:
https://stackoverflow.com/questions/389 ... ary-update
I was wondering, why the Android Studio was reporting to have Hyper-V enabled, when I "knewed" that it was disabled! So, I guessed that the same problem could be making the Virtualbox to crash my laptop. And it was!
I now have all my machines back!
António Carvalho
I've found the solution, and I'm sharing it now!
It seems to be related to "Credential Guard and Virtualization Based Security", as I've found in this post on stackoverflow:
https://stackoverflow.com/questions/389 ... ary-update
I was wondering, why the Android Studio was reporting to have Hyper-V enabled, when I "knewed" that it was disabled! So, I guessed that the same problem could be making the Virtualbox to crash my laptop. And it was!
I now have all my machines back!
António Carvalho
-
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: Windows 10 (1803) stop working after starting a virtualmachine
Actually, we have a FAQ here too, "I have a 64bit host, but can't install 64bit guests", which describes the potential culprits that could be stealing your VT-x/AMD-V. In the Additional Notes, part 2, it's the Credential Guard.António Carvalho wrote:It seems to be related to "Credential Guard and Virtualization Based Security", as I've found in this post on stackoverflow
Your computer was freezing, that's why I didn't immediately pointed you to the FAQ, it wasn't one of the usually described symptoms. Maybe things have changed. I'll remember that...
Thank you very much for the feedback! Marking as [Resolved].
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.