Hyper-V VM - KERNEL SECURITY CHECK FAILURE

Niche issue here.

The tldr is that the my Hyper-V VM BSODs when installing any build of Windows 11 (22h1 or 22h2) to a physical drive.
The BSOD occurs immediately after proceeding from the partitioning menu.

• In the same VM with identical configuration, Windows 11 installs just fine to a virtual disk.

I thought there might be an error with the Intel RST VMD.
Background: To clean install Win11 on the host machine, the Intel RST driver has to be loaded before the installation is able to recognize any attached drives.
But...

• In the same VM with identical configuration, Windows 10 22h2 installs just fine to the physical drive.

Upgrading the Windows 10 install to Windows 11 via the Upgrade Assistant also causes the same crash.

Given that Windows 10 installed to that physical drive without issue, I'm perplexed.
Any ideas?

The V2 log collector doesn't query the Hyper-V events, but the pertinent entry is included below.

Event ID 18590
'VM 1' has encountered a fatal error. The guest operating system reported that it failed with the following error codes:
VmErrorCode0 0x139
VmErrorCode1 0x3a
VmErrorCode2 0xffffbf8e4645efd0
VmErrorCode3 0xffffbf8e4645ef28
VmErrorCode4 0x0

Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE - Windows drivers

Did you ever sort out that issue? I am having a similar issue with Hyper-V throwing KERNEL_SECURITY_CHECK_FAILURE BSODs when booting from Physical disks. I was able to isolate the issue explicitly to Hyper-V and Physical SATA Drives. If I use a NVME the KERNEL_SECURITY_CHECK_FAILURE BSODs don't occur.

NoProblemAtoll said:

Did you ever sort out that issue? I am having a similar issue with Hyper-V throwing KERNEL_SECURITY_CHECK_FAILURE BSODs when booting from Physical disks. I was able to isolate the issue explicitly to Hyper-V and Physical SATA Drives. If I use a NVME the KERNEL_SECURITY_CHECK_FAILURE BSODs don't occur.

Click to expand...

Hi, I had same problem on my HP ProBook 450 G5 (no BIOS option to change SATA/AHCI/RAID mode so just AHCI mode). My KERNEL_SECURITY_CHECK_FAILURE occur when I tryied insert my SSD boot drive from USB3 case (testing with Windows11 23H2) to internal SATA port and trying boot from internal SATA port as physical or virtutal Hyper-V machine (P2V =physical to virtual). Sometimes physical boot but virtual never, always just BSOD. Same BSOD occur when you trying install the new Windows from ISO, BSOD occur during installation.
I find out that problem is in host SATA AHCI driver on host machine. When my laptop used original vendor INTEL chipset AHCI driver, it uses storvsc.sys (whole driver name: Intel 6th Generation Core Processor Family Platform I/O SATA AHCI Controller).
This solution working for me without BSOD:
go to Device Manager > right click on above controller and update from local driver store to "Standard SATA AHCI Controller"
in registry this basic AHCI driver is using storahci.sys instead of vendor storvsc.sys
So after that change all my testing SSD are booting correct now wihout BSOD from laptop internal SATA port, and also working booting in Hyper-V Gen2 VM with UEFI+TPM support with attached physical drive to SCSI controller as virtual hard drive.
Like this reply if it was helpful, thanks :]

Please see posting instructions: