Then I re-ran Windows Update pointed at my WSUS server and it worked. I copied SSU-19041.1022-圆4.cab to a computer not updating and ran Dism.exe /online /add-package:c:\SSU-19041.1022-圆4.cab I then extracted using expand windows10.0-kb5003214-圆4_ea5dec15d30be080e9aa13c46daa299781b2611d. 0x80073701 ERRORSXSASSEMBLYMISSING which means there are some system files are missing, which caused the update installation failure. So, as a test I downloaded kb5003214 from the Microsoft Catalog server. The problem from a WSUS perspective is the May CU will be expired and will not installed / flagged as needed if a computer missed it (for instance, offline or whatever). Stattdessen blendet Windows Update den Fehlercode. Without this CU installed (and the embedded SSU) then this cumulative update will not install. Aber auch bei Windows 10 Version 1909 gibt es Nutzer, bei denen Windows Update sich weigert, die Aktualisierung durchzuführen.
However, there was a SSU packaged with the May cumulative update. The last standalone service stack update I see is from January. It seems that service stack updates are packaged with the cumulative updates sporadically. I'm getting the same errors as described. On my Windows 10 21H1 19043.1052 machine, updates have consistently failed since KB5004237. After your Windows Updates have been installed then re-enable that setting.ĭell Inspiron 5584 * 64-bit Win 10 Pro v21H2 build 19044.2130 * Firefox v106.0.5 * Microsoft Defender v.4-0.3 * Malwarebytes Premium v4.5.Ok, I think I've figured this out. Windows Update keeps failing - 0x80073701 STATUSSXSASSEMBLYMISSING Mario 1 Aug 3, 2021, 5:40 AM Hi, I have looked extensively for an answer, and while there are related issues posted and solved here, none of the existing answers fixed my problem. I’ve never seen this problem on my Windows 10 laptop, but instead of temporarily disabling your Malwarebytes service, you can also disable the Malwarebytes Premium setting at Settings | Security | Launch Malwarebytes in Background When Windows Starts Up and re-boot to ensure your Malwarebytes service doesn’t start at boot up. The latest topic on this problem was davei1’s 1 Malwarebytes Interfering with Windows Update KB5018427 on Windows 11 22H2 but it was quickly marked as “Resolved” and locked from further comment because davei1 noted they could get their Windows cumulative update to install if they temporarily disabled their Malwarebytes service.
This problem has been reported by several Win 11 users in the Malwarebytes forum but employee AdvancedSetup’s 2 post in AgentZer0’s Win 11 Cumulative Update KB5016629 Failing to Install Due to Malwarebytes suggests that Malwarebytes isn’t planning to do anything about it because they believe it is something that Microsoft needs to fix on their end.
0 kommentar(er)
