A possible cause for this issue could be a third-party driver loading during boot, which may be conflicting with Hyper-V's vhdmp.sys, specifically on Windows 11, while Windows 10 was running fine. To identify the problematic driver, follow these steps:
- Use Sysinternals Autoruns Tool:
- Download and run the Autoruns tool
- Navigate to the Drivers tab and disable all drivers listed under
HKLM\System\CurrentControlSet\Services.
- Reboot and Enable Hyper-V:
- Before rebooting, enable Hyper-V with the following command:
bcdedit /set {default} hypervisorlaunchtype auto - After rebooting, check if the system boots successfully and if WSL, Docker, or other related services are running. If yes, a driver is causing the problem.
- Before rebooting, enable Hyper-V with the following command:
- Binary Search Method:
- If the system boots successfully, gradually re-enable the drivers (using a binary search approach) to pinpoint the driver causing the issue.
- If the system fails to boot after enabling a particular driver, go into the emergency environment and disable Hyper-V with this command:
bcdedit /set {default} hypervisorlaunchtype off
In my case, the driver causing the issue was pxhlpa64.sys, but this could vary depending on your system configuration. Be sure to create a restore point or backup your data before proceeding to avoid potential issues.