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

E

EPLTechBH

Active member
Joined
Dec 20, 2023
Posts
30
Hey there! I've been trying to fix a server that won't update properly, and just a day or two ago stopped being able to allow RemoteApp connections for our users (RDP to desktop still works though). I've been messing around with it all day but nothing helps. Most importantly, "sfc /scannow" finds corruption but can't fix it, and DISM is unable to find a source, even when it's mounted and pointed to explicitly. ComponentsScanner took about 2 hours to run and found many warnings, but no errors. When running SFCFix it either crashes immediately, or it gets to step 6 of the scan and then crashes.

Thanks for your help in advance!
 

Attachments

Hi and welcome to Sysnative,

Here's the first fix with replacement files.

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

DISM Result (Failure):
Code: 
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

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

I've attached a new version of CBS.zip, SFCFix.txt, and also dism.log just in case you need it.
 

Attachments

Here's the next fix with replacment files.

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

DISM Result (Failure):
Code: 
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

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

Attachments

Here's the next fix with replacement files.

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

DISM Result (Failure):
Code: 
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

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

Attachments

Here's the next fix with replacement files.

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

DISM still failed, but it ran about twice as fast as all the previous runs.

DISM Result (Failure):
Code: 
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

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

Attachments

Here's the next fix with the unpacked files which will resolve the latest hash mismatch issue.

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

The DISM command ran successfully!
Code: 
The restore operation completed successfully.
The operation completed successfully.
 

Attachments

Great, please run
61f7aba7309a1-ComponentsScanner_Icon.png
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.
 
Hi,

Open an elevated prompt and run the following command, copy and paste the result in your next post.
Code: 
DISM /online /cleanup-image /AnalyzeComponentStore
 
DISM Result:
Code: 
Component Store (WinSxS) information:

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

Date of Last Cleanup : 2019-09-12 15:50:33

Number of Reclaimable Packages : 1
Component Store Cleanup Recommended : Yes

The operation completed successfully.
 
The current Components Store is pretty big, and partially cleaned up seen the reported warnings.

Please run the following to check on of the warnings and post the result.
Code: 
dir /s /a %systemroot%\WinSxS\amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_10.0.14393.3085_none_a5bd47e8202d6aa2
 
All I got from the command is the following:
Code: 
 Volume in drive C has no label.
 Volume Serial Number is 60A0-6949

 Directory of C:\Windows\WinSxS\amd64_microsoft-windows-t..s-clientactivexcore_31bf3856ad364e35_10.0.14393.3085_none_a5bd47e8202d6aa2

08/23/2023  07:02 AM    <DIR>          .
08/23/2023  07:02 AM    <DIR>          ..
07/16/2016  09:18 AM             2,055 mstscax.mof
09/12/2019  03:14 PM                12 tsgqec.dll
               2 File(s)          2,067 bytes

     Total Files Listed:
               2 File(s)          2,067 bytes
               2 Dir(s)  56,272,678,912 bytes free
 
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