New
#770
Hello @Brink,
Yes, I started off with a valid Win 10 ISO, and then customised it [ Win 10 Pro ] a LOT. I created a bootable USB and installed it. Once installed, I customised it even further with registry tweaks etc. Everything works great.
I do NOT have a problem at present. I just thought I would test out the RestoreHealth from source in case of problems in the future.
I copied the customised ISO to "R" drive, mounted it, which mounted it to "G" drive, and then ran the following cmd . . .
Code:Dism /Online /Cleanup-Image /RestoreHealth /Source:wim:G:\sources\install.wim:1 /LimitAccess
It gave me the following . . .
Thanks in advance.Deployment Image Servicing and Management tool
Version: 10.0.18362.1
Image Version: 10.0.18363.418
[==========================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
@Paul Black,
Just to verify, did you already do step 6A or step 7A in option 2 to make sure you have the correct path and index number for the install.wim or install.esd file?
Thanks for the reply @Brink, it is appreciated.
I know that I can do that as I still have the original ISO. If I was to use that though, what impact will it have on the installed OS considering the fact that I have removed almost all of the apps, onedrive, and made over 100 reg tweaks etc etc etc?
If I was to use the original ISO as the source /RestoreHealth, would it ONLY target the OS system files etc that are installed, or will it try and ADD back those which have been removed either prior to the creation of the customised ISO, or system files that have been removed post installation?
Thanks in advance,