808bits

BitLocker® Windows Resume (winresume) in Microsoft Windows 10, Windows 10 Pro, Windows 10 Enterprise, Windows 10 Enterprise LTSB, Windows Server 2016 Standard, Windows Server 2016 Datacenter, Windows Storage Server 2016

FIPS 140-2 certificate #3501 · Microsoft Corporation · data as of 2026-08-28
Historical. Moved to historical list due to dependency on certificate #3487. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode with module Boot Manager in Microsoft Windows 10, Windows 10 Pro, Windows 10 Enterprise, Windows 10 Enterprise LTSB, Windows 10 Mobile, Windows Server 2016 Standard, Windows Server 2016 Datacenter, Windows Storage Server 2016 validated to FIPS 140-2 under Cert. #3487 operating in FIPS mode

Certificate

Certificate number3501
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorMicrosoft Corporation · website
Software versions10.0.14393.1770

Module description

BitLocker® Windows Resume is an operating system loader which loads the Windows OS kernel (ntoskrnl.exe) and other boot stage binary image files, as well as previous operating system state information, when Windows has been previously put into a sleep or hibernate power state.

Security level exceptions

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

Approved algorithms

AlgorithmCAVP certificate
AES5295, 5297
RSA2833
SHS4250

Tested configurations

  • Windows 10 Anniversary Update (x64) running on a Dell XPS 8700 with an Intel Core i7 with PAA
  • Windows 10 Anniversary Update (x64) running on a Microsoft Surface 3 with an Intel Atom x7 with PAA
  • Windows 10 Anniversary Update (x86) running on a Dell Inspiron 660s with an Intel Core i3 without PAA
  • Windows 10 Enterprise Anniversary Update (x64) running on a Dell Precision Tower 5810MT with an Intel Xeon with PAA
  • Windows 10 Enterprise Anniversary Update (x64) running on a HP Compaq Pro 6305 with an AMD A4 with PAA
  • Windows 10 Enterprise Anniversary Update (x64) running on a Microsoft Surface Book with an Intel Core i7 with PAA
  • Windows 10 Enterprise Anniversary Update (x64) running on a Microsoft Surface Pro 3 with an Intel Core i7 with PAA
  • Windows 10 Enterprise Anniversary Update (x64) running on a Microsoft Surface Pro 4 with an Intel Core i5 with PAA
  • Windows 10 Enterprise Anniversary Update (x86) running on a Dell Inspiron 660s with an Intel Core i3 without PAA
  • Windows 10 Enterprise LTSB Anniversary Update (x64) running on a Dell Precision Tower 5810MT with an Intel Xeon with PAA
  • Windows 10 Enterprise LTSB Anniversary Update (x64) running on a Dell XPS 8700 with an Intel Core i7 with PAA
  • Windows 10 Enterprise LTSB Anniversary Update (x86) running on a Dell Inspiron 660s with an Intel Core i3 without PAA
  • Windows 10 Pro Anniversary Update (x64) running on a Dell Precision Tower 5810MT with an Intel Xeon with PAA
  • Windows 10 Pro Anniversary Update (x64) running on a Microsoft Surface Book with an Intel Core i7 with PAA
  • Windows 10 Pro Anniversary Update (x64) running on a Microsoft Surface Pro 3 with an Intel Core i7 with PAA
  • Windows 10 Pro Anniversary Update (x64) running on a Microsoft Surface Pro 4 with an Intel Core i5 with PAA
  • Windows 10 Pro Anniversary Update (x86) running on a Dell Inspiron 660s with an Intel Core i3 without PAA
  • Windows Server 2016 Datacenter Edition (x64) running on a Dell PowerEdge R630 Server with an Intel Xeon with PAA
  • Windows Server 2016 Standard Edition (x64) running on a Dell PowerEdge R630 Server with an Intel Xeon with PAA
  • Windows Server 2016 Standard Edition (x64) running on a HP Compaq Pro 6305 with an AMD A4 with PAA
  • Windows Storage Server 2016 (x64) running on a Dell PowerEdge R630 Server with an Intel Xeon with PAA (single-user mode)

Validation history

DateTypeLab
2019-08-01InitialLeidos 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: 2019-08-01

Source documents