[SOLVED] Windows Server 2019 - Updates failing with error 0x800f0983

D

dozo

Member
Joined
Nov 19, 2023
Posts
10
Location
Finland
Hello,

I'm stuck on 2022-01 OS build (17763.2369) on Windows Server 2019. Updates are failing and generating errors 0x80246007 or 0x800f0983. SFC and DISM keeps failing as well. I've been trying to fix this server for over a month and tried about everything to no avail.

Any help is much appreciated! Logs attached.

Link to CBS log files: CBS.zip
 

Attachments

Hi and welcome to Sysnative,

Step 1. 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.


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

Hi, thank you! DISM restore operation completed successfully, which is good progress already. However, cumulative updates are still failing with error 0x800f0983. Any ideas how to proceed?

SFCFix.txt attached.
CBS log files can be found here: CBS.zip
 

Attachments

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.
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 reboot the server and attempt to update if it fails attach a new copy of the CBS logs.
 

Attachments

Applied the fix, restarted the server and tried to install a cumulative update. Ended up with error code 0x800f0983 once again.

SFXFix.txt attached and CBS logs can be found here: CBS.zip
 

Attachments

Rich (BB code): 
2023-11-22 17:57:45, Error                 CSI    0000012e (F) Hydration failed for component Microsoft-Windows-Geolocation-Framework, version 10.0.17763.4644, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} on file LocationFramework.dll with NTSTATUS -2146498170[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.
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 reboot the server and attempt to update if it fails attach a new copy of the CBS logs.
 

Attachments

Applied the fix and restarted. Unfortunately cumulative update fails with the same error code (0x800f0983).

Logs attached. CBS log can be found here: CBS.zip

Appreciate your help!
 

Attachments

Rich (BB code): 
2023-11-22 20:32:45, Error                 CSI    00000033 (F) Hydration failed for component Microsoft-Windows-TabletPC-TextAndInkInputServices, version 10.0.17763.2989, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} on file tiptsf.dll with NTSTATUS -2146498170[gle=0x80004005]

Hi,

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 reboot the server and attempt to update if it fails attach a new copy of the CBS logs.[/code]
 

Attachments

Fix applied, server restarted and attempted to install cumulative update, which eventually failed. It took a lot longer to process the update than before.

Logs attached.
CBS log can be found here: CBS.zip

I don't know if it's worth mentioning but I analyzed CBS logs a while back and this is something that stood out to me:

Code: 
CSI    000051d6 [SR] Cannot repair member file [l:27]'MSFT_MpComputerStatus.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-10-31 18:36:26, Info                  CSI    000051d8 [SR] Cannot repair member file [l:19]'MSFT_MpThreat.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-10-31 18:36:26, Info                  CSI    000051da [SR] Cannot repair member file [l:26]'MSFT_MpThreatCatalog.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-10-31 18:36:26, Info                  CSI    000051dc [SR] Cannot repair member file [l:28]'MSFT_MpThreatDetection.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-10-31 18:36:26, Info                  CSI    000051de [SR] Cannot repair member file [l:23]'MSFT_MpPreference.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-10-31 18:36:26, Info                  CSI    000051e0 [SR] Cannot repair member file [l:17]'MSFT_MpScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-10-31 18:36:26, Info                  CSI    000051e2 [SR] Cannot repair member file [l:20]'MSFT_MpWDOScan.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-10-31 18:36:26, Info                  CSI    000051e4 [SR] Cannot repair member file [l:22]'MSFT_MpSignature.cdxml' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-10-31 18:36:26, Info                  CSI    000051e6 [SR] Cannot repair member file [l:13]'Defender.psd1' of Windows-Defender-Management-Powershell, version 10.0.17763.831, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

What's your opinion, is this something we should look into?
 

Attachments

dozo said:
What's your opinion, is this something we should look into?
Click to expand...
We can look at this later, 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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-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 reboot the server and attempt to update if it fails attach a new copy of the CBS logs.
 

Attachments

Ran the script, restarted server and tried to install cumulative update. Took over three hours until it failed with error code 0x8007371b. Log attached.

CBS logs: CBS.zip
 

Attachments

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 (*.*).

    652ff1dfded79-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.
 
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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
650ef5dbdfd06-62151e1bebac4-SFCFix-Txt-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 reboot the server and attempt to update if it fails attach a new copy of the CBS logs.
 

Attachments

Thank you! 2023-11 cumulative update was successfully installed after the last fix. I used standalone installer.

However, I've been stuck on this the whole day:

1700944754001.png

Don't have guts to power cycle at this point. Maybe I wait until tomorrow morning and see what's the status.
 
Update: Server eventually restarted and now everything seems to be working as expected.

Thank you so much for your help, you have no idea how relieved I am right now. 😅 I really appreciate what you do.
 
Hi,

You're welcome. Glad to hear the issue has been resolved...(y)
I will mark this thread as solved then.
 
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