rudrax Posted May 26, 2017 Share Posted May 26, 2017 To cut the long story short, please view the following image and tell me what in the name of Chuck Noris is going wrong! Link to comment Share on other sites More sharing options...
Togijak Posted May 26, 2017 Share Posted May 26, 2017 https://lmgtfy.com/ Quote If you get the error message "cannot find source files"you need to have an ISO file mounted and need to specify where it is located with the below command DISM /Online /Cleanup-Image /RestoreHealth /source:WIM:X:\Sources\Install.wim:1 /LimitAccess Where "X" is the drive letter where the ISO is located. Simply change the "X" to the correct drive letter Link to comment Share on other sites More sharing options...
tomm Posted May 26, 2017 Share Posted May 26, 2017 /source:WIM:G:\sources\install.wim:1 NOT /source:G:\sources\install.wim:1 Link to comment Share on other sites More sharing options...
rudrax Posted May 26, 2017 Author Share Posted May 26, 2017 Thank you guys. I will try and report back. Link to comment Share on other sites More sharing options...
rudrax Posted May 26, 2017 Author Share Posted May 26, 2017 Link to comment Share on other sites More sharing options...
tomm Posted May 26, 2017 Share Posted May 26, 2017 2 hours ago, rudrax said: OK why don't you try executing /RestoreHealth command without specifying /Source and /LimitAccess so DISM will get repaired files from WU? I think that Windows image still contains corrupted files dism /online /cleanup-image /restorehealth Link to comment Share on other sites More sharing options...
rudrax Posted May 26, 2017 Author Share Posted May 26, 2017 30 minutes ago, tomm said: OK why don't you try executing /RestoreHealth command without specifying /Source and /LimitAccess so DISM will get repaired files from WU? I think that Windows image still contains corrupted files dism /online /cleanup-image /restorehealth I have tried this command line with data off. It failed as it couldn't connect to the WU. Tomorrow I will try with data ON. BTW, the windows image which I have specified as repair source is completely fine. I have formatted many laptops with that source. Link to comment Share on other sites More sharing options...
tomm Posted May 26, 2017 Share Posted May 26, 2017 21 minutes ago, rudrax said: I have tried this command line with data off. It failed as it couldn't connect to the WU. Tomorrow I will try with data ON. BTW, the windows image which I have specified as repair source is completely fine. I have formatted many laptops with that source. No, I mean these corrupted files have already presented in original Windows image (it's Microsoft's fault to make files corrupt) Link to comment Share on other sites More sharing options...
straycat19 Posted May 26, 2017 Share Posted May 26, 2017 10 hours ago, rudrax said: To cut the long story short, please view the following image and tell me what in the name of Chuck Noris is going wrong! You mean what is going wrong other than you misspelled Chuck's name? It's Norris. As far as DISM goes, no shot in the dark. This is a common problem with Windows 10 and the fix is listed on this website. You can say you don't want to do a specific fix but these are the only ways you can fix your problem. https://appuals.com/fix-dism-restorehealth-error-0x800f081f/ Link to comment Share on other sites More sharing options...
mikie Posted May 26, 2017 Share Posted May 26, 2017 Microsoft fixed that error ... allow and run windows updates, maybe you will get the fix. an updated .mum file. Or run the dism offline, after making a Scratch folder, something like this; dism /image:c:\ /cleanup-image /restorehealth /source:wim:d:\Sources\install.wim:1 /scratchdir:c:\Scratch Link to comment Share on other sites More sharing options...
straycat19 Posted May 26, 2017 Share Posted May 26, 2017 1 hour ago, mikie said: Microsoft fixed that error ... allow and run windows updates, maybe you will get the fix. an updated .mum file. Or run the dism offline, after making a Scratch folder, something like this; dism /image:c:\ /cleanup-image /restorehealth /source:wim:d:\Sources\install.wim:1 /scratchdir:c:\Scratch I noticed one thing that has caused problems in the past. The name is Install.wim not install.wim. The capital I has caused errors in other cases. Link to comment Share on other sites More sharing options...
Clusterphuck Posted May 26, 2017 Share Posted May 26, 2017 Online DISM will fail in the Creators Update because Microsoft "accidently" shipped the CU with a test FlightSigning package with a wrong signature. Offline DISM will pass though. https://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-10-creator-update-1703-build-15063138-has/804efb8b-ba6b-40cb-a151-1f372b5c4227 http://borncity.com/win/2017/04/26/windows-10-v1703-fix-for-dism-error-0x800f081f/ I've personally removed the FlightSigning package files and registry keys from my install, and now online DISM works fine again. Link to comment Share on other sites More sharing options...
mikie Posted May 26, 2017 Share Posted May 26, 2017 6 hours ago, straycat19 said: I noticed one thing that has caused problems in the past. The name is Install.wim not install.wim. The capital I has caused errors in other cases. fwiw; Windows10_InsiderPreview_EnterpriseVL_x64_en-us_15063.iso uses lower case i.on the install.wim Link to comment Share on other sites More sharing options...
mikie Posted May 26, 2017 Share Posted May 26, 2017 2 minutes ago, Clusterphuck said: I've personally removed the FlightSigning package files and registry keys from my install, and now DISM works fine. I did that too... then replaced the registry keys and restarted, windows downloaded and replaced the removed .mum and other total 4 files and RestoreHealth works 100% fine. Link to comment Share on other sites More sharing options...
rudrax Posted May 27, 2017 Author Share Posted May 27, 2017 17 hours ago, straycat19 said: You mean what is going wrong other than you misspelled Chuck's name? It's Norris. As far as DISM goes, no shot in the dark. This is a common problem with Windows 10 and the fix is listed on this website. You can say you don't want to do a specific fix but these are the only ways you can fix your problem. https://appuals.com/fix-dism-restorehealth-error-0x800f081f/ To fix a problem in windows one have to fix the program that fixes the problem. Damn you microsoft assholes. What the hell you freaks are doing in the development department - watching gay porn 24/7? Disgusting! Link to comment Share on other sites More sharing options...
csmdew Posted May 27, 2017 Share Posted May 27, 2017 17 hours ago, mikie said: I did that too... then replaced the registry keys and restarted, windows downloaded and replaced the removed .mum and other total 4 files and RestoreHealth works 100% fine. Can u provide step by step directions on that method to fix this problem; I can't get the restorehealth to work either and have tried mounting several versions of 10 (including what's on pc) but still have 3 minor errors I would like to get rid of, thanks. Link to comment Share on other sites More sharing options...
xyzdev Posted May 27, 2017 Share Posted May 27, 2017 This issue was fixed last week by Microsoft. You need to run "DISM /Online /Cleanup-Image /RestoreHealth" with internet access once. Then, you will be able to do it offline with .wim/.esd Link to comment Share on other sites More sharing options...
mikie Posted May 27, 2017 Share Posted May 27, 2017 11 minutes ago, csmdew said: Can u provide step by step directions on that method to fix this problem; I can't get the restorehealth to work either and have tried mounting several versions of 10 (including what's on pc) but still have 3 minor errors I would like to get rid of, thanks. Which version of Win10 ? .. I have winver 15063 which is the 1703 Creators release version. I know that all of the 15063 versions are now fixed for a bummed .mum file that shipped and wouldn't let the RestoreHealth command finish saying it couldn't find path .. they have replaced the corrupted .mum file or actually its package on windows servers so that when you do run DISM RestoreHealth on 15063 it replaces that bad .mum file and runs to completion - where before it would run up to about 90% completion and say it couldn't find the path to the Source file. The main thing to replace that bad .mum is to be booted into windows and connected online - run windows updates and while still connected online to run the standard command DISM /Online /Cleanup-Image /RestoreHealth which will connect to Microsoft servers and download and replace any corrupted files. If you cant be connected online you have to boot from a DVD or USB .iso and run the offline DISM command to the correct drive letters which you can run DiskPart / list volume & exit,, to discover the oddly lettered drives that show sometimes when you boot from install media. Then run dism from the booted media... something like this, with corrected paths after making a scratch directory manually; dism /image:c:\ /cleanup-image /restorehealth /source:wim:d:\Sources\install.wim:1 /scratchdir:c:\Scratch Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.