Main Forum > General Computer Support
Re Pre Repairs Scan in version 3
Shane:
Sounds good :-)
Just put out v3.1.0 today. And sometime this week I am going to see if I can trace down what else will be needed for restoring those files :-)
Shane
Shane:
I got an answer and got some working code done yesterday :-)
Windows has a .cat database it keeps. So when checking the .mum files it would pull the signature info from that database.
Well since we added the new .cat files to the folder, those cat files are not in the catalog database, so the windows api cant find what signature the .mum file is suppose to have and so says it is bad.
So I found the proper APIs to call to add a .cat file to the catalog database. I did a test run on my system and it worked great.
So I am not sure what I am going to do with it yet, I might keep it simple and add to the pre scan to auto add the cat files in the folder, but I want to see if I can make a more automated tool for restoring or replacing the files in that folder easier, and if I do that I can have it add the cat files again.
Through the process I also found that the catalog database can become corrupted and I found the repair commands for it, something I will be looking into and see about adding as another repair in a future update :-)
Shane
elw:
That sounds good news especially for all those that have got missing or corrupt files.
One thought - as you have now are able to repair the Reparse Points and the Environmental Variables it seems logical to be able to replace the missing package files (is that possible?) and then to address the corrupt .mum files (as you indicate) either as separate processes or both together if that's possible? Can this be one stage or would it need to be two? It would also be good to be able to obtain or replace any missing Package file via the program rather than having to seek your help via the forums?
Another thought - it seems that Peter might have got confused with the new Pre Scan tool thinking that it would repair automatically. Changing the name (to Pre Scan as you have done would partly solve this I think - from a users point of view anyway). But I wonder whether having the Pre Scan as a separate tool which includes two and soon presumbably, three repair options might not also be confusing as up until Version 3.0.0 the only repair options are contained in the one section (Repairs). Why not include these Pre Scans and then the repairs under the Repairs section say at the beginning? This is what is done under No. 29 "Repair Windows 8 Component Store" i.e Dism /Online /Cleanup-Image /StartComponentCleanup and Dism /Online /Cleanup-Image /RestoreHealth.
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?
I hope you don't mind me continuing with this feed but I am interested in the process; however I do not understand computer programming. That's why I think you made the Windows Repairs program for people like me.
Regards,
Erik
Shane:
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
--- Quote ---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?
--- End quote ---
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.aspx
Shane
elw:
Hi Shane,
Thanks for putting me in the picture - much appreciated. :smiley:
I won't bother you any more as I know you are busy with other people's issues but I will look forward to further developments in the program.
Regards,
Erik
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version