[SOLVED] Windows Server 2019 - 2023-10 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5031361) -Error 0x80073701

Code: 
PS C:\Windows\system32> SFC /Scannow

Beginning system scan.  This process will take some time.

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

Windows Resource Protection did not find any integrity violations.
PS C:\Windows\system32> DISM /online /cleanup-image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.4252

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\Windows\system32>

Sadly the same update error as before.
 

Attachments

Rich (BB code): 
2023-10-31 16:02:13, Error                 CBS    Exec: Failed to pre-stage package: Package_9412_for_KB5031361~31bf3856ad364e35~amd64~~10.0.1.9, file: MsSense.exe.mui, sandbox: \\?\C:\Windows\CbsTemp\31067154_2125458298\Windows10.0-KB5031361-x64.cab\ [HRESULT = 0x800f0988 - PSFX_E_INVALID_DELTA_COMBINATION]
2023-10-31 16:02:13, Info                  CBS    Failed to gather all required files. [HRESULT = 0x800f0988 - PSFX_E_INVALID_DELTA_COMBINATION]
2023-10-31 16:02:13, Info                  CBS    Failed to gather all missing files for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.4974.1.9 [HRESULT = 0x800f0988 - PSFX_E_INVALID_DELTA_COMBINATION]

Please attempt to update again with Process Monitor running, and attach this trace with the new CBS logs to our next post.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link.
 
Hi,

Please make a complete image of the server and then perform the next fix.

Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • 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

I thought the software crashed, so I force closed it...
Then I restarted it, and let it finish.

Part1: Fixlog.1.txt
Part2: Fixlog2.txt

Currently trying to update. Will post again.

2023-10 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5031361) -Error 0x800f0982
 
Rich (BB code): 
2023-11-06 11:44:01, Error                 CSI    00000018 (F) Can not identify matching versions for component machine.inf.Resources, version 10.0.17763.1971, arch amd64, culture [l:5]'ja-JP', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-11-06 11:44:01, Error                 CSI    00000019@2023/11/6:11:44:01.307 (F) Attempting to mark store corrupt with category [l:21 ml:22]'CorruptComponentValue'[gle=0x80004005]

Please attach a new copy of the COMPONENTS 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.
 
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.
650c22f99662d-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

Please reboot the server and attempt to update again, this because the latest CBS logs does not reveal a new error.
 
Hmm, at this stage I would suggest to perform an in-place-upgrade to repair this VM.
  • Mount the Windows Server ISO and run Setup.exe. You can use the Microsoft Evaluation Centre to download the ISO files.
  • Use the option Download updates, drivers, and optional features (recommended) and click Next.
  • Depending on your Windows Server version and license, you may see a screen prompting you to enter the licensing key.
  • In the next screen, select the image of the installed Windows Server edition and click Next.
  • Then accept the EULA. To perform a in-place upgrade, you need to check keep personal files and apps. Then click Next.
  • After clicking Next, an upgrade process will start checking for updates, when this is ready click install to start the in-place upgrade.
 
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