| Event Id | 42 |
| Source | Microsoft-Windows-Hyper-V-Hypervisor |
| Description | Hyper-V launch failed; Either SVM not present or not enabled in BIOS. |
| Event Information | According to Microsoft : Cause: This event is logged when Hyper-V launch failed because SVM not present or not enabled in BIOS. Resolution : Check BIOS settings Contact your hardware supplier for an updated BIOS. Hyper-V requires hardware support, including: an x64 CPU; VT (Intel) or AMD-V (AMD) hardware extensions; No eXecute (NX)/eXecute Disable (XD) and full BIOS support for hardware virtualization. Check your physical computer's BIOS settings to ensure that virtualization features are enabled, then turn off the power to your physical computer. Restart the physical computer. NOTE: Restarting the physical computer is not sufficient. You can use the Virtualization Detect (DetectVp.EXE) tool to check if the physical computer meets the requirements for Microsoft Virtualization Software. This test checks virtualization support for both Intel and AMD processors. Verify : Hypervisor successfully starts. |
| Reference Links | Event ID 42 from Source Microsoft-Windows-Hyper-V-Hypervisor |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.