Couldn't verify 'C:\WINDOWS\ccmsetup\ccmsetup.cab' authenticode signature. Return code 0x800b010c RRS feed

  • Question

  • Windows 10 1809 17636.104

    I can not install CM client, as Windows claims that certificate was revoked

    • Edited by scerazy Wednesday, October 24, 2018 1:12 PM
    Wednesday, October 24, 2018 11:35 AM

All replies

  • serial no 33000001b1ddedba54e965b85f0001000001b1 issued by Microsoft Code Signing PCA ex 26/07/2019
    • Edited by scerazy Wednesday, October 24, 2018 1:12 PM
    Wednesday, October 24, 2018 1:01 PM
  • Same certificate on Windows 10 1607 14393.2551 shows perfectly fine

    Both machines update from the same local TrustedRootsCertificates location (which is pushed by GPO)

    • Edited by scerazy Wednesday, October 24, 2018 2:05 PM
    Wednesday, October 24, 2018 1:55 PM
  • It happened on upgrade from 1607–>1809

    I checked my snapshot before upgrade and all well, after upgrade this most odd error

    I will test clean install.

    Would it have anything to do with do with Microsoft retiring SHA-1 code signing (for over 2 years now...)

    • Edited by scerazy Wednesday, October 24, 2018 6:30 PM
    Wednesday, October 24, 2018 4:36 PM
  • CRL for this certificate


    only states that certificate with serial no


    is revoked

    Wednesday, October 24, 2018 7:16 PM
  • Hi,

    Certificates are issued with a planned lifetime and explicit expiration date. Once issued, a certificate becomes valid once its validity time has been reached, and it is considered valid until its expiration date. However, various circumstances may cause a certificate to become invalid prior to the expiration of the validity period. Such circumstances include change of name, change of association between subject and Certificate Authority (for example, when an employee terminates employment with an organization), and compromise or suspected compromise of the corresponding private key. Under such circumstances, the Certificate Authority needs to revoke the certificate.

    For more details, please refer to:


    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, October 25, 2018 7:24 AM
  • I am sorry, but why did you bother to reply?

    It makes no sense & it is definitely UNRELATED!

    Another pointless reply from (MSFT CSG) - whatever it stands for!

    Thursday, October 25, 2018 10:21 AM
  • Just to verify, what version exactly of ConfigMgr are you running (this is a 2012 forum)?

    Jason | https://home.configmgrftw.com | @jasonsandys

    Thursday, November 1, 2018 2:42 PM
  • It has really nothing to do with CM version.

    It is LTSC 2019 upgrade process that makes this certificate as revoked (no idea how, I expect it to be a bug in LTSC 2019, even updated to latest official 17763.55)

    I have done the upgrade again with same result.

    Clean install is perfectly fine!

    Thursday, November 1, 2018 10:17 PM
  • https://social.technet.microsoft.com/Forums/windows/en-US/8ee36fb1-eb0e-44e5-bb0d-b822458517b0/certificates-issue-this-certificate-has-been-revoked-by-its-certification-authority-after-ltsb?forum=win10itprogeneral

    • Edited by scerazy Wednesday, November 7, 2018 11:13 AM
    Saturday, November 3, 2018 9:37 AM
  • Maybe time to ask in a Windows 10 forum or open a support case.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Monday, November 5, 2018 4:12 PM