HVCI / Core Isolation with loader and Hyper-V leftovers
Closed thread Closed by archive SetupRequirements page and Cloud DMA doc both insist HVCI, TPM, and Secure Boot enabled. The TPM and Secure Boot guide matches the Windows checks the catalog lists. I turned on Core Isolation memory integrity but Hyper-V features are still listed enabled from Docker ages ago.
Loader throws a generic virtualization warning. idk if I uninstall Hyper-V role fully or if go cloud users just disable one checkbox.
comments: HVCI / Core Isolation with loader and Hyper-V leftovers 5
Replies are closedDisable Hyper-V platform and reboot twice. HVCI stayed on for me after that.
Two reboots is the magic number lol
TPM attestation screenshot saved me a support loop. Have it ready.
yes include firmware TPM version too
Leave WSL off until you confirm Battlefield 6 stable. You can add it back later maybe.
This thread beats guessing. Javelin loves messy PCs.