System Restore can't restore to a previous Restore Point?

[Chuck Dreier]

Help please. System Restore is creating restore points. When I attempt to
roll back, the files appear to decompile (or whatever they do), and then I'm
asked to Restart. Once the computer restarts, there is always a message
that System Restore wasn't able to return to the previous point. Any idea
why this is happening, and what can be done about it? BTW, I've checked the
MS Knowledge Base but haven't been able to find anything. Thanks!

 

[Jupiter Jones [MVP]]

Chuck;
There may be corrupted data in system Restore.
Turn off/on System Restore to delete corrupted files:
Start/All Programs/Accessories/System Tools/System Restore.
Click System Restore Settings on left side.
Check "Turn off System Restore", click OK, follow prompts and reboot.
This deletes ALL Restore Points including corruption.
Then go back and turn on system Restore and create a Restore Point.
Otherwise:
http://www.microsoft.com/technet/community/newsgroups/faqsrwxp.mspx

 

[Chuck Dreier]

That did the trick. Something must have been corrupted. Thanks for your
help!!!!

 

[Alex Nichol]

That did the trick. Something must have been corrupted. Thanks for your
help!!!!

One point that may help for the future. By Default SR is allowed up to
12% of each drive - on modern big ones this seems to be too much for its
own good. Go to System - System restore, highlight the drive and take
settings; reduce to somewhere I suggest under 1GB - I find 500MB
adequate for a couple of weeks of normal restore points

 

[Jupiter Jones [MVP]]

Alex;
I never thought of that.
Is that your experience or is there a reference somewhere?

I may start asking on this issue how large a hard drive is.

--
Jupiter Jones [MVP]
http://www3.telus.net/dandemar/


One point that may help for the future. By Default SR is allowed up
to

 

[Alex Nichol]

Alex;
I never thought of that.
Is that your experience or is there a reference somewhere?

I may start asking on this issue how large a hard drive is.

It's a strong suspicion, based on putting the problems people have
together. I suspect it is a bit like the overload of indexes in Temp
Internet files. With the way it chains a succession of points, the more
there are the more chance of a foul up - and it certainly appears that
once it *has* fouled up the only course is to clear out and start over.
And in any case 10 plus GB of restore points is a pretty unnecessary
load on the disk