sodcalculator

10 Tech How-To

Repair Error 0x8009000f 0x90002: Full Fix Guide

Guide 10-50468 · Updated · Step by step

Error code 0x8009000f 0x90002 appears during Windows installation or upgrade when the system cannot read or write the BitLocker encryption key, often due to a corrupted TPM (Trusted Platform Module) or a failed Secure Boot configuration. The fix is to clear the TPM and reset the Secure Boot keys in the UEFI/BIOS firmware, then restart the setup process. Below is a step-by-step guide, plus background on why this happens and how to avoid it.

What This Error Means

The code 0x8009000f maps to NTE_EXISTS in Windows cryptographic functions, indicating that a key already exists or cannot be created. The suffix 0x90002 is a TPM-specific error, usually TPM_E_AUTHFAIL or a related auth failure. Together, they typically surface during Windows 10/11 installation when the setup tries to initialize the TPM for BitLocker or device encryption but the TPM is in an unexpected state. This is common after a previous failed installation, a BIOS update, or when the TPM has leftover keys from an old operating system.

Pre-Fix: Check TPM Status

Before changing firmware settings, confirm your TPM is present and enabled. Press Win + R, type tpm.msc, and press Enter. In the TPM Management window, look at the status:

  • “TPM is ready for use” – the TPM is fine; the issue lies elsewhere.
  • “Compatible TPM cannot be found” – the TPM is disabled in the BIOS or not present.
  • “TPM is not initialized” – you may need to initialize it.

If the TPM appears disabled, you must enable it in the UEFI/BIOS. If it’s ready, proceed to the reset steps below.

Fix 1: Clear TPM and Reset Secure Boot

This is the most reliable fix. It resets the TPM to factory state and clears any conflicting keys. Important: Clearing the TPM will remove all keys, including those used for BitLocker, Windows Hello, and some apps. Back up any encrypted data or recovery keys first.

  1. Restart your PC and enter the UEFI/BIOS setup. This is usually done by pressing Del, F2, F10, or Esc immediately after power-on (check your motherboard manual).
  2. Find the TPM settings. They are often under Security, Trusted Computing, or Advanced. The option may be called Clear TPM, Reset TPM, or Erase TPM.
  3. Select the clear/reset option and confirm. This does not disable the TPM; it just wipes its keys.
  4. Locate the Secure Boot settings, usually under Boot or Security. Set it to Disabled, save changes, and exit.
  5. Boot into Windows normally (if possible) or start the installation again. The setup will now create fresh keys.
  6. After a successful install, you can re-enable Secure Boot in the BIOS if desired.

If you don’t see a Clear TPM option, you can also clear it from Windows: open tpm.msc, click Actions > Clear TPM, then restart. However, this only works if Windows boots.

Fix 2: Use Command Prompt During Setup

If the error appears during Windows installation and you can’t get past it, you can use the command prompt from the setup environment to clear the TPM.

  1. Boot from your Windows installation media (USB or DVD).
  2. On the first screen, press Shift + F10 to open Command Prompt.
  3. Type tpm.msc and press Enter – this won’t work in the setup environment. Instead, use the tpmtool command if available (Windows 10 1809+):
  4. Type tpmtool /clear and press Enter. If it returns success, close the prompt and continue setup.
  5. If tpmtool is not recognized, you’ll need to reset via BIOS as in Fix 1.

Fix 3: Disable TPM and Secure Boot Temporarily

Some users find that disabling TPM entirely in the BIOS allows the installation to proceed, after which they re-enable it. This is a workaround, not a permanent solution, as Windows 11 requires TPM 2.0.

  1. Enter BIOS, find TPM settings, and set it to Disabled.
  2. Also disable Secure Boot if it’s on.
  3. Save and exit. Install Windows.
  4. After installation, re-enable TPM and Secure Boot. Windows will reinitialize them.

Note: If you’re installing Windows 11, disabling TPM may block the installation. In that case, use Fix 1 instead.

Common Mistakes to Avoid

  • Not backing up BitLocker keys – clearing TPM without a recovery key can permanently lock you out of encrypted drives.
  • Disabling Secure Boot and forgetting to re-enable – this can cause boot issues later.
  • Using a corrupted installation media – if the error persists, recreate your USB drive using the Media Creation Tool.
  • Assuming it’s a hardware failure – in most cases, the TPM is fine; it just needs a reset.

Frequently Asked Questions

Will clearing the TPM delete my files?

No, clearing the TPM does not touch your hard drive files. It only removes encryption keys stored in the TPM chip. However, if you use BitLocker, you’ll need your recovery key to unlock the drive after the TPM is cleared.

Can I fix this without entering BIOS?

Yes, if Windows boots, you can use tpm.msc to clear the TPM. If Windows doesn’t boot, you can try the command prompt from the installation media with tpmtool /clear. Otherwise, BIOS is the only way.

Is this error related to Windows 11’s TPM requirement?

Yes, Windows 11 mandates TPM 2.0. If your TPM is in a bad state, the installer may throw this error. Resetting the TPM usually resolves it.

What if the error appears after a BIOS update?

BIOS updates can reset TPM settings or leave stale keys. Re-enter BIOS, check if TPM is still enabled, and clear it if necessary. Also ensure Secure Boot is set to standard mode.

Does this error affect dual-boot setups?

It can, especially if you have another OS that uses the TPM. Clearing the TPM may invalidate keys used by other systems, so back up any recovery keys for all OSes.

Is there a way to bypass the error without resetting TPM?

You could try updating the BIOS to the latest version, as manufacturers often fix TPM initialization bugs. Also, ensure the installation media is the latest version. If those don’t work, resetting is the safest option.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →