KB5017380 Cumulative Update Preview for Windows 10 Build 19042.2075, 19043.2075, 19044.2075

September 20, 2022 – KB5017380 (OS Builds 19042.2075, 19043.2075, and 19044.2075) Preview

8/26/22
REMINDER Windows Server, version 20H2 reached end of service on August 9, 2022. These devices no longer receive monthly security and quality updates that contain protection from the latest security threats. To continue receiving security and quality updates, Microsoft recommends updating to the latest version of Windows Server.
We will continue to service the following editions: Windows 10 Enterprise and Education, Windows 10 IoT Enterprise, Windows 10 Enterprise multi-session, and Windows 10 on Surface Hub.

5/10/22
REMINDER To update to one of the newer versions of Windows 10, we recommend that you use the appropriate Enablement Package KB (EKB). Using the EKB makes updating faster and easier and requires a single restart. To find the EKB for a specific OS, go to the Improvements section and click or tap the OS name to expand the collapsible section.

11/17/20
For information about Windows update terminology, see the article about the types of Windows updates and the monthly quality update types. For an overview of Windows 10, version 20H2, see its update history page.

Note Follow @WindowsUpdate to find out when new content is published to the Windows release health dashboard.

Highlights

New! You can now search for the controls for news and interests on the taskbar and modify them using the Settings app. To change your settings, navigate to Settings > Personalization > Taskbar > News and interests. Otherwise,right-click the taskbar and select Taskbar settings.
New! All taskbar orientations now support news and interests. A top, left, or right taskbar now has features and settings much like the horizontal taskbar.
Addresses an issue that requires you to reinstall an app if you did not get the app from the Microsoft Store. This issue occurs after you upgrade to Windows 10 or a newer OS.
Addresses a rare error that leads to a blue screen. This occurs after you change the display mode while you are using more than one display.
Addresses an issue that forces the IE mode tabs in a session to reload.
Addresses an issue that affects IE mode after you open a PDF file. When you try to open a different page using the same browser window, the page will not open in that browser window.
Addresses an issue that affects the Microsoft Japanese IME when it is active and the IME mode is on. When you use the numeric keypad to insert a dash (-) character, the IME inserts the wrong one.
Addresses an issue that affects the rendering of the search box. It does not render properly if you sign in using Tablet mode.
Addresses a known issue that affects daylight saving time in Chile. This issue might affect the time and dates used for meetings, apps, tasks, services, transactions, and more.

Improvements

Note: To view the list of addressed issues, click or tap the OS name to expand the collapsible section.

Windows 10, version 21H2

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

This non-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 non-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 the supported editions of Windows 10, version 20H2.

This non-security update includes quality improvements. Key changes include:

New! Turns off Transport Layer Security (TLS) 1.0 and 1.1 by default in Microsoft browsers and applications. For more information, see KB5017811.
New! You can now search for the controls for news and interests on the taskbar and modify them using the Settings app. To change your settings, navigate to Settings > Personalization > Taskbar > News and interests. Otherwise,right-click the taskbar and select Taskbar settings.
New! All taskbar orientations now support news and interests. A top, left, or right taskbar now has features and settings much like the horizontal taskbar.
New! Introduces WebAuthn redirection. It lets you authenticate in apps and on websites without a password when you use Remote Desktop. Then, you can use Windows Hello or security devices, such as Fast Identity Online 2.0 (FIDO2) keys.
New! Introduces functionality that lets you use Azure Active Directory (AD) authentication to sign in to Windows using Remote Desktop. Then, you can use Windows Hello or security devices, such as Fast Identity Online 2.0 (FIDO2) keys, for remote sign in. It also enables the use of Conditional Access policies.
Addresses an issue that requires you to reinstall an app if the Microsoft Store has not signed that app. This issue occurs after you upgrade to Windows 10 or a newer OS.
Addresses an issue that prevents MSIX updates from installing from the same URL.
Addresses an issue that stops codecs from being updated from the Microsoft Store.
Addresses an issue that affects cached credentials for security keys and Fast Identity Online 2.0 (FIDO2) authentications. On hybrid domain-joined devices, the system removes these cached credentials.
Addresses an issue that affects a network’s static IP. The issue causes the configuration of the static IP to be inconsistent. Because of this, NetworkAdapterConfiguration() fails sporadically.
Addresses an issue that affects rendering in Desktop Window Manager (DWM). This issue might cause your device to stop responding in a virtual machine setting when you use certain video graphics drivers.
Addresses a rare stop error that happens after you change the display mode and more than one display is in use.
Addresses an issue that affects graphics drivers that use d3d9on12.dll.
Addresses an issue that forces the IE mode tabs in a session to reload.
Addresses an issue that affects URLs generated by JavaScript: URLs. These URLs do not work as expected when you add them to the Favorites menu in IE mode.
Addresses an issue that affects window.open in IE mode.
Addresses an issue that successfully opens a browser window in IE mode to display a PDF file. Later, browsing to another IE mode site within the same window fails.
Introduces a Group Policy that enables and disables Microsoft HTML Application (MSHTA) files.
Addresses an issue that affects the Microsoft Japanese input method editor (IME). Text reconversion fails when you use some third-party virtual desktops.
Addresses an issue that affects the App-V client service. The service leaks memory when you delete App-V registry nodes.
Addresses an issue that might change the default printer if the printer is a network printer.
Addresses an issue that affects the ProjectionManager.StartProjectingAsync API. This issue stops some locales from connecting to Miracast Sinks.
Addresses an issue that affects Group Policy Objects. Because of this, the system might stop working.
Addresses an issue that affects Windows Defender Application Control (WDAC) path rules. This issue stops .msi and PowerShell scripts from running.
Addresses an issue that might bypass MSHTML and ActiveX rules for WDAC.
Addresses an issue that causes WDAC to log 3091 and 3092 events in audit mode.
Addresses an issue that affects Windows Defender Application Control (WDAC). It stops WDAC from logging .NET Dynamic Code trust verification failures.
Addresses an issue that affects WDAC policies. If you enable SecureLaunch on a device, WDAC policies will not apply to that device.
Addresses an issue that occurs when a WDAC policy fails to load. The system logs that failure as an error, but the system should log the failure as a warning.
Addresses an issue that affects non-Windows devices. It stops these devices from authenticating. This issue occurs when they connect to a Windows-based remote desktop and use a smart card to authenticate.
Addresses an issue that occasionally causes explorer.exe to stop working when explorer.exe opens.
Addresses an issue that affects the Microsoft Japanese IME when it is active and the IME mode is on. When you use the numeric keypad to insert a dash (-) character, the IME inserts the wrong one.
Addresses an issue that affects the rendering of the search box. It does not render properly if you sign in using Tablet mode.
Addresses an issue that affects the FindNextFileNameW() function. It might leak memory.
Addresses an issue that affects robocopy. Robocopy fails to set a file to the right modified time when using the /IS option.
Addresses an issue that affects cldflt.sys. A stop error occurs when it is used with Microsoft OneDrive.
Addresses an issue that affects the LanmanWorkstation service. It leaks memory when you mount a network drive.
Addresses an issue that affects Roaming User Profiles. After you sign in or sign out, some of your settings are not restored.
Addresses a known issue that affects XML Paper Specification (XPS) viewers. This might stop you from opening XPS files in some non-English languages. These include some Japanese and Chinese character encodings. This issue affects XPS and Open XPS (OXPS) files.
Addresses a known issue that affects daylight saving time in Chile. This issue might affect the time and dates used for meetings, apps, tasks, services, transactions, and more.

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

Windows 10 servicing stack update – 19042.1940, 19043.1940, and 19044.1940

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.

Known issues in this update

Symptoms	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 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 <destination path> Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path> 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, 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.
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: Uncheck the “Run in logged-on user’s security context (user policy option)”. Note: This might not mitigate the issue for items using a wildcard (). Within the affected Group Policy, change “Action” from “Replace” to “Update”. If a wildcard () is used in the location or destination, deleting the trailing “” (backslash, without quotes) from the destination might allow the copy to be successful. We are working on a resolution and will provide an update in an upcoming release.

Symptoms

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 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 <destination path>
Extract the SSU from the previously extracted cab via this command line: expand Windows10.0-KB5000842-x64.cab /f:* <destination path>
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, 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.

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:

Uncheck the “Run in logged-on user’s security context (user policy option)”. Note: This might not mitigate the issue for items using a wildcard (*).
Within the affected Group Policy, change “Action” from “Replace” to “Update”.
If a wildcard (*) is used in the location or destination, deleting the trailing “” (backslash, without quotes) from the destination might allow the copy to be successful.

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

How to get this update

Before installing this update
Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates and Servicing Stack Updates (SSU): Frequently Asked Questions.

Prerequisite:

Based on your installation scenario, choose one of the following:

For offline OS image servicing:
If your image does not have the March 22, 2022 (KB5011543) or later LCU, you must install the special standalone May 10, 2022 SSU (KB5014032) before installing this update.
For Windows Server Update Services (WSUS) deployment or when installing the standalone package from Microsoft Update Catalog:
If your devices do not have the May 11, 2021 (KB5003173) or later LCU, you must install the special standalone August 10, 2021 SSU (KB5005260) before installing this update.

Install this update

Release Channel	Available	Next Step
Windows Update or Microsoft Update	Yes	Go to Settings > Update & Security > Windows Update. In the Optional updates available area, you’ll find the link to download and install the update.
Windows Update for Business	No	None. These changes will be included in the next security update to this channel.
Microsoft Update Catalog	Yes	To get the standalone package for this update, go to the Microsoft Update Catalog website.
Windows Server Update Services (WSUS)	No	You can import this update into WSUS manually. See the Microsoft Update Catalog for instructions.

If you want to remove the LCU

To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages.

Running Windows Update Standalone Installer (wusa.exe) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.

File information

For a list of the files that are provided in this update, download the file information for cumulative update 5017380.

For a list of the files that are provided in the servicing stack update, download the file information for the SSU – version 19042.1940, 19043.1940, and 19044.1940.