Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,170 questions
no support whatsoever
dism server 2016 cannot find source error 0x800f081f
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 33%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETH%3C/text%3E%3C/svg%3E)
Tarek Halloun
36
Reputation points
hello
I have one server 2016 standard that is having some errors
SFC shows errors that it cant repair
DISM /Online /Cleanup-Image /ScanHealth shows it is repairable
Tried DISM /Online /Cleanup-Image /RestoreHealth and DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:2 /LimitAccess (index 2 is the server 2016 standard GUI) but i get "cannot find source error 0x800f081f"
the server is a VM with SQL , version 1607 build 14393.4889 but in DISM the image version is 10.0.14393.4169 ( it's the last iso i could find )
i get the same error when trying to update (stuck at kb5013952) - manually installing this KB failed as well
what to do ?
6 answers
Sort by: Most helpful
-
-
MotoX80 31,656 Reputation points2022-05-21T14:27:34.813+00:00 Review my reply that starts with "This sequence worked on my Win10 test VM.". Give that a try.
ISO download.
https://www.microsoft.com/en-us/evalcenter/download-windows-server-2016
-
Tarek Halloun 36 Reputation points
2022-05-21T19:14:48.973+00:00 Same error
Even without a local source i dont see any network activity
It reaches to 100%..hangs a bit then the error -
MotoX80 31,656 Reputation points
2022-05-21T23:02:12.79+00:00 Can you share your dism log? Rename C:\Windows\Logs\DISM\dism.log to dism.old. The rerun the dism /restorehealth /source command (that points to the install.wim file). That way the dism.log will only contain the last run.
I kinda doubt that I will find a solution for you, but one never knows. I'm curious to see if what dism is encountering.
-
Tarek Halloun 36 Reputation points
2022-05-22T18:13:10.997+00:00 i forced an cu update by using CAB instead of msu and add package from dism .. SFC is clear now but dism still doesnt work
i attached the new dism log204358-dism.log -
MotoX80 31,656 Reputation points
2022-05-22T22:02:05.997+00:00 You might have to open a case with MS product support to get in contact with the engineers that troubleshoot cases like this. This is beyond my pay grade.
I didn't find what I was hoping to see in your dism log.
Regarding your comment about using a CAB file... I found this post.
Is there an SSU that you can install? (Reinstall?)
https://www.catalog.update.microsoft.com/Search.aspx?q=servicing%20stack%20update%20server%202016
Sign in to comment -
-
Tarek Halloun 36 Reputation points
2022-05-22T22:31:22.307+00:00 the latest ssu is already installed..
-
Tarek Halloun 36 Reputation points
2022-05-22T22:33:15.533+00:00 this is the error i can find , probably wrong version ?
Error code 0x800F081F
This error code can occur when an alternative installation source is specified and one of the following conditions is true:The location that is specified by the path does not contain the files that are required to install the feature.
The user who tries to install the feature does not have at least READ access to the location and to the files.
The set of installation files is corrupted, incomplete, or invalid for the version of Windows that you are running.
To fix this problem, make sure that the full path of the source is correct (x:\sources\sxs) and that you have at least Read access to the location. To do this, try to access the source directly from the affected computer. Verify that the installation source contains a valid and complete set of files. If the problem persists, try to use a different installation source.
-
MotoX80 31,656 Reputation points
2022-05-22T23:06:40.59+00:00 Yeah, I was hoping to see an entry in the log that provided more info, like "you are running 10.0.1234, but your source is 10.0.4567".
But I have discovered that if you point dism to the install.esd on the ISO it will display the build number.
dism /Get-WimInfo /WimFile:D:\sources\install.esd /index:1
You can compare that to Winver on your server. But with patches getting installed all the time, I don't understand how dism resolves the file versions, because whatever you download will almost never match the OS on the server. I don't know if it's better to have a higher level on the ISO or not.
Do you have another healthy 2016 server that is the same build as the broken one? See if you can use that as a source.
Dism.exe /Online /Cleanup-Image /restoreHealth /source:\server\C$\windows