Cumulative update won't install (KB4571756) (Error 0x800f081f)

Anonymous
2020-09-11T07:31:06+00:00

I am running Windows 10 Home 2004 (Build 19041.450). Windows Update notified me that there was a cumulative update available to install (2020-09 Cumulative Update for Windows 10 Version 2004 for x64-based Systems (KB4571756)). When I told it to install the update, it will download and go up to "Installing - 100%" and then just show this error: 

I've tried the following in an attempt to fix the error:

  • Run "sfc /scannow" in an elevated command prompt
  • Run "DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:<Source of clean Windows 10 2004 ISO created using Windows Media Creation Tool> /LimitAccess" in an elevated command prompt
  • Uninstall and reinstall NET framework 3.5 from "Turn Windows features on or off" in Control Panel
  • Manually download the specific update from the Microsoft Update Catalog and install it
  • Stop the Windows Update service and delete the Windows Update cache located in "%SystemRoot%\SoftwareDistrubution", then restart the service

Obviously, none of these worked so I'm looking for any other solutions to this problem. Any help is appreciated.

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

217 answers

Sort by: Newest
  1. Anonymous
    2020-10-14T06:30:04+00:00

    The Amazing Windows updates continue to get interesting (read troubling) with every passing day.

    After this much hyped and much awaited "October" or "Tuesday" update that is supposed to fix the error of KB4571756, another issue has cropped up.

    First, the in-place install failed completely (see my earlier post on page 15 of this thread).

    Second, after 2 days of system recovery from that failed update, the bootloader failed on its own. No hardware changed, no software installed. The PC just refused to start and showed the bootloader problem hex code ending in (14c error code).

    Another 2 hours spent on "Recovering" the PC, and Fortunately, it was successful.

    One of this community posts advised to run "chkdsk /f /x /r", and it ran for more than 8 hours leaving me handicapped. No errors reported at the end, so no insights into what caused the bootloader failure.

    And now today, the much awaited "October" or "Tuesday" update starts on its own, and here we go again - There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x80080005)

    One error after the other. Its an amazing never-ending cycle

    You are at the mercy of Microsoft Lords. Completely handicapped. You pay for computer, you pay for Windows, and no help is available when things go bad. Everything is left at the mercy of some community forums where you keep posting lengthy messages with all the logs, and "volunteers" offer some help.

    While help by volunteers is appreciated, it has turned out to be nothing better than "trial and error" in this case (and for few others in the past).

    No one knows what MS releases, what it screws up, and how lame you end up being despite paying high cost and abiding by their rules.

    Truly feeling sick!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-10-14T05:11:58+00:00

    Same here. Here we go again!

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-10-14T04:09:20+00:00

    I have the same problem😢

    What's going on Microsoft??!!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-10-13T22:58:09+00:00

    I just got Update 9311 and it fails to install. Tried twice. Same error 0x800f081f.

    **** POS:

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-10-13T20:25:19+00:00

    Just got the October updates.  Rebooted.  No new updates found.  1756 is gone now.  

    Was this answer helpful?

    0 comments No comments