Microsoft Known Issue

Known issues in Microsoft Patches:
 
Microsoft often releases patches to address security and reliability issues. Sometimes, patches itself will introduce unprecedented issues after installing them. Here's the updated list of all the known issues in Microsoft patches and possible workaround for them.

Oops! No results for your search.

workaround
Feb 14, 2024
KB5034833
2024-02 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5034833)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Feb 14, 2024
KB5034795
2024-02 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5034795)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Feb 14, 2024
KB5034763
2024-02 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5034763)
"Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview)."
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.
workaround
Feb 14, 2024
KB5034763
2024-02 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5034763)
"Copilot in Windows (in preview) is not currently supported when your taskbar is located vertically on the right or left of your screen."
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.
workaround
Feb 14, 2024
KB5034770
2024-02 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5034770)
"After you install KB5034129, chromium-based internet browsers, such as Microsoft Edge, might not open correctly. Browsers affected by this issue might display a white screen and become unresponsive when you open them.  Devices that have browser specific Image File Execution Options (IFEO) might be affected by this issue. When an entry for Microsoft Edge (msedge.exe) or other chromium-based browsers is found in the Windows registry, the issue might occur. A registry "
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.
workaround
Feb 14, 2024
KB5034204
2024-01 Cumulative Update Preview for Windows 11 Version 22H2 for arm64-based Systems (KB5034204)
"Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview)."
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.
workaround
Feb 14, 2024
KB5034203
2024-01 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5034203)
"Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview)."
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.
workaround
Feb 14, 2024
KB5034203
2024-01 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5034203)
"Copilot in Windows (in preview) is not currently supported when your taskbar is located vertically on the right or left of your screen."
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.
workaround
Feb 14, 2024
KB5034203
2024-01 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5034203)
"Some eligible Windows 10 might receive a 0xd0000034 error when attempting to upgrade to Windows 11 from Windows Update. Note This issue should not affect the ability to continue to use Windows devices with Windows 10."
This issue is addressed in KB5034763.
workaround
Feb 14, 2024
KB5034129
2024-01 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5034129)
"After you install KB5034129, chromium-based internet browsers, such as Microsoft Edge, might not open correctly. Browsers affected by this issue might display a white screen and become unresponsive when you open them.  Devices that have browser specific Image File Execution Options (IFEO) might be affected by this issue. When an entry for Microsoft Edge (msedge.exe) or other chromium-based browsers is found in the Windows registry, the issue might occur. A registry "
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.
workaround
Jan 10, 2024
KB5034167
2024-01 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5034167) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History."
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.
workaround
Jan 10, 2024
KB5034176
2024-01 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5034176) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Jan 10, 2024
KB5034169
2024-01 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5034169) (ESU)
"After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History."
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.
workaround
Jan 10, 2024
KB5034173
2024-01 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5034173) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Jan 10, 2024
KB5034123
2024-01 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5034123)
"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.
workaround
Jan 10, 2024
KB5034123
2024-01 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5034123)
"The color font format for COLRv1 does not render properly. This format enables Windows to display emoji with a 3D-like appearance."
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jan 10, 2024
KB5034121
2024-01 Cumulative Update for Windows 11 for ARM64-based Systems (KB5034121)
"Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview)."
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.
workaround
Jan 10, 2024
KB5034122
2024-01 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5034122)
"Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview)."
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.
workaround
Jan 10, 2024
KB5034122
2024-01 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5034122)
"Copilot in Windows (in preview) is not currently supported when your taskbar is located vertically on the right or left of your screen."
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.
workaround
Jan 10, 2024
KB5034122
2024-01 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5034122)
"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 an"
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.
workaround
Dec 20, 2023
KB5033375
2023-12 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5033375)
"The color font format for COLRv1 does not render properly. This format enables Windows to display emoji with a 3D-like appearance. "
We are working on a resolution and will provide an update in an upcoming release.
workaround
Dec 20, 2023
KB5033375
2023-12 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5033375)
"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."
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.
workaround
Dec 20, 2023
KB5033375
2023-12 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5033375)
"Microsoft has received reports of an issue in which some Wi-Fi adapters might not connect to some networks?after installing this update. We have confirmed this issue was caused by this update and KB5033375. As reported, you are more likely to be affected by this issue if you are attempting to connect to an enterprise, education, or public Wi-Fi network using 802.1x authentication. This issue is not likely to occur on home networks."
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 >
workaround
Dec 13, 2023
KB5033424
2023-12 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5033424)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History."
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.
workaround
Dec 13, 2023
KB5033427
2023-12 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5033427)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Dec 13, 2023
KB5033433
2023-12 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5033433)
"After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History."
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.
workaround
Dec 13, 2023
KB5033422
2023-12 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5033422)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Dec 13, 2023
KB5033375
2023-12 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5033375)
"IT admins"
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.
workaround
Dec 13, 2023
KB5033375
2023-12 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5033375)
"All users"
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.
workaround
Dec 13, 2023
KB5033369
2023-12 Cumulative Update for Windows 11 for ARM64-based Systems (KB5033369)
"IT admins"
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.
workaround
Dec 13, 2023
KB5033372
2023-12 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5033372)
"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 an"
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.
workaround
Dec 13, 2023
KB5033372
2023-12 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5033372)
"Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview)."
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.
workaround
Dec 13, 2023
KB5033372
2023-12 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5033372)
"Copilot in Windows (in preview) is not currently supported when your taskbar is located vertically on the right or left of your screen."
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.
workaround
Dec 13, 2023
KB5033371
2023-12 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5033371)
"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 an"
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.
workaround
Dec 13, 2023
KB5032288
2023-11 Cumulative Update Preview for Windows 11 Version 22H2 for arm64-based Systems (KB5032288)
"IT admins"
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.
workaround
Dec 13, 2023
KB5032288
2023-11 Cumulative Update Preview for Windows 11 Version 22H2 for arm64-based Systems (KB5032288)
"All users"
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.
workaround
Dec 13, 2023
KB5032278
2023-11 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5032278)
"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 an"
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.
workaround
Dec 13, 2023
KB5032278
2023-11 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5032278)
"Windows devices using more than one (1) monitor might experience issues with desktop icons moving unexpectedly between monitors or other icon alignment issues when attempting to use Copilot in Windows (in preview)."
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.
workaround
Dec 13, 2023
KB5032278
2023-11 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5032278)
"Copilot in Windows (in preview) is not currently supported when your taskbar is located vertically on the right or left of your screen."
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.
workaround
Nov 15, 2023
KB5032250
2023-11 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5032250) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History."
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.
workaround
Nov 15, 2023
KB5032248
2023-11 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5032248) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Nov 15, 2023
KB5032252
2023-11 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5032252) (ESU)
"After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History."
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.
workaround
Nov 15, 2023
KB5032254
2023-11 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5032254) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Nov 15, 2023
KB5032190
2023-11 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5032190)
"All users"
The color font format for COLRv1 does not render properly. This format enables Windows to display emoji with a 3D-like appearance.
workaround
Nov 15, 2023
KB5032190
2023-11 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5032190)
"IT admins"
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.
workaround
Nov 15, 2023
KB5032192
2023-11 Cumulative Update for Windows 11 for ARM64-based Systems (KB5032192)
"IT admins"
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.
workaround
Nov 15, 2023
KB5032189
2023-11 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5032189)
"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 an"
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.
workaround
Nov 15, 2023
KB5032196
2023-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5032196)
"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 an"
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.
workaround
Nov 15, 2023
KB5031455
2023-10 Cumulative Update Preview for Windows 11 Version 22H2 for arm64-based Systems (KB5031455)
"All users"
The color font format for COLRv1 does not render properly. This format enables Windows to display emoji with a 3D-like appearance.
workaround
Nov 15, 2023
KB5031455
2023-10 Cumulative Update Preview for Windows 11 Version 22H2 for arm64-based Systems (KB5031455)
"IT admins"
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.
workaround
Nov 15, 2023
KB5031445
2023-10 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5031445)
"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 an"
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.
workaround
Nov 15, 2023
KB5031354
2023-10 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5031354) (CVE-2023-36563) (CVE-2023-44487)
"IT admins"
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.
workaround
Nov 15, 2023
KB5031354
2023-10 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5031354) (CVE-2023-36563) (CVE-2023-44487)
"All users"
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.
workaround
Nov 15, 2023
KB5031358
2023-10 Cumulative Update for Windows 11 for ARM64-based Systems (KB5031358) (CVE-2023-36563) (CVE-2023-44487)
"IT admins"
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.
workaround
Nov 15, 2023
KB5031361
2023-10 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5031361) (CVE-2023-36563) (CVE-2023-44487)
"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 an"
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.
workaround
Nov 15, 2023
KB5031364
2023-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5031364) (CVE-2023-36563) (CVE-2023-44487)
"After installing this update on virtual machines (VMs) running on VMware ESXi hosts, Windows 2022 might fail to start up. Affected VMs will receive an error with a blue screen and Stop code : PNP DETECTED FATAL ERROR. This issue only affects guest VMs with the following configuration on VMware ESXi hosts only: AMD Epyc physical processor "Expose IOMMU to guest OS" enabled in VMware settings for the VM. “Enable Virtualization Based Security” enabled in Windows Server"
This issue is addressed in KB5032198. 
workaround
Oct 11, 2023
KB5031356
2023-10 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5031356)
"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."
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.
workaround
Oct 11, 2023
KB5031356
2023-10 Cumulative Update for Windows 10 Version 22H2 for x64-based Systems (KB5031356)
"This update might not be installed successfully. Devices might initially display progress, but then not finish the installation. A common error code encountered with this issue is Error 8007000D (ERROR_INVALID_DATA). This error can be found in Update History."
This issue is resolved by using Known Issue Rollback (KIR). Please realize that it might require up to 48 hours for the resolution to propagate automatically to consumer devices and unmanaged business devices.
workaround
Oct 11, 2023
KB5031441
2023-10 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5031441)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History."
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.
workaround
Oct 11, 2023
KB5031411
2023-10 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5031411)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Oct 11, 2023
KB5031408
2023-10 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5031408)
"After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History."
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.
workaround
Oct 11, 2023
KB5031416
2023-10 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5031416)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Oct 11, 2023
KB5031364
2023-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5031364)
"After installing this update on guest virtual machines (VMs) running Windows Server 2022 on some versions of VMware ESXi, Windows Server 2022 might not start up. Only Windows Server 2022 VMs with Secure Boot enabled are affected by this issue. Affected versions of VMware ESXi are versions vSphere ESXi 7.0.x and below."
Please see VMware’s documentation to mitigate this issue. Microsoft and VMware are investigating this issue and will provide more information when it is available.
workaround
Oct 11, 2023
KB5030211
2023-09 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5030211) (CVE-2023-36802)
"After installing this update, apps that you used ClickOnce to deploy might begin to prompt for installation even when the ClickOnce apps are already installed and marked as “trusted”."
This issue is addressed in KB5030300. If you cannot install this KB, see the information below. This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can be resolved by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration ->Administrative Templates ->. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. Group Policy downloads with Group Policy name: Download for Windows 10, version 21H2- Windows 10 20H2, 21H1, 21H2 and 22H2 KB5028244 230814_03351 Known Issue Rollback Download for Windows 10, version 22H2- Windows 10 20H2, 21H1, 21H2 and 22H2 KB5028244 230814_03351 Known Issue Rollback Important You will need to install and configure the Group Policy for your version of Windows to resolve this issue.
workaround
Oct 11, 2023
KB5029244
2023-08 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5029244)
"After installing this update, apps that you used ClickOnce to deploy might begin to prompt for installation even when the ClickOnce apps are already installed and marked as “trusted”."
This issue is addressed in KB5030300. If you cannot install this KB, see the information below. This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can be resolved by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration ->Administrative Templates ->. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. Group Policy downloads with Group Policy name: Download for Windows 10, version 21H2- Windows 10 20H2, 21H1, 21H2 and 22H2 KB5028244 230814_03351 Known Issue Rollback Download for Windows 10, version 22H2- Windows 10 20H2, 21H1, 21H2 and 22H2 KB5028244 230814_03351 Known Issue Rollback Important You will need to install and configure the Group Policy for your version of Windows to resolve this issue.
workaround
Oct 11, 2023
KB5028244
2023-07 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5028244)
"After installing this update, apps that you used ClickOnce to deploy might begin to prompt for installation even when the ClickOnce apps are already installed and marked as “trusted”."
This issue is addressed in KB5030300. If you cannot install this KB, see the information below. This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can be resolved by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration ->Administrative Templates ->. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. Group Policy downloads with Group Policy name: Download for Windows 10, version 22H2- Windows 10 20H2, 21H1, 21H2 and 22H2 KB5028244 230814_03351 Known Issue Rollback Important You will need to install and configure the Group Policy for your version of Windows to resolve this issue.
workaround
Oct 11, 2023
KB5029331
2023-08 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5029331)
"After installing this update, apps that you used ClickOnce to deploy might begin to prompt for installation even when the ClickOnce apps are already installed and marked as “trusted”."
This issue is addressed in KB5030300. If you cannot install this KB, see the information below. This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster.
workaround
Sept 13, 2023
KB5028946
KB5029648, KB5029649, 2023-08 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 10 Version 21H2 for x64 (KB5028946)
"Windows 11, version 22H2"
After installing windows KB5028244, applications which were deployed using ClickOnce might begin to prompt for installation even when the ClickOnce apps are already installed and marked as “trusted”.
workaround
Sept 13, 2023
KB5028946
KB5029648, KB5029649, 2023-08 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 10 Version 21H2 for x64 (KB5028946)
"Windows 11, version 21H2"
After installing windows KB5029244, applications which were deployed using ClickOnce might begin to prompt for installation even when the ClickOnce apps are already installed and marked as “trusted”.
workaround
Sept 13, 2023
KB5028951
KB5029648, KB5029649, 2023-08 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H2 for x64 (KB5028951)
"Windows 11, version 22H2"
After installing windows KB5028244, applications which were deployed using ClickOnce might begin to prompt for installation even when the ClickOnce apps are already installed and marked as “trusted”.
workaround
Sept 13, 2023
KB5028951
KB5029648, KB5029649, 2023-08 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 21H2 for x64 (KB5028951)
"Windows 11, version 21H2"
After installing windows KB5029244, applications which were deployed using ClickOnce might begin to prompt for installation even when the ClickOnce apps are already installed and marked as “trusted”.
workaround
Sept 13, 2023
KB5030261
2023-09 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5030261) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History."
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.
workaround
Sept 13, 2023
KB5030286
2023-09 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5030286) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Sept 13, 2023
KB5030265
2023-09 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5030265) (ESU)
"After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History."
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.
workaround
Sept 13, 2023
KB5030271
2023-09 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5030271) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Sept 13, 2023
KB5030216
2023-09 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5030216)
"After installing this update on guest virtual machines (VMs) running Windows Server 2022 on some versions of VMware ESXi, Windows Server 2022 might not start up. Only Windows Server 2022 VMs with Secure Boot enabled are affected by this issue. Affected versions of VMware ESXi are versions vSphere ESXi 7.0.x and below."
Please see VMware’s documentation to mitigate this issue. Microsoft and VMware are investigating this issue and will provide more information when it is available.
workaround
Sept 13, 2023
KB5029351
2023-08 Cumulative Update Preview for Windows 11 Version 22H2 for arm64-based Systems (KB5029351)
"All users"
Microsoft has received reports of an issue in which users are receiving an “UNSUPPORTED_PROCESSOR” error message on a blue screen after installing updates released on August 22, 2023 and then restarting their device. This update might automatically uninstall to allow Windows to start up as expected. If you are experiencing issues, please use Feedback Hub to file a report following the below steps: Open Feedback Hub by opening the Start menu and typing "Feedback hub", or pressing the Windows key + F Fill in the "Summarize your feedback" and "Explain in more detail" boxes, then click Next. Under the "Choose a category" section, click the "Problem" button, and select "Install and Update" category. Then select "Downloading, installing, and configuring Windows Update” subcategory. Click Next. Under the "Find similar feedback" section, select the "Make new bug" radio button and click Next. Under the "Add more details" section, supply any relevant detail (Note this is not critical to addressing your issue). Expand the "Recreate my problem" box and press "Start recording". Reproduce the issue on your device. Press "Stop recording" once finished. Click the "Submit" button. For additional information, see Send feedback to Microsoft with the Feedback Hub app.
workaround
Sept 13, 2023
KB5029332
2023-08 Cumulative Update Preview for Windows 11 for ARM64-based Systems (KB5029332)
"All users"
Microsoft has received reports of an issue in which users are receiving an “UNSUPPORTED_PROCESSOR” error message on a blue screen after installing updates released on August 22, 2023 and then restarting their device. This update might automatically uninstall to allow Windows to start up as expected. If you are experiencing issues, please use Feedback Hub to file a report following the below steps: Open Feedback Hub by opening the Start menu and typing "Feedback hub", or pressing the Windows key + F Fill in the "Summarize your feedback" and "Explain in more detail" boxes, then click Next. Under the "Choose a category" section, click the "Problem" button, and select "Install and Update" category. Then select "Downloading, installing, and configuring Windows Update” subcategory. Click Next. Under the "Find similar feedback" section, select the "Make new bug" radio button and click Next. Under the "Add more details" section, supply any relevant detail (Note this is not critical to addressing your issue). Expand the "Recreate my problem" box and press "Start recording". Reproduce the issue on your device. Press "Stop recording" once finished. Click the "Submit" button. For additional information, see Send feedback to Microsoft with the Feedback Hub app.
workaround
Sept 13, 2023
KB5029331
2023-08 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5029331)
"Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. Note Devices that connect dire"
To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the SSU: Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cabExtract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:*You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU. If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business.
workaround
Sept 13, 2023
KB5029331
2023-08 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5029331)
"Microsoft has received reports of an issue in which users are receiving an “UNSUPPORTED_PROCESSOR” error message on a blue screen after installing updates released on August 22, 2023 and then restarting their device. This update might automatically uninstall to allow Windows to start up as expected. If you are experiencing issues, please use Feedback Hub to file a report following the below steps: Open Feedback Hub by opening the Start menu and typing "Feedback hub""
After investigating these reports, we have found that the “UNSUPPORTED_PROCESSOR” error was not caused by issues in this update and is limited to a specific subset of processors. For more information, see 13th Gen Intel® Core™ Processor Families with Performance Hybrid Architecture Blue Screen Hang Issue with Windows* Preview Updates. This issue will not affect future monthly updates released for Windows. This update will not be offered to Windows devices that might be affected by this issue and we recommend that you do not attempt to manually install it on affected devices.
workaround
Aug 9, 2023
KB5029307
2023-08 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5029307)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History."
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.
workaround
Aug 9, 2023
KB5029301
2023-08 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5029301)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Aug 9, 2023
KB5029296
2023-08 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5029296)
"After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History."
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.
workaround
Aug 9, 2023
KB5029318
2023-08 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5029318)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Aug 9, 2023
KB5029263
2023-08 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5029263)
"IT admins"
Using provisioning packages on Windows 11, version 22H2 (also called Windows 11 2022 Update) might not work as expected. Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart unexpectedly. Provisioning packages are .PPKG files which are used to help configure new devices for use on business or school networks. Provisioning packages which are applied during initial setup are most likely to be impacted by this issue. For more information on provisioning packages, please see Provisioning packages for Windows. Note Provisioning Windows devices using Windows Autopilot is not affected by this issue. Windows devices used by consumers in their home or small offices are not likely to be affected by this issue.
workaround
Aug 9, 2023
KB5029244
2023-08 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5029244)
"Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. Note Devices that connect dire"
To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the SSU: Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cabExtract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:*You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU. If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business.
workaround
Aug 9, 2023
KB5029247
2023-08 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5029247)
"After installing KB5001342 or later, the Cluster Service might fail to start because a Cluster Network Driver is not found."
This issue occurs because of an update to the PnP class drivers used by this service.  After about 20 minutes, you should be able to restart your device and not encounter this issue. For more information about the specific errors, cause, and workaround for this issue, please see KB5003571.
workaround
Aug 9, 2023
KB5029250
2023-08 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5029250)
"After installing this update on guest virtual machines (VMs) running Windows Server 2022 on some versions of VMware ESXi, Windows Server 2022 might not start up. Only Windows Server 2022 VMs with Secure Boot enabled are affected by this issue. Affected versions of VMware ESXi are versions vSphere ESXi 7.0.x and below."
Please see VMware’s documentation to mitigate this issue. Microsoft and VMware are investigating this issue and will provide more information when it is available.
workaround
Aug 9, 2023
KB5028254
2023-07 Cumulative Update Preview for Windows 11 Version 22H2 for arm64-based Systems (KB5028254)
"IT admins"
Using provisioning packages on Windows 11, version 22H2 (also called Windows 11 2022 Update) might not work as expected. Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart unexpectedly. Provisioning packages are .PPKG files which are used to help configure new devices for use on business or school networks. Provisioning packages which are applied during initial setup are most likely to be impacted by this issue. For more information on provisioning packages, please see Provisioning packages for Windows. Note Provisioning Windows devices using Windows Autopilot is not affected by this issue. Windows devices used by consumers in their home or small offices are not likely to be affected by this issue.
workaround
Aug 9, 2023
KB5028244
2023-07 Cumulative Update Preview for Windows 10 Version 22H2 for x64-based Systems (KB5028244)
"Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. Note Devices that connect dire"
To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the SSU: Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cabExtract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:*You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU. If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business.
workaround
Jul 11, 2023
KB5028224
2023-07 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5028224) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History."
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.
workaround
Jul 11, 2023
KB5028226
2023-07 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5028226) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Jul 11, 2023
KB5028240
2023-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5028240) (ESU)
"After installing this update and restarting your device, you might receive the error, "Failure to configure Windows updates. Reverting Changes. Do not turn off your computer", and the update might show as Failed in Update History."
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.
workaround
Jul 11, 2023
KB5028222
2023-07 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5028222) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer”, and the update might show as Failed in Update History."
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.
workaround
Jul 11, 2023
KB5028185
2023-07 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5028185)
"IT admins"
Using provisioning packages on Windows 11, version 22H2 (also called Windows 11 2022 Update) might not work as expected. Windows might only be partially configured, and the Out Of Box Experience might not finish or might restart unexpectedly. Provisioning packages are .PPKG files which are used to help configure new devices for use on business or school networks. Provisioning packages which are applied during initial setup are most likely to be impacted by this issue. For more information on provisioning packages, please see Provisioning packages for Windows. Note Provisioning Windows devices using Windows Autopilot is not affected by this issue. Windows devices used by consumers in their home or small offices are not likely to be affected by this issue.
workaround
Jul 11, 2023
KB5028182
2023-07 Cumulative Update for Windows 11 for ARM64-based Systems (KB5028182)
"All users"
After installing this or later updates, Windows devices with some third-party UI customization apps might not start up. These third-party apps might cause errors with explorer.exe that might repeat multiple times in a loop. The known affected third-party UI customization apps are ExplorerPatcher and StartAllBack. These types of apps often use unsupported methods to achieve their customization and as a result can have unintended results on your Windows device.
workaround
Jul 11, 2023
KB5028166
2023-07 Cumulative Update for Windows 10 Version 21H2 for x64-based Systems (KB5028166)
"Devices with Windows installations created from custom offline media or custom ISO image might have Microsoft Edge Legacy removed by this update, but not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipstreaming this update into the image without having first installed the standalone servicing stack update (SSU) released March 29, 2021 or later. Note Devices that connect dire"
To avoid this issue, be sure to first slipstream the SSU released March 29, 2021 or later into the custom offline media or ISO image before slipstreaming the LCU. To do this with the combined SSU and LCU packages now used for Windows 10, version 20H2 and Windows 10, version 2004, you will need to extract the SSU from the combined package. Use the following steps to extract the SSU: Extract the cab from the msu via this command line (using the package for KB5000842 as an example): expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cabExtract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:*You will then have the SSU cab, in this example named SSU-19041.903-x64.cab. Slipstream this file into your offline image first, then the LCU. If you have already encountered this issue by installing the OS using affected custom media, you can mitigate it by directly installing the new Microsoft Edge. If you need to broadly deploy the new Microsoft Edge for business, see Download and deploy Microsoft Edge for business.
workaround
Jul 11, 2023
KB5028168
2023-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5028168)
"After installing KB5001342 or later, the Cluster Service might fail to start because a Cluster Network Driver is not found."
This issue occurs because of an update to the PnP class drivers used by this service.  After about 20 minutes, you should be able to restart your device and not encounter this issue. For more information about the specific errors, cause, and workaround for this issue, please see KB5003571.
workaround
Jul 11, 2023
KB5028171
2023-07 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5028171)
""
 
workaround
Jul 11, 2023
KB5028171
2023-07 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5028171)
"After installing this update on guest virtual machines (VMs) running Windows Server 2022 on some versions of VMware ESXi, Windows Server 2022 might not start up. Only Windows Server 2022 VMs with Secure Boot enabled are affected by this issue. Affected versions of VMware ESXi are versions vSphere ESXi 7.0.x and below."
Please see VMware’s documentation to mitigate this issue. Microsoft and VMware are investigating this issue and will provide more information when it is available.
workaround
May 9, 2023
KB5026426
2023-05 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5026426) (ESU)
"After installing this update and restarting your device, you might receive the error, “Failure to configure Windows updates. Reverting Changes. Do not turn off your computer,” and the update might show as Failed in Update History."
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.

Disclaimer:This webpage is intended to provide you information about patch announcement for certain specific software products. The information is provided "As Is" without warranty of any kind. The links provided point to pages on the vendors websites. You can get more information by clicking the links to visit the relevant pages on the vendors website.