KB5016616

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 <destination path>

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

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, IE mode tabs in Microsoft Edge might stop responding when a site displays a modal dialog box. A modal dialog box is a form or dialog box that requires the user to respond before continuing or interacting with other portions of the webpage or app.

Developer Note Sites affected by this issue call window.focus.

This issue is addressed in KB5016688. If you do not want to install this release, see the instructions below.

This issue is resolved using Known Issue Rollback (KIR). Please note that it might take up to 24 hours for the resolution to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the resolution apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue can resolve it by installing and configuring the special Group Policy listed below. For information on deploying and configuring these special Group Policy, please see How to use Group Policy to deploy a Known Issue Rollback. 

Group Policy download with Group Policy name: 

• Download for Windows 10, version 20H2 and Windows 10, version 21H1 - Windows 10 20H2, 21H1 and 21H2 KB5014023 220624_22551 Known Issue Rollback

Important You will need to install and configure the Group Policy for your version of Windows to resolve this issue.

After installing this update, XPS Viewer might be unable to open XML Paper Specification (XPS) documents in some non-English languages, including some Japanese and Chinese character encodings. This issue affects both XML Paper Specification (XPS) and Open XML Paper Specification (OXPS) files. When encountering this issue, you may receive an error, "This page cannot be displayed" within XPS Viewer or it might stop responding and have high CPU usage with continually increasing memory usage. When the error is encountered, if XPS Viewer is not closed it might reach up to 2.5GB of memory usage before closing unexpectedly.

This issue does not affect most home users. The XPS Viewer is no longer installed by default as of Windows 10, version 1803 and must be manually installed.

This issue is addressed in KB5017380.

After installing this update, some Windows devices might have issues with audio not working. Some affected Windows devices might have no audio, but other affected Windows devices might only have issues on certain ports, certain audio devices or only within certain applications. Most affected audio devices drivers have the "audio enhancements" setting disabled before installing this update or the sound device driver has issues with the "audio enhancements" feature.

This issue can be mitigated differently depending on your symptoms and if you have installed the update already. Please see the known issue on Windows release health for instructions to prevent and mitigate this issue.

This issue is addressed using a Known Issue Rollback (KIR). This KIR will prevent the issue on Windows devices that have not installed KB5015878,but will have no effect on devices already affected by this known issue. Please note that it might take up to 24 hours for the KIR to propagate automatically to consumer devices and non-managed business devices. Restarting your Windows device might help the KIR apply to your device faster. For enterprise-managed devices that have installed an affected update and encountered this issue, you can address it by installing and configuring a special Group Policy. The special Group Policy can be found in Computer Configuration > Administrative Templates> <Group Policy name listed below>. For information about deploying and configuring these special Group Policy, see How to use Group Policy to deploy a Known Issue Rollback.

Group Policy downloads with Group Policy name:

• Download for Windows 10, version 21H2, Windows 10, version 21H2, Windows 10, version 20H2 - KB5015878 220706_045043 Known Issue Rollback

Important You must install and configure the Group Policy for your version of Windows to resolve this issue.

Starting at 12:00 A.M. Saturday, September 10, 2022, the official time in Chile will advance 60 minutes in accordance with the August 9, 2022 official announcement by the Chilean government about a daylight saving time (DST) time zone change. This moves the DST change which was previously September 4 to September 10.

Symptoms if the workaround is not used on devices between September 4, 2022 and September 11, 2022:

• ​Time shown in Windows and apps will not be correct.

• ​Apps and cloud services which use date and time for integral functions, such as Microsoft Teams and Microsoft Outlook, notifications and scheduling of meetings might be 60 minutes off.

• ​Automation that uses date and time, such as Scheduled tasks, might not run at the expected time.

• ​Timestamp on transactions, files, and logs will be 60 minutes off.

• ​Operations that rely on time-dependent protocols such as Kerberos might cause authentication failures when attempting to logon or access resources.

• ​Windows devices and apps outside of Chile might also be affected if they are connecting to servers or devices in Chile or if they are scheduling or attending meetings taking place in Chile from another location or time zone. Windows devices outside of Chile should not use the workaround, as it would change their local time on the device.

This issue is addressed in KB5017380.