one hell of a patch with no fix in sight...
Cumulative update won't install (KB4571756) (Error 0x800f081f)
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.
217 answers
Sort by: Newest
-
Anonymous
2020-10-01T12:23:30+00:00 -
Anonymous
2020-09-30T23:39:33+00:00 I am running Windows 10 Home Version 10.0.19041 Build 19041. Sandbox is not a standard feature of Windows 10 Home Edition and is not listed as a choice in "Windows Features".
I do have a a sub directory named C:\DUImageSandbox that was created on 27 SEP 2020 when I downloaded the latest Windows update.
The cabinet file "c:\DUImageSandbox\Microsoft-Windows-Printing-WFS-FoD-Package~31bf3856ad364e35~amd64~en-gb~.cab" does exist.
Now, how do I stop "Windows Update" from trying to run this file?
This is the information posted in the SetupDiagResults log file:
Error: SetupDiag reports rollback failure found.
Last Phase = Safe OS
Last Operation = Add [1] package C:$WINDOWS.~BT\DUImageSandbox\Microsoft-Windows-Printing-WFS-FoD-Package~31bf3856ad364e35~amd64~en-gb~.cab
Error = 0x800F0830-0x20003
LogEntry: 2020-09-27 14:40:08, Error SP CAddCbsPackage::DoExecute: The new OS image is corrupt and cannot be repaired. Error: 0x800F0830[gle=0x0000007a]
-
Anonymous
2020-09-30T20:13:00+00:00 Since the error is pointing to a Windows Sandbox source file, you could perhaps try first installing or uninstalling Windows Sandbox, to see if that makes any difference.
Run optionalfeatures.exe to add or remove Sandbox.
-
Anonymous
2020-09-30T20:06:24+00:00 All 64-bit Windows files are named "amd64". It has nothing to do with the brand of processor that we may have in our PC.
I think AMD was first to market a 64-bit CPU, so their achievement has been honoured in this naming convention ever since.
-
Anonymous
2020-09-30T19:29:48+00:00 I get the same error when I try to update my PC. I ran the utility setupdiag.exe. The log file reports that the update is failing when it tries to load the file "C:$WINDOWS.~BT\DUImageSandbox\Microsoft-Windows-Printing-WFS-FoD-Package~31bf3856ad364e35~amd64~en-gb~.cab"
I have an 64-bit Intel based PC, why is the update trying to load an amd64 file?
I have tried all of the listed suggestions (sfc, dism...) and none of them worked.
Pause updates till October 13th, that's next Patch Tuesday