Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x80090016

Office Sign-in 0x80090016 Keyset Does Not Exist: Broken Identity and Device State

10 min read Updated October 5, 2026 Outlook & Office Applications

Fix it now

0x80090016 is NTE_BAD_KEYSET: the keyset does not exist. Microsoft names two causes for it during device registration – the TPM was cleared on the system, or the machine came from a bad sysprep image. Retyping the password changes nothing, because sign-in never reaches a password.

Run these in an elevated Command Prompt, in order

dsregcmd /status
w32tm /query /status
w32tm /resync
  1. Read the device state and single sign-on state sections of the dsregcmd output. That tells you whether the device still has a usable identity at all.
  2. Sign out of Office from File, Account, then close every Office process from Task Manager.
  3. Clear the stored credentials for Office and Microsoft accounts from Credential Manager, under Windows Credentials.
  4. Restart the machine, open Word and sign in again.
  5. If the code returns and the device state is not healthy, the registration has to be rebuilt. Confirm someone can recover BitLocker for this machine first.

Rebuilding device registration affects conditional access decisions, BitLocker recovery key escrow and management enrolment. Check BitLocker escrow before you touch device state, not after.

If Office signs in silently after a reboot, you are done. The next section covers where the key is supposed to live and what removes it.

Why it happens

When a device joins or registers with Entra ID it generates a key pair. The private half goes into the device’s key store, held in the TPM where one is available, and the public half is recorded against the device object in the directory. From then on the authentication broker in Windows uses that key to prove the device’s identity and to obtain tokens that Office applications refresh silently in the background.

0x80090016 is the cryptographic layer reporting that the key container is not there. Microsoft’s own device-registration troubleshooting names it as a Trusted Platform Module operation that failed or was invalid, indicating the keyset does not exist, and states plainly when it happens: when the TPM is cleared on the system, or when there is a bad sysprep image. Those two causes account for most of what you will see, and neither is fixed by anything you do inside Office.

The neighbouring codes come from the same provider. 0x80090011 is NTE_NOT_FOUND, object was not found. 0x80090019 is NTE_KEYSET_NOT_DEF, the keyset is not defined. They describe slightly different failures of the same lookup and lead to the same place. 0x8007052E is different in kind: Win32 error 1326, ERROR_LOGON_FAILURE, the user name or password is incorrect. It appears once sign-in has fallen back to a credential prompt and the prompt cannot succeed either.

0x80180018 is the odd one out. Microsoft publishes several codes in the 0x8018xxxx mobile device management enrolment range – a device already enrolled, an organisation that does not support this version of Windows, an auto-enrolment that failed – but not this value. Take its presence as a hint to look at enrolment state, not as a statement about what went wrong.

The TPM was cleared, or the image was built badly

You have this one if The error appeared after firmware work, a TPM clear or a security setting change; or every machine from one image behaves this way.

  1. Open the TPM management console and read the TPM’s status and readiness.
  2. If the TPM was cleared, the device’s key material is genuinely gone and the registration has to be rebuilt.
  3. If the machines came from an image, fix the image. A reference image captured without a proper generalise step reproduces this on every machine built from it.
  4. Resolve any hardware fault with the vendor before re-registering, or you will simply repeat the failure.

The device registration is stale or gone

You have this one if dsregcmd /status reports the device as not joined, or reports a device authentication failure, while the tenant still lists an object for it.

  1. Confirm someone can recover BitLocker for this machine before going further.
  2. Run dsregcmd /leave from an elevated prompt and reboot. Microsoft uses this pair in its own sign-in troubleshooting.
  3. Let the device register again, or re-join it through the work-or-school account page in Windows Settings.
  4. Run dsregcmd /status again and confirm the device state and device authentication now report correctly.

Once the machine has registered cleanly, delete the orphaned device object in the tenant so you are not left with duplicates confusing the next investigation.

The credential cache on this user profile is damaged

You have this one if A different Windows user signs in on the same machine and Office activates without complaint.

  1. Sign out of Office and close every Office process.
  2. Remove the Office and Microsoft account entries from Credential Manager, under Windows Credentials.
  3. Sign in again and let the cache rebuild.
  4. If it persists, create a new Windows user account on the machine and test there to separate profile damage from machine damage.

The clock or the time source is wrong

You have this one if Other sign-in or Kerberos problems are present too, and the time status shows a large offset or an unreachable source.

  1. Run w32tm /resync from an elevated prompt. There is no /force parameter on that command; adding one makes it print usage and do nothing.
  2. Check the configured source and confirm it is appropriate for a machine of this type.
  3. On a virtual machine, choose either host time synchronisation or the domain hierarchy and disable the other.
  4. Confirm the offset is small before retesting sign-in.

Full reference

Narrowing the scope

What you find Where the fault sits
dsregcmd shows the device not joined or not registered Device state; the registration has to be rebuilt
Device state looks correct but sign-in still fails The credential store on this user profile
Only one user on a shared machine is affected Per-user key material or that Windows profile
It started after a TPM clear or firmware change The key material is genuinely gone
Every machine from one image behaves this way The image was captured without a proper generalise step

The five codes and what each one names

Code Constant Published text
0x80090016 NTE_BAD_KEYSET Keyset does not exist; in device registration, the TPM was cleared or the image is bad
0x80090011 NTE_NOT_FOUND Object was not found
0x80090019 NTE_KEYSET_NOT_DEF The keyset is not defined
0x8007052E ERROR_LOGON_FAILURE The user name or password is incorrect
0x80180018 – No published meaning; neighbouring 0x8018xxxx values are MDM enrolment errors

Rebuilding device registration safely

  1. Confirm BitLocker recovery keys for this machine are escrowed somewhere you can reach. Do this first, every time.
  2. Note the current state from dsregcmd /status so you can compare afterwards.
  3. Run dsregcmd /leave from an elevated prompt.
  4. Reboot.
  5. Let a hybrid-joined machine re-register on the next sign-in, or re-join an Entra-joined machine through the work-or-school account page in Windows Settings.
  6. Run dsregcmd /status again and confirm both the device state and the single sign-on state look correct before testing Office.
  7. Remove the orphaned device object from the tenant.

Where to read what actually happened

Windows keeps a record of device registration and token acquisition in Event Viewer, under Applications and Services Logs. The User Device Registration log carries the join phase: event 204 contains the error code, HTTP status and message for a join failure, event 220 appears when Windows cannot access the computer object in Active Directory, and events 304, 305 and 307 carry join and authentication status. The Microsoft Entra operational log carries the token side: events 1006 and 1007 bracket a token acquisition attempt and 1007 logs the final error code.

Steps that make this worse

  • Do not delete the Office identity keys from the registry as a first move. It is widely recommended and it is not documented as a supported repair; export anything you remove and treat it as a last resort after the device state is known good.
  • Do not clear the TPM to fix a TPM error without confirming BitLocker recovery first. Clearing it destroys the key material that this error is already complaining about.
  • Do not reinstall Office. Nothing in this failure is inside Office, and a reinstall costs an hour and changes nothing.
  • Do not assume a browser sign-in that works means the account is at fault. Browser sign-in does not use the device key, which is exactly why it still works.

Every code this article covers

Code What it points at Source
0x80090016 NTE_BAD_KEYSET, keyset does not exist. Microsoft attributes it in device registration to the TPM being cleared or to a bad sysprep image Microsoft Learn
0x8007052E Win32 error 1326 ERROR_LOGON_FAILURE: the user name or password is incorrect Microsoft Learn
0x80180018 Sits in the range Microsoft uses for Windows MDM enrolment errors, but no meaning is published for this value not published by the vendor
0x80090011 NTE_NOT_FOUND: object was not found Microsoft Learn
0x80090019 NTE_KEYSET_NOT_DEF: the keyset is not defined Microsoft Learn

Confirm the fix worked

  1. dsregcmd /status shows the expected join state and a successful device authentication.
  2. File, Account in Word shows the correct account and the expected product.
  3. Outlook connects without prompting for credentials.
  4. A reboot leaves sign-in silent rather than prompting once per session.
  5. BitLocker recovery for the machine is still escrowed and readable after the work.

Questions people ask about this

Do I need a new licence to fix this?

No. Your entitlement is unaffected; this is device and key state on one machine. Once sign-in works the same licence activates the same applications.

Will re-registering the device lose anything?

No user data, but it resets device state. Confirm BitLocker recovery keys are escrowed somewhere reachable first, and expect conditional access rules that depend on device state to treat the machine as new until it re-registers.

Why does the browser version work when the apps do not?

Because browser sign-in does not need the device key. It authenticates the user directly, which makes it a useful test: if the web apps work, the account is fine and the problem is on the device.

We see this on every machine from one image. Is that relevant?

Very. Microsoft names a bad sysprep image as one of the two causes of this code. Fix the reference image rather than repairing machines one at a time, or you will be doing this again next quarter.

Can users fix this themselves?

Partly. Signing out of Office, clearing their own Office credentials and restarting is safe and resolves a fair proportion of cases. Anything touching device registration or the TPM needs an administrator and a BitLocker check first.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error Outlook Error 0x800CCC0E and 0x800CCC0F: Mail Server Connection Keeps Dropping Free Fix Office Save Errors 0x80070070 and 0x8007003B on Network Shares and Mapped Drives Free Fix Access Error 3343 Unrecognized Database Format: Repair a Corrupt ACCDB or MDB Free Fix Excel #REF!, #VALUE! and #NAME? Errors: Why Your Formulas Return Codes Not Numbers
โ† Back to Knowledge Base