Forum Discussion
Windows 11 22h2 enabling Hyper-V cause BSOD
- Jun 30, 2023
Since no one gave a solution, I reply to my own question to help people who may have the same problem.
I seems many people go into Windows 11 22H2 madness, despite last updates of everything I could done, I was keeping those weird BSOD, with error changing between installations without any reason.
In my case, the Kernel DMA Protection in the UEFI Setup was responsible of it. I needed to disable it in order to boot with Hyper-V. I am not able to enable it again after Hyper-V installation correctly done. If so, I go into BSOD again...
thanks to this thread on hp forum :
https://h30434.www3.hp.com/t5/Desktop-Operating-Systems-and-Recovery/Inaccessible-Boot-Device-BSOD-after-upgrading-to-Win-11-22H2/td-p/8611767
This UEFI setting seems causing many problems with this Windows version, with Lenovo, HP or Dell, in some cases it even prevent to install Windows with BSOD of first or second reboot.
I hope this help
Since no one gave a solution, I reply to my own question to help people who may have the same problem.
I seems many people go into Windows 11 22H2 madness, despite last updates of everything I could done, I was keeping those weird BSOD, with error changing between installations without any reason.
In my case, the Kernel DMA Protection in the UEFI Setup was responsible of it. I needed to disable it in order to boot with Hyper-V. I am not able to enable it again after Hyper-V installation correctly done. If so, I go into BSOD again...
thanks to this thread on hp forum :
https://h30434.www3.hp.com/t5/Desktop-Operating-Systems-and-Recovery/Inaccessible-Boot-Device-BSOD-after-upgrading-to-Win-11-22H2/td-p/8611767
This UEFI setting seems causing many problems with this Windows version, with Lenovo, HP or Dell, in some cases it even prevent to install Windows with BSOD of first or second reboot.
I hope this help
- OrinThomasJul 02, 2023
Microsoft
Thank you very much C-Fou - this solved a problem that had me flummoxed on one of my ThinkPads. - dieterp0203Jul 01, 2023Copper Contributor
Many thanks to you!!!!
Since today, hyper-V is running on my system.
BIOS --> Security --> Virtualisation --> DMA Protection --> Disable --> Save and restart
Best regards, Dieter