[SOLVED] Server 2019 DISM fails

[danrdj]

Although updates are successfully applying, I'm troubleshooting lockup issues and wanted to make sure DISM returned healthy. This seemed like the place to ask about DISM.

SFC /scannow says there's no issues but DISM...

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.4499

[==========================100.0%==========================]
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 Configure a Windows Repair Source.

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

I tried a couple other methods...
Copied the sources folder from the Std 2109 ISO to D:\ and ran this

dism /online /cleanup-image /restorehealth /source:wim:\sources\install.wim:1 /limitaccess

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.

Tried different renditions of this with 2 different ISOs and always got same error

Used a fresh downloaded ISO (eval edition)
Used the ISO already on the server from its 2012 R2 to 2019 upgrade

Used Index 1 and Index 2

Haven't found the winning combo yet!

 

[Maxstar]

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]

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth


Deployment Image Servicing and Management tool
Version: 10.0.17763.3406


Image Version: 10.0.17763.4499


[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

Thanks! I'll see if this clears up the lockup issues. If not, I understand it's probably past the limits of this particular forum.

 

[Maxstar]

Hi,

You're welcome. But I do not suppose the lockups are caused by the missing cat/mum packages which we have replaced. This must be another issue I guess!

 

[danrdj]

You're right! Happy to report I solved the other issue as well -- offsite backup software was accepting a UDP stream of backup files and unable to offload it to a local NAS because it was full. The OS had to hold on to that data mid-stream and started to lockup as memory and pagefile also showed the impact.

 

[Maxstar]

Hi,

Great! Glad to hear you were able to resolve the other issue as well, I will mark this thread as solved then. Let's hope we can resolve the issues on the other server as well, but we're still looking into that case.