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.

This scares the hell out of me. Until now I have a perfectly running system for about 2 years and 6 Months. This is beyond ridiculous that I will have to install Windows 10 from scratch and spend days to reinstall everything as it runs today. It all started with KB4566782 around August patch Tuesday and as you can see updates are still failing after September and October patch Tuesday. Since the next feature update is around the corner ( 20H2 ) , I will just sit this out and attempt the in place upgrade after 20H2 is released for a few weeks. My strong feeling reading all events in this thread is that Microsoft does not care about Windows 10 and Windows 10 customers anymore. Anyone jumped to Linux or Mac ? PS. I did all the magic advised in this thread ( except media creation ) , but no avail.

So what else can we do right now? Do we have to wait until this annoying problem solved or let the update stuck like this, in the previous version (KB4571756)? I can't do anything but wait, hoping that there might be some good news. I am wondering whether I should go for the media creation tool right now since I've attempted to solve this problem for 2 months, and it seems that all solutions provided by Microsoft can't get rid of this problem. P.S. Two error codes I've received are 0x8024200d ( happened when I install the latest update manually) and 0x800f081f.

You can wait for the 20H2 update. Should be out in a month or so I think.

@mattpayne6 Your Windows may still be in a recoverable state. If you have USB bootable Windows 10 install media, you can boot from that. Instead of installing Windows, SHIFT-F10 will give you a Command Prompt from where you can perform repairs. You can check your C: drive, check and repair the Windows files there and even replace your System partition, if need be, to get things running again. Today, "Patch Tuesday", there should soon be a new Cumulative Update for Windows 10. Downloading an ISO file and running setup.exe should repair and incorporate today's CU at the same time (once your computer is back up and running).

(...) This is beyond ridiculous that I will have to install Windows 10 from scratch and spend days to reinstall everything as it runs today. (...) PS. I did all the magic advised in this thread ( except media creation ) , but no avail. It didn't take days, only a couple of hours. I was having dinner and watching Netflix and only would check back with my computer once in a while to click a button. As I wasn't patient enough to wait for it to finish before I went to bed I left it on over night, and this morning everything worked perfectly. I am relieved, really. Had this issue since the August update, too, which was the first ever to fail installing. But from here on out I hope that won't happen again.

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

Anonymous

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.

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

Anonymous

2020-10-13T15:07:20+00:00

This scares the hell out of me. Until now I have a perfectly running system for about 2 years and 6 Months. This is beyond ridiculous that I will have to install Windows 10 from scratch and spend days to reinstall everything as it runs today.

It all started with KB4566782 around August patch Tuesday and as you can see updates are still failing after September and October patch Tuesday.

Since the next feature update is around the corner ( 20H2 ) , I will just sit this out and attempt the in place upgrade after 20H2 is released for a few weeks.

My strong feeling reading all events in this thread is that Microsoft does not care about Windows 10 and Windows 10 customers anymore. Anyone jumped to Linux or Mac ?

PS. I did all the magic advised in this thread ( except media creation ) , but no avail.
Was this answer helpful?

0 comments No comments
Anonymous

2020-10-13T15:45:24+00:00

So what else can we do right now? Do we have to wait until this annoying problem solved or let the update stuck like this, in the previous version (KB4571756)? I can't do anything but wait, hoping that there might be some good news. I am wondering whether I should go for the media creation tool right now since I've attempted to solve this problem for 2 months, and it seems that all solutions provided by Microsoft can't get rid of this problem.

P.S. Two error codes I've received are 0x8024200d ( happened when I install the latest update manually) and 0x800f081f.
Was this answer helpful?

0 comments No comments
Anonymous

2020-10-13T16:41:46+00:00

You can wait for the 20H2 update. Should be out in a month or so I think.
Was this answer helpful?

0 comments No comments
Anonymous

2020-10-13T16:46:07+00:00

@mattpayne6

Your Windows may still be in a recoverable state. If you have USB bootable Windows 10 install media, you can boot from that. Instead of installing Windows, SHIFT-F10 will give you a Command Prompt from where you can perform repairs.

You can check your C: drive, check and repair the Windows files there and even replace your System partition, if need be, to get things running again.

Today, "Patch Tuesday", there should soon be a new Cumulative Update for Windows 10. Downloading an ISO file and running setup.exe should repair and incorporate today's CU at the same time (once your computer is back up and running).
Was this answer helpful?

0 comments No comments
Anonymous

2020-10-13T17:01:41+00:00

(...)

This is beyond ridiculous that I will have to install Windows 10 from scratch and spend days to reinstall everything as it runs today.

(...)

PS. I did all the magic advised in this thread ( except media creation ) , but no avail.

It didn't take days, only a couple of hours. I was having dinner and watching Netflix and only would check back with my computer once in a while to click a button. As I wasn't patient enough to wait for it to finish before I went to bed I left it on over night, and this morning everything worked perfectly.

I am relieved, really. Had this issue since the August update, too, which was the first ever to fail installing. But from here on out I hope that won't happen again.
Was this answer helpful?

0 comments No comments