Forum Discussion
Solved
Error 0x80242017 when installing KB5004945 from WSUS (but not from Microsoft)
I have several clients running Win 10 v20H2 that are failing to install the update "2021-07 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems (KB5004945) from our WSUS server with "...
- I posted a reply with the answer and it was removed. No idea why. It's a service stack update issue. If a computer missed the May cumulative update then KB5004945 won't install in my experience. The May CU included the latest SSU. Without it, you get 0x80242017
Nope. Rebooted and retried after dism and sfc, and still failed with the exact same error.
Are they Domain-Joined devices?
If yes, just for test try remove one of them from the Domain and see if the problem persist?
Make sure report this issue through the Feedback Hub app.
If yes, just for test try remove one of them from the Domain and see if the problem persist?
Make sure report this issue through the Feedback Hub app.
- Yes, they are domain-joined. I tried removing a client from the domain, then re-importing the WSUS registry settings to point it back at the WSUS server, and it still gives the same error (0x80242017).
- I posted a reply with the answer and it was removed. No idea why. It's a service stack update issue. If a computer missed the May cumulative update then KB5004945 won't install in my experience. The May CU included the latest SSU. Without it, you get 0x80242017
skilley1425I have just tested this solution and have installed the KB5003173. Even after a reboot, I continue to get into the error. Are there any other ideas or do I need to do something else? I am clueless
- Ok, I think I've figured this out. I'm getting the same errors as described. It seems that service stack updates are packaged with the cumulative updates sporadically. The last standalone service stack update I see is from January. However, there was a SSU packaged with the May cumulative update. Without this CU installed (and the embedded SSU) then this cumulative update will not install. 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).
So, as a test I downloaded kb5003214 from the Microsoft Catalog server. I then extracted using expand windows10.0-kb5003214-x64_ea5dec15d30be080e9aa13c46daa299781b2611d . -F:*
I copied SSU-19041.1022-x64.cab to a computer not updating and ran Dism.exe /online /add-package:c:\SSU-19041.1022-x64.cab
Then I re-ran Windows Update pointed at my WSUS server and it worked.
Credit from this post https://borncity.com/win/2021/07/08/the-chaos-printnightmare-emergency-update-july-6-7-2021/
See the section titled "WSUS detection and installation problems"
More info can be found at https://borncity.com/win/2021/07/04/windows-10-der-wsus-und-das-ssulcu-erkennungs-chaos/- Hello there. This detailed explanation worked for me. Before I found this post, I tried to install KB5003214 update but failed with this error message: This update is not applicable to your computer. So thank you, problem solved.
