Event ID 124

My system is usually error free or if not I can sort it easily but after the most recent MS update this error appears after a reboot.
The virtualization-based security enablement policy check at phase 6 failed with status: Unknown NTSTATUS Error code: 0xc000ffff
Doesn't seem to be causing any issues but curiosity gets the better of me. Event ID 124. 24H2 Build 26100.4351, anyone else seeing this? What is phase 6?
Have done all usual checks. Cheers.

I don't see it on my comp.

Had to look that up.

Have you been adjusting or turning off anything in your BIOS lately?

It could be the update, it could be Secure Boot or TPM 2.0 issues.
Apparently, If virtualization settings (Intel VT-x or AMD-V) are disabled in BIOS, VBS may not function properly.

If you temporarily disable (or enable) Secure Boot” do you still get that?

I would try uninstalling, then reinstalling the most up-to-date graphics driver from your graphics driver's website.

Source:
https://www.bing.com/search?q=event+id+124+kernel-boot&PC=U316

Hyper-V
in the May update there were 9 Hyper-V new services installed in the service menu
and 1 Hyper-V service within the registry service hive which is not visible in the service menu.

in the device manager there are at least two new Hyper-V devices installed
you may need to use 'show hidden devices' to see them all. i had 4, two of which were hidden.

i do NOT have Hyper-V installed or enabled on my system. i disabled all services and removed all devices.
please note .. i never had any error reports or messages.

this maybe the cause of your errors.
best of luck, Steve ..

@Garrett

Common causes of this issue could be one of:

• Incompatible drivers – legacy or unsigned drivers can cause HVCI/Memory Integrity to fail.
• Corrupted Windows installation or registry misconfiguration.
• Missing or incorrect UEFI/BIOS settings:
  • Virtualization (VT-x / AMD-V) not enabled.
  • Secure Boot disabled.
• Device Guard or VBS Group Policy misconfiguration.
• Outdated firmware or incompatible hardware.

Click to expand...

Have you tried running these from an elevated command prompt?
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

Or open the Event Viewer and check System or Applications and Services Logs >> Microsoft >> Windows >> CodeIntegrity/DeviceGuard for error messages that may give clues hinting what the issue is.

Thanks everyone for your suggestions. I have made no changes to the bios and have no instances of Hyper V in device manager but do have entries in services all set to manual. This error appeared only after a day after last update KB5063060.
Funny that some apps also didn't load on first attempt after this update but all fine on second attempt. (Photos, Power shell).
I have disabled Autologger for {15ca44ff-4d7a-4baa-bba5-0998955e531e} so I don't see the error at least. System is working fine!

Hi all,

Apologies for posting on an old thread, but I've just discovered my PC has developed a persistant Event 124 issue also; it's happening now for every (re)start done (as far as I can tell) since Oct 6, according to Event Viewer. The error detail here is different however, with...

"The virtualization-based security enablement policy check at phase 6 failed with status: TPM 2.0: The TPM is not in the right mode for upgrade."

This is unexpected as I have always, deliberately, kept TPM disabled in the UEFI BIOS, and yet today found in Device Manager that a driver was installed for it, athough not active. I've removed that now, without any apparent effect, but the issue remains.

I do have Secure Boot enabled, and the reason I found this issue, is whilst looking at another issue whereby I could not view the Bitlocker state (I always have that OFF), via the Manage Bitlocker (Control Panel) feature.

I tried a Recovery Startup Repair which ran with "attempting to make repairs" but the SrtTrail.log merely says...

Root cause found:
---------------------------
A recent driver update installation could be preventing Windows from starting.

Repair action: Uninstall newly installed driver update
Result: Completed successfully. Error code = 0x0

No idea what driver its on about, and as I said above, the issue persists.

Finally, there is nothing I can find that's associate with the Oct 6 date e.g. KB/patches, installs/uninstalls etc.

There's not much info on the web re this issue, so any help/advise via this thread would be much appreciated.

Loo