TCB Launcher
TCB Launcher, from Microsoft Corporation, holds FIPS 140-2 certificate #4457 at overall level 1. The validation is historical: agencies may keep the module in existing systems but not buy it new. Below are its algorithm certificates, its validation history, and the list moves this tracker has observed, which NIST does not date.
Caveat: When operated in FIPS mode with modules Windows OS Loader validated to FIPS 140-2 under Cert. #4339 operating in FIPS mode or Windows Resume validated to FIPS 140-2 under Cert. #4348 operating in FIPS mode
Certificate
| Certificate number | 4457 |
|---|---|
| Standard | FIPS 140-2 |
| Status | historical |
| Overall level | 1 |
| Module type | Software-Hybrid |
| Embodiment | Multi-Chip Stand Alone |
| Vendor | Microsoft Corporation · website |
| Software versions | 10.0.18363[1] and 10.0.19041[2] |
| Hardware versions | Intel Core i5-8365U[2] and Intel Core i7-8665U[1] |
Module description
Quoted from the NIST CMVP entry for this certificate.
The TCB Launcher Module, which consists of the binary TCBLAUNCH.EXE, is the module that launches the Hypervisor and Secure Kernel and other binary image files needed to launch those two components.
Security level exceptions
- Design Assurance: Level 2
Approved algorithms (5)
| Algorithm | CAVP certificates |
|---|---|
| AES | C1363, C1897 |
| CKG | vendor affirmed |
| DRBG | C1363, C1897 |
| RSA | C1367, C1947 |
| SHS | C1363, C1897 |
Allowed algorithms
NDRNG
Tested configurations
- Windows 10 Enterprise May 2020 Update (x64) running on a Panasonic Toughbook FZ 55 with an Intel Core i5-8365U with PAA [2]
- Windows 10 Enterprise November 2019 Update (x64) running on a Dell Latitude 5300 2-in-1 with an Intel Core i7-8665U with PAA [1] (single-user mode)
Validation history
| Date | Type | Lab |
|---|---|---|
| 2023-03-22 | Initial | Leidos Accredited Testing & Evaluation (AT&E) Lab |
Status timeline
As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.
- 2026-08-21: first observed by this tracker, status historical at the time of the earliest snapshot
- 2026-09-22: observed moving from active to historical
- Validation dates on record: 2023-03-22