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

217 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2020-10-06T03:31:25+00:00

    I beg to differ.

    https://www.bleepingcomputer.com/news/microsoft/windows-10-alert-defragger-bug-defrags-ssd-drives-too-often/

    This is where I got the notion that it was bugged and doing damage to ssd by running too much. Can you confirm this?

    And yes I agree I hope tomorrow's CU will fix this stuff or I am going to roll back to 1909.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2020-10-06T03:17:28+00:00

    Based on what we were told by Microsoft, the only issue with TRIM was that after successfully running, it soon displayed in the user interface as if it had never been run. It actually worked properly besides that, so no harm was being done to SSDs.

    I just let it run as scheduled, in the background, and almost never check defrag in the user interface.

    Since then it has been resolved with a CU to properly report in the user interface that it has been run before. That is assuming that you can get that CU to actually install.

    Hopefully tomorrow's CU will work better . . .

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-10-06T02:34:53+00:00

    I also cannot install kb4577063 along with KB4571756, same error. KB4577063 is fix for the TRIM bug in win10 2004? How can MS allow this bug given how bad it can slowly destroy SSD's???

    Sure you can disable sysmain but how many people know this to do that? No warning from MS on that issue is really epic fail.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-10-05T20:40:22+00:00

    There's no **** way I'm going to reinstall Windows to install a useless update for this bloatware POS. That's an absurd "solution", are you kidding me?!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-10-05T18:38:19+00:00

    At the very beginning of a Windows 10 upgrade (running setup.exe to upgrade from a mounted ISO file) there is a link where you can select to install updates, or not, during the upgrade. This usually defaults to enabled. The end result is that doing an upgrade this way results in the most recent Cumulative Update being incorporated into the upgrade.

    Tomorrow there should be a new CU, which would normally be incorporated into such an upgrade, if you want to try that method.

    Also, there should soon be a public release of Windows 10 Version 20H2, which would add the 20H2 enablement package to the public ISO that we can download.

    Was this answer helpful?

    0 comments