DISM Not finding source

Question

I am having some difficulty with DISM, and it appears that nothing that I do will resolve the issue.
I confirmed that the server in question and the image that I am using for the WIM repair are of the same build - 14393.4169 however every time I run DISM it fails with an error indicating that it cannot find the source.

The source is mounted as E: and is the Windows Server 2016 Standard x64 ISO evaluation downloaded directly from Microsoft.

C:\Windows\system32>dism.exe /online /cleanup-image /restorehealth /Source:E:\Sources\install.wim:1

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================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 http://go.microsoft.com/fwlink/?LinkId=243077.

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

C:\Windows\system32>dism.exe /online /cleanup-image /restorehealth /Source:E:\Sources\install.wim:1 /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================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 http://go.microsoft.com/fwlink/?LinkId=243077.

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

C:\Windows\system32>dism.exe /online /cleanup-image /restorehealth /Source:E:\Sources\install.wim /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================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 http://go.microsoft.com/fwlink/?LinkId=243077.

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

The DISM log is showing the same error.
2021-02-11 07:50:00, Error DISM DISM Package Manager: PID=5520 TID=9676 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
2021-02-11 07:50:00, Error DISM DISM Package Manager: PID=5520 TID=9676 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2021-02-11 07:50:00, Error DISM DISM Package Manager: PID=5520 TID=9676 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
2021-02-11 07:50:00, Error DISM DISM Package Manager: PID=5520 TID=9676 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2021-02-11 07:50:00, Error DISM DISM Package Manager: PID=5520 TID=9676 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
2021-02-11 07:50:00, Error DISM DISM Package Manager: PID=5520 TID=9676 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

If you look up above at the syntax of my DISM, I am using the /source option. What the heck, Microsoft?
Anyone else run into this?
I could use some assistance.

Thanks,
Joseph

Answer 1

MotoX80 and Dale,

Thank you for your responses.
I started with Dale's suggestions.
I tried option 1 and received an error.

C:\Windows\system32>dism.exe /online /cleanup-image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================100.0%==========================]

Error: 2

The system cannot find the file specified.

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

I started looking at option 2.
DISKPART> list volume

Volume ### Ltr Label Fs Type Size Status Info

---

Volume 0 D DVD-ROM 0 B No Media
Volume 1 E SSS_X64FREE UDF DVD-ROM 6649 MB Healthy
Volume 2 C NTFS Partition 126 GB Healthy Boot
Volume 3 Recovery NTFS Partition 450 MB Healthy Hidden
Volume 4 FAT32 Partition 99 MB Healthy System

As above in the initial post, I was called the ISO on the E: drive.
Ran: dism.exe /online /cleanup-image /restorehealth /source:WIM:E:\sources\install.wim:1 /LimitAccess
The result was unfortunately the same.
C:\Windows\system32>dism.exe /online /cleanup-image /restorehealth /source:WIM:E:\sources\install.wim:1 /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================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 http://go.microsoft.com/fwlink/?LinkId=243077.

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

So neither of Dale's options to try worked. Any other ideas Dale?

Next I looked at MotoX80's suggestion and it resulted in the same output.
C:\Windows\system32>dism.exe /online /cleanup-image /restorehealth /source:WIM:E:\sources\install.wim:2 /LimitAccess

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================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 http://go.microsoft.com/fwlink/?LinkId=243077.

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

So, we are back to any ideas to resolve this issue?
It is possible to separately mount the WIM file and then use that as the source instead of using the mounted ISO of the Windows Server 2016 disc?

Thanks,
Joseph

Answer 2

Try this.

md C:\test\offline 
DISM.exe /Mount-Wim /WimFile:e:\sources\install.wim /index:2 /MountDir:C:\test\offline /ReadOnly
Dism.exe /Online /Cleanup-Image /restoreHealth /source:C:\test\offline /loglevel:4

When you are done.

DISM.exe /Unmount-Wim /MountDir:C:\test\offline /discard

I added the loglevel in the hope that if it fails again, there might be something useful in C:\WINDOWS\Logs\DISM\dism.log

Answer 3

@Joseph Rapoport
Can you confirm if the issue resolved with MotoX80's advice
I am on the same boat
md C:\test\offline
DISM.exe /Mount-Wim /WimFile:e:\sources\install.wim /index:2 /MountDir:C:\test\offline /ReadOnly
Dism.exe /Online /Cleanup-Image /restoreHealth /source:C:\test\offline /loglevel:4

When you are done.

DISM.exe /Unmount-Wim /MountDir:C:\test\offline /discard

I added the loglevel in the hope that if it fails again, there might be something useful in C:\WINDOWS\Logs\DISM\dism.log

Answer 4

This failed for me with

Error: 14

Not enough storage is available to complete this operation.

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

Plenty of space on the C drive, and plenty of RAM. So. Unclear why it failed.

And this seems pertinent from %WINDIR%\logs\CBS\cbs.log

Checking System Update Readiness.

(p) CSI Payload Corrupt amd64_microsoft-windows-t..-licensingadminpack_31bf3856ad364e35_10.0.14393.2515_none_b9d230ab0a3952a7\RD Licensing Manager.lnk
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-t..tion-snapin-nonmsil_31bf3856ad364e35_10.0.14393.4046_none_8ea1960065bd174d\Remote Desktop Licensing Diagnosis.lnk
Repair failed: Missing replacement payload.

Summary:
Operation: Detect and Repair
Operation result: 0x8007000e
Last Successful Step: Entire operation completes.
Total Detected Corruption: 2
CBS Manifest Corruption: 0
CBS Metadata Corruption: 0
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 2
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True

Total Operation Time: 764 seconds.

Answer 5

I am having this exact issue with 2 separate servers. 1 is a 2016 and the other a 2019 os. Going to try Motox method and report back shortly