DISM Error 0x800f081f

G

gpm

Member
Joined
Jan 2, 2016
Posts
5
Since installing the "Creators Update", the command "DISM /online /cleanup-image /restorehealth" returns error code 0x800f081f with this info:- 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.

SFC fix results are attached.View attachment SFCFix.txt

After looking around the web, I used the windows media creation tool to get an ISO image and tried DISM with the following command C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth /source:ESD:J:\ESD-ISO\sources\install.esd:1 /limitaccess, but it didn't work. I've tried converting the install.esd file to install.wim and placing it in the root directory with the command C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth /source:WIM:C:\install.wim:1 /limitaccess but that didn't work.


So I must be doing something wrong! Any suggestions would be appreciated. Thanks, Greg.
 
The only possible mistake I see is
Code: 
dism /online /cleanup-image /restorehealth /source:ESD:[COLOR="#FF0000"][B]J:\ESD-ISO\sources\install.esd[/B][/COLOR]:1 /limitaccess
Shouldn't it be J:\sources\install.esd instead? ESD-ISO is just the name of the ISO. Or are you not mounting the ISO?

I just did
Code: 
dism /online /cleanup-image /restorehealth /source:ESD:F:\sources\install.esd:1 /limitaccess
and it still failed, so this seems like a Windows Creators Update issue rather than an issue on your system.

Code: 
PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth /source:ESD:F:\sources\install.esd:1 /limitaccess

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[===========================89.3%===================       ]
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 informat
ion 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 joined this forum just to comment and hopefully get some decent, relevant help, on this exact issue.

My machine used to boot in under 30seconds before the Creator's Update. Now it takes over 3 minutes to get to the login screen, and another 3 minutes after I log in!

I did like others have done; ran sfc /scannow (came back good) and then dism command.

SFC /Scannow said no issues whatsoever.
DISM says there's one instance of corruption.


I've read and re-read the dang dism.log

I can't find a single reference to an actual file that is corrupted.

In desperation, I deleted the dism log file and re-ran dism.

It still claims there is corruption.

The dism.log file still doesn't appear to me to tell me what file is corrupt.


Is there another log file I should be examining?

I also checked the CBS.log file, and see it clearly states there is a single file that is corrupted... but once again, WHAT FILE!?!

I tried to get dism to use the media creation tool downloaded files to a USB drive-
I tried to get dism to use the DVD I burned from the media creation tool-
I tried to get dism to use the pristine, perfect, ISO file I downloaded directly from a nice M$ employee that tried to help me-
always says it can't find the sources.

So I decided to simply run setup.exe from the USB drive. It re-installed Windows 10 on top of itself. The problem is still there.

I wiped the whole dang drive and ran setup.exe from the USB drive. The problem is still there.

I wiped again, ran setup.exe from the DVD. STILL THE SAME PROBLEM.

I am so frustrated right now, as this is a 3 month old laptop that was totally dominating everything I had ever thrown at it. Stupid me, believing M$ when they said Game-Mode would increase FPS in GTA:V. Shortly after actually using that feature, the machine started having major issues. Now, I'm here! :P
 
Deaddude said:
I joined this forum just to comment and hopefully get some decent, relevant help, on this exact issue.
Click to expand...
Seems that there might be some help. Please refer to this post in another forum: Creators update component store shows corruption but unable to repair - Page 3 - - Windows 10 Forums Basically, two registry entries have to be deleted as DISM is unable to find the corresponding source files in the install.esd or install.wim:
1st Loction: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

2nd Location: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]

Exported, then Deleted the 2 Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0 KEYS

ONLY Note: They were already owned by Administrators, but I had to give Administrators Full Control to be able to delete them.
Click to expand...
Unfortunately, this does not seem to work here. The error 0x800f081f still remains.

Kind regards,
DAC324
 
Hi Everyone, i ended up on this forum because SFC wouldn,t complete and ran into

DISM Error 0x800f081f somewhere trying to fix Windows 10 System File Checker


i found this link to fix the problem > Download Windows 10

i installed a newer version of Windows 10

maybe someone here can post the lastest versions

but the one I installed is the 2nd* lastest

Hope this helps someone :-)
 
DAC324 said:
Seems that there might be some help.

Please refer to this post in another forum: Creators update component store shows corruption but unable to repair - Page 3 - - Windows 10 Forums

Basically, two registry entries have to be deleted as DISM is unable to find the corresponding source files in the install.esd or install.wim:

1st Loction: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

2nd Location: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]

Exported, then Deleted the 2 Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0 KEYS

ONLY Note: They were already owned by Administrators, but I had to give Administrators Full Control to be able to delete them.
Click to expand...
Click to expand...
There is one step which has to be completed in addition: Delete or move all files starting with "Microsoft-Windows-TestRoot-and-FlightSigning-Package" in their names, from the C:\windows\servicing\packages folder.

After completing both (editing registry and deleting or moving these files) DISM will be able to run without errors.

Kind regards,
DAC324
 
DAC324 said:
DAC324 said:
Seems that there might be some help.

Please refer to this post in another forum: Creators update component store shows corruption but unable to repair - Page 3 - - Windows 10 Forums

Basically, two registry entries have to be deleted as DISM is unable to find the corresponding source files in the install.esd or install.wim:

1st Loction: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0]

2nd Location: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0]

Exported, then Deleted the 2 Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0 KEYS

ONLY Note: They were already owned by Administrators, but I had to give Administrators Full Control to be able to delete them.
Click to expand...
Click to expand...
There is one step which has to be completed in addition: Delete or move all files starting with "Microsoft-Windows-TestRoot-and-FlightSigning-Package" in their names, from the C:\windows\servicing\packages folder.

After completing both (editing registry and deleting or moving these files) DISM will be able to run without errors.

Kind regards,
DAC324
Click to expand...

That seems to have done the trick on my system. Thanks!

I'll pass this along to the rest of the Sysnative troubleshooting team.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top