How do I review my old Windows application's compatibility with upcoming code-signing change

Jeremy S Slaughter 0 Reputation points
2026-10-13T11:35:21.1233333+00:00

Hi all!

I'm running a web application that I commissioned but did not develop. I am the user not the developer. I received a warning from Microsoft today as in the title above. Could my application cease to function on 19th October 2026 when Microsoft Windows Production PCA 2011 expires? If so, can I do the following actions suggested by Microsoft myself, without engaging a developer? Perhaps there's a how-to document somewhere I can work through in Azure.

  1. Review your Windows applications' certificate-validation behavior and identify custom checks tied to specific Microsoft certificates, certificate chains, or signing algorithms.
  2. Update application validation to use supported Windows trust APIs, such as WinVerifyTrust, rather than custom checks tied to fixed certificates or signing algorithms.
  3. Verify that software using a private trust store has a process for recognizing legitimate Microsoft certificate rotations.
Artifact Signing
Artifact Signing

A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)

0 comments No 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.