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: Oldest
  1. Sumit 44,306 Reputation points Volunteer Moderator
    2020-09-14T15:58:25+00:00

    No, a Reset removes all the apps and files(depending on which option you select). A repair install keeps most of the settings, all apps and files. It should fix the issue usually, and there is no harm in trying. Step 6 is what is the easiest one to do and the whole process is automatic.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2020-09-14T18:38:37+00:00

    Same issue security update fails every time and wont allow any other updates to install i also have noticed that the 2004 update completely trashes SSD's and even mechanical hard drives as well

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2020-09-15T04:33:13+00:00

    So it is a buggy update. Ahh it never gets old... Windows 10 is too buggy.

    Yup Windows is always buggy

    I have surfed the web regarding error code: 0x800f091f 

    and found many possible reasons why the error code is showing up

    like

    1: Net Framework 3.5 is not installed reinstall it

    2: Automatic installing will not work 

       So tried manually installing update

    3: Restart Windows update services

    4: Some says Update files getting corrupted while downloading

       Not a working solution for me tried all  but not an valid reason behind this error code

    Upgrading my pc with MCT worked perfectly fine for some of the users I haven't faced

    any problems after installation of September patch till now

    You can wait for October Patch

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2020-09-15T04:35:01+00:00

    I'll check it out but I don't have high hopes since it's very likely the update is bugged (so no matter what I try, the update might still not install).

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2020-09-15T04:37:38+00:00

    Yeah the SSD bug can be fixed though by disabling the automatic defragging of the drive (at least I think so because presonally I've never had issues so far but heard a lot of people complaining and saying this fixed their issue). Although I must mention that for me, after every reboot, Windows tells me the drive needs optmization (like after every single reboot). And when I do click on optimze, it only runs the TRIM command and doesn't defrag it. I don't know for sure, but this might just be another bug.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments