For details, see 6.1

For details, see 6.2.1

Required for phones that run WindowsВ 10 Mobile

Optional for other devices that run WindowsВ 10 Mobile and for any devices that run WindowsВ 10 Mobile Enterprise

For details, see 6.2.2

Required for phones

Optional for other devices

Required for phones

Optional for other devices

Required for phones that run WindowsВ 10 Mobile

Optional for other devices that run WindowsВ 10 Mobile and for any devices that run WindowsВ 10 Mobile Enterprise

Required for phones

Optional for other devices

For details, see 6.3

For details, see 6.5

Required for phones

Optional for other devices

See 2.6 for the required, optional, and not supported buttons

See 6.6 for button behavior requirements

See 3.6 for the required, optional, and not supported buttons

See 6.6 for button behavior requirements

Power button is required, all other buttons are not supported

See 6.6 for button behavior requirements

All buttons are optional

See 6.6 for button behavior requirements

For details, see 6.7

Required for phones

Optional for other devices

At least one video output port is required for desktop PCs

Optional for other devices

Required for phones

Optional for other devices

Section 2.0 — Minimum hardware requirements for WindowsВ 10 Mobile

This section provides detailed hardware requirements that apply to any device that runs WindowsВ 10 Mobile. See Table 2 for the list of devices that can run WindowsВ 10 Mobile. For additional component requirements that may also apply, see Section 6.

NoteВ В Throughout this specification, all requirements for WindowsВ 10 Mobile also apply to WindowsВ 10 Mobile Enterprise except where specified otherwise.

2.1 SoC

Table 4 lists the supported SoCs for devices that run WindowsВ 10 Mobile. Any official variants that are available from the SoC vendor (for example, a version of the SoC with a higher clock speed) are also supported.

Table 4: SoCs with integrated modems supported in devices that run WindowsВ 10 Mobile

Qualcomm Technologies, Inc.

Snapdragon 820, 810, 808, 617, 210

Table 5 lists the additional supported SoCs for devices that run WindowsВ 10 Mobile Enterprise . These SoCs do not have cellular support, and are intended for devices that either use Wi-Fi only or do not have network connectivity. Devices that run the WindowsВ 10 Mobile Enterprise can use any of the SoCs listed in Table 4 and Table 5.

Table 5: Wi-Fi only SoCs supported in devices that run WindowsВ 10 Mobile Enterprise

Qualcomm Technologies, Inc.

Snapdragon 810, 808, 617, 210 (All: APQ variants only)

Existing Windows Phones that include the SoCs listed in Table 6 can be updated to WindowsВ 10 Mobile.

Table 6: SoCs supported in Windows Phones that can be updated to WindowsВ 10 Mobile

Qualcomm Technologies, Inc.

Snapdragon 810, 808, 801, 800, 617, 410, 400, 210, 200, S4 Plus

2.2 Memory

The RAM requirements for devices that run WindowsВ 10 Mobile are listed in Table 7.

Table 7: RAM requirements for devices that run WindowsВ 10 Mobile

2560 x 1440 (WQHD)

вЃ¶This resolution is not natively supported. Windows Phone 10 supports WXGA 1280 x 800 displays by rendering the UI at 1280 x 768 resolution (15:9 aspect ratio) and displaying pillarboxes for the unused pixels.

вЃ·Windows Phone 10 supports native qHD resolution in addition to scaling from HD or WVGA to qHD.

вЃёFWVGA resolutions always have software navigation buttons enabled.

2.4.2 Pixel aspect ratio

Display pixels in devices that run Windows 10 Mobile must be square—that is, have an aspect ratio of 1:1.

2.4.3 Refresh rate for display panel hardware

The display panel hardware in devices that run WindowsВ 10 Mobile must support an update and refresh rate of 59.97 В±0.03 Hz. The range for smart panels (panels that support self-refresh) is extended to 59.97 В±3.0 Hz at room temperature (25ЛљC). Update rate is defined as the rate at which new frames can be sent to the display hardware. The refresh rate is defined as the number of times in a second that display hardware draws the data. This specification applies for all display configurations and all supported overlay modes (primary + secondary).

2.4.4 Display brightness levels

All displays in devices that run WindowsВ 10 Mobile must support a minimum of 16 levels of brightness.

2.5 Sensors

2.5.1 Ambient light sensor

If the device includes an ambient light sensor, it must support a reporting rate of ≥4 Hz.

2.6 Hardware buttons

Table 10lists the required, optional, and not supported hardware buttons for devices that run WindowsВ 10 Mobile and WindowsВ 10 Mobile Enterprise .

All other buttons not included in this table, including custom hardware buttons specified by the OEM, are optional. See section 6.6 for additional requirements about hardware button behavior.

Table 10: Button implementation requirements for WindowsВ 10 Mobile and WindowsВ 10 Mobile Enterprise

вЃ¶ Phones that use a WVGA display must include Start, Back, and Search buttons that are implemented in hardware (as mechanical or capacitive buttons). For phones that use a non-WVGA display, hardware-implemented Start, Back, and Search buttons are optional. If the OEM chooses to not include hardware-implemented Start, Back, and Search buttons on a phone that uses a non-WVGA display, the OEM must configure the OS to render these buttons via software. For more information, see the Windows 10 Partner Documentation when it is available.

вЃ· For phones that use a non-WVGA display, see the previous footnote. For tablets and other devices, software-rendered Start, Back, and Search buttons are always available through the OS.

2.6.1 Button placement requirements for phones that run WindowsВ 10 Mobile

This section provides button placement requirements that are specific to phones that run WindowsВ 10 Mobile. These requirements do not apply to any other device that runs WindowsВ 10 Mobile or WindowsВ 10 Mobile Enterprise . Figure 1 shows the placement of the Back, Start, and Search controls for phones.

Figure 1: Button placement for phones

The Start, Back, and Search buttons must be in alignment as shown in Figure 2.

Figure 2: Button vertical offset restrictions for phones

2.6.1.1 Start, Back, and Search button placement

The Search, Start, and Back buttons must be placed directly below the display.

Button locations in relation to one another are as follows:

• Start is located below the display, centered horizontally on the phone.
• Back is located to the left of Start.
• Search is located to the right of Start.

Additional buttons, text, logos, or graphics must not be placed on the front of the phone in the area surrounding the Start, Back, and Search buttons, defined as:

• The area to the left or right of the three buttons, horizontally.
• The area within 4 mm of the top and bottom of the three buttons, vertically.

Figure 1 shows the disallowed region, which is outlined in red.

2.6.1.2 Power button placement

The Power button must not be placed in the disallowed region on the front of the phone, which is outlined in red in Figure 1.

2.6.1.3 Volume Up and Volume Down button placement

The Volume Up and Volume Down buttons must not overlap the zone that contains the Search, Start, and Back buttons.

2.6.1.4 Camera button placement

If a camera button is implemented, the requirements for positioning it on the phone are as follows:

• The camera button must be positioned so that it enables natural landscape left camera behavior.
• The camera button must be positioned to facilitate camera operation with the right index finger while holding the phone in landscape left orientation.
• The camera button must not be placed on the face of the phone.

2.6.1.5 Start, Back, and Search buttons with FWVGA

On phones that use an FWVGA display panel, the following button options are available.

• You can choose not to include mechanical or capacitive Start, Back, and Search buttons. In this case, the Windows Phone OS reserves the bottom 54 scan lines to render the Start, Back, and Search buttons through software.
• You can include mechanical or capacitive Start, Back, and Search buttons. In this case, the OEM must select from the Windows Phone natively supported resolutions (WVGA for scale-up, and HD for scale-down), and the display driver will then scale the output. Selecting FWVGA with mechanical or capacitive buttons without scaling to a different resolution is not supported.

NoteВ В Phones that use a combination of an FWVGA display and the MSM8x10 or MSM8x12 applications processor must use software-rendered Start, Back, and Search buttons. Mechanical or capacitive Start, Back, and Search buttons are not supported on these phones.

2.7 Accessibility

In regions where TTY support is required by regulation, phones that run WindowsВ 10 Mobile must support a TTY mode for compatibility with standard TTY text devices plugged in through the 3.5-mm headset jack. In regions where hearing aid compatibility (HAC) is required by regulation, the minimum HAC device rating considered hearing-aid compatible is M3 or T3.

For additional accessibility guidance, see section 6.9.

2.8 Trusted Platform Module (TPM)

Devices that run WindowsВ 10 Mobile must include a Trusted Platform Module (TPM) that implements version 2.0 of the TPM specification. The TPM can be a firmware-based solution integrated into the SoC or included as a discrete component in the device. The TPM 2.0 must meet the following requirements:

• An EK certificate must be either pre-provisioned to the TPM by the hardware vendor or be capable of being retrieved by the device during the first boot experience.
• It must ship with SHA-256 PCR banks and implement PCRs 0 through 23 for SHA-256. Note it is acceptable to ship TPMs with a single switchable PCR bank that can be used for both SHA-1 and SHA-256 measurements.
• It must support TPM2_HMAC command.

For detailed TPM information, see Trusted Platform Module Technology Overview on TechNet.

Section 3.0 — Minimum hardware requirements for WindowsВ 10 for desktop editions

This section provides detailed hardware requirements that apply to any device that runs WindowsВ 10 for desktop editions. See Table 2 for the list of devices that can run WindowsВ 10 for desktop editions. For additional component requirements that may also apply, see section 6.0.

NoteВ В Throughout this specification, all requirements for WindowsВ 10 for desktop editions also apply to WindowsВ 10 Enterprise.

3.1 Processor

Devices that run WindowsВ 10 for desktop editions require a 1 GHz or faster processor or SoC that meets the following requirements:

• Compatible with the x86* or x64 instruction set.
• Supports PAE, NX and SSE2.
• Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW for 64-bit OS installation

* Beginning with Windows 10, version 2004, all new Windows 10 systems will be required to use 64-bit builds and Microsoft will no longer release 32-bit builds for OEM distribution. This does not impact 32-bit customer systems that are manufactured with earlier versions of Windows 10; Microsoft remains committed to providing feature and security updates on these devices, including continued 32-bit media availability in non-OEM channels to support various upgrade installation scenarios.

3.2 Memory

Devices that run WindowsВ 10 for desktop editions must meet the RAM requirements shown in Table 11.

Table 11: RAM requirements for devices that run WindowsВ 10 for desktop editions

3.3 Storage

3.3.1 Storage device size

Devices that run WindowsВ 10 for desktop editions must include a storage device that meets the size requirements shown in Table 12.

Table 12: Storage size requirements for devices that run WindowsВ 10 for desktop editions

3.3.2 Storage controller

Storage controllers used in devices that run WindowsВ 10 for desktop editions must meet the following requirements:

• Storage controllers must support booting using the Extensible Firmware Interface (EFI) and implement device paths as defined in EDD-3.
• Storage host controllers and adapters must meet the requirements for the device protocol used and any requirements related to the device storage bus type.
• Bus-attached controllers must implement the correct class/subclass code as specified in the PCI Codes and Assignments v1.6 specification.

3.4 Display and graphics

3.4.1 Resolution, bit depth, and size

WindowsВ 10 for desktop editions supports a minimum display resolution of SVGA (800 x 600) with a depth of 32 bits on each output simultaneously, and a minimum diagonal display size for the primary display of 7-inches or larger. Tablets, 2-in-1s, and laptops that run WindowsВ 10 for desktop editions must include a display that meets the minimum requirements listed earlier. A display is optional for desktop PC’s that run WindowsВ 10 for desktop editions.

Note Display size requirements do not apply to Windows 10 IoT Enterprise

3.4.2 Graphics

Devices that run WindowsВ 10 for desktop editions must include a GPU that supports DirectX 9 or later.

3.5 Networking

Devices that run WindowsВ 10 for desktop editions must include at least one network connectivity option, such as Wi-Fi or an Ethernet adapter.

3.6 Hardware buttons

Table 13 lists the required, optional, and not supported hardware buttons for devices that run WindowsВ 10 for desktop editions. All other buttons not included in this table, including custom hardware buttons specified by the OEM, are optional. See section 6.6 for additional requirements about hardware button behavior.

Table 13: Button implementation requirements for WindowsВ 10 for desktop editions

вЃё A software-rendered Start button is always available through the OS.

3.7 Trusted Platform Module (TPM)

As of July 28, 2016, all new device models, lines or series must implement and be in compliance with the International Standard ISO/IEC 11889:2015 or the Trusted Computing Group TPM 2.0 Library and a component which implements the TPM 2.0 must be present and enabled by default from this effective date.

The following requirements must be met:

• All TPM configurations must comply with local laws and regulations.
• Firmware-based components that implement TPM capabilities must implement version 2.0 of the TPM specification.
• An EK certificate must either be pre-provisioned to the TPM by the hardware vendor or be capable of being retrieved by the device during the first boot experience.
• It must ship with SHA-256 PCR banks and implement PCRs 0 through 23 for SHA-256. Note that it is acceptable to ship TPMs with a single switchable PCR bank that can be utilized for SHA-256 measurements.
• It must support TPM2_HMAC command.

For detailed TPM information, see Trusted Platform Module Technology Overview on TechNet, and for TPM 1.2 and 2.0 version comparisons, see TPM recommendations, also on TechNet.

Note While TPM requirements are highly encouraged for Windows 10 IoT Enterprise, it is not required. The use of a TPM for Windows 10 IoT Enterprise devices is determined based on the usage and security requirements of each device.

Section 4.0 — Minimum hardware requirements for Windows ServerВ 2016

This section provides detailed hardware requirements that apply only to computers that run Windows ServerВ 2016. For additional component requirements that may also apply, see section 6.0.

4.1 Processor

Computers that run Windows ServerВ 2016 require a 64-bit 1.4 GHz or faster processor or SoC that meets the following requirements:

• Compatible with the x64 instruction set.
• Supports NX and DEP.
• Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW.
• Supports Second Level Address Translation (EPT or NPT).

4.2 Buses

Computers that run Windows ServerВ 2016 must support PCI Express natively.

4.3 Memory

Computers that run Windows ServerВ 2016 must include at least 512 MB RAM. The RAM must use ECC or similar technology to prevent single-bit errors from causing system failure.

4.4 Storage

4.4.1 Storage device size

Computers that run Windows ServerВ 2016 must include a 60 GB or larger storage device.

4.4.2 Storage controller

Computers that run Windows ServerВ 2016 must include a Windows Compatible storage adapter that is compliant with the PCI Express architecture specification. Persistent storage devices on servers classified as hard disk drives must not be PATA. Windows ServerВ 2016 does not allow ATA/PATA/IDE/EIDE for boot, page, or data drives.

4.5 Display and graphics

4.5.1 Resolution and bit depth

Windows ServerВ 2016installation option of Server with Desktop Experience supports a minimum display resolution of XGA (1024 x 768) with a depth of 32 bits on each output simultaneously. The Nano Server installation option only requires VGA support if you want to use the Recovery Console locally.

4.5.2 Graphics

A GPU is optional for computers that run Windows ServerВ 2016. If a GPU is included, it must support DirectX 9 or later.

4.6 Networking

Computers that run Windows ServerВ 2016 must include the following in a Windows Compatible driver:

• A Gigabit Ethernet adapter
• A network adapter that is compliant with the PCI Express architecture specification.
• A network adapter that supports Pre-boot Execution Environment (PXE). The network adapter may optionally support network debugging (KDNet).

4.7 Trusted Platform Module (TPM)

For devices or computers that run Windows ServerВ 2016, a Trusted Platform Module (TPM) is optional. If a TPM is implemented, the following requirements must be met:

• Hardware-based and firmware-based TPMs must implement version 2.0 of the TPM specification.
• An EK certificate must either be pre-provisioned to the TPM by the HW vendor or be capable of being retrieved by the device during the first boot experience.
• It must ship with SHA-256 PCR banks and implement PCRs 0 through 23 for SHA-256. Note that it is acceptable to ship TPMs with a single switchable PCR bank that can be utilized for both SHA-1 and SHA-256 measurements.

A UEFI firmware option to turn off the TPM is not required.

For detailed TPM information, see Trusted Platform Module Technology Overview on TechNet.

Section 5.0 — Minimum hardware requirements for IoT Core

This section provides detailed hardware requirements that apply only to devices that run IoT Core. For additional component requirements that may also apply, see section 6.0.

5.1 Processor

Devices that run IoT Core require an ARM SoC or x86, x64 processor/SoC that meets the following requirements:

• x86/x64 processor/SoC:
  • 400 MHz or faster.
  • Compatible with the x86 or x64 instruction set.
  • Supports PAE, NX and SSE2.
  • Supports CMPXCHG16b, LAHF/SAHF, and PrefetchW for 64-bit OS installation
• ARM SoCs:
  • Compatible with the ARMv7 instruction set

NoteВ В Faster processor performance may be required based on the design and functionality of the device.

For a sample of enabled SoCs, see Enabled SoCs.В

5.2 Memory

Devices that run IoT Core must meet the RAM requirements shown in Table 14.

Table 14: RAM requirements for devices that run IoT Core

* Available RAM needed after any carve-out by SoC vendor/OEM components. A minimum of 512 MB of RAM is required for update functionalilty. Additional RAM may be required based on the design and functionality of the device and display resolution.

5.3 Storage

Devices that run IoT Core must include a minimum of 2 GB of storage.

Note: A minimum of 1GB of storage is to remain free for update functionality. Additional storage may be required based on the design and functionality of the device.

5.4 Trusted Platform Module (TPM)

As of July 28, 2016, WindowsВ 10 Mobile Enterprise editions based on IoT Mobile licensing for all new devices and platforms must implement and be in compliance with the TPM 2.0 ISO/IEC 11889 standard with either an integrated firmware-based solution or included as a discrete component. IoT Core requirements for TPM 2.0 are optional.

TPM 2.0 must meet the following requirements:

• An EK certificate must either be pre-provisioned to the TPM by the hardware vendor or be capable of being retrieved by the device during the first boot experience.
• It must ship with a SHA-256 PCR bank and implement PCRs 0 through 23 for SHA-256. Note it is acceptable to ship TPMs with a single switchable PCR bank that can be used for both SHA-1 and SHA-256 measurements.

TPM 2.0 will be required for IoT Core in a future release

For detailed TPM information, see Trusted Platform Module Technology Overview on TechNet.

5.5 graphics

A GPU is optional for computers that run Windows 10 IoT Core. If a GPU is included, it must support DirectX 9 or later.

Section 6.0 — Shared minimum hardware requirements for components

This section provides minimum requirements for components that apply to more than one OS or device type. For each component in this section, the specified requirements apply if the component is implemented for a given device.

Refer to Table 3 to determine whether the components in this section are required or optional for each OS and device type.

6.1 Touch, touch pad, and active pen

If a touch solution, a precision touch pad solution, or an active pen solution is implemented, the solution must meet the requirements in Table 15. For additional guidance about user experience and compatibility, refer to the related content in the Hardware Lab Kit.

Table 15: Touch, precision touch pad, and active pen requirements for Windows 10

The solution must be HID compliant per the Windows specification for touch digitizer reporting, active pen digitizer reporting, or precision touchpad digitizer reporting, as appropriateвЃ№. Solutions that are not HID compliant will not function with Windows 10.

The solution must provide input data by using one of the following options:

• One of the bus-specific HID miniport drivers included with Windows (USB, I2C or Bluetooth). For this scenario, the touch solution must follow the bus-specific HID requirements.В№вЃ°
• A third-party HID miniport driver.

All necessary bus drivers and third-party HID miniport drivers (if applicable) for the solution must be available on Windows Update, part of the factory image, and functional in Windows PE.

The solution must report all genuine contacts to the operating system. The solution must not generate false contact reports (also known as ghost points), whether the device is running on AC or DC power.

False contact reports render a device unusable and may prevent the user from successfully servicing or performing basic interactions with the device.

For gestures such as zoom and pinch to be enabled, a touch or precision touch pad digitizer must be able to detect, track, and report at least 2 contacts simultaneously. For additional guidance about accessibility compliance, user experience and compatibility for simultaneous contact reporting, please refer to the related content in the Hardware Lab Kit.

В№вЃ°For HID over I2C requirements, see HID Over I2C Protocol Specification. For HID over Bluetooth requirements, see HID Service Specification.

6.2 Multimedia

6.2.1 Camera

If a camera is implemented, it must meet the requirements in this section.

6.2.1.1 Camera specifications

The camera must support the following requirements:

• The camera must have a resolution of VGA or better.
• For camera button specifications, see section 6.6.3 «Camera button behavior.»
• The camera must support auto exposure (AE) and auto white balance (AWB).

Autofocus is optional, but highly recommended for rear-facing cameras.

Functional specifications for the camera are shown in Table 16 (for still pictures) and Table 17 (for video).

Table 16: Camera still-capture functional specifications