[SOLVED] WS2019 - 0x800f0982 KB5028168

K

kama

Active member
Joined
Jul 18, 2023
Posts
28
Many thanks for your work!

The cumulative update KB5028168 for Windows Server 2019 Standard x64 fails permanently.

First I got the error 0x80073701. Then I removed the previous cumulative update KB5027222. Since then I get the error 0x800f0982.

A manual installation attempt fails, also the KB5027222 cannot be installed anymore.

sfc /scannow reports successfully repaired errors on every run.

"Dism /Online /Cleanup-Image /RestoreHealth /Source:... /LimitAccess" was run with a 3 week old backup.
 

Attachments

Windows update now additionally shows error 0x80240007. If desired, I can upload a current cbs.zip. But the error message in the Windows update history remains 0x800f0982.
 
Hi and welcome to Systnative,

Please post the latest CBS as well as a copy of the COMPONENTS and SBS hive.

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.


Export SBS (SideBySide) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbdc454cdb-Export-SBS-hive.png

  • Name this file SideBySide (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Thanks again. Do you have any idea what could be a reason for this error? I ask because recently hardware (hard drives and raid controller) in the system was renewed. Previously SATA disks were installed on an onboard raid controller. Windows events reported that one disk was out of raid 5 and then the raid was rebuilt. After that, there were data errors and a database had to be repaired. A memory test showed no error, virus scans were negative. The system was nevertheless reinstalled. The entire SATA part of the Supermicro motherboard is now disabled.

Or does the current problem have no discernible relation to a hardware error?

wetransfer
 

Attachments

Last edited:
Hi,

This is a common issue and not hardware related. Please do the following to check the payload files for the corrupted components.

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.
 

Attachments

Please perform the same steps with FRST and the attached script to see if the *.manifest files exists.
 

Attachments

Thanks, I'll need to compare some things to provide a fix for this issue, so this can take some time.
 
Hi,

Step 1. Download
56f31e53c97da-SFCFix.PNG
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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Thank you!

The result from step 2:
############### Start ###############
Version: 10.0.17763.1

Image version: 10.0.17763.107

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
############### End ############### (English translation)

After that I ran Windows Update. The error 0x800f0982 still exists. The CBS logs are attached.
 

Attachments

Rich (BB code): 
2023-07-29 11:29:29, Error                 CSI    00000015 (F) Can not identify matching versions for component Microsoft-Windows-Shell-GroupPolicy.Resources, version 10.0.17763.2330, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]

Here's the next fix.

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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

This is a Windows Server 2019 Standard ROK license. And I have a running VirtualBox installation.
 
Rich (BB code): 
2023-07-29 13:40:16, Error                 CSI    00000015 (F) Can not identify matching versions for component Microsoft-Windows-ControlPanelDisplay-Adm.Resources, version 10.0.17763.404, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 13:40:17, Error                 CSI    00000019 (F) Can not identify matching versions for component TSGenericUSBDriver.inf.Resources, version 10.0.17763.2090, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]

For now there's no restart needed. Here's the next fix.

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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

I'll need to update my VM's with multile other updates to provide the next fix, so this may take some time.
 
Rich (BB code): 
2023-07-29 14:35:01, Error                 CSI    0000001a (F) Can not identify matching versions for component Microsoft-Windows-win32calc.Resources, version 10.0.17763.771, arch x86, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 14:35:01, Error                 CSI    0000001e (F) Can not identify matching versions for component Microsoft-Windows-win32calc.Resources, version 10.0.17763.771, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 14:35:01, Error                 CSI    00000027 (F) Can not identify matching versions for component Microsoft-Hyper-V-VStack-HyperVCluster.Resources, version 10.0.17763.3770, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 14:35:02, Error                 CSI    00000030 (F) Can not identify matching versions for component Microsoft.Windows.ServerManager.Common.resources, version 10.0.17763.4010, arch msil, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 14:35:02, Error                 CSI    00000038 (F) Can not identify matching versions for component Microsoft-Hyper-V-VStack-VMMS.Resources, version 10.0.17763.2867, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 14:35:02, Error                 CSI    0000003c (F) Can not identify matching versions for component Microsoft-Hyper-V-VStack-VirtualizationV2.Resources, version 10.0.17763.3770, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 14:35:03, Error                 CSI    0000004d (F) Can not identify matching versions for component Microsoft-Windows-WindowsConnectionManager-Adm.Resources, version 10.0.17763.404, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 14:35:02, Error                 CSI    00000034 (F) Can not identify matching versions for component Microsoft-Windows-Ntdll.Resources, version 10.0.17763.4252, arch Host= amd64 Guest= x86, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 14:35:02, Error                 CSI    0000002b (F) Can not identify matching versions for component Microsoft-Windows-AD-PropertyPages.Resources, version 10.0.17763.4377, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 14:35:02, Error                 CSI    00000040 (F) Can not identify matching versions for component Microsoft-Windows-DirectoryServices-Domain-Tools-Command-ldp.Resources, version 10.0.17763.4377, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 14:35:03, Error                 CSI    00000045 (F) Can not identify matching versions for component Windows-SenseClient-Service.Resources, version 10.0.17763.4644, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-29 14:35:03, Error                 CSI    00000049 (F) Can not identify matching versions for component Microsoft-Windows-MssecFilter.Resources, version 10.0.17763.4644, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]

Here's the next fix.

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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

Rich (BB code): 
2023-07-29 19:19:14, Error                 CSI    0000001f (F) Can not identify matching versions for component Microsoft-Windows-MSInfo32-Exe-Common.Resources, version 10.0.17763.2145, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]

Hi,

Here's the next fix.

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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top