Tuesday (KB5018410) on Windows 10 October 2022 Patch Here's what's new and what's been broken

Tuesday (KB5018410) on Windows 10 October 2022 Patch Here's what's new and what's been broken ...

The second Tuesday of the month, which means it''s Patch Tuesday again. Today Microsoft will distribute the monthly security update (also known as "B release") for Windows Server 20H2, and Windows 10 for the most recent versions, 21H1, 21H2. The new updates are being distributed under KB5018410, bumping up the versions of 19042.2130, 19043.2130, and 19044.2130. This link allows you to find standalone links to the Microsoft Update Catalog.

The major highlight of the program is Windows 10 security updates, and as is usually the case, the Redmond company has listed the known issues in the update, which is always helpful. Here are a few suggestions as well as their respective solutions.

SymptomsWorkaround

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 SSU:

  1. 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

  2. Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:*

  3. 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 this update, file copies using Group Policy Preferences might fail or might create empty shortcuts or files using 0 (zero) bytes. Known affected Group Policy Objects are related to files and shortcuts in User Configuration > Preferences > Windows Settings in Group Policy Editor.

To mitigate this issue, you can do ONE of the following:

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

This update may result in Microsoft Edge Legacy being removed, but it is not automatically replaced by the new Microsoft Edge. This issue is only encountered when custom offline media or ISO images are created by slipping this update into the image without having first installed the standalone servicing stack update (SSU) on 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 that connects to Windows Update should always receive the latest updates of the SSU and the latest cumulative update (LCU) without any additional steps.

Before dumping the SSU before to transform it into a custom offline media or ISO image, be sure to first enter the SSU on March 29, 2021 or later in the custom offline media or ISO image. 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.

Expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab

Expand Windows10.0-KB5000842-x64.cab /f:* Extract the SSU from the previously extracted taxi via this command line.

In this example, you will have the SSU taxi, formerly called SSU-19041.903-x64.cab. Take this file into your offline image first, then the LCU.

If you have already encountered this issue by utilizing affected custom media, you may mitigate it directly using the new Microsoft Edge. Download and deploy Microsoft Edge for your business if you need to.

One of the following steps can be taken to mitigate this problem.

In a upcoming release, we are working on a resolution and will provide an update.

Microsoft Edge Legacy might be removed when custom offline media or ISO images are created by slipping this update into the image without having first installed the standalone servicing stack update (SSU) created on March 29, 2021 or later.

Note Devices that connect directly to Windows Update to receive updates are not affected. This includes devices that use Windows Update for Business. Any device that connects to Windows Update should always receive the latest updates of the SSU and the latest cumulative update (LCU) without any additional steps.

Before you slipstream the SSU from the LCU, make sure to include it in the custom offline media or ISO image. To do this with the combined SSU and LCU packages now available for Windows 10, version 20H2, and Windows 10, version 2004, you will need to extract the SSU from the combined package.

Expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab: extract the cab from the msu via this command line.

Expand Windows10.0-KB5000842-x64.cab /f:* to extract the SSU from the previously extracted cab from the previous command line.

In this example, you will have the SSU cab, which is now known as SSU-19041.903-x64.cab. Before you get this file, you may paste it into your offline image, then the LCU.

Expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab

Expand Windows10.0-KB5000842-x64.cab /f:* extract the SSU from the previously extracted taxi via this command line.

In this example, you will have the SSU cab, which is now called SSU-19041.903-x64.cab. Before you get this file, then you will get the LCU.

If you have already encountered this problem by installing the OS with affected custom media, you may mitigate it by directly installing the new Microsoft Edge. See Download and deploy Microsoft Edge for your convenience.

ONE of the following steps may be taken to mitigate this issue.

In a later release, we''ll be working on a resolution and will provide an update.

Some of the older Windows 10 versions have also received updates today, which have been listed below, as well as their respective release notes (KB) linked together as as links to them in Microsoft''s Update Catalog:

VersionKBBuildDownloadSupport
1809

KB5018419

17763.3532

Update CatalogLong Term Servicing Channel (LTSC)
1607

KB5018411

14393.5427

Update Catalog
1507

KB5018425

10240.19507

Update Catalog

KB5018419

17763.3532

KB5018411

14393.5427

KB5018425

10240.19507

KB5018419

17763.3532

KB5018411

14393.5427

KB5018425

10240.19507

The service of Windows 10 20H2 and Windows 10 1909 has reached an end.