As is the case every second Tuesday of the month, Microsoft is releasing cumulative updates for all supported Windows versions. That includes all supported Windows 10 versions, along with Windows 8.1, and Windows 7 customers that have opted to receive extended security updates. As for Windows 10 users, it must be noted that versions 1909, 1809, and 1803 will be reaching the end of support, with 1803 being completely unsupported – including for enterprises – starting today.
As for Windows 7 and Windows 8.1 (and the corresponding Windows Server versions), there are two kinds of updates. The monthly rollup packages are downloaded automatically from the Windows Update, while security-only packages are made available for manual download.
Starting with Windows 8.1, the monthly rollup for this month is KB5003209 and can be manually downloaded from the Update Catalog here. The changelog for the patch is as follows:
- Security updates to Windows App Platform and Frameworks, Windows Silicon Platform, and Microsoft Scripting Engine.
As for known issues, there is just one known issue that is being tracked for a while, and it still seems to not have been addressed:
|
Symptom |
Workaround |
|---|---|
|
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:
Microsoft is working on a resolution and will provide an update in an upcoming release. |
Heading to the security-only update, it is listed in the knowledge base article KB5003220 and is available for manual download from here. It includes the following fixes and comes with the same known issue as that of the monthly rollup:
- Security updates to Windows App Platform and Frameworks, and Windows Silicon Platform.
Moving on to Windows 7, the monthly rollup is KB5003233 and can be downloaded from the link here. The list of fixes being made to users of the OS with this month’s update includes the following:
- Addresses an issue in the Server Message Block (SMB) protocol which may cause frequent crashes with Stop error 0xA on devices that run Windows Server 2008 R2 Service Pack 1 (SP1).
- Security updates to Windows App Platform and Frameworks, Windows Silicon Platform, and Microsoft Scripting Engine.
And here are the known issues that users should be aware of:
|
Symptom |
Workaround |
|---|---|
|
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 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. |
|
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:
Microsoft is working on a resolution and will provide an update in an upcoming release. |
For those looking for the security-only update, it is KB5003228 for this month and can be manually pulled from the Update Catalog here. The list of changes and fixes are as follows:
- Addresses an issue in the Server Message Block (SMB) protocol which may cause frequent crashes with Stop error 0xA on devices that run Windows Server 2008 R2 Service Pack 1 (SP1).
- Security updates to Windows App Platform and Frameworks, and Windows Silicon Platform.
The known issues for this update are shared with the monthly rollup, which means that the rename operation problem – which has been around for a while now, is still not fixed.
As usual, you can head to Windows Update and check for updates to pull the monthly rollup patches. You can also head to the individual download links for the security-only updates which can only be manually installed.
