I am going to be working on a repair tool for the cat and mum files. It means I will have to have the files on my server so the program can download them, but it would take most of the work out of the users hands, then if some files are not on the server they can let me know, I upload the files and then they just the scan again.
When I first made the pre scan tool I didnt have any repair options for it. But then I realized I had better make something or it is going to be a pain to answer so many forum posts to help with it.
So right now they are separate tools for one reason, they are not fully automated. I didnt make them fully automated (Yet anyways) because of all the different variables out there I am not sure yet if having it on full auto is a good idea. BUT, after a little time goes by and I find that they can safely be ran on full auto then I will change them to just auto repair after the scan is done. That way the users donest have to do much at all.
It is just for right now they are brand new repairs, and so I need more time and testing to see how they do before I put them on autopilot lol
Finally is there any relationship between SFC /Scannow, Dism /Online /Cleanup-Image /StartComponentCleanup and Dism /Online /Cleanup-Image /RestoreHealth and Windows Package files, Reparse Points and Environmental variables (which are supposed to fix Windows Store corruptions) and the Pre Scan and repair options?
The package files, are read and used by Windows updates, the options features in the add/remove programs sections and in the sfc scan and dism.
But the way MS has done it is if there is a single error then it will just bomb out and not move forward. So this is why the features list will show up blank, or an update will refuse to install. All because it couldnt read one of those files. I did some testing where I removed a missing file from the registry so windows wouldnt think to look at it and the updates installed fine.
And why the optional features wouldnt just skip the one that gives and error and move on I dont know. But I found that the packages folder plays a big freaking roll in it all and the sfc doesnt even scan that folder!
So I made a tool to do it instead. The replacing of the cat and mum files is what the system readiness tool from MS does, but you dont have to download a 500 MB file with my tool lol
Here is an example of that
https://technet.microsoft.com/en-us/library/ee619779%28v=ws.10%29.aspxShane