Windows 10 Patch Tuesday updates begin rolling out, here's the complete changelog

Windows 10 logo with a PC running the OS next to it over a green background

It’s the time of the month that Microsoft rolls out updates to all supported Windows versions. That includes Windows 10, Windows 8.1, and those who have opted to pay for Windows 7 updates. As for Windows 10, the three latest versions – 2004, 20H2, 21H1 – that are fully supported are receiving the same cumulative updates, along with updates rolling out to certain older versions that are being supported for a specific set of customers.

The reason that the three latest Windows 10 versions receive the same update is that they are built on the same codebase, with version 20H2 and 21H1 being enablement packages that light-up features in the OS in the dormant state. Windows 10 version 21H2 that is slated to release later this year will also be served the same update package in the Release Preview ring.

Additionally, when Windows 11 does release to consumers starting October 5, that version of the OS will also begin being serviced with Patch Tuesday updates. Currently, though it is in the Beta channel, it is following the same update cadence like that of the Dev channel builds. With Windows 11 now also available in the Release Preview channel for commercial customers, it is likely that the builds will begin rolling out to all Release Preview channel Insiders.

With that out of the way, the update for Windows 10 versions 21H1, 20H2, and 2004 is KB5005565, bringing build 19043.1237, 19042.1237, and 19041.1237. The update contains a fix for the recently discovered Windows zero-day vulnerability. Those who did not install the C/D release updates will receive all those fixes rolled into today’s update. The update package can be manually installed from the Update Catalog here.

Here is the single highlight mentioned by the firm, likely referring to the fix for the zero-day:

Updates security for your Windows operating system.

And here is the quality improvement listed in the changelog, which does not include the list present in KB5005101 released earlier this month:

Addresses an issue that causes PowerShell to create an infinite number of child directories. This issue occurs when you use the PowerShell Move-Item command to move a directory to one of its children. As a result, the volume fills up and the system stops responding.

In addition to these fixes, there are a couple of known issues listed in the changelog. Here are the details of the known issues and the possible workarounds:

Symptom	Workaround
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 directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps.	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.cab Extract 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.
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.

Symptom

Workaround

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 directly to Windows Update to receive updates are not affected. This includes devices using Windows Update for Business. Any device connecting to Windows Update should always receive the latest versions of the SSU and latest cumulative update (LCU) without any extra steps.

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.cab
Extract 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.

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.

Windows 10 versions older than version 2004, such as version 1909, are supported for specific SKUs. For example, Version 1909 is only supported for Enterprise, Education, or IoT Enterprise SKUs, while version 1809 is supported only for Long Term Servicing Channel customers. Here is a summary of the versions, the corresponding KB articles for the updates and links for manual downloads, the build numbers, and the SKUs they are supported in:

Version	KB	Build	Download	Support
1909	KB5005566	18363.1801	Update Catalog	Enterprise, Education, or IoT Enterprise SKUs
1809	KB5005568	17763.2183	Update Catalog	Long Term Servicing Channel (LTSC)
1607	KB5005573	14393.4651	Update Catalog
1507	KB5005569	10240.19060	Update Catalog