Forum Discussion
Windows 11 22h2 enabling Hyper-V cause BSOD
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
Hi,
Thanks for your answer.... but, have you read my original post, more than the title, I mean ?
As I said :
All my tests were from fresh install, so no other virtualization software.
I have double check my hardware (cpu, ram, ssd, nvme bus, ethernet) with no issue.
Hyper-V is working with Windows 10 all versions and Windows 11 21H2, so no UEFI miss configuration.
Before installation, all firmwares (uefi, ssd, thunderbolt, dock, ...) have been updated.
Installations tested :
1- Fresh install to wiped disk with no previous partition present + Windows Drivers only
2- Fresh install to wiped disk with no previous partition present + Windows Drivers only + All Windows updates
3- Fresh install to wiped disk with no previous partition present + Fully updated drivers (from Lenovo)
4- Fresh install to wiped disk with no previous partition present + Fully updated drivers (from Lenovo) + All Windows Updates
5- Fresh install to wiped disk with no previous partition present + Unattend file to enable Hyper-V during installation + Windows Driver
6- Fresh install to wiped disk with no previous partition present + Unattend file to enable Hyper-V during installation + Fully updated drivers (from Lenovo) during setup
7- Fresh install to wiped disk with no previous partition present of Windows 11 21H2 + Windows Drivers + All Windows updates + Enable Hyper-V (without any problem here) + in-place upgrade to Windows 11 22H2.
8- Fresh install to wiped disk with no previous partition present with dock unplugged, I don't remember which drivers was used nor if Windows updates were applied.
The installations 1 to 4 and 8 crashed on first reboot after having enable Hyper-V, final result is come back to original state without Hyper-V enabled. The installations 5 to 6 crashed after second reboot (after drivers installation and before entering OOBE), installation KO. The Installation 7 crashed during in-place upgrade after "I don't remember how much reboot" but went back to 21H2.
Since Hyper-V is fully functionnal in Windows 10 and Windows 11 21H2. I think the problem is more on 22H2 side. There may be an hardware compatibility issue since dieterp0203 has the same problem with another Lenovo model. But if it is, this would be more "Lenovo wide". I don't know what exactly changed in Hyper-V 22H2, but Microsoft can resolve this for sure.
I took all the actions what C-Fou already mentioned. Additionally, I did the Lenovo Hardware Scan for all installed hardware components. Hyper-V is enabled, other BIOS settings are on standard values. Hyper-V runs on 21H2 on the same machine.
Question to Mark_Albin: What do you mean with: "...and make any necessary changes to ensure compatibility with Hyper-V."
Next step for me: Checking out the Oracle-Stuff...
regards, Dieter
- short update: Virtual Box did it! Next step: converting all the VHDs to Virtual box...
- It probably does 😉 unfortunally, I need Hyper-V.