Microsoft Known Issue

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the How to get this update section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the "How to get this update" section of this article.

After installing this update, you might be unable to change your user account profile picture. When attempting to change a profile picture by selecting the button Start> Settings> Accounts > Your info, and then selecting Choose a file, you might receive an error message with error code 0x80070520.We are working on a resolution and will provide an update in an upcoming release.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

Option 1: Configure Microsoft Connected Cache endpoint in DOCacheHost policy as indicated in Cache hostname. Additionally, DOCacheHostSourcehas to be set to 1or removed as indicated in Cache hostname source. By default, the DOCacheHost and DOCacheHostSource policies have no value. Option 2: You can mitigate this issue using Group Policies available through our support channel. Organizations can request help at Support for business. We are working on a resolution and will provide an update in an upcoming release.

We are working on a resolution and will provide an update in an upcoming release.

We are working on a resolution and will provide an update in an upcoming release.

This issue is addressed in KB5039212.

This issue is addressed in KB5039212.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

Option 1: Configure Microsoft Connected Cache endpoint in DOCacheHost policy as indicated in Cache hostname. Additionally, DOCacheHostSourcehas to be set to 1or removed as indicated in Cache hostname source. By default, the DOCacheHost and DOCacheHostSource policies have no value. Option 2: You can mitigate this issue using Group Policies available through our support channel. Organizations can request help at Support for business. We are working on a resolution and will provide an update in an upcoming release.

We are working on a resolution and will provide an update in an upcoming release.

This issue is addressed in KB5039705.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the How to get this update section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the "How to get this update" section of this article.

We are working on a resolution and will provide an update in an upcoming release.

We are working on a resolution and will provide an update in an upcoming release.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

Option 1: Configure Microsoft Connected Cache endpoint in DOCacheHost policy as indicated in Cache hostname. Additionally, DOCacheHostSourcehas to be set to 1or removed as indicated in Cache hostname source. By default, the DOCacheHost and DOCacheHostSource policies have no value. Option 2: You can mitigate this issue using Group Policies available through our support channel. Organizations can request help at Support for business. We are working on a resolution and will provide an update in an upcoming release.

We are working on a resolution and will provide an update in an upcoming release.

We are working on a resolution and will provide an update in an upcoming release.

This issue is resolved in the Windows update (KB5037803) released on or after May 14, 2024.

This issue is resolved in the Windows update (KB5037803) released on or after May 14, 2024.

This issue is resolved in the Windows update (KB5037836) released on or after May 14, 2024.

This issue is resolved in the Windows update (KB5037836) released on or after May 14, 2024.

This issue is resolved in the Windows update (KB5037823) released on or after May 14, 2024.

This issue is resolved in the Windows update (KB5037823) released on or after May 14, 2024.

This issue is resolved in the Windows update (KB5037778) released on or after May 14, 2024.

This issue is resolved in the Windows update (KB5037778) released on or after May 14, 2024.

This issue is resolved in the Windows update (KB5037780) released on or after May 14, 2024.

This issue is resolved in the Windows update (KB5037780) released on or after May 14, 2024.

This issue is resolved in the Windows update (KB5037800) released on or after May 14, 2024.

This issue is resolved in the Windows update (KB5037800) released on or after May 14, 2024.

This issue is addressed in KB5037771.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

Option 1: Configure Microsoft Connected Cache endpoint in DOCacheHost policy as indicated in Cache hostname. Additionally, DOCacheHostSourcehas to be set to 1or removed as indicated in Cache hostname source. By default, the DOCacheHost and DOCacheHostSource policies have no value. Option 2: You can mitigate this issue using Group Policies available through our support channel. Organizations can request help at Support for business. We are working on a resolution and will provide an update in an upcoming release.

We are working on a resolution and will provide an update in an upcoming release.

This issue is addressed in KB5037768.

This issue is addressed in KB5037771.

This issue is addressed in KB5037770.

Option 1: Configure Microsoft Connected Cache endpoint in DOCacheHost policy as indicated in Cache hostname. Additionally, DOCacheHostSourcehas to be set to 1or removed as indicated in Cache hostname source. By default, the DOCacheHost and DOCacheHostSource policies have no value. Option 2: You can mitigate this issue using Group Policies available through our support channel. Organizations can request help at Support for business. We are working on a resolution and will provide an update in an upcoming release.

We are working on a resolution and will provide an update in an upcoming release.

This issue is addressed in KB5037768.

This issue is addressed in KB5037765.

This issue is addressed in KB5037765.

This issue is addressed in KB5037763.

This issue is addressed in KB5037763.

We are working on a resolution and will provide an update in an upcoming release.

This issue is addressed in KB5037782.

This issue is addressed in KB5037782.

This issue is resolved in update KB5037426.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

This issue is addressed in KB5037425.

This issue is addressed in KB5037423.

This issue is addressed in KB5037422.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the How to get this update section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the "How to get this update" section of this article.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

This issue is addressed in KB5035853.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

This issue is addressed in KB5035853.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the How to get this update section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the "How to get this update" section of this article.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

You can prevent this issue by removing certain keys related to Image File Execution Options in the Windows registry.  Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, see How to back up and restore the registry in Windows. Modify the Windows registry using the steps below. Open the Windows Registry Editor. Open the Windows start menu and type regedit. Select Registry Editor from the results. Go to the registry location ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution Options. Type this location in the path field that is below the File menu or use the left-side panel of the editor to find that path. Expand this path in the editor. At that location, find the registry key related to the browser that is in use (denoted with a folder icon). Examples of the key name include msedge.exe for Microsoft Edge or chrome.exe. Click the key. Examine the right-side panel that contains values associated with the key. If the right-side panel only includes a value titled “(Default)”, it should be safe to remove the registry key. Right-click the key in the left-side panel of the editor and select Delete. After this, restart the device. This should address the issue, and the browser should open as expected. If the right-side panel contains several values in addition to the one titled “(Default)”, it is still possible to address the issue by removing the registry key for this browser and restarting the device. However, note that doing so might remove configurations associated with the opening or starting process of the browser. We are workingc on a resolution and will provide an update in an upcoming release.

This issue is addressed on the service-side for Windows 11, versions 22H2 and 23H2 on devices with updates released January 9, 2024, or later. Note Managed devices in your environment that have been used or are currently being used in a multimonitor configuration will not yet have Copilot for Windows available.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

This issue is addressed in KB5034763.

You can prevent this issue by removing certain keys related to Image File Execution Options in the Windows registry.  Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, see How to back up and restore the registry in Windows. Modify the Windows registry using the steps below. Open the Windows Registry Editor. Open the Windows start menu and type regedit. Select Registry Editor from the results. Go to the registry location ComputerHKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution Options. Type this location in the path field that is below the File menu or use the left-side panel of the editor to find that path. Expand this path in the editor. At that location, find the registry key related to the browser that is in use (denoted with a folder icon). Examples of the key name include msedge.exe for Microsoft Edge or chrome.exe. Click the key. Examine the right-side panel that contains values associated with the key. If the right-side panel only includes a value titled “(Default)”, it should be safe to remove the registry key. Right-click the key in the left-side panel of the editor and select Delete. After this, restart the device. This should address the issue, and the browser should open as expected. If the right-side panel contains several values in addition to the one titled “(Default)”, it is still possible to address the issue by removing the registry key for this browser and restarting the device. However, note that doing so might remove configurations associated with the opening or starting process of the browser. We are working on a resolution and will provide an update in an upcoming release.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the "How to get this update" section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see the Obtaining Extended Security Updates for eligible Windows devices b;og post. For information on the prerequisites, see the How to get this update section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, see the Obtaining Extended Security Updates for eligible Windows devices blog post. For information on the prerequisites, see the "How to get this update" section of this article.

To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured. We are working on a resolution and will provide an update in an upcoming release.

We are working on a resolution and will provide an update in an upcoming release.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured. We are working on a resolution and will provide an update in an upcoming release.

We are working on a resolution and will provide an update in an upcoming release.

We are working on a resolution and updated media which can be used to install Windows 11, version 23H2 without this issue. We will provide an update in an upcoming release.

This issue is addressed using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the KIR to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the KIR apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be addressed by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration > Administrative Templates >

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the "How to get this update" section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the "How to get this update" section of this article.

Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

When using physical media or disc images (ISO) to install Windows 11, version 23H2 (also referred to as the Windows 11 2023 Update) on a device, Microsoft Narrator might not start. Narrator is commonly initialized using keyboard commands, such as Ctrl + Windows key + Enter. Although Narrator is present in Windows when the installation process begins, it might open in an unresponsive state when initialized using any method. Please note this issue does not occur when Windows 11, version 23H2 is installed using Windows Update on a device which is already running Windows 10 or Windows 11. This issue only occurs when physical media or ISOs are used for this installation and Narrator is only affected while the installation process is taking place. It should continue to work as expected once the installation is completed.

Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured. We are working on a resolution and will provide an update in an upcoming release.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured. We are working on a resolution and will provide an update in an upcoming release.

Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

When using physical media or disc images (ISO) to install Windows 11, version 23H2 (also referred to as the Windows 11 2023 Update) on a device, Microsoft Narrator might not start. Narrator is commonly initialized using keyboard commands, such as Ctrl + Windows key + Enter. Although Narrator is present in Windows when the installation process begins, it might open in an unresponsive state when initialized using any method. Please note this issue does not occur when Windows 11, version 23H2 is installed using Windows Update on a device which is already running Windows 10 or Windows 11. This issue only occurs when physical media or ISOs are used for this installation and Narrator is only affected while the installation process is taking place. It should continue to work as expected once the installation is completed.

To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured. We are working on a resolution and will provide an update in an upcoming release.

To prevent users from encountering this issue, Copilot in Windows (in preview) might not be available on devices that have been used or are currently being used in a multimonitor configuration. We are working on a resolution and will provide an update in an upcoming release.

To access Copilot in Windows, make sure your taskbar is positioned horizontally on the top or bottom of your screen. We are working on a resolution and will provide an update in an upcoming release.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the "How to get this update" section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the How to get this update section of this article.

This is expected in the following circumstances: If you are installing this update on a device that is running an edition that is not supported for ESU. For a complete list of which editions are supported, see KB4497181. If you do not have an ESU MAK add-on key installed and activated. If you have an ESU key and have encountered this issue, please verify you have applied all prerequisites and that your key is activated. For information on activation, please see this blog post. For information on the prerequisites, see the "How to get this update" section of this article.

The color font format for COLRv1 does not render properly. This format enables Windows to display emoji with a 3D-like appearance.

Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured. We are working on a resolution and will provide an update in an upcoming release.

To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured. We are working on a resolution and will provide an update in an upcoming release.

The color font format for COLRv1 does not render properly. This format enables Windows to display emoji with a 3D-like appearance.

Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured. We are working on a resolution and will provide an update in an upcoming release.

Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

Third-party wallpaper apps might not work as expected when Copilot in Windows (in preview) is opened. You might see the default wallpaper or the wallpaper set in Windows instead of your custom wallpaper set in the third-party wallpaper app.

Using the FixedDrivesEncryptionType or SystemDrivesEncryptionType policy settings in the BitLocker configuration service provider (CSP) node in mobile device management (MDM) apps might incorrectly show a 65000 error in the "Require Device Encryption" setting for some devices in your environment. Affected environments are those with the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies set to enabled and selecting either "full encryption" or "used space only". Microsoft Intune is affected by this issue but third-party MDMs might also pe affected. Important This issue is a reporting issue only and does not affect drive encryption or the reporting of other issues on the device, including other BitLocker issues.

To mitigate this issue in Microsoft Intune, you can set the “Enforce drive encryption type on operating system drives” or "Enforce drive encryption on fixed drives" policies to not configured. We are working on a resolution and will provide an update in an upcoming release.

This issue is addressed in KB5032198.