Share via

Azure code signing update

Fahme Elhakeem 26 Reputation points
2026-03-25T16:38:35.3133333+00:00

Hello

We have identified several devices that are missing the Azure Code Signing update. These devices are currently running Windows 10 version 1703. However, the available updates provided for other versions (1607, 1809, and 1909) do not appear to be compatible with version 1703.

Could you please advise on the appropriate steps to resolve this issue for Windows 10 version 1703? Specifically, we would like to know if there is a supported update for this version, or if an alternative solution is recommended.

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Chen Tran 9,090 Reputation points Independent Advisor
    2026-03-25T17:21:07.0233333+00:00

    Hello Fahme,

    Thank you for posting question on Microsoft Windows Forum!

    Based on the issue description. Well! For Windows 10 version 1703 (Creators Update), the reason you are encountering compatibility issues is that this version reached its end of servicing several years ago and does not have a native or supported update for Azure Code Signing (ACS). Now known as Microsoft Trusted Signing. While Microsoft released KB5022661 to backport ACS support to many older versions (like 1607, 1809, and 1909), version 1703 was explicitly excluded because it was already out of support for both General and Enterprise/Education channels by the time the ACS requirement was implemented.

    The suggestion here is to upgrade those devices to a supported Windows version that includes the Trusted Signing support update, then install the latest cumulative update for that version. Also, it is worth noting that the required update is cumulative, so applying the latest supported update is the recommended path.

    Some vendors require ACS for their newer agents. If you cannot upgrade the OS immediately, check if the vendor offers a "Legacy" or "Extended Support" agent version that still uses the older SHA-2 signing method instead of the newer ACS/Trusted Signing.

    The following article is useful for your further reference for addressing your concerns.

    Hope the above information is helpful! If it is. Free feel to hit "Accepted" for benefitting others in community having the same issue too.

  2. Q&A Assist
    2026-03-25T16:38:48.31+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Windows 10 version 1703 is not listed as a supported platform for the Azure Code Signing / Trusted Signing update (KB5022661). The documented compatibility matrix only includes:

    • Windows 10, version 1909 (KB5005624 or later)
    • Windows 10, version 1809 (KB5005625 or later)
    • Windows 10, version 1607 (KB5006669 or later)
    • Windows 10, version 1507 (KB5006675 or later)

    There is no corresponding Trusted Signing support update published for Windows 10 version 1703.

    In addition, Windows 10 version 1703 is at end of service and no longer receives security and quality updates. The recommended and supported path is to upgrade these devices to a supported Windows 10 release that has Trusted Signing support (for example, 1909 with KB5005624 or later, or another currently supported version that includes the Trusted Signing update), rather than trying to retrofit Azure Code Signing support onto 1703.

    For devices stuck on 1703 that cannot be upgraded, there is no supported Azure Code Signing / Trusted Signing enablement update documented; the alternative is to move the workload that requires Trusted Signing to devices on a supported Windows version.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.