Fix 0X80090011 NTE_NOT_FOUND on Windows 10/11

The 30-Second Fix: Reboot and Check TPM

First things first. The most common trigger for 0X80090011 is a temporary glitch in the Trusted Platform Module (TPM) driver or the Windows security stack. This happens after a Windows update, after a crash, or when you've just enabled BitLocker and the system hasn't fully caught up.

1. Save any open work and restart your PC. Not a shutdown-and-start — a full restart. Shutdown might not clear the TPM state on some systems.
2. After reboot, press Windows key + R, type tpm.msc, and hit Enter. The TPM Management window should open.
3. Look at the status at the bottom. If it says "The TPM is ready for use," you're good. If it says "Compatible TPM cannot be found" or "TPM is not initialized," that's a separate problem — but often a BIOS setting change fixes it.

If the reboot didn't solve the error, move to the next fix. Don't waste time rebooting again.

The 5-Minute Fix: Clear the Certificate Store

The error message "Object was not found" usually means Windows is looking for a certificate or key that's been deleted or corrupted. This happens after you've replaced a motherboard, run a disk cleanup that removed temp certs, or used a tool like CCleaner that strips registry entries too aggressively.

Here's how to force Windows to rebuild its certificate cache:

1. Press Windows key + R, type certmgr.msc, and press Enter.
2. In the left pane, expand Personal → Certificates. You'll see a list of certs with your user name or the machine name.
3. Right-click each certificate and choose Delete. Yes, all of them. Don't panic — these are user-specific certs, and Windows recreates them when needed. But if you're not sure, export them first: right-click, All Tasks → Export, and save a .pfx file.
4. Close certmgr. Then press Windows key + R, type services.msc, and hit Enter.
5. Scroll to Certificate Propagation. Right-click it and choose Restart. If the service is disabled, set it to Automatic and start it.
6. Restart your PC again. Try the operation that gave you the error.

If you're still seeing 0X80090011, it's time to dig deeper.

The 15-Minute Fix: Reset the Security Stack (Advanced)

This is the fix that works when everything else fails. It involves editing the registry and clearing the TPM keys. Do this only if you're comfortable with regedit, and back up your registry first (File → Export).

Step 1: Back up your registry

1. Press Windows key + R, type regedit, and press Enter.
2. Click File → Export. Choose a location, give it a name, and save.

Step 2: Delete the corrupt key containers

Errors like NTE_NOT_FOUND often come from broken key containers in the registry. Here's the path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb

1. Navigate to that path in regedit.
2. Right-click the folder df9d8cd0-1501-11d1-8c7a-00c04fc297eb and choose Export to back it up.
3. Then right-click it again and choose Delete. Confirm.

Windows will recreate this key automatically when it needs it. Deleting it clears any corrupted entries.

Step 3: Clear the TPM and reinitialize

This step clears the TPM keys that might be out of sync. Warning: if you use BitLocker, have your recovery key handy.

1. Press Windows key + R, type tpm.msc, and press Enter.
2. In the Actions pane (right side), click Clear TPM. You'll be prompted to restart. Do it.
3. After restart, Windows will automatically reinitialize the TPM. You might need to press a key at a BIOS prompt — that's normal.

Step 4: Repair system files

While you're at it, run a disk check and system file checker. Corrupted system files can also cause this error.

sfc /scannow
dism /online /cleanup-image /restorehealth

Run both commands in an elevated Command Prompt (right-click Command Prompt → Run as administrator). The first takes about 15 minutes, the second about 10. If SFC finds files it can't fix, DISM usually does.

Step 5: Final restart

Restart one last time and test. If the error is gone, great. If not, you might need to do a system restore to a point before the error first appeared.

When this happens most often: After a Windows feature update (like 22H2) or when you've used a third-party registry cleaner. The error pops up in event logs as NTE_NOT_FOUND and usually surfaces when you try to sign in with a PIN or unlock a BitLocker drive.

One more thing: if you're on a work or school PC, this error can come from group policies that restrict certificate usage. In that case, contact your IT admin before trying the registry fix — they might have a specific policy that needs adjusting.