808bits

Windows OS Loader

FIPS 140-2 certificate #3194 · Microsoft Corporation · data as of 2026-08-28
Historical. Moved to historical list due to dependency on certificate #3089. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with module Boot Manager validated to FIPS 140-2 under Cert. #3089 operating in FIPS mode

Certificate

Certificate number3194
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorMicrosoft Corporation · website
Software versions10.0.15063.674 [1], 10.0.15254 [2] and 10.0.16299 [3]

Module description

The BitLocker® Windows OS Loader loads the boot-critical driver and OS kernel image files.

Security level exceptions

  • Physical Security: N/A
  • Design Assurance: Level 2

Approved algorithms

AlgorithmCAVP certificate
AES4894, 4895, 4896, 4897, 4901, 4902
RSA2673, 2674, 2675
SHS4009, 4010, 4011

Allowed algorithms

NDRNG

Tested configurations

  • Surface Hub (x64) running on a Microsoft Surface Hub with PAA [1]
  • Windows 10 Education Fall Creators Update (x64) running on a Microsoft Surface Pro with PAA [3]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Book 2 with PAA [3]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Book with PAA [3]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Laptop with PAA [3]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Pro 4 with PAA [3]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Pro with PAA [3]
  • Windows 10 Enterprise Fall Creators Update (x64) running on a Microsoft Surface Studio with PAA [3]
  • Windows 10 Enterprise Fall Creators Update (x64) running on an HP Pro x2 612 G2 Detachable PC with LTE with PAA [3]
  • Windows 10 Home Fall Creators Update (x86) running on a Dell Inspiron 660s without PAA [3]
  • Windows 10 Mobile Fall Creators Update (ARMv7) running on a Microsoft Lumia 650 [2]
  • Windows 10 Mobile Fall Creators Update (ARMv7) running on a Microsoft Lumia 950 [2]
  • Windows 10 Mobile Fall Creators Update (ARMv7) running on a Microsoft Lumia 950 XL [2]
  • Windows 10 Mobile Fall Creators Update (ARMv7) running on an HP Elite x3 [2]
  • Windows 10 Pro Fall Creators Update (x64) on Hyper-V on Windows Server 2016 running on a Surface Pro 4 with PAA [3]
  • Windows 10 Pro Fall Creators Update (x64) running on a Dell Latitude 5285 with PAA [3]
  • Windows 10 Pro Fall Creators Update (x64) running on a Dell Latitude 5290 with PAA [3]
  • Windows 10 Pro Fall Creators Update (x64) running on a Dell PowerEdge R630 Server with PAA [3]
  • Windows 10 Pro Fall Creators Update (x64) running on a Dell Precision Tower 5810MT with PAA [3]
  • Windows 10 Pro Fall Creators Update (x64) running on a Microsoft Surface 3 with LTE with PAA [3]
  • Windows 10 Pro Fall Creators Update (x64) running on a Microsoft Surface Laptop with PAA [3]
  • Windows 10 Pro Fall Creators Update (x64) running on a Microsoft Surface Pro 3 with PAA [3]
  • Windows 10 Pro Fall Creators Update (x64) running on a Microsoft Surface Pro with PAA [3]
  • Windows 10 Pro Fall Creators Update (x64) running on a Panasonic Toughbook with PAA [3]
  • Windows 10 Pro Fall Creators Update (x64) running on an HP Compaq Pro 6305 with PAA [3]
  • Windows 10 Pro Fall Creators Update (x64) running on an HP Slimline Desktop with PAA [3]
  • Windows 10 S Fall Creators Update (x64) running on a Microsoft Surface Laptop with PAA [3]
  • Windows Server Datacenter Core (x64) on Hyper-V on Windows Server running on a Dell Precision Tower 5810MT with PAA [3]
  • Windows Server Datacenter Core (x64) running on a Dell PowerEdge R630 Server with PAA [3]
  • Windows Server Datacenter Core (x64) running on a Dell PowerEdge R740 Server with PAA [3] (single-user mode)
  • Windows Server Datacenter Core (x64) running on a Dell Precision Tower 5810MT with PAA [3]
  • Windows Server Standard Core (x64) on Hyper-V on Windows Server running on a Dell Precision Tower 5810MT with PAA [3]
  • Windows Server Standard Core (x64) running on a Dell PowerEdge R630 Server with PAA [3]
  • Windows Server Standard Core (x64) running on a Dell PowerEdge R740 Server with PAA [3]
  • Windows Server Standard Core (x64) running on a Dell Precision Tower 5810MT with PAA [3]

Validation history

DateTypeLab
2018-09-26InitialLeidos 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
  • Validation dates on record: 2018-09-26

Source documents