Windows 10: Windows 10 Powershell DISM RestoreHealth error 0x800f081f

Hello everyone. This is my first time here so I'm hoping I'm in the right section and that the title is clear and all that. So basically I had some trouble with viruses a while back. I did manage to get rid of them (I think) but my PC has been a bit odd since then. For starters the Start Menu wont open, neither will the Search window. I also can't right click anything on the....actually I'm not sure what it's called but the Start bar at the bottom of the screen. I checked online for help and found the RestoreHealth command of Powershell, so I tried it out. However I ran into the error in the title of this thread. I went through the logs and found this:

2016-12-29 11:34:03, Error DISM DISM Package Manager: PID=4216 TID=5304 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)2016-12-29 11:34:03, Error DISM DISM Package Manager: PID=4216 TID=5304 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg2016-12-29 11:34:03, Error DISM DISM Package Manager: PID=4216 TID=5304 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)2016-12-29 11:34:03, Error DISM DISM Package Manager: PID=4216 TID=5304 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg2016-12-29 11:34:03, Error DISM DISM Package Manager: PID=4216 TID=5304 Failed to restore the image health. - CPackageManagerCLIHandler:rocessCmdLine_CleanupImage(hr:0x800f081f)2016-12-29 11:34:03, Error DISM DISM Package Manager: PID=4216 TID=5304 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

These were the only lines marked with "Error". The problem is I don't really know where to go from here. Any and all help is greatly appreciated! Thank you.

:)

 

DISM ‘restorehealth’ error 0x800f081f

16299 is what is important the .248 or other doesn't matter with dism the original dism.exe will stay the same 16299.15 until the Spring build is finalized about the end of april. Then its number might be 180xx.15

Problem looks like you are actually missing a windows file & running Dism against the iso hopefully will replace that missing or corrupt file with a new copy from the iso.

 

DISM ‘restorehealth’ error 0x800f081f

So you're saying that if I did do the media creation tool, then created an ISO then did the instructions that you gave me will fix the problem?

And also can I save the iso file (the created Windows ISO) in a drive is that is not empty?

 

You need to supply access to the install.wim or install.esd for the image that matches your installed version of Windows 10. It has to be the same version (probably 1607), same bittedness (32-bit or 64-bit), and same base language. You can download the ISO from the Windows ISO source and then right-click and mount it as a drive. Let's say this is drive J: Thus, your DISM syntax should be

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

if it's an .esd file (which it shouldn't be if you get the ISO from the recommended download point) change the WIM to ESD and the .wim in the filename to .esd

HTH and good luck. If this fails, you might need to change the number after the filename to :2 insead of :1.

And BTW, there's a great tutorial on this subject here at TenForums, too: https://www.tenforums.com/tutorials/...-10-image.html
--Ed--

 

Hello Ed, thank you very much for responding! Unfortunately your solution did not seem to work. I tried it with the value set to 1 and 2 and I get the exact same error, with the exact same text in the logs. I'll search through that guide you linked (thank you for that as well) but as of right now my problem is still not fixed.

 

Had this issue just pop up on my stable Windows build. Tried my .iso and .esd and even downloaded the .iso from Microsoft. Finally resolved it with a clean install (repair install may well have worked).

 

Personally I went round and round on this with one of my machines earlier this year. Turns out I thought I'd installed en-US but had installed en-GB instead. I couldn't get DISM to work until I used an ISO for en-GB on that machine. It may be something weird and unexpected like that, so check everything...TWICE!
*Devil
--Ed--

 

It might very well be something like that. I don't quite understand the different options on the ISO page actually. Like what is "Windows 10 N" and "Windows 10 Single Language"? Also my computer language is UK English but again on the ISO site it has English listed as "English" and "English International". Pardon my language but what in the actual **** is that supposed to mean? I assumed that "English" was the UK one, but I might very well be wrong there. I'll just look around the internet to see if I can figure out what I'm supposed to select, thank you again for your quick and informative answers!

EDIT: After some searching it seems that the English International option does indeed stand for the UK English, or as it's more commonly known; English! Will try again with the new ISO.

EDIT 2: Nope, still didn't work *cry

 

Hi,

DISM doesn't handle .ESD file well. Best is to try the .WIM version.

The error code generated points to a version mismatch.

To check the .WIM version run this code from command prompt (Admin):

Code: dism /Get-WimInfo /WimFile:E:\sources\install.wim /index:1[/quote] Replace E:\ with the corresponding drive letter.

Cheers, *Wink

 

I am guessing that once you succeed in matching the wim file you target in the /source attribute to the image running on your PC, repairs will go through. Follow Frank's (fdegrove's) advice on how to identify your source info. Try this command to see what you online environment is/has: dism /online /get-intl. Here's mine:



HTH,
--Ed--

 

The problem has been fixed! *Biggrin What did it for me was manually updating Windows through microsofts website. Having said that though it turns out all the different ISO files I had were indeed wrong. Not only the language but the actual version of Windows itself. For some reason my Windows had not updated itself to 1607, so I was stuck with 1511, which of course meant that no matter what language I selected it would've always been the wrong version. In conclusion I'm quite certain the solutions posted in this thread WOULD have worked if I had the correct ISO file *Smile.

Thank you SO MUCH to everyone who's contributed to this thred! Especially EdTittel, your expertise and patience are truly legendary my friend. Happy New Years to you all!!

 

You're welcome. I've still got the lumps that DISM handed out to me this summer, so happy to help others avoid the head-banging against the wall that inflicted them. Happy New Year, too.
--Ed--