When i turn on HVCI and reboots it turn of again automaticly

Question

When i turn on HVCI and reboots it turn of again automaticly

Thor Tranto 20

Hi everyone

i'm encountering issues enabling Hypervisor-protected Code Integrity (HVCI) as required by Valorant.

Backstory:

I was playing a game yesterday and encountered and Error that told me to enable: UEFI Secure boot, HVCI and Firmware TPM 2.0. I Figured out how to enable TPM 2.0 and UEFI Secure boot but i hopelessly stuck on HVCI.

My first attempt was to update from windows 10 to 11 (Home) then after that i reset my PC.

when that didnt work i went into BIOS and changed the following settings:
TPM 2.0 Enabled

BIOS mode: UEFI

Secure boot state: Enabled

SVM: Enabled

IOMMU: Enabled

I also forced Virtualization-based security to run with in "registry editor" via a CMD (Admin) command
(cant show it here, i think my last attempt to post got deleted due to having code in the question maybe, i dont know?)

Current problem:
When i try to turn on HVCI on in the following menu Windows security > Device security > Core isolation details > Menu intergrity = ON the following happends:

It prompts me to restart my PC, after trying to start up again its fails and begins to "rapair" something. no info is given by the system here.

after completing the repair it reboots again and start up normaly but with HVCI turned OFF again.

I hope anyone out the can figure this one out with me. i feel like i have tried everything i could find online, even following another guide from okt 2025 but with no luck.

Have a nice day
And thanks in advance :)****

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hendrix-V 20,575 Microsoft External Staff Moderator

Hi Thor Tranto,

Welcome to the Microsoft Q&A forum. Thanks for sharing the detailed background.

When Memory Integrity (HVCI) is turned on, Windows performs a strict safety check during startup. If any existing kernel driver isn’t compatible, Windows will automatically recover and turn HVCI back off so the system can start normally. This recovery happens silently, which is why there’s no clear on‑screen message.

Here are some possible checking steps that you can try in this situation:

1 - Check the exact blocking driver

Open Event Viewer
Go to Applications and Services Logs > Microsoft > Windows > CodeIntegrity > Operational
Look for an error after the failed reboot, it will name the driver (.sys) causing the rollback

2 - Review Windows Security notice

Open Windows Security > Device Security > Core isolation
Select Review incompatible drivers (small link under Memory Integrity)

3 - Remove common blockers

Uninstall any motherboard control or RGB software (ASUS / MSI / Gigabyte / ASRock tools)
In Device Manager > Sound, uninstall the audio device and check Delete the driver software
Restart after each removal

4 - Retry Memory Integrity

Turn Memory Integrity ON
Restart and confirm it stays enabled

Let me know if you need further assistance, feel free to ask me by clicking "Add Comment" or "Add Answer" if you cannot add comment so your response will be visible. Thanks for your effort.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Thor Tranto 20 Reputation points

2026-02-04T08:13:52.3933333+00:00

Hi Hendrix-V
first of, let me thank you for taking the time to try and help me with my problem :)

I have tried the steps you suggested and here are the results

1: To get a fresh example i enbaled Memory Integrity (HVCI) and performed the promted restart. It then failed to boot, repaired then booted (as expected).

i opened event viewer and went into:

Applications and Services Logs > Microsoft > Windows > CodeIntegrity > Operational

the log showed no error or warning, only information logs, and non of the logs after the boot suggested anything to do with drivers.

dont know if its relevant but i looked in som other logs and in:

Applications and Services Logs > Microsoft > Windows > Kernel boot > Operational

and error showed after the boot saying: "Failed to update the SBAT value in FW"

2: There was no link under Core isolation that linked to Incompatible drivers.

3: I found no motherboard or RGB software.

Deleted the audio software: Realtek(R) Audio, checked the box and restarted.

4: Turned on Memory integrity and restarted, sadly it still failed and rolled back
Hendrix-V 20,575 Reputation points Microsoft External Staff Moderator

2026-02-05T02:24:23.2833333+00:00
Hi Thor Tranto,

Thank you for taking the time to walk through the steps and share the results.

Based on what you’ve tested, your system is correctly set up for Windows 11 security requirements. The key detail here is the Kernel‑Boot log message indicating an issue updating SBAT (Secure Boot Advanced Targeting) in firmware.

Please try the checking steps below:

Check for a newer BIOS/UEFI update from your device or motherboard manufacturer that mentions Secure Boot, TPM, or Windows 11 improvements.

In BIOS, reset Secure Boot keys to factory defaults (often labeled “Restore Factory Keys” or “Reset Secure Boot Keys”), then re‑enable Secure Boot.

After applying changes, retry enabling Memory Integrity and restart.

If the behavior continues, it means the current firmware does not fully support keeping HVCI enabled across reboots on this hardware. In that case, Windows is operating as designed by prioritizing system stability and recovery.

Let me know if you need further assistance, feel free to ask me in the Comments section.
Thor Tranto 20 Reputation points

2026-02-06T10:33:49.48+00:00

So the problem was the BIOS firmware. its was from 2020 and i think it didnt support HVCI maybe?

anyways after updating BIOS to newest version it worked

thanks for the help :)
have a fantastic day
Hendrix-V 20,575 Reputation points Microsoft External Staff Moderator

2026-02-08T00:31:27.3233333+00:00

Hi Thor Tranto,

I'm relieved to know that you made a great decision and everything is good to go on your side. I hope the insights shared in the forum help address your concerns effectively. And thank you for accepting my answer since accepting it helps others with similar concerns can find useful information.

If you have any updates or further questions, please feel free to share them with us.