Kb5050021 breaks Certificate Chain, (0x800b010c) "A certificate was explicitly revoked by its issuer"

Anonymous
2025-01-16T04:52:55+00:00

Kb5050021 breaks 'DigiCert Trusted Root G4' chain, Windows 11 x64 23H2

Unable to load Everything (C:\Program Files\Everything 1.5a\Everything64.exe), or run the signed installer which can be downloaded here: https://www.voidtools.com/forum/viewtopic.php?t=9787Author asserts his cert was not revoked. It was signed Jan 1 2025.

It was working before the update. I reproduced this issue after completing a disk image recovery prior to the kb5050021 update ; Everything worked fine once again. After updating windows a second time the problem returned once again. Windows claims the certificate was revoked by issuer for executables signed by the Digicert Trusted Root G4 chain. Next, to factor out the certificates, assuming the cert store would remain unchanged, I simply uninstalled the update and the problem also went away again.

Says the signature is OK under properties/details of the Installer

But when I try run the installer I get the following error

I used digicerts own certificate testing utility for windows and verified its authenticity.

Any ideas how to fix this problem?

***moved from Windows / Windows 11 / Security and privacy***

Windows for business | Windows Client for IT Pros | Devices and deployment | Set up, install, or upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

8 answers

Sort by: Most helpful
  1. Anonymous
    2025-02-10T08:44:08+00:00

    Thank you - error 404, but expect the developer to fix it soon.

    Regards George

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-02-02T14:13:25+00:00

    Hello,

    Any fix for "non-technical" users? Downloading an older one is not an acceptable remedy - right?

    I really appreciate any help you can provide.

    Regards George

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-01-18T11:24:46+00:00

    Found a work around, remove the signature with microsoft sdk signtool:

    signtool remove /s Everything64.exe

    Was this answer helpful?

    0 comments No comments