[SOLVED] Server 2016 - SFC fails; DISM source not found

[danrdj]

I'm needing help repairing Server 2016. Updates are installing successfully but we're troubleshooting an issue with backup software which brought us to make sure the OS is healthy. DISM is failing with the familiar "source files could not be found". I've exhausted the options I could find to try to work around it:

Used the original ISO from 2017, and downloaded the new eval ISO from MS. Same results. I'd love to know how to get this to work.

DISM /Online /Cleanup-Image /RestoreHealth /Source:I:\Sources\install.wim
Error: 0x800f081f
The source files could not be found

DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:I:\Sources\install.wim:2 /limitaccess
Error: 0x800f081f
The source files could not be found

DISM /mount-wim /wimfile:"E:\support software\windows server\SSS_X64FREE_EN-US_DV9-latest\sources\install.wim" /index:2 /mountdir:C:\temp\offline
dism /online /cleanup-image /restorehealth /source:C:\temp\offline /loglevel:4
Error: 1734
The array bounds are invalid.

Now when I run the dism /online /cleanup-image /restorehealth without specifying source, it gives the "array bounds" error instead of "source files" -- what changed?

Thanks,
Dan

 

[Maxstar]

2023-11-27 16:11:50, Info                  CSI    0000798c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-t..languages.resources_31bf3856ad364e35_10.0.14393.6451_sl-si_0fcca9869a1e7c64\tipresx.dll.mui do not match actual file [l:15]'tipresx.dll.mui' :
  Found: {l:32 Fex78LUHMrSfgijgfSQ2Uzj546uZSwCvCOWjv/5V/Ys=} Expected: {l:32 Hp1VYxy+jycX9txfY65buGx9QZ4Rc7Awrid/p+GzQh0=}

Hi,

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

 

[danrdj]

Hi Maxstar, after SFCFix, DISM is now successful and SFC found no issues. Thank you!!
Is there any write-up that explains why Windows gets to the point where it can't fix itself with its own built-in tools? I'd very much like to know why even introducing an ISO to DISM usually doesn't cut it these days, in my experience. What's the actual issue?

 

[Maxstar]

Hi,

You're welcome. Glad to hear the issue has been resolved.

See this article for more information how to fix common issues. Unfortunately, it is true that a Windows ISO is not very helpful as source with DISM, this because each ISO contains files for specific builds. So it does not contain files for newer updates for example. Using DISM with another (similiar) server (same patch level and language packs) as source is often more effective.

DISM /Online /Cleanup-Image /RestoreHealth /Source:\\ServerName\C$\Windows\WinSxS\ /LimitAccess