Main Forum > Tweaking.com Support & Help
Windows Repair task 04 (Register System Files) clobbering Vista VSS??
GLykos:
Thanks for having exercised this. The problem continues at my end.
- Updated to WR 3.8.1.
- Ran task 19 (repair VSC service) only, rebooted - initiating create restore point ends in same "catastrophic failure".
- Ran tasks 1-4, 19 for grins, rebooted - initiating create restore point ends in same "catastrophic failure".
vssadmin list writers still returns blank.
This is a docked Dell laptop E6400 running Vista Business with all updates.
Would be happy to assist with further information and/or actions if/as helpful.
Note that I received forum e-mail notification of Boggin's acknowledgement of my original post but none since - happened to revisit the thread and discovered the ensuing exchange.
Thanks all, and regards,
George
Willy2:
- Did you try "Beta System Restore" ? there's a button in the bottom right hand corner that opens "BETA Repairs" and leads you to the "BETA System Restore Repair". Try it (with the usual precautions (backup etc.)) and perhaps it could help.
- It seems you didn't run all repairs. Try running all repairs. All repairs would include "Repair WMI" and WMI is used to pull up A LOT OF info from your system.
GLykos:
Correct - I first tried the fix approach described above and reported as successful, which was just the VSC Service repair. I then looped around and tried the fuller sequence, i.e. (re?)break it by (re)registering all services and then fixing it. Neither worked for me.
Thanks for your several suggestions re what to try next. Will exercise this over the next several days and report back.
Shane:
Interesting. For me, in vista in my vmware I was able to replicate the problem every time I registered the system files and was able to fix it every time I ran the vss repair.
Then when i made the changes to the order of the dlls in the register system files i was no longer able to replicate the problem.
Of course one thing I didnt do, since my vista is bare bones with no 3rd party programs I ran the repairs in normal mode and not safe mode. Not sure if that would have anything to do with it.
Shane
GLykos:
Well, have worked on this a bit - have more questions than answers, both in relation to the status of affairs on my computer and what WR is doing or not doing.
As approximately suggested above, tried a relatively full repair set: tasks 1,2,3,4,5,7,19. Watching the CMD window, see a lot of errors go flashing by during the WMI repair. The associated log file shows repeated occurrences of some same nature of error - don't know what's to be done with it. Most of the log files, attached, show almost nothing and little detail (because "output suppressed to speed up execution" when in fact numerous errors were reported during execution of various repairs. Interrupting the WMI execution, can't get Snipping Tool to save a capture so manually transcribe one line to a text file, attached. System32\config\systemprofile\AppData\Local\Application Data\Application Data\Application Data ad nauseum is hosed (I presume) - directory capture attached. So in the case of WMI, two different sets of errors that don't intersect - in the case of IE repair, "batch file not found" - which batch files?. The VSC service repair log says the service is not started. Check the Services viewer, see it's in manual - after running the repair?
Try running the same repair set one more time, this time adding task 26 wondering how this interacts with VSC service repair leaving it in manual and stopped. Then checked again, is still in manual and stopped - the normal state?
So long story short, issues have cropped up in my system, from appearances over iterations with time. WR isn't feeding through the run-time errors it encounters (may be operator error), system issues continue to exist and indications are discarded when abnormal things occur during repair. Not sure how to best approach this, but sure wish I could get a report of all encountered repair run-time issues to at least get a feeling for scope of corruption. Would appreciate any other thoughts on how to best proceed.
Thanks, and regards,
George
P.S. Remembering the suggestion to try Beta Repair, looped back, read about it, ran it. No change in system behavior re create restore point catastrophic failure.
P.P.S. In looking through backups to see what was in Application Data previously, realize that AppData/Roaming and Application Data are tied together as/in (?) a junction, related to a reparse point (in my limited understanding). I do recall on one or more earlier WR repairs having stepped through Option 2 Pre-Scan, and it once having mentioned something related to reparse point corrective actions. Don't know if related to the oddball recursing hierarchy down to the System32 config etc. IE Restore folder.
P.P.P.S Updated attachment to include omitted directory pic as intended.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version