Share via

Cumulative updates for Windows 10 and Windows 11 - May 2022

Anonymous
2022-05-11T01:10:05+00:00

The following release notes coincide with Cumulative updates for all the supported versions of Windows released on 05.11.2022.

Windows 11

Windows 11 (original release): KB5013943 Build 22000.675

May 10, 2022—KB5013943 (OS Build 22000.675) (microsoft.com)

Highlights 

  • Addresses security issues for your Windows operating system.
  • Updates an issue that might cause video subtitles to be partially cut off.
  • Displays the temperature on top of the weather icon on the taskbar if your taskbar is aligned on the left.
  • Updates an issue that prevents you from using the minimize, maximize, and close buttons on a maximized app window.

Improvements

This security update includes improvements that were a part of update KB5012643(released April 25, 2022) and also addresses the following issues: 

  • Addresses a known issue that might cause your screen to flicker if you start your device in Safe Mode. Components that rely on explorer.exe, such as File Explorer, the Start menu, and the taskbar, might be affected and appear unstable.

Known issues in this update

Applies to Symptom Workaround
IT admins After installing the Windows updates released January 11, 2022 or later Windows versions on an affected version of Windows, recovery discs (CD or DVD) created by using the Backup and Restore (Windows 7) app in Control Panel might be unable to start.<br><br>Recovery discs that were created by using the Backup and Restore (Windows 7) app on devices which have installed Windows updates released before January 11, 2022 are not affected by this issue and should start as expected.<br><br>NoteNo third-party backup or recovery apps are currently known to be affected by this issue We are working on a resolution and will provide an update in an upcoming release.
IT admins After installing this update, some .NET Framework 3.5 apps might have issues or might fail to open. Affected apps are using certain optional components in .NET Framework 3.5, such as Windows Communication Foundation (WCF) and Windows Workflow (WWF) components. You can mitigate this issue by re-enabling .NET Framework 3.5 and the Windows Communication Foundation in Windows Features. For instructions, please see Enable the .NET Framework 3.5 in Control Panel. Advanced users or IT admins can do this programmatically using an elevated Command Prompt (run as administrator) and running the following commands:<br><br>dism /online /enable-feature /featurename:netfx3 /all<br><br><br><br>dism /online /enable-feature /featurename:WCF-HTTP-Activation<br><br><br><br>dism /online /enable-feature /featurename:WCF-NonHTTP-Activation<br>
All users After installing this update, Windows devices that use certain GPUs might cause apps to close unexpectedly or cause intermittent issues that affect some apps that use Direct3D 9. You might also receive an error in Event Log in Windows Logs/Applications, and the faulting module is d3d9on12.dll and the exception code is 0xc0000094. 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 Policies, seeHow to use Group Policy to deploy a Known Issue Rollback.<br><br>Group Policy download with Group Policy name:<br><ul><li style="margin-left: 0"><p data-prewrap="true"><a href="https://download.microsoft.com/download/3/9/e/39eb177b-6570-4eba-87dc-df157ea3d2cc/Windows%2011%20(original%20release)%20KB5012643%20220509_20053%20Known%20Issue%20Rollback.msi" target="_blank" rel="noreferrer nofollow">Download for Windows 11, version 21H2</a> - Group Policy name: KB5012643 220509_20053 Known Issue Rollback</p></li></ul><br>Important You must installand configurethe Group Policy to resolve this issue. Please see, How to use Group Policy to deploy a Known Issue Rollback.

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 /uninstallswitch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.

Windows 10

May 10, 2022—KB5013942 (OS Builds 19042.1706, 19043.1706, and 19044.1706)

May 10, 2022—KB5013942 (OS Builds 19042.1706, 19043.1706, and 19044.1706) (microsoft.com)

Highlights

  • Addresses security issues for your Windows operating system.

Known issues with KB5013942

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.<br><br>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. 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:<br><ol type="1"><li style="margin-left: 0"><p data-prewrap="true">Extract the cab from the msu via this command line (using the package for KB5000842 as an example): <b>expand Windows10.0-KB5000842-x64.msu /f:Windows10.0-KB5000842-x64.cab <destination path></b></p></li><li style="margin-left: 0"><p data-prewrap="true">Extract the SSU from the previously extracted cab via this command line: <b>expand Windows10.0-KB5000842-x64.cab /f:* <destination path></b></p></li><li style="margin-left: 0"><p data-prewrap="true">You will then have the SSU cab, in this example named <b>SSU-19041.903-x64.cab</b>. Slipstream this file into your offline image first, then the LCU.</p></li></ol><br>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.
After installing the Windows updates released January 11, 2022 or later Windows versions on an affected version of Windows, recovery discs (CD or DVD) created by using the Backup and Restore (Windows 7) app in Control Panel might be unable to start.<br><br>Recovery discs that were created by using the Backup and Restore (Windows 7) app on devices which have installed Windows updates released before January 11, 2022 are not affected by this issue and should start as expected.<br><br>NoteNo third-party backup or recovery apps are currently known to be affected by this issue We are working on a resolution and will provide an update in an upcoming release.
We are receiving reports that the Snip & Sketch app might fail to capture a screenshot and might fail to open using the keyboard shortcut (Windows key+shift+S). This issue occurs after installing KB5010342 (February 8, 2022) and later updates. We are presently investigating and will provide an update when more information is available.
After installing this update, Windows devices that use certain GPUs might cause apps to close unexpectedly or cause intermittent issues that affect some apps that use Direct3D 9. You might also receive an error in Event Log in Windows Logs/Applications, and the faulting module is d3d9on12.dll and the exception code is 0xc0000094. 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 Policies, seeHow to use Group Policy to deploy a Known Issue Rollback.<br><br><br><br>Group Policy download with Group Policy name:<br><br><br><ul><li style="margin-left: 0"><p data-prewrap="true"><a href="https://download.microsoft.com/download/4/f/6/4f634cd3-db60-4f8d-8e9a-7b99c4be5700/Windows%2010%2020H2,%2021H1%20and%2021H2%20KB5011831%20220509_20051%20Known%20Issue%20Rollback.msi" target="_blank" rel="noreferrer nofollow">Download for Windows 10, version 2004, Windows 10, version 20H2, Windows 10, version 21H1, and Windows 10, version 21H2</a> - Group Policy name: KB5011831 220509_20051 Known Issue Rollback</p></li></ul><br>Important You must installand configurethe Group Policy to resolve this issue. Please see, How to use Group Policy to deploy a Known Issue Rollback.

^UPDATED 5/10/22^
REMINDERWindows 10, version 20H2 is at end of service today, May 10, 2022, for devices running the Home, Pro, Pro Education, and Pro for Workstations editions. After May 10, 2022, these devices will 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 10 or Windows 11.

We will continue to service the following editions: Enterprise, IoT Enterprise, Windows on Surface Hub, and Windows Server, version 20H2.

^UPDATED 05/10/22^
REMINDERTo 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.

Download the updates manually from the Microsoft Update Catalog.

Windows for home | Windows 11 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

45 answers

Sort by: Most helpful
  1. Anonymous
    2022-05-11T08:26:09+00:00

    After installing this update (or after some updates were installed) most of my apps stopped working:

    • VS22 installer
    • KeePass
    • Teams
    • ShareX
    • some other apps nonessentials to use this PC to continue my job.

    Re-enabling .net 3.5 in 'Turn Windows Features on or off' seems like it resolved this issue.

    ---------------------------
    
    KeePass.exe - Application Error
    

    The application was unable to start correctly (0xc0000135). Click OK to close the application.  
    

    10 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-05-11T05:32:54+00:00

    After installing this update, my computer won't boot. I get stuck on the mobo wheel of death. I updated the bios of my mobo hoping it would work, but still it won't boot. I'm going through all of the trouble shooting now. All of my HDDs and SSDs are being read in BIOS as well as my CPU. My next step is to try and create a new Windows 10 boot stick and hopefully re-install windows.

    8 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-05-11T12:36:37+00:00

    After this update Kaspersky internet security and Dell support assist were not opening. So force uninstalled them. But now not able to install them. Showing error as above for Dell support assist " The application was unable to start correctly (0xc0000135)".

    135 is a common symptom of .net framework problem.

    Please see the known issues section and bondarenkod fix. I also posted an article on how to correct it.

    Fix Apps not working after installing KB5013943 - Your Windows Guide

    6 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-05-11T12:33:07+00:00

    After this update Kaspersky internet security and Dell support assist were not opening. So force uninstalled them. But now not able to install them. Showing error as above for Dell support assist " The application was unable to start correctly (0xc0000135)".

    6 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2022-05-11T01:14:44+00:00

    I updated my PC to May 10, 2022—KB5013943 and the update went smoothly but after the restart, I found the Corsair ICUE app was not working well the app starts but Corsair Service failed to start and I keep getting error notifications for it.

    I checked it and the Corsair service is not working at all I tried to restart the service and start it manually didn't work and got this error:

    Image

    and here is the troubleshooting I did:

    • sfc /scannow
    • DISM /Online /Cleanup-Image /RestoreHealth
    • Creating ServicesPipeTimeout in regedit
    • Tried to install the Corsair ICUE again

    Finally, I managed to make it work again by uninstalling KB5013943 from my PC and the app and other services worked again.

    6 people found this answer helpful.
    0 comments No comments