Update09/15/2022

Provides OS Security Fixes

Windows 10 22H2
Microsoft

Improvements

Windows 10, version 21H2

Important: Use EKB KB5003791 to update to Windows 10, version 21H2.

This security update includes quality improvements. Key changes include:

This build includes all the improvements from the supported Windows 10, version 20H2 editions.

No additional issues were documented for this release.

Windows 10, version 21H1

Important: Use EKB KB5000736 to update to Windows 10, version 21H1.

This security update includes quality improvements. Key changes include:

This build includes all the improvements from the supported Windows 10, version 20H2 editions.

No additional issues were documented for this release.

Windows 10, version 20H2 editions: Windows 10 Enterprise Multi-Session , Windows 10 Enterprise and Education, Windows 10 IoT Enterprise

Important: Use EKB KB4562830 to update to Windows Server, version 20H2.

This security update includes improvements that were a part of update KB5016688 (released August 26, 2022) and also addresses the following issues:

This update contains miscellaneous security improvements to internal OS functionality. No additional issues were documented for this release.

If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.

For more information about security vulnerabilities, please refer to the new Security Update Guide website and the September 2022 Security Updates.

Bug fixes

Addresses security issues for your Windows operating system.

Open issues

*Symptom -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.

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

Workaround:

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:

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

*Symptom: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 andmust be manually installed.

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

*Symptom: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.

Workaround:

To mitigate this issue, please see one of the following:

Windows 10, version 21H2:Possible issues caused by new Daylight Savings Time in Chile

Windows 10, version 21H1:Possible issues caused by new Daylight Savings Time in Chile

Windows 10, version 20H2:Possible issues caused by new Daylight Savings Time in Chile

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

Note We plan to release an update to support this change; however, there might be insufficient time to properly build, test, and release such an update before the change goes into effect. Please use the workaround above.