21H221H120H2
This update brings a plethora of fixes to the operating system. You can install it using the given guide below, which will upgrade your operating system’s build to 1904X.1566. Note: Windows 11 KB5010414 has also been released which offers similar improvements to this one. Continue reading this post to learn what’s new in this release, and how to install it.
Fixes and Improvements in KB5010415
Since all mentioned Windows 10 versions above share the same core, the same update is applicable to all. The following improvements have been made to these operating systems:
An issue where the servers randomly stop responding after running for a while which occurs when Windows Server 2016 runs as a terminal server using certain cloud computing Virtual Desktop Infrastructure (VDI) has been fixed. This also fixes a regression that proactively checks to ensure that the CSharedLock in rpcss.exe is set correctly to avoid a deadlock.An issue that affects the Windows search service and occurs when you query using the proximity operator has been fixed.An issue that fails to show the Startup impact values in Task Manager has been fixed.An issue that prevents ShellWindows() from returning the InternetExplorer object when iexplore.exe runs in the Microsoft Edge Internet Explorer mode context has been fixed.The ability to share cookies between Microsoft Edge Internet Explorer mode and Microsoft Edge has been integrated.An issue that affects dialog boxes in Microsoft Edge Internet Explorer mode has been addressed.An issue that causes Microsoft Edge Internet Explorer mode to stop working when you press the F1 key has been taken care of.An issue that causes the improper cleanup of Dynamic Data Exchange (DDE) objects has been addressed.An issue that prevents printing from operating properly for some low integrity process apps has been fixed.Support for Windows Hello for Business Cloud Trust has been added. This is a new deployment model for hybrid deployments of Windows Hello for Business.An issue that prevents you from unloading and reloading drivers when the drivers are protected Hypervisor-protected Code Integrity (HVCI) has been fixed.An issue that might cause BitLocker to damage Virtual Machine (VM) system files if you expand the BitLocker partition while the VM is offline has been addressed.A reliability issue has been fixed that affects the use of the Remote Desktop app to mount a client’s local drive to a terminal server session.An issue that causes a mismatch between a Remote Desktop session’s keyboard and the Remote Desktop Protocol (RDP) client when signing in has been fixed.An issue that occurs when you try to write a Service Principal Name (SPN) alias which has already been assigned to another SPN has been fixed, and you will now receive an “Access Denied” error.An issue that disconnects Offline Files on the network drive after you restart the OS and sign in again has been fixed.An issue that displays the authentication dialog twice when you mount a network drive has been addressed.Support for hot adding and the removal of Non-Volatile Memory (NVMe) namespaces has been added.A memory leak in the wmipicmp.dll module that causes a lot of false alarms in the System Center Operations Manager (SCOM) datacenter monitoring system has been fixed.An issue that causes the Remote Desktop Service (RDS) server to become unstable when the number of signed in users exceeds 100 has been addressed.An issue that returns an error message when you browse for a domain or organizational unit (OU) has been fixed.An issue that causes the Group Policy Management Console to stop working after you close it has been fixed.An issue that affects OpenGL and GPU reparenting in indirect display scenarios has been addressed.An issue that might cause a device to stop working when you use more than 50 window trees has been fixed.An issue that prevents printing from operating properly for some low integrity process apps has been taken care of.An issue that causes certificate enrollment to fail with the error message “0x800700a0 (ERROR _BAD_ARGUMENTS)” has been fixed.An issue that affects applications that are written to only integrate with Azure Active Directory (AAD) has been fixed.An issue that might cause the Get-TPM PowerShell command to fail when it attempts to report Trusted Platform Module (TPM) information has been fixed.An issue that sometimes causes the Chinese Simplified Input Method Editor (IME) to become completely unusable has been addressed.An issue that causes screen readers to describe a back button as “button” rather than “back button” has been addressed.An issue that prevents administrators and content owners from opening expired Active Directory Rights Management Services (AD RMS) content has been addressed.An issue that causes VM Live Migration to fail because vhdmp.sys receives different file control block (FCB) object pointers for the same file has been fixed.A memory leak in the Redirected Drive Buffering Subsystem (RDBSS) and the mrxsmb.sys drivers has been taken care of.An issue that causes a deadlock in the WebDav redirector has been fixed, which resulted in the system not responding.An issue that prevents Work Folder sync from recovering from the error code 0x80c80003, “Server is currently busy” on the client has been fixed.An issue that calls a context function in a page fault path, which causes a 7F error, has been fixed.
Since this is a cumulative update, if you have installed the previous updates, only the new fixes will be applied to your PC. With these improvements, the release also has a few known issues.
Known Issues
An issue with the standalone (clean) installation of Windows 10 with this update is causing Microsoft Edge Legacy to be removed. However, it is not being replaced by the new Chromium-based Edge. This occurs only when Windows has a custom offline media or an ISO image installed that does not include the 29th March 2021 SSU update. Microsoft suggests that you either install the March SSU update through slipstreaming or simply update an existing OS through Windows Update, so you will not be facing this issue. Alternatively, you can simply download and install the new Microsoft Edge if you have already encountered this problem. Another issue that users might face with this update is that they are unable to install it entirely. This may be because of a previously installed update KB5003690. If that is the case, you can find a workaround for it here in Microsoft’s post. Users may also see an error message “Your credentials did not work. The credentials that were used to connect to (device name) did not work. Please enter new credentials” when connecting to devices in an untrusted domain using Remote Desktop while using smart card authentication. Microsoft has found a temporary fix around the issue which you can find here. Users may experience a problem where the recent emails are not visible in the search results in Microsoft Outlook. The problem is related to the PST or OST files that store the emails locally on your PC. Microsoft suggests that you disable Windows Desktop Search which will result in Outlook using its own built-in search operations. We have noticed that these issues have been around for Windows 10 for quite some time now. However, Microsoft has not been successful at fixing them as of yet.
Download and Install Windows 10 KB5010415
Offline Installers
For Windows 10 Version 21H2
Download KB5010415 for Windows 10 Version 21H2 64-Bit [653.3 MB] Download KB5010415 for Windows 10 Version 21H2 32-Bit [308.5 MB]
For Windows 10 Version 21H1
Download KB5010415 for Windows 10 Version 21H1 64-Bit [653.3 MB] Download KB5010415 for Windows 10 Version 21H1 32-Bit [308.5 MB]
For Windows 10 Version 20H2
Download KB5010415 for Windows 10 Version 20H2 64-Bit [653.3 MB] Download KB5010415 for Windows 10 Version 20H2 32-Bit [308.5 MB] To install the update, simply run the downloaded MSU file and Windows will automatically install the update. To download any other updates related to any of the above, please check the Microsoft Catalog.
Windows Update
To install this update via Windows Update, you need to be running Windows 10 version 21H2, 21H1, or 20H2. To check your version of the operating system, type in winver in Run and press Enter. Once the PC boots up again, you can then confirm that the update has been installed successfully through winver.KB5010415 successfully installed
Rollback/Remove Windows 10 Cumulative Update
If you do not wish to keep the installed update for some reason, you can always roll back to the previous build of the OS. However, this can only be performed within the next 10 days after installing the new update. To roll back after 10 days, you will need to apply this trick.
Cleanup After Installing Windows Updates
If you want to save space after installing Windows updates, you can run the following commands one after the other in Command Prompt with administrative privileges: Also see:
Windows 10 Cumulative Update KB5009596 Released With FixesDownload Windows 10 Cumulative Update KB5007186 and KB5007189: Fixes Zero-Day VulnerabilitiesWindows 10 Cumulative Update KB5009543 Released For 21H2, 21H1, 20H2Windows 10 Cumulative Update KB5008212 Released for 21H2, 21H1, 20H2, 2004Windows 10 build 19044.1499 (KB5009596) Released With Fixes
