Skip to content

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

Your vault is empty.

License Error 0x800B0100

0x800B0100 and 0x800B0109: update signature and certificate failures

12 min read Updated October 5, 2026 Windows Update & Setup

Recommended fix

Windows 11 Pro Retail license

Original price was: 25,00 €.Current price is: 14,99 €.

Fix It Now

Fix it now

0x800B0100 is TRUST_E_NOSIGNATURE: no signature was present in the subject. 0x800B0109 is CERT_E_UNTRUSTEDROOT: the chain processed but ended in a root this machine does not trust. Windows will not install code it cannot vouch for, and the machine is nearly always the problem rather than the package.

Run these in an elevated Command Prompt, in order. The last three rebuild the catalogue cache

w32tm /resync
w32tm /query /status
net stop cryptsvc
ren %windir%\System32\catroot2 catroot2.old
net start cryptsvc
  1. Read the w32tm /query /status output before anything else. A wrong clock fails certificate validation exactly like an untrusted root does, and it takes seconds to rule out.
  2. Open Services and confirm Cryptographic Services is running. Microsoft describes it as supporting file signature confirmation and retrieval of root certificates from Windows Update, and says reconfiguring it is not recommended.
  3. If the machine has been offline or has automatic root updates blocked, refresh the trusted roots. On a connected machine run certutil -generateSSTFromWU roots.sst, then import that file into the local machine’s trusted root store on the affected machine.
  4. Reboot and retry the update.

Import root certificates only from a machine and a source you control. The root store decides what your machine trusts, so it deserves the same care as an administrative password.

If the update installs, you are done. If it still fails, the next section separates the trust-layer codes from the crypt-layer ones, which need different answers.

Why it happens

Update packages are signed, and the catalogue files that accompany them carry hashes for every file inside. Before servicing touches anything, the trust provider validates that a signature is present, that the digest matches the content, that the chain of certificates leads to a root in the machine’s trusted root store, and that the countersigned timestamp shows the signing happened while the signing certificate was valid. Four separate checks, and each has its own code.

The trusted root store is not static. Roots roll over and Windows normally refreshes them quietly. Machines that have been offline for a long time, or that sit behind the policy that turns automatic root updates off, fall behind until a package arrives they cannot chain. That policy is a real registry value: DisableRootAutoUpdate under HKLM\SOFTWARE\Policies\Microsoft\SystemCertificates\AuthRoot, where 1 disables the automatic update of the trusted certificate trust list.

Clock errors produce the same symptoms for a different reason. A certificate that is not yet valid, or has expired according to the machine’s idea of the date, fails validation exactly as an untrusted one does. Check it first because it costs nothing, and because it explains a surprising number of these cases on virtual machines restored from old checkpoints and on hardware with a dead battery.

Not every code here is a trust problem, and treating them as one group sends you to the wrong place. 0x80092003 is CRYPT_E_FILE_ERROR, an error reading or writing a file, and 0x80092004 is CRYPT_E_NOT_FOUND, an object or property that could not be found. Those two are the cryptography layer failing at the file and lookup level, which is what a damaged catalogue database looks like. 0x80096010 is TRUST_E_BAD_DIGEST, the signature not matching the content it covers, and 0x80096005 is TRUST_E_TIME_STAMP, a timestamp signature or certificate that could not be verified.

The system clock is wrong

You have this one if The date or time zone is visibly off, or the machine is a virtual machine restored from an old checkpoint.

  1. Set the correct time zone first, then the time.
  2. Run w32tm /resync and confirm with w32tm /query /status that a source is being used and the offset is small.
  3. On domain members, confirm the machine syncs with the domain hierarchy rather than an unreachable external server.
  4. Replace the motherboard battery if the clock resets on every power cycle.

/force is not a documented parameter of w32tm /resync. The documented ones are /computer, /nowait, /rediscover and /soft; an unrecognised switch makes w32tm print usage and exit without resynchronising anything.

The trusted root store is out of date

You have this one if 0x800B0109 on an isolated or long-offline machine, or one where automatic root certificate updates are switched off by policy.

  1. Check HKLM\SOFTWARE\Policies\Microsoft\SystemCertificates\AuthRoot for DisableRootAutoUpdate set to 1. That is the setting that stops the refresh.
  2. On a connected machine run certutil -generateSSTFromWU roots.sst to produce a current bundle of the third-party roots from Windows Update.
  3. Transfer the file and import it into the local machine trusted root store on the affected machine.
  4. If the policy has to stay, schedule regular manual refreshes rather than leaving the store to drift.

The catalogue database is damaged

You have this one if Cryptographic errors about missing objects or file access (0x80092003, 0x80092004) rather than untrusted roots, across several unrelated packages.

  1. Stop Cryptographic Services with net stop cryptsvc.
  2. Rename %windir%\System32\catroot2 to catroot2.old.
  3. Start the service again with net start cryptsvc; Windows rebuilds the folder.
  4. Retry the update, then run sfc /scannow if the problem persists.

Stop the service before renaming. Renaming catroot2 while Cryptographic Services is running can leave the machine unable to verify anything until it is restarted.

An inspection appliance is rewriting the download

You have this one if 0x80096010: the package downloads and fails its digest check, on a network that inspects and re-signs HTTPS traffic.

  1. Ask for the Windows Update endpoints to be excluded from TLS inspection. Update content is already signed and verified, so inspecting it adds nothing except failures.
  2. As a test, fetch the same update on a connection that is not inspected and install it by hand. If it installs cleanly you have proved where the corruption comes from.
  3. For managed fleets, deliver updates from an internal update server so client traffic never crosses the inspection point.
  4. Check any caching proxy for a stale or truncated copy of the file.

The platform no longer supports the signing algorithm

You have this one if Updates installed happily until a point in the past and nothing has installed since, on a platform that is out of support.

  1. Install the servicing stack update for that platform first, then the code signing support update it depends on.
  2. Reboot and retry the update that was failing.
  3. Treat this as a stopgap. Signing algorithms and roots move on, and a platform nobody ships trust updates for will keep failing verification in new ways.
  4. Plan the move to a supported release rather than repeating this every few months.

Full reference

Sorting the variants before you change anything

What you see Likely cause
The browser also warns about certificates on ordinary sites Clock, or a broken root store
Only updates fail, on an isolated machine Trusted roots have not been refreshed
A digest mismatch on a downloaded package An inspection proxy altering traffic, or a damaged download
Crypt errors about missing objects or file access A damaged catalogue database rather than a trust problem
Everything after a certain date fails on an unsupported platform Missing code signing support for the algorithm in use

The codes, split by which layer raised them

Code Published name Layer
0x800B0100 TRUST_E_NOSIGNATURE Trust: no signature was present in the subject
0x800B0109 CERT_E_UNTRUSTEDROOT Trust: the chain processed but terminated in an untrusted root
0x80096010 TRUST_E_BAD_DIGEST Trust: the digital signature of the object did not verify
0x80096005 TRUST_E_TIME_STAMP Trust: the timestamp signature or certificate could not be verified, or is malformed
0x80092003 CRYPT_E_FILE_ERROR Cryptography: an error reading or writing a file
0x80092004 CRYPT_E_NOT_FOUND Cryptography: cannot find object or property

Certutil, for checking rather than guessing

Command Documented behaviour
certutil -verify -urlfetch <file> Verifies a certificate or chain; -urlfetch retrieves and verifies AIA certificates and CDP CRLs
certutil -generateSSTFromWU roots.sst Generates a store file synced with Windows Update, containing the third-party roots
certutil -syncWithWU <dir> Syncs certificates with Windows Update, downloading the AuthRoot and Disallowed CTLs and their certificate files to a directory

certutil -verify -urlfetch against the failing file is the fastest way to separate the three possibilities. It walks the chain, fetches revocation information and reports where validation stops, which tells you whether the problem is trust, time or the file itself. Run it before you start renaming folders.

The registry that controls root refresh

Path Value Effect
HKLM\SOFTWARE\Policies\Microsoft\SystemCertificates\AuthRoot DisableRootAutoUpdate 1 disables the automatic update of the trusted certificate trust list. Absent or 0 leaves the normal refresh in place

This is worth checking on any machine that has been through a hardening baseline. The setting is a legitimate control for isolated environments, but it is frequently applied estate-wide by someone who did not intend to stop trust updates on internet-connected desktops. If it stays, the root store becomes something you have to maintain by hand.

When the clock, the roots and the catalogue are all fine

  • Check whether the machine is behind a proxy that requires authentication. A proxy error page returned in place of a package fails verification, because it is not a signed package.
  • Check free space on the system volume. The crypt-layer file errors can be nothing more exotic than a full disk.
  • Confirm Cryptographic Services is running and set to start automatically. Microsoft explicitly says reconfiguring it is not recommended and that services depending on it fail to start if it is disabled.
  • Try the update from the Microsoft Update Catalog by hand. If the standalone package installs and the same update fails through the client, the fault is in the delivery path rather than in trust.
  • 0x80240061 has no published meaning. If you see it, treat it as an update-agent failure during package handling and diagnose from the other codes in the same log rather than from that one.

When a licence is the actual fix

If the machine is stuck on a build nobody supports, this will keep happening: signing algorithms and root certificates move on, and a platform that receives no trust updates keeps failing verification in new ways. Moving to a supported release is the durable fix, and a Windows 11 Pro upgrade licence is one route where the hardware allows it. Arco can check which edition and entitlement the machine already holds first, because many machines are already covered. On a supported machine everything in this article is free.

Every code this article covers

Code What it points at Source
0x800B0100 TRUST_E_NOSIGNATURE: no signature was present in the subject Microsoft Learn
0x800B0109 CERT_E_UNTRUSTEDROOT: a certificate chain processed, but terminated in a root certificate not trusted by the trust provider Microsoft Learn
0x80092004 CRYPT_E_NOT_FOUND: cannot find object or property Microsoft Learn
0x80092003 CRYPT_E_FILE_ERROR: an error occurred while reading or writing to a file Microsoft Learn
0x80096010 TRUST_E_BAD_DIGEST: the digital signature of the object did not verify Microsoft Learn
0x80096005 TRUST_E_TIME_STAMP: the timestamp signature and/or certificate could not be verified, or is malformed Microsoft Learn
0x80240061 Seen during update package handling alongside the trust codes above. Microsoft’s Windows Update error reference does not carry this value, so diagnose it from the codes around it rather than from this one not published by the vendor

Confirm the fix worked

  1. Run w32tm /query /status and confirm the machine has a valid time source and a small offset.
  2. Confirm Cryptographic Services is running and that catroot2 has been rebuilt with a current timestamp.
  3. Run certutil -verify -urlfetch against the package that was failing and confirm the chain validates.
  4. Install the update that was failing and confirm it completes.
  5. Open an ordinary HTTPS site and confirm no certificate warnings, which shows the root store is healthy.

Questions people ask about this

Can I just turn off signature checking?

No. The check is what stops a modified package installing itself into the operating system. There is no supported switch to disable it for updates, and anything claiming to offer one is not something to run on a machine you care about.

Why did this start without anything changing?

Because something did change, just not on your machine. Roots and signing certificates roll over on Microsoft’s schedule, and a machine that has stopped refreshing its root store only finds out when it meets a package signed under the new arrangement.

Are all of these codes root certificate problems?

No, and that assumption sends people down the wrong path. 0x800B0109 is genuinely an untrusted root. 0x80092003 and 0x80092004 are the cryptography layer failing to read a file or find an object, which usually means a damaged catalogue database. 0x80096010 is a digest that does not match, which points at the download rather than at trust.

Does this cost money to fix?

On a supported version of Windows, no. Time synchronisation, root refresh and the catalogue cache reset are all free. Cost only comes into it if the machine is on a version nobody supports, in which case you are buying a supported platform rather than a fix for this code.

How do I check a package’s signature myself?

Run certutil -verify -urlfetch against the file. It walks the chain, fetches revocation information and reports where validation stops, which tells you whether the problem is trust, time or the file itself.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix 0x80246001 and 0x80246005: the download manager has no usable source License Error 0x800F0923: a driver or binary is not compatible with the new build Free Fix 0xC1800118: WSUS is holding feature update content it has no key to decrypt License Error 0xC1900208: an incompatible app blocks the Windows 11 feature update
โ† Back to Knowledge Base