Contact [Email], Microsoft’s published address for Windows FIPS questions, to request a module-by-module Windows Server 2025 status and any publishable target quarter; no authoritative public completion date is currently available.^1^
Current public status
As of November 17, 2026:
- Microsoft’s Windows FIPS validation page does not list Windows Server 2025 among releases with completed validations. Its completed Windows Server list currently includes Windows Server 2022, 2019, 2016, and older semi-annual releases.^1^
- NIST’s CMVP IUT list contains Microsoft modules associated with Windows 11 version 24H2, Windows Server 2025, and Azure Local version 24H2, including:
- Boot Manager
- Code Integrity
- Cryptographic Primitives Library
- Kernel Mode Cryptographic Primitives Library
- Secure Kernel Code Integrity
- Windows OS Loader
- BitLocker Dump Filter
- The first six listed modules have public IUT dates of April 10, 2025; BitLocker Dump Filter has an IUT date of June 12, 2026.^2^
An IUT entry is not a validation certificate. It indicates testing at an accredited laboratory. After the laboratory submits its report, the module can move into Modules In Process; validation is complete only when CMVP issues and publishes the corresponding certificate. CMVP does not provide the laboratory’s expected report-submission date and directs schedule questions to the vendor.^2^
Consequently, the public records do not currently establish that these Windows Server 2025 modules have completed FIPS 140-3 validation.
Timeline
There is no published Microsoft or NIST target quarter for completion in the available official material. A reliable quarter should not be inferred from the IUT dates:
- Modules can remain in laboratory testing for an indeterminate period.
- Each module can progress separately.
- NIST reports that CMVP processing remains substantially manual, making completion timing difficult to predict.^3^
Only Microsoft can confirm an unpublished forecast, and it may decline to provide a committed date. For a regulated deployment, treat publication of the applicable CMVP certificates and Security Policies—not IUT or MIP appearance—as the release gate.
Request a written Microsoft response
Send the following to [Email]:
Subject: Windows Server 2025 FIPS 140-3 CMVP status and target timeline
Please provide the current IUT/MIP status and any publishable target quarter for the Windows Server 2025 Boot Manager, Windows OS Loader, Code Integrity, Secure Kernel Code Integrity, Cryptographic Primitives Library, Kernel Mode Cryptographic Primitives Library, and BitLocker Dump Filter modules.
Planned deployment: Windows Server 2025 [edition, build, and servicing level].
Regulatory deadline: [date].Please also confirm:
- Which builds and editions are intended to be covered.
- Whether each module is being validated to FIPS 140-3.
- Whether additional Windows Server 2025 modules are required for the intended approved mode.
- Where the final certificates and Security Policies will be published.
- Whether Microsoft can provide a written compliance statement for procurement records before certificate issuance.
CMVP validates particular cryptographic modules and their defined versions, environments, and operating rules—not Windows Server 2025 as one blanket module. After certificates appear, compare the planned build, edition, module versions, algorithm scope, and approved-mode instructions against every applicable certificate and Security Policy. Microsoft states that all rules in those Security Policies must be followed for Windows to operate in a FIPS-approved mode.^1^
Official pages to monitor
- Microsoft Windows FIPS page: completed Windows validations, certificate links, Security Policies, and approved-mode guidance.^1^
- NIST CMVP IUT/MIP records: submission-processing status before certificate issuance.^2^
The September 21, 2026 transition moves remaining FIPS 140-2 validations to the historical list; it does not itself convert Windows Server 2025’s in-process modules into validated FIPS 140-3 modules. CMVP notes that historical FIPS 140-2 modules may remain usable for existing systems, subject to agency risk decisions, but that does not satisfy an organization’s explicit requirement for active FIPS 140-3 certificates.^4^
References