Post-Quantum Cryptography Is Coming to Windows — Is Your Fleet Ready?

The Standards Are Final. The Migration Clock Is Running.

In August 2024, NIST finalized the first post-quantum cryptography standards: ML-KEM for key establishment (FIPS 203), ML-DSA for digital signatures (FIPS 204), and SLH-DSA as a hash-based signature backup (FIPS 205). That was the starting gun, not the finish line. Migrating an organization's cryptography takes years — new algorithms have to land in protocols, libraries, certificates, and hardware, and every long-lived secret encrypted today with classical algorithms is exposed to "harvest now, decrypt later" attacks. An adversary recording your TLS traffic now doesn't need a quantum computer today; they need one eventually.

This is why the commentary around post-quantum readiness has shifted in 2026 from whether to how fast. Government timelines like CNSA 2.0 set concrete dates for quantum-resistant algorithms in national security systems, and vendors across the stack — Microsoft included — are shipping post-quantum support in their platforms. The question for Windows admins is no longer theoretical: what does your fleet actually run today?

Before You Can Migrate, You Have to Inventory

Every post-quantum migration guide says the same thing first: build a cryptographic inventory. You cannot plan a migration for algorithms you don't know you're using. On a Windows fleet, that inventory has uncomfortable corners:

• Legacy TLS and cipher suites. Machines still negotiating TLS 1.0/1.1 or weak ciphers are the same machines least likely to pick up post-quantum key exchange cleanly. Retiring legacy protocols is a prerequisite, not a side quest.
• Long-lived certificates. Internal CAs, code-signing certificates, and device certificates with multi-year lifetimes will still be in force when quantum-resistant algorithms become mandatory. Their algorithms and key lengths need to be on a list today.
• Hardcoded crypto in line-of-business apps. The app nobody maintains, pinned to an old TLS stack, is exactly the app that breaks — or silently stays classical — during a migration.
• Endpoints that never get audited. The forgotten workstation in a branch office, the build machine under someone's desk, the server everyone assumes was decommissioned. Crypto debt hides where visibility ends.

What to Audit Right Now

You don't need a quantum computer to start, and you don't need to wait for a vendor's migration wizard. The useful audit work is available today on every Windows machine:

1. Schannel configuration: which protocols and cipher suites are enabled, and whether legacy TLS is still negotiable. If TLS 1.0 is still on, your post-quantum story hasn't started.
2. Certificate store hygiene: expired, self-signed, and weak-key certificates, plus any trusted roots that shouldn't be there. A migration that carries a compromised trust store forward is worse than no migration.
3. Protocol surface: SMB signing, LDAP signing and channel binding, NTLM usage. Post-quantum key exchange protects future traffic; these settings protect today's traffic from relay and downgrade attacks that don't need quantum anything.
4. Update posture: machines behind on updates won't receive post-quantum algorithm support when it ships in platform updates. Patch latency is crypto-agility latency.

Each of these is a single-machine audit — the kind of check WinSentinel runs locally, with full results on that machine, no limits. When you're managing an organization, the same checks rolled up across the fleet — which machines still allow legacy TLS, which sites carry the most weak certificates, which nodes are behind on updates — are what turn a one-machine finding into a migration plan. That's the fleet view: centralized rollups, drift alerts when a machine regresses, and compliance evidence that the migration is actually progressing.

The Honest Timeline

Nobody serious claims a cryptographically relevant quantum computer arrives next quarter, and nobody serious says migration can wait until it does. The honest position is in the middle: standards are final, vendor support is rolling out, and the inventory-and-hygiene work is useful right now regardless of when the quantum deadline lands. Every legacy protocol you retire and every weak certificate you replace is a smaller migration later — and a smaller attack surface today.

The post-quantum migration is not a future project. It is a present-day audit problem with a future deadline — and the audit part is the part you can finish this week.

Start with one machine. Check its TLS settings, its certificate store, its update state. Then ask the harder question: how many machines in your fleet can you say the same about, with evidence rather than hope? That gap — between what you audited and what you assume — is the real post-quantum risk, and it's measurable today.