-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Operating System and Recovery
- Windows Update fails to install cumulative updates since Aug...

Create an account on the HP Community to personalize your profile and ask a question
09-15-2022 11:29 AM - edited 09-15-2022 11:31 AM
Hello,
My HP Envy x360 laptop has been failing to install Windows cumulative updates since August (KB5016616) with error code 0x80073701. This month the cumulative update failing is KB5017308. Other Windows Updates (.NET, Windows Defender definition, Windows malware removal tool,...) are installing correctly without problems.
Both the Windows (Windows Update diagnostics) and the HP (OS checker) troubleshooters report no problems whatsoever. I'm on Windows 10 build 19044.1706 with firmware version F.47, my CPU is a AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx with 8GB of RAM available.
What should I do? Is there an incompatibility with my hardware and the recent Windows updates?
10-25-2022 02:03 PM - edited 10-25-2022 02:14 PM
Man what?! I have 2 HP laptops that have been getting cumulative update errors since May or June. They do through the update process but during the restart it's always "something didn't go as planned."
I'm so fed up with this they I have to turn off updates for as long as can. Otherwise when I turn them back on they'll go through the process again. Just to fail again.
My PC feels unsafe at this point. I've tried every "fix" online but nothing helps. After months some of the older ones say they've installed after 10+ fails. But did they really install? No clue.
I share your pain. Wish I could offer you a solution. My next laptop purchase won't be an HP!
Edit: adding laptop models. TouchSmart m6-n015dx & Pavilion 15-eg1097nr.
Edit 2: The only thing I find in common on both of my systems is the Windows update troubleshooting report says it resolved issue with "WaaSMedicService".