Support for Windows 11 in Configuration Manager

Applies to: Configuration Manager (current branch)

Learn about the Windows 11 versions that Configuration Manager supports as a client.

For more information about support for the Windows Assessment and Deployment Kit (ADK) for Windows 11, see Support for the Windows ADK.

Note

You can continue to use Microsoft Endpoint Manager to manage devices running Windows 11 the same as with Windows 10. If another article doesn't explicitly reference Windows 11, assume that feature support for Windows 10 also includes Windows 11. This article lists some known issues.

Windows 11 versions

Configuration Manager attempts to provide support as a client for each new Windows 11 version soon 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, Configuration Manager doesn't support Windows 11 versions when their support lifecycle ends.

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

Windows 11 version ConfigMgr 2006 ConfigMgr 2010 ConfigMgr 2103 ConfigMgr 2107
21H2
(10.0.22000)
Not supported Not supported Not supported Supported

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

Key
Supported = Supported
Not supported = Not supported

Support notes

  • Support for Windows 11 versions includes the following editions: Enterprise, Pro, Education, Pro Education, and Pro for Workstation.

  • Windows 11 reports the Operating System property as Microsoft Windows NT Workstation 10.0, which is identical to Windows 10. To distinguish devices running Windows 11, use the Operating System Build device property for build number 10.0.22000 or later.

  • OS deployment images and upgrade packages for Windows 11 show the image name as Windows 10. For more information, see Using deployment tools with Windows 11 images.

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, its support is best effort. Configuration Manager might not issue a hotfix for this functionality if it doesn't work.

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

Known issues

Desktop Analytics

Desktop Analytics doesn't support Windows 11. For information about Windows 11 hardware readiness, Microsoft recommends that you enable tenant attach and Endpoint analytics.

Windows servicing dashboard

The Windows Servicing dashboard currently includes Windows 11 devices with the latest version of Windows 10. It doesn't yet distinguish a version for Windows 11. For more information on this dashboard, see Manage Windows as a service using Configuration Manager.

Software Center notifications don't display during quiet period

By default, Windows 11 enables focus assist for the first hour after a user signs on for the first time. For more information, see Reaching the Desktop and the Quiet Period.

Software Center notifications are currently suppressed during this time. For more information, see Turn Focus assist on or off in Windows.

Pre-provisioning BitLocker during task sequence doesn't own TPM

Applies to: Windows ADK for Windows 11

When you use a Windows 11-based boot image with an OS deployment task sequence that includes the Pre-provision BitLocker step, the step might fail. You'll see errors similar to the following strings in the smsts.log:

'TakeOwnership' failed (2147942402)
pTpm->TakeOwnership(sOwnerAuth), HRESULT=80070002
Failed to take ownership of TPM. Ensure that Active Directory permissions are properly configured
The system cannot find the file specified. (Error: 80070002; Source: Windows)
Process completed with exit code 2147942402
Failed to run the action: Pre-provision BitLocker. Error -2147024894

To work around this issue, add a Run Command Line step to the task sequence before the Pre-provision BitLocker step. Run the following command:

reg.exe add HKLM\SOFTWARE\Policies\Microsoft\TPM /v OSManagedAuthLevel /t REG_DWORD /d 2 /f

For more information on this registry key, see Change the TPM owner password.

Next steps

Support for the Windows ADK