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
Jan 12, 2022
KB5009595
2022-01 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5009595) (CVE-2022-21919) (CVE-2022-21836)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5009619
2022-01 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5009619) (CVE-2022-21919) (CVE-2022-21836)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5009621
2022-01 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5009621) (ESU) (CVE-2022-21919) (CVE-2022-21836)
"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 purchased 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 12, 2022
KB5009621
2022-01 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5009621) (ESU) (CVE-2022-21919) (CVE-2022-21836)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5009601
2022-01 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5009601) (ESU) (CVE-2022-21919) (CVE-2022-21836)
"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 purchased 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 12, 2022
KB5009601
2022-01 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5009601) (ESU) (CVE-2022-21919) (CVE-2022-21836)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5009624
2022-01 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5009624) (CVE-2022-21919) (CVE-2022-21836)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5009586
2022-01 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5009586) (CVE-2022-21919) (CVE-2022-21836)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5009610
2022-01 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5009610) (ESU) (CVE-2022-21919) (CVE-2022-21836)
"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 purchased 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 12, 2022
KB5009610
2022-01 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5009610) (ESU) (CVE-2022-21919) (CVE-2022-21836)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5009627
2022-01 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5009627) (ESU) (CVE-2022-21919) (CVE-2022-21836)
"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 purchased 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 12, 2022
KB5009627
2022-01 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5009627) (ESU) (CVE-2022-21919) (CVE-2022-21836)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5010197
2022-01 Cumulative Update Preview for Microsoft server operating system version 21H2 for x64-based Systems (KB5010197)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Server 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Jan 12, 2022
KB5010197
2022-01 Cumulative Update Preview for Microsoft server operating system version 21H2 for x64-based Systems (KB5010197)
"After installing this update, text input using a Japanese IME might be entered out of order or the text cursor might move unexpectedly in apps that use the multibyte character set (MBCS). This issue affects both the Microsoft Japanese IME and third-party Japanese IMEs."
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, it can be resolved by installing and configuring a special Group Policy (preferred). Important Verify that you are using the correct Group Policy for your version of Windows: Windows Sever 2022.
workaround
Jan 12, 2022
KB5009566
2022-01 Cumulative Update for Windows 11 for x64-based Systems (KB5009566) (CVE-2021-22947) (CVE-2021-22947) (CVE-2022-21919) (CVE-2022-21836) (CVE-2022-21874)
"All users"
After installing Windows 11, some image editing programs might not render colors correctly on certain high dynamic range (HDR) displays. This is frequently observed with white colors, which could display in bright yellow or other colors. This issue occurs when certain color-rendering Win32 APIs return unexpected information or errors under specific conditions. Not all color profile management programs are affected, and color profile options available in the Windows 11 Settings page, including Microsoft Color Control Panel, are expected to function correctly.
workaround
Jan 12, 2022
KB5009543
2022-01 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems (KB5009543) (CVE-2021-22947) (CVE-2021-22947) (CVE-2022-21919) (CVE-2022-21836) (CVE-2022-21874)
"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 using 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
Jan 12, 2022
KB5009543
2022-01 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems (KB5009543) (CVE-2021-22947) (CVE-2021-22947) (CVE-2022-21919) (CVE-2022-21836) (CVE-2022-21874)
"After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING"."
For more information and a workaround, see KB5005322.
workaround
Jan 12, 2022
KB5009543
2022-01 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems (KB5009543) (CVE-2021-22947) (CVE-2021-22947) (CVE-2022-21919) (CVE-2022-21836) (CVE-2022-21874)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Server 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Jan 12, 2022
KB5010196
2022-01 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5010196)
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5010196
2022-01 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5010196)
"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
Jan 12, 2022
KB5010196
2022-01 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5010196)
"After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note This does not affect activation of any other version or edition of Windows. Client devices "
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5009557
2022-01 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5009557) (CVE-2021-22947) (CVE-2021-22947) (CVE-2022-21919) (CVE-2022-21836) (CVE-2022-21839) (CVE-2022-21874)
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5009557
2022-01 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5009557) (CVE-2021-22947) (CVE-2021-22947) (CVE-2022-21919) (CVE-2022-21836) (CVE-2022-21839) (CVE-2022-21874)
"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
Jan 12, 2022
KB5009557
2022-01 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5009557) (CVE-2021-22947) (CVE-2021-22947) (CVE-2022-21919) (CVE-2022-21836) (CVE-2022-21839) (CVE-2022-21874)
"After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note This does not affect activation of any other version or edition of Windows. Client devices "
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5010195
2022-01 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5010195)
"After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note This does not affect activation of any other version or edition of Windows. Client devices "
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5009546
2022-01 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5009546) (CVE-2022-21919) (CVE-2022-21836) (CVE-2022-21874)
"After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note This does not affect activation of any other version or edition of Windows. Client devices "
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jan 12, 2022
KB5009555
2022-01 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5009555) (CVE-2021-22947) (CVE-2021-22947) (CVE-2022-21919) (CVE-2022-21836) (CVE-2022-21874)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Server 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Dec 15, 2021
KB5008285
2021-12 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5008285) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008255
2021-12 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5008255) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008282
2021-12 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5008282) (ESU) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"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 purchased 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 15, 2021
KB5008282
2021-12 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5008282) (ESU) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008271
2021-12 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5008271) (ESU) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"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 purchased 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 15, 2021
KB5008271
2021-12 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5008271) (ESU) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008263
2021-12 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5008263) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008277
2021-12 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5008277) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008244
2021-12 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5008244) (ESU) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"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 purchased 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 15, 2021
KB5008244
2021-12 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5008244) (ESU) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008274
2021-12 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5008274) (ESU) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"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 purchased 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 15, 2021
KB5008274
2021-12 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5008274) (ESU) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008212
2021-12 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5008212) (CVE-2021-43240) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"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 using 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
Dec 15, 2021
KB5008212
2021-12 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5008212) (CVE-2021-43240) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING"."
For more information and a workaround, see KB5005322.
workaround
Dec 15, 2021
KB5008212
2021-12 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5008212) (CVE-2021-43240) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Server 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Dec 15, 2021
KB5008218
2021-12 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5008218) (CVE-2021-43883) (CVE-2021-43893)
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008218
2021-12 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5008218) (CVE-2021-43883) (CVE-2021-43893)
"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
Dec 15, 2021
KB5008218
2021-12 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5008218) (CVE-2021-43883) (CVE-2021-43893)
"After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note This does not affect activation of any other version or edition of Windows. Client devices "
We are working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008207
2021-12 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5008207) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note This does not affect activation of any other version or edition of Windows. Client devices "
We are working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008223
2021-12 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5008223) (CVE-2021-43240) (CVE-2021-41333) (CVE-2021-43883) (CVE-2021-43893)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Server 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Dec 15, 2021
KB5007253
2021-11 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5007253)
"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 using 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
Dec 15, 2021
KB5007253
2021-11 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5007253)
"After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING"."
For more information and a workaround, see KB5005322.
workaround
Dec 15, 2021
KB5007253
2021-11 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5007253)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Server 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Dec 15, 2021
KB5007266
2021-11 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5007266)
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5007266
2021-11 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5007266)
"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
Dec 15, 2021
KB5007266
2021-11 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5007266)
"After installing this or later updates, Microsoft Defender for Endpoint might fail to start or run on devices with a Windows Server Core installation. Note This issue does not affect Microsoft Defender for Endpoint on Windows 10."
This issue is resolved in KB5008218.
workaround
Dec 15, 2021
KB5007266
2021-11 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5007266)
"After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note This does not affect activation of any other version or edition of Windows. Client devices "
We are working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5007254
2021-11 Cumulative Update Preview for Microsoft server operating system version 21H2 for x64-based Systems (KB5007254)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Server 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Dec 15, 2021
KB5007254
2021-11 Cumulative Update Preview for Microsoft server operating system version 21H2 for x64-based Systems (KB5007254)
"After installing this or later updates, Microsoft Defender for Endpoint might fail to start or run on devices with a Windows Server Core installation. Note This issue does not affect Microsoft Defender for Endpoint on Windows 10."
This issue is resolved in KB5008223.
workaround
Dec 15, 2021
KB5008602
2021-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5008602)
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008602
2021-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5008602)
"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
Dec 15, 2021
KB5008602
2021-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5008602)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
This issue is resolved in KB5007266.
workaround
Dec 15, 2021
KB5008602
2021-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5008602)
"After installing this update, Microsoft Installer (MSI) might have issues repairing or updating apps. Apps that are known to be affected include some apps from Kaspersky. Affected apps might fail to open after an update or repair has been attempted."
This issue is resolved in KB5007266.
workaround
Dec 15, 2021
KB5008602
2021-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5008602)
"After installing this or later updates, Microsoft Defender for Endpoint might fail to start or run on devices with a Windows Server Core installation. Note This issue does not affect Microsoft Defender for Endpoint on Windows 10."
This issue is resolved in KB5008218.
workaround
Dec 15, 2021
KB5008602
2021-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5008602)
"After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note This does not affect activation of any other version or edition of Windows. Client devices "
We are working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008601
2021-11 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5008601)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008601
2021-11 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5008601)
"After installing this update, Microsoft Installer (MSI) might have issues repairing or updating apps. Apps that are known to be affected include some apps from Kaspersky. Affected apps might fail to open after an update or repair has been attempted."
To mitigate this issue, you will need to uninstall the affected app, then install the latest version of the app. We are working on a resolution and will provide an update in an upcoming release.
workaround
Dec 15, 2021
KB5008601
2021-11 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5008601)
"After installing updates released April 22, 2021 or later, an issue occurs that affects versions of Windows Server that are in use as a Key Management Services (KMS) host. Client devices running Windows 10 Enterprise LTSC 2019 and Windows 10 Enterprise LTSC 2016 might fail to activate. This issue only occurs when using a new Customer Support Volume License Key (CSVLK). Note This does not affect activation of any other version or edition of Windows. Client devices "
We are working on a resolution and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5006674
2021-10 Cumulative Update for Windows 11 for x64-based Systems (KB5006674) (CVE-2021-40449)
"Devices which attempt to connect to a network printer for the first time might fail to download and install the necessary printer drivers. This issue has been observed in devices which access printers via a print server, using HTTP connections. When a client connects to the server to install the printer, a directory mismatch occurs, which causes the installer files to generate incorrectly. As a result, the drivers may not download. Note: The printer connection metho"
This issue is resolved in KB5006746.
workaround
Nov 10, 2021
KB5006674
2021-10 Cumulative Update for Windows 11 for x64-based Systems (KB5006674) (CVE-2021-40449)
"Installation of printers using Internet Printing Protocol (IPP) might not complete successfully. Note IPP is not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations."
This issue is resolved in KB5006746.
workaround
Nov 10, 2021
KB5006674
2021-10 Cumulative Update for Windows 11 for x64-based Systems (KB5006674) (CVE-2021-40449)
"Printing properties defined on a server might not be correctly provided to clients. Note this issue is specific to print servers and does not impact standard network printing. This issue will not cause printing operations to fail, however, custom settings defined on the server – for example, duplex print settings – will not be applied automatically, and clients will print with default settings only. This issue results from an improper building of the data file which"
This issue is resolved in KB5006746.
workaround
Nov 10, 2021
KB5006674
2021-10 Cumulative Update for Windows 11 for x64-based Systems (KB5006674) (CVE-2021-40449)
"You might receive a prompt for administrative credentials every time you attempt to print in environments in which the print server and print client are in different times zones. Note The affected environments described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations."
This issue is resolved in KB5006746.
workaround
Nov 10, 2021
KB5006674
2021-10 Cumulative Update for Windows 11 for x64-based Systems (KB5006674) (CVE-2021-40449)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5006675
2021-10 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB5006675) (CVE-2021-40449) (CVE-2021-41335) (CVE-2021-41338)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5006699
2021-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5006699) (CVE-2021-40449) (CVE-2021-40469)
"After installing KB5005575, installation of printers using Internet Printing Protocol (IPP) might not complete successfully. Devices which had connected to and installed the printer prior to the installation of KB5005575 are unaffected and print operations to that printer will succeed as usual. Note IPP is not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations."
This issue is resolved in KB5006745.
workaround
Nov 10, 2021
KB5006699
2021-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5006699) (CVE-2021-40449) (CVE-2021-40469)
"After installing KB5005619 on a print server, printing properties defined on that server might not be correctly provided to clients. Note this issue is specific to print servers and does not impact standard network printing. This issue will not cause printing operations to fail, however, custom settings defined on the server – for example, duplex print settings – will not be applied automatically, and clients will print with default settings only. This issue results"
This issue is resolved in KB5006745.
workaround
Nov 10, 2021
KB5006699
2021-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5006699) (CVE-2021-40449) (CVE-2021-40469)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Sever 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Nov 10, 2021
KB5006699
2021-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5006699) (CVE-2021-40449) (CVE-2021-40469)
"You might receive a prompt for administrative credentials every time you attempt to print in environments in which the print server and print client are in different times zones. Note The affected environments described in this issue are not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations."
This issue is resolved in KB5006745.
workaround
Nov 10, 2021
KB5006699
2021-10 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5006699) (CVE-2021-40449) (CVE-2021-40469)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5006667
2021-10 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5006667) (CVE-2021-40449) (CVE-2021-41335) (CVE-2021-41338)
"After installing KB5005566, installation of printers using Internet Printing Protocol (IPP) might not complete successfully. Devices which had connected to and installed the printer prior to the installation of KB5005566 are unaffected and print operations to that printer will succeed as usual. Note IPP is not commonly used by devices designed for home use. The printing environments affected by this issue are more commonly found in enterprises and organizations."
Microsoft is working on a resolution and targeting its release in a future update.
workaround
Nov 10, 2021
KB5006667
2021-10 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5006667) (CVE-2021-40449) (CVE-2021-41335) (CVE-2021-41338)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5006669
2021-10 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5006669) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5006744
2021-10 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5006744)
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5006744
2021-10 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5006744)
"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
Nov 10, 2021
KB5006744
2021-10 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5006744)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5006746
2021-10 Cumulative Update Preview for Windows 11 for x64-based Systems (KB5006746)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5006746
2021-10 Cumulative Update Preview for Windows 11 for x64-based Systems (KB5006746)
"Starting on November 1, 2021, some users might be unable to open or use certain built-in Windows apps or parts of some built-in apps. This is caused by an issue with a Microsoft digital certificate, which expired October 31, 2021. The following might be affected: Snipping Tool Accounts page and landing page in the Settings app (S mode only) Start menu (S Mode only) Touch Keyboard, Voice Typing, and Emoji Panel Input Method Editor user interface (IME UI) Getting star"
This issue is resolved in KB5008295.
workaround
Nov 10, 2021
KB5006738
2021-10 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5006738)
"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 using 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
Nov 10, 2021
KB5006738
2021-10 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5006738)
"After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING"."
For more information and a workaround, see KB5005322.
workaround
Nov 10, 2021
KB5006738
2021-10 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5006738)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Sever 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Nov 10, 2021
KB5006738
2021-10 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5006738)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health: OS Build 19041.1288 OS Build 19042.1288 OS Build 19043.1288 We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5006745
2021-10 Cumulative Update Preview for Microsoft server operating system version 21H2 for x64-based Systems (KB5006745)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Sever 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Nov 10, 2021
KB5006745
2021-10 Cumulative Update Preview for Microsoft server operating system version 21H2 for x64-based Systems (KB5006745)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007205
2021-11 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5007205)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Sever 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Nov 10, 2021
KB5007205
2021-11 Cumulative Update for Microsoft server operating system version 21H2 for x64-based Systems (KB5007205)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007233
2021-11 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5007233) (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 purchased 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 10, 2021
KB5007233
2021-11 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5007233) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007233
2021-11 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5007233) (ESU)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007247
2021-11 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5007247)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007247
2021-11 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5007247)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007206
2021-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5007206)
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007206
2021-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5007206)
"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
Nov 10, 2021
KB5007206
2021-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5007206)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007245
2021-11 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5007245)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007245
2021-11 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5007245)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007207
2021-11 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB5007207)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007255
2021-11 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5007255)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007255
2021-11 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5007255)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007186
2021-11 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5007186)
"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 using 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
Nov 10, 2021
KB5007186
2021-11 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5007186)
"After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING"."
For more information and a workaround, see KB5005322.
workaround
Nov 10, 2021
KB5007186
2021-11 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5007186)
"After installing this update, when connecting to devices in an untrusted domain using Remote Desktop, connections might fail to authenticate when using smart card authentication. You might receive the prompt, "Your credentials did not work. The credentials that were used to connect to [device name] did not work. Please enter new credentials." and "The login attempt failed" in red."
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 non-managed personal 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, it can be resolved by installing and configuring a special Group Policy linked below. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview. Group Policy installation files: Windows Sever 2022 Windows 10, version 2004, Windows 10, version 20H2 and Windows 10, version 21H1 Important Verify that you are using the correct Group Policy for your version of Windows.
workaround
Nov 10, 2021
KB5007186
2021-11 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5007186)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health: OS Build 19041.1288 OS Build 19042.1288 OS Build 19043.1288 We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007263
2021-11 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5007263) (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 purchased 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 10, 2021
KB5007263
2021-11 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5007263) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007263
2021-11 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5007263) (ESU)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007189
2021-11 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5007189)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007236
2021-11 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5007236) (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 purchased 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 10, 2021
KB5007236
2021-11 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5007236) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007236
2021-11 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5007236) (ESU)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007192
2021-11 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5007192)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007246
2021-11 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5007246) (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 purchased 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 10, 2021
KB5007246
2021-11 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5007246) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007246
2021-11 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5007246) (ESU)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007260
2021-11 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5007260)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Nov 10, 2021
KB5007260
2021-11 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5007260)
"After installing this update, Windows print clients might encounter the following errors when connecting to a remote printer shared on a Windows print server: 0x000006e4 (RPC_S_CANNOT_SUPPORT) 0x0000007c (ERROR_INVALID_LEVEL) 0x00000709 (ERROR_INVALID_PRINTER_NAME) Note The printer connection issues described in this issue are specific to print servers and are not commonly observed in devices designed for home use. Printing environments affected by this issue are mo"
For workarounds and the latest status for this issue, please see Windows release health. We are presently investigating and will provide an update in an upcoming release.
workaround
Oct 13, 2021
KB5006714
2021-10 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5006714) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Oct 13, 2021
KB5006732
2021-10 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5006732) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Oct 13, 2021
KB5006739
2021-10 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5006739) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Oct 13, 2021
KB5006728
2021-10 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5006728) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Oct 13, 2021
KB5006728
2021-10 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5006728) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338) (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 purchased 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 13, 2021
KB5006672
2021-10 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5006672) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338)
"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
Oct 13, 2021
KB5006672
2021-10 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5006672) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338)
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Oct 13, 2021
KB5006743
2021-10 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5006743) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Oct 13, 2021
KB5006743
2021-10 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5006743) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338) (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 purchased 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 13, 2021
KB5006715
2021-10 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5006715) (CVE-2021-40449) (CVE-2021-40469) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Oct 13, 2021
KB5006715
2021-10 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5006715) (CVE-2021-40449) (CVE-2021-40469) (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 purchased 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 13, 2021
KB5006670
2021-10 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5006670) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338)
"After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING"."
For more information and a workaround, see KB5005322.
workaround
Oct 13, 2021
KB5006670
2021-10 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5006670) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338)
"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 using 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
Oct 13, 2021
KB5006736
2021-10 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5006736) (CVE-2021-40449) (CVE-2021-40469) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Oct 13, 2021
KB5006736
2021-10 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5006736) (CVE-2021-40449) (CVE-2021-40469) (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 purchased 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 13, 2021
KB5006729
2021-10 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5006729) (CVE-2021-40449) (CVE-2021-40469) (CVE-2021-41335) (CVE-2021-41338)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Oct 13, 2021
KB5005611
2021-09 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5005611)
"After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING"."
For more information and a workaround, see KB5005322.
workaround
Oct 13, 2021
KB5005611
2021-09 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5005611)
"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 using 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
Oct 13, 2021
KB5005625
2021-09 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5005625)
"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
Oct 13, 2021
KB5005625
2021-09 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5005625)
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Sep 15, 2021
KB5005565
2021-09 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5005565)
"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 using 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
Sep 15, 2021
KB5005565
2021-09 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5005565)
"After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING"."
For more information and a workaround, see KB5005322.
workaround
Sep 15, 2021
KB5005606
2021-09 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5005606) (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 purchased 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
Sep 15, 2021
KB5005606
2021-09 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5005606) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Sep 15, 2021
KB5005633
2021-09 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5005633) (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 purchased 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
Sep 15, 2021
KB5005633
2021-09 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5005633) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Sep 15, 2021
KB5005568
2021-09 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5005568)
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Sep 15, 2021
KB5005568
2021-09 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5005568)
"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
Sep 15, 2021
KB5005618
2021-09 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5005618) (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 purchased 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
Sep 15, 2021
KB5005618
2021-09 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5005618) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Sep 15, 2021
KB5005623
2021-09 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5005623)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Sep 15, 2021
KB5005615
2021-09 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5005615) (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 purchased 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
Sep 15, 2021
KB5005615
2021-09 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5005615) (ESU)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Sep 15, 2021
KB5005613
2021-09 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5005613)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Sep 15, 2021
KB5005607
2021-09 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5005607)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Sep 15, 2021
KB5005627
2021-09 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5005627)
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Sep 15, 2021
KB5005102
2021-08 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5005102)
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Sep 15, 2021
KB5005102
2021-08 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5005102)
"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
Sep 15, 2021
KB5005101
2021-08 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5005101)
"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 using 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
Sep 15, 2021
KB5005101
2021-08 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5005101)
"After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING"."
For more information and a workaround, see KB5005322.
workaround
Aug 11, 2021
KB5004308
"2021-07 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5004308)"
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5004308
"2021-07 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5004308)"
"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 11, 2021
KB5005394
"2021-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5005394)"
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5005394
"2021-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5005394)"
"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 11, 2021
KB5004296
"2021-07 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5004296)"
"When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually. Note The affected apps are using the ImmGetCompositionString() function."
We are working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5004296
"2021-07 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5004296)"
"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 using 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 11, 2021
KB5004296
"2021-07 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5004296)"
"After installing the May 25, 2021 (KB5003214) and June 21, 2021 (KB5003690) updates, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING"."
For more information and a workaround, see KB5005322.
workaround
Aug 11, 2021
KB5005030
"2021-08 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5005030)"
"After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND.""
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5005030
"2021-08 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5005030)"
"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 11, 2021
KB5005030
"2021-08 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5005030)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005088
"2021-08 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5005088) (ESU)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005088
"2021-08 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5005088) (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 purchased 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 11, 2021
KB5005088
"2021-08 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5005088) (ESU)"
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5005031
"2021-08 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5005031)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005099
"2021-08 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5005099)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005099
"2021-08 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5005099)"
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5005033
"2021-08 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5005033)"
"When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually. Note The affected apps are using the ImmGetCompositionString() function."
We are working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5005033
"2021-08 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5005033)"
"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 using 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 11, 2021
KB5005033
"2021-08 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5005033)"
"After installing the June 21, 2021 (KB5003690) update, some devices cannot install new updates, such as the July 6, 2021 (KB5004945) or later updates. You will receive the error message, "PSFX_E_MATCHING_BINARY_MISSING"."
For more information and a workaround, see KB5005322.
workaround
Aug 11, 2021
KB5005033
"2021-08 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5005033)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005095
"2021-08 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5005095) (ESU)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005095
"2021-08 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5005095) (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 purchased 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 11, 2021
KB5005095
"2021-08 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5005095) (ESU)"
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5005076
"2021-08 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5005076)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005076
"2021-08 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5005076)"
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5005040
"2021-08 Cumulative Update for Windows 10 Version 1507 for x64-based Systems (KB5005040)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005089
"2021-08 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5005089) (ESU)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005089
"2021-08 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5005089) (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 purchased 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 11, 2021
KB5005089
"2021-08 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5005089) (ESU)"
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5005043
"2021-08 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5005043)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005094
"2021-08 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5005094)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005094
"2021-08 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5005094)"
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5005106
"2021-08 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5005106)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005106
"2021-08 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5005106)"
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Aug 11, 2021
KB5005090
"2021-08 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5005090) (ESU)"
"After installing this update, the Elastic File System (EFS) API OpenEncryptedFileRaw(A/W), often used in backup software, will not work when you back up to or from a Windows Server 2008 SP2 device. OpenEncryptedFileRaw will continue to work on all other versions of Windows (local and remote)."
This behavior is expected because we addressed the issue in CVE-2021-36942. Note If you cannot use backup software on Windows 7 SP1 and Server 2008 R2 SP1 or later after installing this update, contact the manufacturer of your backup software for updates and support.
workaround
Aug 11, 2021
KB5005090
"2021-08 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5005090) (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 purchased 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 11, 2021
KB5005090
"2021-08 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5005090) (ESU)"
"Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege."
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004289
2021-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5004289) (ESU)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004237
2021-07 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5004237)
When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually. Note The affected apps are using the ImmGetCompositionString() function.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004237
2021-07 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5004237)
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 using 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 14, 2021
KB5004305
2021-07 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5004305) (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 purchased 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 14, 2021
KB5004305
2021-07 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5004305) (ESU)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004235
2021-07 Cumulative Update for Azure Stack HCI, version 20H2 and Windows Server 2019 Datacenter: Azure Edition for x64-based Systems (KB5004235)
You might have issues installing this update by using the Windows Admin Center or Cluster Aware Updating (CAU) through the Windows Update Plugin.
For more information about this issue, please see KB5004971: Issue installing updates in some Azure Stack HCI clusters
workaround
Jul 14, 2021
KB5004285
2021-07 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5004285)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004302
2021-07 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5004302)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004298
2021-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5004298)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004307
2021-07 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5004307) (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 purchased 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 14, 2021
KB5004307
2021-07 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5004307) (ESU)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004244
2021-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5004244)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004244
2021-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5004244)
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 14, 2021
KB5004294
2021-07 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5004294)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004299
2021-07 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5004299) (ESU)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004960
2021-07 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5004960) (CVE-2021-34527)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004956
2021-07 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5004956) (CVE-2021-34527)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004955
2021-07 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5004955) (ESU) (CVE-2021-34527)
After installing this update or later updates, connections to SQL Server 2005 might fail. You might receive an error, "Cannot connect to, Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 4
This is expected behavior due to a security hardening change in this update. To resolve this issue, you will need to update to a supported version of SQL Server.
workaround
Jul 14, 2021
KB5004955
2021-07 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5004955) (ESU) (CVE-2021-34527)
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 purchased 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 14, 2021
KB5004955
2021-07 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5004955) (ESU) (CVE-2021-34527)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004954
2021-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5004954) (CVE-2021-34527)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004953
2021-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5004953) (ESU) (CVE-2021-34527)
After installing this update or later updates, connections to SQL Server 2005 might fail. You might receive the following error: "Cannot connect to, Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provide
This is expected behavior due to a security hardening change in this update. To resolve this issue, you will need to update to a supported version of SQL Server.
workaround
Jul 14, 2021
KB5004953
2021-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5004953) (ESU) (CVE-2021-34527)
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 purchased 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 14, 2021
KB5004953
2021-07 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5004953) (ESU) (CVE-2021-34527)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004945
2021-07 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5004945) (CVE-2021-34527)
When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually. Note The affected apps are using the ImmGetCompositionString() function.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004945
2021-07 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5004945) (CVE-2021-34527)
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 using 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 14, 2021
KB5004945
2021-07 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5004945) (CVE-2021-34527)
After installing this update, you might have issues printing to certain printers. Various brands and models are affected, primarily receipt or label printers that connect via USB. Note This issue is not related to CVE-2021-34527 or CVE-2021-1675.
This issue is resolved in KB5004237.
workaround
Jul 14, 2021
KB5004947
2021-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5004947) (CVE-2021-34527)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004947
2021-07 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5004947) (CVE-2021-34527)
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 14, 2021
KB5004959
2021-07 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5004959) (ESU) (CVE-2021-34527)
After installing this update or later updates, connections to SQL Server 2005 might fail. You might receive an error, "Cannot connect to, Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 4
This is expected behavior due to a security hardening change in this update. To resolve this issue, you will need to update to a supported version of SQL Server.
workaround
Jul 14, 2021
KB5004959
2021-07 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5004959) (ESU) (CVE-2021-34527)
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 purchased 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 14, 2021
KB5004959
2021-07 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5004959) (ESU) (CVE-2021-34527)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004958
2021-07 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5004958) (CVE-2021-34527)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jul 14, 2021
KB5004951
2021-07 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5004951) (ESU) (CVE-2021-34527)
After installing this update or later updates, connections to SQL Server 2005 might fail. You might receive the following error: "Cannot connect to, Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provide
This is expected behavior due to a security hardening change in this update. To resolve this issue, you will need to update to a supported version of SQL Server.
workaround
Jul 14, 2021
KB5004951
2021-07 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5004951) (ESU) (CVE-2021-34527)
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 purchased 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 14, 2021
KB5004951
2021-07 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5004951) (ESU) (CVE-2021-34527)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, "STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)". This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.

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.

workaround
Jun 9, 2021
KB5003637
2021-06 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5003637)
After installing this update, 5.1 Dolby Digital audio may play containing a high-pitched noise or squeak in certain apps when using certain audio devices and Windows settings. Note This issue does not occur when stereo is used.
To mitigate this issue, you can try one or more of the following: Streaming the video or audio in a web browser or different app, instead of the app affected by this issue. Enable Spatial sound settings by right clicking or long pressing on the volume icon in the notification area, selecting Spatial sound (Off) and selecting any of the available options. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003637
2021-06 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5003637)
A small subset of users have reported lower than expected performance in games after installing this update. Most users affected by this issue are running games full screen or borderless windowed modes and using two or more monitors.
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 device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview.
workaround
Jun 9, 2021
KB5003637
2021-06 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5003637)
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 using 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
Jun 9, 2021
KB5003637
2021-06 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5003637)
When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually. Note The affected apps are using the ImmGetCompositionString() function.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003637
2021-06 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5003637)
System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when
If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options. We are working on a resolution and will provide updated bundles and refreshed media in the coming weeks.
workaround
Jun 9, 2021
KB5003667
2021-06 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5003667) (ESU)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003667
2021-06 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5003667) (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 purchased 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
Jun 9, 2021
KB5003667
2021-06 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5003667) (ESU)
After installing this update or later updates, connections to SQL Server 2005 might fail. You might receive an error, "Cannot connect to, Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 4
This is expected behavior due to a security hardening change in this update. To resolve this issue, you will need to update to a supported version of SQL Server.
workaround
Jun 9, 2021
KB5003635
2021-06 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB5003635)
System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when
If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options. We are working on a resolution and will provide updated bundles and refreshed media in the coming weeks.
workaround
Jun 9, 2021
KB5003661
2021-06 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5003661) (ESU)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003661
2021-06 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5003661) (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 purchased 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
Jun 9, 2021
KB5003661
2021-06 Security Monthly Quality Rollup for Windows Server 2008 for x64-based Systems (KB5003661) (ESU)
After installing this update or later updates, connections to SQL Server 2005 might fail. You might receive an error, "Cannot connect to, Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 4
This is expected behavior due to a security hardening change in this update. To resolve this issue, you will need to update to a supported version of SQL Server.
workaround
Jun 9, 2021
KB5003681
2021-06 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5003681)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003696
2021-06 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5003696)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003694
2021-06 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5003694) (ESU)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003694
2021-06 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5003694) (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 purchased 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
Jun 9, 2021
KB5003694
2021-06 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5003694) (ESU)
After installing this update or later updates, connections to SQL Server 2005 might fail. You might receive an error, "Cannot connect to, Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 4
This is expected behavior due to a security hardening change in this update. To resolve this issue, you will need to update to a supported version of SQL Server.
workaround
Jun 9, 2021
KB5003646
2021-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5003646)
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
Jun 9, 2021
KB5003646
2021-06 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB5003646)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003671
2021-06 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5003671)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003695
2021-06 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5003695) (ESU)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003695
2021-06 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5003695) (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 purchased 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
Jun 9, 2021
KB5003695
2021-06 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5003695) (ESU)
After installing this update or later updates, connections to SQL Server 2005 might fail. You might receive an error, "Cannot connect to, Additional information: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 4
This is expected behavior due to a security hardening change in this update. To resolve this issue, you will need to update to a supported version of SQL Server.
workaround
Jun 9, 2021
KB5003697
2021-06 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5003697)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003214
2021-05 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5003214)
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 using 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
Jun 9, 2021
KB5003214
2021-05 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5003214)
After installing this update, 5.1 Dolby Digital audio may play containing a high-pitched noise or squeak in certain apps when using certain audio devices and Windows settings. Note This issue does not occur when stereo is used.
To mitigate this issue, you can try one or more of the following: Streaming the video or audio in a web browser or different app, instead of the app affected by this issue. Enable Spatial sound settings by right clicking or long pressing on the volume icon in the notification area, selecting Spatial sound (Off) and selecting any of the available options. We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003214
2021-05 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5003214)
A small subset of users have reported lower than expected performance in games after installing this update. Most users affected by this issue are running games full screen or borderless windowed modes and using two or more monitors.
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 device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview.
workaround
Jun 9, 2021
KB5003214
2021-05 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5003214)
When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually. Note The affected apps are using the ImmGetCompositionString() function.
We are working on a resolution and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003214
2021-05 Cumulative Update Preview for Windows Server, version 2004 for x64-based Systems (KB5003214)
System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when
If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options. We are working on a resolution and will provide updated bundles and refreshed media in the coming weeks.
workaround
Jun 9, 2021
KB5003212
2021-05 Cumulative Update Preview for Windows 10 Version 1909 for x64-based Systems (KB5003212)
After installing this update and restarting your device, you might be unable to sign into some Microsoft 365 desktop client apps such as Microsoft Teams, OneDrive for Business and Microsoft Outlook. You might also receive an 80080300 error or "We ran into a problem. Reconnecting…" when attempting to authenticate or sign into Teams. Note Mobile, web and non-Windows versions are not impacted.
To mitigate this issue on most devices, you can restart your device a second time. Most devices will sign into affected apps as expected for all subsequent restarts after the first restart that completes installation of the update. If restarting does not mitigate the issue on your device, you can use the web versions of the apps: Microsoft Teams OneDrive for Business Outlook We are presently investigating and will provide an update in an upcoming release.
workaround
Jun 9, 2021
KB5003212
2021-05 Cumulative Update Preview for Windows 10 Version 1909 for x64-based Systems (KB5003212)
System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when
If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options. We are working on a resolution and will provide updated bundles and refreshed media in the coming weeks.
workaround
Jun 9, 2021
KB5003217
2021-05 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5003217)
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
Jun 9, 2021
KB5003217
2021-05 Cumulative Update Preview for Windows 10 Version 1809 for x64-based Systems (KB5003217)
After installing KB4493509, devices with some Asian language packs installed may receive the error, "0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND."
Uninstall and reinstall any recently added language packs. For instructions, see Manage the input and display language settings in Windows 10. Select Check for Updates and install the April 2019 Cumulative Update. For instructions, see Update Windows 10. Note If reinstalling the language pack does not mitigate the issue, reset your PC as follows: Go to the Settings app > Recovery. Select Get Started under the Reset this PC recovery option. Select Keep my Files. Microsoft is working on a resolution and will provide an update in an upcoming release.

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.

workaround
May 12, 2021
KB5003220
2021-05 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB5003220)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 12, 2021
KB5003197
2021-05 Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB5003197)
After installing KB4467684, the cluster service may fail to start with the error “2245 (NERR_PasswordTooShort)” if the group policy “Minimum Password Length” is configured with greater than 14 characters.
Set the domain default "Minimum Password Length" policy to less than or equal to 14 characters. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 12, 2021
KB5003203
2021-05 Security Only Quality Update for Windows Server 2012 for x64-based Systems (KB5003203)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 12, 2021
KB5003209
2021-05 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB5003209)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 12, 2021
KB5003228
2021-05 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5003228) (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 purchased 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
May 12, 2021
KB5003228
2021-05 Security Only Quality Update for Windows Server 2008 R2 for x64-based Systems (KB5003228) (ESU)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 12, 2021
KB5003173
2021-05 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5003173)
System and user certificates might be lost when updating a device from Windows 10, version 1809 or later to a later version of Windows 10. Devices will only be impacted if they have already installed any Latest cumulative update (LCU) released September 16, 2020 or later and then proceed to update to a later version of Windows 10 from media or an installation source which does not have an LCU released October 13, 2020 or later integrated. This primarily happens when
If you have already encountered this issue on your device, you can mitigate it within the uninstall window by going back to your previous version of Windows using the instructions here. The uninstall window might be 10 or 30 days depending on the configuration of your environment and the version you’re updating to. You will then need to update to the later version of Windows 10 after the issue is resolved in your environment. Note Within the uninstall window, you can increase the number of days you have to go back to your previous version of Windows 10 by using the DISM command /Set-OSUninstallWindow. You must make this change before the default uninstall window has lapsed. For more information, see DISM operating system uninstall command-line options. We are working on a resolution and will provide updated bundles and refreshed media in the coming weeks.
workaround
May 12, 2021
KB5003173
2021-05 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5003173)
When using the Microsoft Japanese Input Method Editor (IME) to enter Kanji characters in an app that automatically allows the input of Furigana characters, you might not get the correct Furigana characters. You might need to enter the Furigana characters manually. Note The affected apps are using the ImmGetCompositionString() function.
We are working on a resolution and will provide an update in an upcoming release.
workaround
May 12, 2021
KB5003173
2021-05 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5003173)
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 using 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
May 12, 2021
KB5003173
2021-05 Cumulative Update for Windows Server, version 2004 for x64-based Systems (KB5003173)
A small subset of users have reported lower than expected performance in games after installing this update. Most users affected by this issue are running games full screen or borderless windowed modes and using two or more monitors.
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 device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, it can be resolved by installing and configuring a special Group Policy. Note Devices need to be restarted after configuring the special Group Policy. For help, please see How to use Group Policy to deploy a Known Issue Rollback. For general information on using Group Policies, see Group Policy Overview.
workaround
May 12, 2021
KB5003225
2021-05 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5003225) (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 purchased 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
May 12, 2021
KB5003225
2021-05 Security Only Quality Update for Windows Server 2008 for x64-based Systems (KB5003225) (ESU)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 12, 2021
KB5003208
2021-05 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5003208)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.
workaround
May 12, 2021
KB5003233
2021-05 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5003233) (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 purchased 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
May 12, 2021
KB5003233
2021-05 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB5003233) (ESU)
Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege.
Do one of the following: Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.

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.