[SOLVED] Server 2016 (Standard) not updating properly and other issues

[Maxstar]

Please run the following commands in an elevated prompt and post the result:

certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_10.0.14393.0_sr-..-cs_25fefef60415aeae\msprivs.dll.mui SHA256
certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_10.0.14393.3085_sr-..-cs_6e59d3a647e83e6c\msprivs.dll.mui SHA256
certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_10.0.14393.3143_sr-..-cs_6e4b302247f3c1bf\msprivs.dll.mui SHA256

 

[EPLTechBH]

C:\Windows\system32>certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_10.0.14393.0_sr-..-cs_25fefef60415aeae\msprivs.dll.mui SHA256
CertUtil: -hashfile command FAILED: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
CertUtil: The system cannot find the file specified.

C:\Windows\system32>certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_10.0.14393.3085_sr-..-cs_6e59d3a647e83e6c\msprivs.dll.mui SHA256
CertUtil: -hashfile command FAILED: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
CertUtil: The system cannot find the file specified.

C:\Windows\system32>certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_10.0.14393.3143_sr-..-cs_6e4b302247f3c1bf\msprivs.dll.mui SHA256
SHA256 hash of file C:\Windows\WinSxS\wow64_microsoft-windows-lsa-msprivs.resources_31bf3856ad364e35_10.0.14393.3143_sr-..-cs_6e4b302247f3c1bf\msprivs.dll.mui:
cd0ec3099c0c22d9a385b8eb8db29a12ac03874c76610a53675015c90a50413b
CertUtil: -hashfile command completed successfully.

 

[Maxstar]

Here's the next fix.

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

 

[EPLTechBH]

Error: 14098

The component store has been corrupted.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

 

[Maxstar]

Please run the following commands in an elevated prompt and post the result:

certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-m..ecore-winrt-storage_31bf3856ad364e35_10.0.14393.1770_none_824e8e4a924927c5\windows.storage.dll SHA256
certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-m..ecore-winrt-storage_31bf3856ad364e35_10.0.14393.3085_none_829acfec920ff7f8\windows.storage.dll SHA256
certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-m..ecore-winrt-storage_31bf3856ad364e35_10.0.14393.3115_none_8288fdfa921e6288\windows.storage.dll SHA256

 

[EPLTechBH]

C:\Windows\system32>certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-m..ecore-winrt-storage_31bf3856ad364e35_10.0.14393.1770_none_824e8e4a924927c5\windows.storage.dll SHA256
CertUtil: -hashfile command FAILED: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
CertUtil: The system cannot find the file specified.

C:\Windows\system32>certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-m..ecore-winrt-storage_31bf3856ad364e35_10.0.14393.3085_none_829acfec920ff7f8\windows.storage.dll SHA256
CertUtil: -hashfile command FAILED: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
CertUtil: The system cannot find the file specified.

C:\Windows\system32>certutil -hashfile %systemroot%\WinSxS\wow64_microsoft-windows-m..ecore-winrt-storage_31bf3856ad364e35_10.0.14393.3115_none_8288fdfa921e6288\windows.storage.dll SHA256
SHA256 hash of file C:\Windows\WinSxS\wow64_microsoft-windows-m..ecore-winrt-storage_31bf3856ad364e35_10.0.14393.3115_none_8288fdfa921e6288\windows.storage.dll:
4fca527fe2c59ba96778e9ba64e9a3d4cb693ad2d1dfa5285ed1d0795c37b6ba
CertUtil: -hashfile command completed successfully.

 

[Maxstar]

Result from a previous log:

The following actions will be performed:
    Regeneration Candidates: 1418
    Removal Candidates: 96899
    Superseded/LDR (Delta Compression) Candidates: 6277

Latest log:

The following actions will be performed:
    Regeneration Candidates: 1324
    Removal Candidates: 96899
    Superseded/LDR (Delta Compression) Candidates: 6230

It seems we make some progress but it looks like we have to deal with a number of remaining corruptions...

Here's the next fix.

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

 

[EPLTechBH]

Error: 14098

The component store has been corrupted.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

 

[Maxstar]

The previous fix failed!

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

 

[EPLTechBH]

It took a really long time for DISM to finish, but it seems to have worked!

The operation completed successfully.

 

[Maxstar]

Hi,

That's great news!

1. Open an elevated prompt and run the following command, copy and paste the result in your next post to check the current size of the Components Store.

DISM /online /cleanup-image /AnalyzeComponentStore

2. Run

ComponentsScanner again.

• Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
• Follow the on-screen instructions.
• Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
• Post the logfile ComponentsScanner.txt as attachment into your next reply.

 

[EPLTechBH]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 10.65 GB

Actual Size of Component Store : 10.46 GB

    Shared with Windows : 6.97 GB
    Backups and Disabled Features : 3.40 GB
    Cache and Temporary Data : 87.55 MB

Date of Last Cleanup : 2024-09-09 14:39:40

Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : No

The operation completed successfully.

 

[Maxstar]

Windows Explorer Reported Size of Component Store : 75.91 GB

Actual Size of Component Store : 62.94 GB

    Shared with Windows : 7.29 GB
    Backups and Disabled Features : 40.51 GB
    Cache and Temporary Data : 15.12 GB

Great, this looks much better than the previous data / logs. Here's the next fix for the latest warnings which may cause the same (Error: 14098) issue in the future!

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

step 3. Run

ComponentsScanner again.

• Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
• Follow the on-screen instructions.
• Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
• Post the logfile ComponentsScanner.txt as attachment into your next reply.

 

[EPLTechBH]

The operation completed successfully.

 

[Maxstar]

Please run the following command again and post the result:

DISM /online /cleanup-image /StartComponentCleanup

 

[EPLTechBH]

The operation completed successfully.

 

[Maxstar]

Great, this server is already on the latest build (14393.7259) so I would wait for the next Cumulative Update which will be released today I guess. So let me know if it installed successfully or if there are still remaining issues.

 

[EPLTechBH]

I ran updates this morning and everything seems to be working. Thank you so much Maxstar!!!

 

[Maxstar]

Hi,

You're welcome. Glad to hear the latest update installed successfully.
I will mark this thread as solved.