KB5000802 CU Windows 10 v2004 build 19041.867 and v20H2 19042.867 Win Update

Ever since last week, KB5000802 has repeatedly failed to install.
It throws an error message "some of the files could not be installed" when trying to install through WU.

Should I install this (LCU) latest cumulative update KB5001567 through the WU release channel?

Am I mis-reading the release note? . . .Where it says "before installing this update through release channel Windows Update...
I've had KB4598481 installed since 1/14/21. I don't know if this is the same "prerequisite" they're talking about.
Last week, SSU 10.0.19041.860 installed successfully.
Additionally last week, KB4601382 installed

https://support.microsoft.com/en-us/...b-4274a5949bf3

I'm not looking to take on more problems and I also don't want to see error: 0x800f0823 – CBS_E_NEW_SERVICING_STACK_REQUIRED, appear and then have to see if installing the standalone KB5001567 will correct the reason I'm having this install issue through WU.

P.S. > No I don't believe this has to do with a 'driver error' in the system causing Windows Update to fail

Thank you very much in advance for any insight.

Windows 10 Home, 20H2
OS Build 19042.844

Caledon Ken said:

If you are having issue with Windows Updates please follow Brink's tutorial on resetting Windows updates.

Reset Windows Update in Windows 10

Wouldn't hurt to run sfc /scannow

easy to do.

Already ran sfc /scannow as well as DISM /Online /Cleanup-Image /CheckHealth, DISM /Online /Cleanup-Image /ScanHealth, and DISM /Online /Cleanup-Image /RestoreHealth.

No integrity violations running an sfc scan
No corruption in the component store.

I then ran SFCFix. It found one system driver error which it corrected 100%

Resetting Windows Update will delete the Update History according to Brink's comment after the tutorial. I haven't attempted to reset Windows Update for that reason.

I'm just thinking MS pulled KB5000802 from the servers where I'm receiving WU's and I'd kind of like to understand whether KB5001567 which was just released (as an optional update) in WU could allow KB5000802 to install after 1567 was installed first.
That was basically the question.

Jaguwaar20 said:

Already ran sfc /scannow as well as DISM /Online /Cleanup-Image /CheckHealth, DISM /Online /Cleanup-Image /ScanHealth, and DISM /Online /Cleanup-Image /RestoreHealth.

No integrity violations running an sfc scan
No corruption in the component store.

I then ran SFCFix. It found one system driver error which it corrected 100%

Resetting Windows Update will delete the Update History according to Brink's comment after the tutorial. I haven't attempted to reset Windows Update for that reason.

I'm just thinking MS pulled KB5000802 from the servers where I'm receiving WU's and I'd kind of like to understand whether KB5001567 which was just released (as an optional update) in WU could allow KB5000802 to install after 1567 was installed first.
That was basically the question.

Reset Windows Update in Windows 10
says This will not clear the Windows Update history. - what are you referring to?

steve108 said:

Reset Windows Update in Windows 10
says This will not clear the Windows Update history. - what are you referring to?

Post #13 by @Brink where he said: "The reset also clears your update history."
Reset Windows Update in Windows 10

Brink said:

That was from an old 2015 post where the reset used to also clear your update history.

The current .bat to reset Windows Update will not clear the update history anymore.

I kinda assumed that, but I was hesitant to take a chance. Thanks @Brink

If anyone could offer guidance on one other question, it would be greatly appreciated.

Will running this .bat file to reset Windows Update pose any issues with these CU's already pending restart?

Ha ha ha. man, talk about poor timing
You posted your reply probably 15 seconds after I pulled the trigger. I figured I should play it best by re-starting and letting the CU fail (which they both did) so as to prevent any potential issues.
After they failed, then I reset Windows Update.

Now I have to wait until the CU's re-download from WU to see if resetting Windows Update solved the issue.