Support for Windows 10 in Configuration Manager
Applies to: Configuration Manager (current branch)
Learn about the Windows 10 versions that Configuration Manager supports as a client. For more information about support for later versions of Windows, see Support for Windows 11.
For more information about support for the Windows Assessment and Deployment Kit (ADK) for Windows 10, see Support for the Windows ADK.
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.
For more information on Windows Server as a site system, see Supported operating systems for Configuration Manager site system servers.
Windows 10 versions
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.
This information supplements Supported operating systems for clients and devices.
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 2006||ConfigMgr 2010||ConfigMgr 2103||ConfigMgr 2107|
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
|= Not supported|
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.
For Windows 10, version 21H1, OS deployment media shows the version as 10.0.19041.844.
Windows 10 on ARM64
Configuration Manager supports the client on Windows 10 ARM64 devices.
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). 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.