KB5020023 failing installation on most of our Server 2012 R2 machines

[sccm4uandme]

Hello,

Have been at this for a couple of days now, but nothing seems to work. We are getting the common error 800F0831, which is stating the store is corrupt. I have had some success with this error in the past because it identifies some sort of prereq, but it is not indicating this at all in the CBS log this time. Below are my notes so far and the required files are attached: NOTE: I have been reading that these are custom fixes for individual machines, but we have many, so I am hoping to be able to duplicate remotely

sfc /scannow

Ran check for update until all failed

Got error 0x800f0831
--Store corruption, manifest missing for package

Clear cache
--Get-Service -Name wuauserv,bits,cryptsvc | Stop-Service
--Remove-Item -Path "$env:ALLUSERSPROFILE\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
--Testing Check update again
----Did not work

Took snapshot
--Ran Chkdsk
--Logs fixed some files
----Did not work

Reset the windows update cache (nuclear)
--The Windows Update Client Troubleshooting Guide
----Did not work

Sysnative Steps
--sfc /scannow
--Dism /Online /Cleanup-Image /RestoreHealth
--Component Scanner
--Tried update again
---Did not work

We are out of ideas at this point

 

[PeterJ]

Hello and welcome,

Following does a scan only to start with.
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the Farbar Recovery Scan Tool and save it to your Desktop:
   64-bit: Downloading Farbar Recovery Scan Tool
   Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
   
2. Download the attachment fixlist.txt and save it to your desktop.
3. Right-click on FRST64.exe and select "Run as administrator".
4. Press the Fix button.
5. The tool will now process fixlist.txt.
6. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
7. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
8. Attach the logfile Fixlog.txt to your next reply.