[German]What about the cumulative update KB4579311 for Windows 10 Version 2004? Do you see issues? There are some users reporting installation errors and other issues.
Update KB4579311 for Windows 10 V2004
Cumulative Update KB4579311 was released on October 13, 2020, for Windows 10 version 2004 and for Windows Server version 2004, raising the OS build to 19041,572. Windows insiders will also receive the update in Windows 10 20H2. I had reported about the update and its fixes in the blog post Patchday: Windows 10 Updates (October 13, 2020).
Issues with Update KB4579311
However, update KB4579311 is proving to be causing issues. I’ve mentioned the known issue, that this update blocks incorrectly signed third-party drivers during installation, within my initial blog post : Windows 10 Updates (October 13, 2020). Later I described some details in the blog post Windows 8.1/10 blocks wrong signed drivers.
The most prominent victim of this innovation is probably HP, which ships the program Sure Click on business notebooks with its Bromium Secure platform. HP has already noticed in advance that its drivers are blocked and published a support article. I had pointed out this issue within my article HP Business Notebooks: Trouble with Sure Click/Bromium and Windows 10 October 2020 Updates. But there are more problems.
Update KB4579311 causes installation errors
On reddit.com there is this thread where a user complains about an installation loop on update KB4579311 which causes the error’ 0x8007370′.
Every time I try to install the update, it goes to 100% and they says “There were some problems installing updates, but we’ll try again later.” (0x8007370). I’ve tried manually installing it and then it just tells me that the update was not installed.
In the above comment one digit is missing in the error code, where it could be a 0 or 1 (i.e. error code 0x80073700/0x80073701). The error 0x80073701 occurs more often during updates and the error code stands for ERROR_SXS_ASSEMBLY_MISSING. This indicates a missing assembly in the WinSxS folder where third-party software swapped out its DLLs. I had taken up this in the blog post Windows 10 V1903: Install errors with Update KB4512508. In August 2019, Microsoft had confirmed the error as a bug in another update (see Windows 10 V1903: Update install error 0x80073701 confirmed), but I’m not sure if the current error from October 2020 can be blamed on the update package. If the error code is 0x80073700, it stands for ERROR_SXS_INVALID_ASSEMBLY_IDENTITY_ATTRIBUTE_NAME and could be caused by the package. But the case is still open because the OP did not respond with details.
Techdows has already pointed out several problems and installation errors with update KB4579311 in this blog post. Here are some of the places that were found in the post and during a Google search:
- MS Answers Forum: A rather large thread with 16 pages so far, where the installation error 0x800f081f is reported initially. I have discussed the error code in the article Windows 10 V1903: Error 0x8024200D or 0x800F081F with update KB4512508. The error code 0x800F081F stands for CBS_E_SOURCE_MISSING, i.e. the source files were not found. In such cases you will first try to repair the system or the component store (I mentioned in the blog post Check and repair Windows system files and component store), see also Windows 10 V1909: Update KB4528760 drops error 0x800F081F.
- Techdows mentioned also error 0x8007000d (stands for ERROR_INVALID_DATA), within the article linked above. The error may be a result of a faulty download. Here the installation should be repeated. Or you can download the update from the Microsoft Update Catalog and try a manual installation.
- reddit.com: Mouse driver cannot be installed (probably the above case of a blocked driver).
- On Techdows the error 0x800f0988 is also mentioned, but I have no meaning for the error code. This error occurs from time to time, as a search here in my blogs reveals (see also Windows 10: KB4551762 causes error 0x800f0988/0x800f0900).
Some users complain about a slow update installation. Here you should be patient if the update stops in the progress bar.
Black-Screen and other errors
A user complains in this reddit.com post that a second monitor is no longer activated. In this reddit.com post in the same thread a user complains that afterwards the screen flickers for 5 minutes before an ad comes up. Techdows mentions here that some users end up with a black screen. In this blog post, Techdows mentiond Windows Explorer crashes, as well as login issues, or freezing after login. For some users, who noticed a reduced performance, this note from Microsoft helped. A summary of various errors can also be found in this post by The Windows Central and in the article here. Anyone of you affected?
Cookies helps to fund this blog: Cookie settings