-
Notifications
You must be signed in to change notification settings - Fork 123
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 10 20H2 x64 Fails to Install - Blue Screen of Death #61
Comments
@DavidBerdik thank you for reporting this issue! To be able to understand the issue better, when having the BSOD. Can you look to see if you have any error messages in the VBox logs? Anything that could hint what the underlaying issue could be would be very valuable. |
You're welcome! I've attached a copy of the logs that get generated by VirtualBox when I attempt to run the VM. Unfortunately, this tool is not sufficient for evading detection (the software I'm trying to use still detects that it's a virtual machine), so I've had to give up on using it, but I'd still be happy to help with the debugging process. |
By the way, this is error doesn't happen when you unset the CustomTable parameter |
@DavidBerdik Thank you reporting, this tool missing clear the hypervisor bit in |
@funte You're welcome! I haven't done any further digging on this issue, so unfortunately, I do not have a solution. |
I'd use one of the ones available $VBoxManager modifyvm $VM --cpu-profile "AMD Ryzen 7 1800X Eight-Core" |
When I try to install Windows 10 20H2 x64 in my patched VM, the boot disk fails. It will attempt to load, display the blue screen of death, and restart.
I have not tried other Windows 10 ISOs, but I was able to install Windows 7 x64 and it has worked so far. For my purposes Windows 7 is sufficient, but I felt that this should still be reported.
I am using VirtualBox 6.1.16, and my host operating system is Windows 10 Pro, x64. The shell script and PowerShell scripts that I am working with were generated on an old laptop running Ubuntu.
The text was updated successfully, but these errors were encountered: