[SOLVED] Server 2022 failing KB5031364 with error 0x800f0982

[linskun]

Hi,

i have a couple of windows 2022 server VMs.
The build number are 20348.1970 and both fail to install KB5031364 with error 0x800f0982

I've tryed in order :

1. SFC /SCANNOW
2. DISM /online /cleanup-image /restorehealth
3. SFCFix
4. ComponentsScanner

Without success (i don't find anything wrong)

sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

DISM /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.20348.681

Image Version: 10.0.20348.1970

[===========================84.9%=================         ]
[===========================86.7%==================        ]
[===========================88.7%===================       ]
[===========================90.5%====================      ]
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

Scan completed with warnings.

Checking store directories . . .
Checking CBS.log . . .
Checking CheckSUR.log . . .
Checking CheckSUR.persist.log . . .

Attempting repair . . .
Stage 1
Stage 2
Stage 3

SUMMARY:
   CBS & SFC total detected corruption count:     0
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          0
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0

Loading registry hive from C:\Windows\System32\config\COMPONENTS
Parsing loaded hive, please wait...
Hive parsed successfully - found 72.689 keys and 222.942 values
Starting corruption scan
Performing regedit load test
Scanning CanonicalData\Catalog for corruptions
Scanning CanonicalData\Deployments for corruptions
Scanning DerivedData\Components for corruptions
Scanning VersionedIndex\...\ComponentFamilies for corruptions
Checking WinSxS catalogs against CanonicalData\Catalogs
Checking WinSxS components against DerivedData\Components
Checking f! marks
Checking manifests
Checking for malformed Deployment keys
Checking CatalogThumbprints & c! marks
Generating report

The corruption scan completed after 9,84 seconds.

No corruptions were detected in the COMPONENTS hive.

Please note this tool is only able to detect certain corruptions and there may be problems that it is unable to find.
If you are experiencing issues with Windows Update or require further support, please visit Sysnative.com for
free advice.

---------------------------

I will attach :

• CBS after wupdate failed (1_wupdate_CBS.zip)
• CBS after SFC /SCANNOW (2_SFC_CBS.zip)
• DISM log (3_dism.zip)
• SFCFix log (4_SFCFix.zip)
• ComponentScanner log (5_ComponentsScanner.txt)
• COMPONENTS export (COMPONENTS.zip)

I've cloned the server to test, so i can do anything

Thanks in advance

 

[Maxstar]

Hi and welcome to Sysnative,

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFix.zip and save it to your desktop.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

DISM /online /cleanup-image /RestoreHealth

 

[linskun]

It's alive !!!

I'm curious, where did you found the issue ? In which logs ?

 

[Maxstar]

Hi,

The issue is logged in "1_wupdate_CBS.zip", and glad to hear the issue has been resolved...