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.

I believe now that this installation bug will not be fixed in subsequent Cumulative Updates. So the only remedy is a clean install ( with or without keeping apps and data) or an in place upgrade. Both require downloading the latest build using Media Creation Tool and that still is Windows 2004 for now. Personally I will wait for the the 20H2 build to become available for download because the current build on my PC is already 2004 which is exactly the build choking at these cumulative updates. This maybe explains the fact that re-installing 2004 does not always solve the issue at hand. While I dont know if 20H2 will really solve the issue. But I know for sure that this "trial and error" approach of re-installing and in-place repair with 2004 is only going to cause more damage. Have tried and failed multiple times. Avoid these experiments please - the existing working machine may also fail.

They are calling version 20H2 the "Windows 10 October 2020 Update", so it should be available to the public soon. If you want 20H2 now, there is a download page that has it. But you need to login using some Microsoft Account that has joined the Windows Insider Program, or you can create a new Microsoft Account and join with that, just so you can do the download. https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewiso

So, I suppose we should just wait it out. I've been trying to update for a while now, only to have the failed status each time. I'm not sure which are successful anymore.

Next Cumulative Update will for sure just repeat the problem. As stated before the next feature update 20H2 will be delivered as a CU, not as an in place upgrade where a full Windows iso is dowloaded and basically does a full install keeping all apps and data. As a result you find the old windows installation in the folder windows.old for reversing the upgrade if needed. This very large folder is deleted after one month. The next feature update with full install will be 21H1 in spring 2021. So the best approach would be to wait for the 20H2 iso to become available soon via the media creation tool and perform an in place upgrade. Currently the iso to download is still 2004, the very source of this faling updates issue.

It's official now.... more and more troubles are emerging globally from these recently released updates. https://betanews.com/2020/10/17/windows-10-kb4579311-cumulative-update-problems/ https://www.windowslatest.com/2020/10/18/windows-10-kb4579311-patch-tuesday-update-issues/ Just don't experiment anything.......don't try to fix anything by in-place or clean reinstall or whatever...... Sit tight with whatever is working....else you risk screwing up that as well :-(

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-16T16:24:51+00:00

I believe now that this installation bug will not be fixed in subsequent Cumulative Updates.

So the only remedy is a clean install ( with or without keeping apps and data) or an in place upgrade. Both require downloading the latest build using Media Creation Tool and that still is Windows 2004 for now.

Personally I will wait for the the 20H2 build to become available for download because the current build on my PC is already 2004 which is exactly the build choking at these cumulative updates.

This maybe explains the fact that re-installing 2004 does not always solve the issue at hand.

While I dont know if 20H2 will really solve the issue. But I know for sure that this "trial and error" approach of re-installing and in-place repair with 2004 is only going to cause more damage. Have tried and failed multiple times.

Avoid these experiments please - the existing working machine may also fail.
Was this answer helpful?

0 comments No comments
Anonymous

2020-10-16T19:50:02+00:00

They are calling version 20H2 the "Windows 10 October 2020 Update", so it should be available to the public soon. If you want 20H2 now, there is a download page that has it. But you need to login using some Microsoft Account that has joined the Windows Insider Program, or you can create a new Microsoft Account and join with that, just so you can do the download.

https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewiso
Was this answer helpful?

0 comments No comments
Anonymous

2020-10-17T00:41:33+00:00

So, I suppose we should just wait it out. I've been trying to update for a while now, only to have the failed status each time. I'm not sure which are successful anymore.
Was this answer helpful?

0 comments No comments
Anonymous

2020-10-17T07:40:35+00:00

Next Cumulative Update will for sure just repeat the problem. As stated before the next feature update 20H2 will be delivered as a CU, not as an in place upgrade where a full Windows iso is dowloaded and basically does a full install keeping all apps and data. As a result you find the old windows installation in the folder windows.old for reversing the upgrade if needed. This very large folder is deleted after one month.

The next feature update with full install will be 21H1 in spring 2021.

So the best approach would be to wait for the 20H2 iso to become available soon via the media creation tool and perform an in place upgrade.

Currently the iso to download is still 2004, the very source of this faling updates issue.
Was this answer helpful?

0 comments No comments
Anonymous

2020-10-18T12:20:13+00:00

It's official now....

more and more troubles are emerging globally from these recently released updates.

https://betanews.com/2020/10/17/windows-10-kb4579311-cumulative-update-problems/

https://www.windowslatest.com/2020/10/18/windows-10-kb4579311-patch-tuesday-update-issues/

Just don't experiment anything.......don't try to fix anything by in-place or clean reinstall or whatever......

Sit tight with whatever is working....else you risk screwing up that as well :-(
Was this answer helpful?

0 comments No comments