Report that this month’s Win10 version 2004 cumulative update, KB 4566782, is throwing error 0x800f0988

Topic

New Reply

Looks like the error also occurred in the preview, released July 31. From artins90 on Reddit: The update KB4566782 is not working 0x800f0988: Exec: Fa
[See the full post at: Report that this month’s Win10 version 2004 cumulative update, KB 4566782, is throwing error 0x800f0988]

1 user thanked author for this post.

ch100

Reply | Quote

Replies

[Mr. Natural]

I just now installed it on my work pc and no errors to report. I even checked event logs and it was installed successfully with no errors.

The error reported appears to be related to good old flash player for windows 10.

It seems like the first question we need to ask folks when they run into issues with the monthly updates is “what anti-malware/anti virus are they using?” It seems to be a common theme over these last several months.

Red Ruffnsore

• This reply was modified 4 years, 9 months ago by Mr. Natural.

2 users thanked author for this post.

ch100, woody

Reply | Quote

0x800f0988 is not new, it happened before in numerous versions. Seems to be something missing in WinSXS folder, possible due to a registry value handling superseeded components.

deeper research here:
Deskmodder.de

quick resolution: inplace upgrade.

Win 10 Pro 1909 x64 (18363.1016)· AMD Ryzen 5 2600X · ASRock X470 Taichi · 64 GB @ 3000 MHz· Desktop
Win 10 Pro 1909 x64 (18363.1016)· Intel i7-8565U · 32 GB @ 1333 MHz ·HP Probook 450 G6
Win 7 Ultimate x64 ESU, Win 8.1 Pro x64, Win 10 Pro 1909 x64, Win 10 Pro 2004 x64, Win 10 Pro 20H2 x64, Win 10 Pro 21H1 x64 20201.1000 (Dev Channel) running on VirtualBox

3 users thanked author for this post.

ch100, abbodi86, Microfix

Reply | Quote

They have been working on a resoulution for that error since v1809

it does not have a fix except in-place upgrade
or manually restore all RTM components from vanilla ISO to WinSXS folder (for experts)

1 user thanked author for this post.

ch100

Reply | Quote

I would be curious if anyone tried removing flash from windows 10 and then re-enabling it in order to fix the situation.

Red Ruffnsore

Reply | Quote

By Dec. 31 2020 Flash support will end on every browser. That will surly fix the bug.

Reply | Quote

The listed adobe-flash component is misleading, it has nothing to do with the erroneous component

adobe-flash updates are totally separate from CU

2 users thanked author for this post.

ch100, Mr. Natural

Reply | Quote

I’ve experienced this error on 1909 and the following worked from my notes.
In an admin cmd type – dism /online /cleanup-image /startcomponentcleanup
followed by (once complete) – dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase  then restart device.

Reply | Quote

I’ve got the same problem. Waiting is probably just what we all need to do. ^^

Reply | Quote

My computer, especially the mouse, are extremely slow after the last W10 updates. Is this a common problem and is there a fix or work around?

Reply | Quote

If you have updated to the new ChrEdge the browser maybe the culprit.
Uninstall and check.

https://www.windowslatest.com/2020/06/28/windows-10-kb4559309-edge-update-issues/

Reply | Quote

Chromium Edge is separate program, which the user start on his own

how it would even affect or cause anything to Windows OS if it’s not running?

1 user thanked author for this post.

ch100

Reply | Quote

Even when not running it does affect Windows 10 behavior and Microsoft acknowledged slowdown, BSOD… after installing ChrEdge.

Reply | Quote

Aware is not acknowledge

Reply | Quote

anonymous wrote:

extremely slow after the last W10 updates

What is slow? Startup, loading programs, typing, etc?

Open Task Manager (right click on the task bar) and see if Windows is using lots of CPU, RAM or disk?

cheers, Paul

Reply | Quote

Here is the relevant part of the CBS.log when this happens (on 20H2, which is 2004 with the 20 H2 Enablement package):

2020-09-12 17:46:04, Error                 CBS    Exec: Failed to pre-stage package: Microsoft-Windows-Printing-PMCPPC-FoD-Package~31bf3856ad364e35~amd64~en-US~10.0.19041.1, component identity: amd64_adobe-flash-for-windows_31bf3856ad364e35_10.0.19041.1_none_e190f18a08ed1a44, file: Flash.ocx,  sandbox: \\?\C:\WINDOWS\CbsTemp\30836952_230277118\Windows10.0-KB4571756-x64.cab\, file format: 0 [HRESULT = 0x800f0988 - PSFX_E_INVALID_DELTA_COMBINATION]
2020-09-12 17:46:04, Info                  CBS    Failed to gather all required files. [HRESULT = 0x800f0988 - PSFX_E_INVALID_DELTA_COMBINATION]
2020-09-12 17:46:04, Info                  CBS    Failed to gather all missing files for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.508.1.9 [HRESULT = 0x800f0988 - PSFX_E_INVALID_DELTA_COMBINATION]
2020-09-12 17:46:04, Info                  CSI    0000010c@2020/9/12:07:46:04.288 CSI Transaction @0x1996b2e8770 destroyed
2020-09-12 17:46:04, Error                 CBS    Failed to pre- stage package: Package_for_KB4562830~31bf3856ad364e35~amd64~~10.0.1.2 [HRESULT = 0x800f0988 - PSFX_E_INVALID_DELTA_COMBINATION]
2020-09-12 17:46:04, Info                  CBS    CommitPackagesState: Started persisting state of packages
2020-09-12 17:46:04, Info                  CBS    CommitPackagesState: Completed persisting state of packages
2020-09-12 17:46:04, Info                  CSI    0000010d@2020/9/12:07:46:04.335 CSI Transaction @0x1996b2e85a0 destroyed
2020-09-12 17:46:04, Info                  CBS    Perf: Stage chain complete.
2020-09-12 17:46:04, Info                  CBS    Failed to stage execution chain. [HRESULT = 0x800f0988 - PSFX_E_INVALID_DELTA_COMBINATION]
2020-09-12 17:46:04, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x800f0988 - PSFX_E_INVALID_DELTA_COMBINATION]
2020-09-12 17:46:04, Info                  CBS    WER: Generating failure report for package: Package_for_KB4562830~31bf3856ad364e35~amd64~~10.0.1.2, status: 0x800f0988, failure source: Stage, start state: Resolved, target state: Installed, client id: UpdateAgentLCU

2 users thanked author for this post.

abbodi86, Kirsty

Reply | Quote

In the end after spending lots of hours experimenting and trying to identify the root cause, this was fixed by using the sledgehammer approach of getting a current ISO of the uupdump Feature update to Windows 10, version 2004 (19041.508) and performing an upgrade in place. Use at your own risk. The uupdump is not an official image, but I have enough checks in place to trust it as being like the original if not better and more useful in some aspects.
https://uupdump.ml/
The likely root cause of the update failing to install is a bug in Windows 10 clean-up mechanism in relation to the Optional FOD components and in combination with the en-GB Language Pack.

Reply | Quote

The complete answer to this issue (and a fix, but not for everyone) is here in German language.
https://www.deskmodder.de/phpBB3/viewtopic.php?f=334&t=24069

Reply | Quote