Support for Windows 10 in Configuration Manager

Applies to: Configuration Manager (current branch)

Learn about the Windows 10 versions that Configuration Manager supports, including:

Windows Server builds as a client are supported the same as the associated Windows 10 version. For example, Windows Server 2016 is the same build version as Windows 10 LTSB 2016, and Windows Server version 1803 is the same build version as Windows 10 version 1803.

Windows 10 as a client

Configuration Manager attempts to provide support as a client for each new Windows 10 version as soon as possible after it becomes available. Because the products have separate development and release schedules, the support that Configuration Manager provides depends on when each becomes available.

A Configuration Manager version drops from the matrix after support for that version ends. Similarly, support for Windows 10 versions like the Enterprise 2015 LTSB or 1511 drops from the matrix when they’re removed from support.

The latest version of Configuration Manager current branch receives both security and critical updates, which can include fixes for issues with Windows 10 versions. When Microsoft releases a new version of Configuration Manager current branch, prior versions only receive security updates. For more information, see Support for Configuration Manager current branch versions.

The best way to stay current with Windows 10 is to stay current with Configuration Manager. For more information, see Configuration Manager and Windows as a Service.

If you use the long-term servicing branch of Configuration Manager, see Supported configurations for the long-term servicing branch.

The following table lists the versions of Windows 10 that you can use as a client with different versions of Configuration Manager.

Windows 10 version	ConfigMgr 1910	ConfigMgr 2002	ConfigMgr 2006	ConfigMgr 2010	ConfigMgr 2103
1803 (10.0.17134)
1809 (10.0.17763)
1909 (10.0.18363)
2004 (10.0.19041)
20H2 (10.0.19042)			Note	Note	Note

All currently supported versions of Configuration Manager current branch support the following Windows 10 LTSB/LTSC editions:

• Enterprise 2015 LTSB
• Enterprise 2016 LTSB
• Enterprise LTSC 2019

For more information on Windows lifecycle, see the Windows lifecycle fact sheet and Windows 10 release information.

Key
= Supported
= Not supported

Windows 10 client support notes

Support for Windows 10 semi-annual channel versions includes the following editions: Enterprise, Pro, Education, Pro Education, and Pro for Workstation.

For Windows 10, version 1909, OS deployment media shows the version as 10.0.18362.418.

For Windows 10, version 20H2, OS deployment media shows the version as 10.0.19041.508.

Windows 10 on ARM64

Configuration Manager supports the client on Windows 10 ARM64 devices.

Starting in version 2002, the All Windows 10 (ARM64) platform is available in the list of supported OS versions on objects with requirement rules or applicability lists.

If you previously selected the top-level Windows 10 platform, this action automatically selected both All Windows 10 (64-bit) and All Windows 10 (32-bit). This new platform isn’t automatically selected. If you want to add All Windows 10 (ARM64), manually select it in the list.

OS deployment isn’t supported, except for a feature update task sequence. Starting in version 2103, you can deploy a task sequence with a feature update to a Windows 10 on ARM64 device. For more information, see Deploy a feature update with a task sequence.

Support for Windows Insider

You can update and service Windows Insider builds. This ability is provided as a convenience to our customers. While this functionality should work, the support for it is best effort. Configuration Manager might not issue a hotfix for this functionality if it ceases to function.

To provide feedback on Windows Insider, use the Feedback Hub.

Sysprep and Windows 10 version 20H2

If you manually customize a reference computer that runs Windows 10 version 20H2, and then use capture media, Windows Sysprep fails with the following entry in the sysprep.log: Failed to clean the package repository database: 0x80070005. This issue happens when you sign in to the device and create a user profile.

To work around this issue, choose one of the following options:

Use the default image file (install.wim) from the installation media. Use the task sequence to apply configurations at run time.

Remove appx packages for the signed-in user before you use capture media. For more information, see Sysprep fails after you remove or update Microsoft Store apps that include built-in Windows images.

Manually run Sysprep, and then boot to the capture media to capture the image.

Windows 10 ADK

When you deploy operating systems with Configuration Manager, the Windows ADK is a required external dependency. For more information, see the following articles:

Starting with Windows 10 version 1809, Windows PE is a separate installer. Otherwise there’s no functional difference.

Make sure to download both the Windows ADK for Windows 10 and the Windows PE add-on for the ADK.

The following table lists the versions of the Windows 10 ADK that you can use with different versions of Configuration Manager.

Windows 10 ADK version	ConfigMgr 1910	ConfigMgr 2002	ConfigMgr 2006	ConfigMgr 2010	ConfigMgr 2103
1809 (10.1.17763)
1903 (10.1.18362)
2004 (10.1.19041)

Key
= Supported This table only shows Windows ADK supportability in relation to the version of Configuration Manager. Microsoft recommends using the Windows ADK that matches the version of Windows you’re deploying. Use the latest Windows ADK version when deploying the latest Windows 10 version. The latest Windows ADK version may support deployment of older OS versions, such as Windows 8.1. For more information on Windows ADK component supportability, see DISM supported platforms and USMT requirements.
= Backward compatible This combination isn’t tested but should work. We’ll document any known issues or caveats.
= Not supported

Windows 10 ADK support notes

Configuration Manager only supports x86 and amd64 components of the Windows 10 ADK. It doesn’t currently support ARM or ARM64 components.

Windows Server builds have the same Windows ADK requirement as the associated Windows 10 version. For example, Windows Server 2016 is the same build version as Windows 10 LTSB 2016.

How to Find Windows 10 Computer Specifications & Systems Requirements

Here’s an overview of how to find computer specification requirements, versions, and languages available for Windows 10.

Table of Contents

System requirements for installing Windows 10

These are the basic requirements for installing Windows 10 on a PC. If your device does not meet these requirements, you may not have the great experience intended with Windows 10 and might want to consider purchasing a new PC.

RAM: 1 gigabyte (GB) for 32-bit or 2 GB for 64-bit

Hard drive size:

32GB or larger hard disk

Note: See below under “More information on hard drive space to install or update Windows 10” for more details.

Compatible with DirectX 9 or later with WDDM 1.0 driver

Display: 800×600 Internet Connection:

Internet connectivity is necessary to perform updates and to download and take advantage of some features. Windows 10 Pro in S mode, Windows 10 Pro Education in S mode, Windows 10 Education in S mode, and Windows 10 Enterprise in S mode require an internet connection during the initial device setup (Out of Box Experience or OOBE), as well as either a Microsoft account (MSA) or Azure Activity Directory (AAD) account. Switching a device out of Windows 10 in S mode also requires internet connectivity. Learn more about S mode here.

There may be additional requirements over time for updates, as well as requirements to turn on specific features within the OS.

Keeping Windows 10 up-to-date

Windows 10 is designed to deliver updates for the supported lifetime of the device. Two types of updates may be provided: quality updates and feature updates. Quality updates include both security and non-security updates and are typically targeted to be released once a month. Feature updates also include security and non-security fixes as well as new features to Windows 10 and are typically provided twice a year. Ensuring that your device receives these updates and is kept up-to-date is important for your device security. Windows 10 periodically checks for updates so you don’t have to. When an update is available—and sufficient free disk space is available on your device—it will be automatically installed. So that Windows 10 continues to stay updated, it’s important to ensure your device has sufficient free space. See additional applicable details in the following notes.

Important notes about updates:

• A device might not be able to receive updates if the device hardware is incompatible, if it lacks current drivers or sufficient available hard drive space, or if it’s otherwise outside of the Original Equipment Manufacturer’s (“OEM”) support period. Visit the Windows Lifecycle Fact Sheet or the Lifecycle FAQ for Windows products to learn more about the servicing timeline for each feature update.
  • Some of the disk space needed for installing updates is only temporarily required. Typically, ten days after installing an update, a disk cleanup will be automatically performed to delete copies of the older, unneeded Windows files and free up space again.
• Not all features in an update will work on all devices.
• An internet connection is required to perform updates and Internet access (ISP) fees might apply.
• If you need assistance installing an update, Windows 10 Update Assistant may be able to help.

More information on hard drive space requirements to install or update Windows 10

The size of the Windows operating system that comes with your device and the amount of space needed to download and install Windows updates, are highly variable as they depend on a variety of factors. Visit here to learn why. The factors that impact the amount of free hard drive space needed to take an update include: the versions of Windows previously installed on the machine, the amount of disk space available to reuse from Windows files, such as the virtual memory pagefile or hibernation file, which applications are installed on your device and how those applications store data. Starting with the May 2019 Update, the system requirements for hard drive size for clean installs of Windows 10 as well as new PCs changed to a minimum of 32GB. The 32GB or larger drive requirement is set to leave space for users to install apps and to keep data on the device. Installing Windows or updating from a previous version of Windows on devices with less than 32GB storage will continue to work if the device has enough free space available. When updating, Windows will attempt to automatically free up enough hard drive space and guide you through freeing up even more if the automatic cleanup is not sufficient. You can also take steps to free up space on your own. For more information, see Free up space to install the latest Windows 10 update or visit the related FAQ.

Feature-specific requirements for Windows 10

In addition to the requirements above that are needed to run Windows, some features have additional requirements. In some cases, features included with updated versions of Windows 10 will be best experienced with newer processors. For specific hardware support please refer to your Original Equipment Manufacturer (OEM). Below are some additional details regarding requirements for key features:

• BitLocker Drive Encryption (available with Windows 10 Pro or Windows 10 Enterprise only) requires a Trusted Platform Module (TPM) 1.2 or higher and Trusted Computing Group (TCG)-compliant BIOS or UEFI. BitLocker can be used on devices without TPM, but you will need to save a startup key on a removable device such as a USB flash drive. TPM 2.0 and InstantGo support is required when you want to automatically encrypt the local drive when joining a device to Azure Active Directory (AAD). Check with your PC manufacturer to confirm if your device supports the correct TPM version and InstantGo for the scenario you want to enable.
• BitLocker To Go requires a USB flash drive (available in Windows 10 Pro and Windows 10 Enterprise only).
• Client Hyper-V requires a 64-bit system with second level address translation (SLAT) capabilities and additional 2 GB of RAM (available in Windows 10 Pro and Windows 10 Enterprise only).
• Cortana is only currently available on Windows 10 for the United States, United Kingdom, China, France, Italy, Germany, Brazil, Mexico, Japan, Canada, Spain, Australia and India.
• Microsoft account is required for some features.
• Miracast requires a display adapter which supports Windows Display Driver Model (WDDM) 1.3, and a Wi-Fi adapter that supports Wi-Fi Direct.
• Movies & TV application is not available in all regions. For the most up-to-date list of regions, please go to the Movies & TV information page.
• Secure boot requires firmware that supports UEFI v2.3.1 Errata B and has the Microsoft Windows Certification Authority in the UEFI signature database.
• Skype is available only in select countries and regions. Calling to select countries and regions only. Excludes special, premium and non-geographic numbers. For details, visit the Office FAQ page.
• Snap: The number of applications that can be snapped will depend upon the minimum resolution for the application with a limit of two applications in Tablet mode and four applications in Desktop mode.
• Speech recognition will vary by device microphone. For a better speech experience, you will need a:
  • High fidelity microphone array
  • Hardware driver with microphone array geometry exposed
• Tablet mode is available on tablets and 2-in-1s with GPIO indicators or those that have a laptop and slate indicator will be able to be configured to enter «tablet mode» automatically.
• Touch: To use touch, you need a tablet or a monitor that supports multi-touch.
• Two-factor authentication requires the use of a PIN, Biometric (finger print reader or illuminated infrared camera), or a phone with Wi-Fi or Bluetooth capabilities.
• Windows Hello requires a camera configured for near infrared (IR) imaging or fingerprint reader for biometric authentication. Devices without biometric sensors can use Windows Hello with a PIN or a portable Microsoft compatible security key.
• Xbox application requires an Xbox Live account, which is not available in all regions. For the most up-to-date list of regions, please go to Xbox Live Countries and Regions website.
• Wi-Fi Direct Printing requires a Wi-Fi adapter that supports Wi-Fi Direct and a device that supports Wi-Fi Direct Printing.