KB5030214 is failing to install on Windows Server 2019 1809

J

jtryan77

Contributor
Joined
Sep 27, 2023
Posts
11
Hi - here are the details of my issue. Seems to be rather common. I sure would love to understand from a high level what is causing these issues.

2023-09 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5030214) is failing to install on Windows Server 2019 1809 (10.0.17763.1817) with error 0x800f0982. I have tried:

-Tried to install from Windows update - fails at 20% with error 0x800f0982

-Tried to install with WUSA and the package: windows10.0-kb5030214-x64_a3cdc7fa59462aa30cbead2831d25bfa79155be6.msu - failed with no error displayed

-Ran Windows disk cleanup utility (cleared ~3 GB of data iirc)

-Ran Windows update troubleshooter - troubleshooter found no issues

-Rebooted PC

-Ran sfc /scannow - no issues reported

-Ran the DISM commands listed below - no issues/repairs reported
--DISM /Online /Cleanup-Image /CheckHealth
--DISM /Online /Cleanup-Image /ScanHealth
--DISM /Online /Cleanup-Image /RestoreHealth

-Rebooted PC

-Reset Windows update components with the following commands:
--net stop wuauserv
--net stop appidsvc
--net stop cryptsvc
--Del “%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\*.*”
--rmdir %systemroot%\SoftwareDistribution /S /Q
--rmdir %systemroot%\system32\catroot2 /S /Q
--regsvr32.exe /s atl.dll
--regsvr32.exe /s urlmon.dll
--regsvr32.exe /s mshtml.dll
--netsh winsock reset
--netsh winsock reset proxy
--net start bits
--net start wuauserv
--net start appidsvc
--net start cryptsvc

-Rebooted PC

-Attempted Windows Update and WUSA again with same failures




The component scanner txt is attached. The CBS folder export was >50 MB so here is a WeTransfer link: https://wetransfer.com/downloads/f08c47c48857d6426d275f4e2ef0ae3f20230928084428/c890a454c91a145d5288dfd61864bc0f20230928084450/a82de3


Please let me know if you have any additional questions. I took the liberty of donating to Sysnative. Thank you for your time!
 

Attachments

Good morning - does anyone have and good ideas as to how to help me with this issue? I thought I saw several others who reported the exact same issue receive assistance within a few days, but it's been nearly 3 weeks since I posted my question, so I'm wondering if perhaps I posted my question incorrectly? Please let me know if I did so. Or maybe someone did reply and I'm just not seeing the reply somehow? I would greatly appreciate any assistance that could be provided. Thank you!

JT
 
Hi and welcome to Sysnative,

Please post the CBS logs again, the WeTransfer link is expired.

Upload a copy of the CBS folder
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
  • Attach the file CBS.zip to your next reply.
 
Good morning - thank you for responding. The CBS logs are attached. Thank you for your help!

JT
 

Attachments

Rich (BB code): 
2023-10-14 00:23:19, Error                 CSI    00000011 (F) Can not identify matching versions for component machine.inf.Resources, version 10.0.17763.1971, arch amd64, culture [l:5]'fr-FR', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-10-14 00:23:19, Error                 CSI    00000012@2023/10/14:04:23:19.118 (F) Attempting to mark store corrupt with category [l:21 ml:22]'CorruptComponentValue'[gle=0x80004005]

Please upload a copy of your COMPONENTS hive as well.

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.
 
Download
6530fbb0f4101-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.
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 if fails attach a new copy of the CBS logs.
 

Attachments

Sorry for the delay, I had to wait for a maintenance window. The update failed again. The .txt file is attached, WeTransfer link to zipped CBS log pasted below. Thank you again for your help.

CBS.zip
 

Attachments

Hi,

The latest CBS logs are clean, what error did you see this time?
 
Fyi, I'm using WUSI to attempt to install the update directly from the .msu file. This is as far as I ever get (see attached screenshot). It gets to this point ~30 seconds after launching the .msu file, and then freezes there for 20-30 minutes before failing. I don't have a screenshot of the failure window, but it says something to the effect of "The update could not be installed...". I will run again and get a screenshot of the failure.

dahv01updateinstallwindow.PNG
 
Here is the failure popup that I get. There's no specific failure codes. I can try to update through Windows Update and see if I get a different result or perhaps an error code. Thanks again.

dahv01wufail.PNG
 
Yes please use Windows Update instead of the *.MSU package, and when it fails attach the new CBS logs.
 
Here is the failure error code from Windows Update as well as the WeTransfer link to the latest CBS logs. Thank you for you help.

CBS.zip

dahv01winupdatefailureerror.PNG
 
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.
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 again. If if fails attach a new copy of the CBS logs.
 

Attachments

Hi,

Please run the fix in post #14 again and attach the SFCFix result.
 
Mmm, the result of SFCFix is still strange, please delete the SFCFix.txt and SFCFix.zip file from your desktop .
Then download the SFCFix.zip from post #14 again and run this fix again.
 
Good evening - I followed your instructions to delete the files from the desktop and here is the new output file. Please let me know if you think I'm doing somethin incorrectly. Thank you again!
 

Attachments

Hi,

This looks good, please attempt to update and let me know the result. If it fails attach a new copy of the CBS logs.
 
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