Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi people,
Just adding new software to my new PC and
for some reason, I can no longer set Restore
points. It worked fine before. Now, when I try, I get the following message:
"System Restore is not able to create a restore point. Please restart the computer and then run system restore again"
However, a reboot does not help. I also noticed that my last restore point was a week ago. What do we have if this failsafe system is unreliable?
I have today also moved my two hard drives onto the Raid controllers (still set as Eide) instead of the standard Eide controllers. Might this be causal?
The drive letters are the same as they were and they are recognised by serial number, anyway.
Does anyone have any thoughts as to the trouble?
thanks
kevH

Open My Computer and right click on your C: open its properties got to the Tools tab and run Error Checking (Chkdsk). Then reboot and try to set a restore point. If you have multiple partitions run Chkdsk on each of those too.

cheers Jawn,
Tried that. No disk errors,
no improvement with creating
Restore. Any other ideas anyone?regards
kevH

You are only allowed a certain amount of space on your hard drive to store restore points. If you have a lot of restore points, you might want to remove some of the older ones and then try it again.

cheers jcksrobbins,
but the clue is that my machine is
only three weeks old. There is plenty
of space....unfortunatelykevH

yeah,
possibly a wise move, but as
I can't save a restore point,
I also can't undo a restore.This will mean that my PC may
end up in a right mess, and a
full reinstall is not what
I want to do, having just spent
the last few weeks creating it.I'm a bit loathe to do this
at the moment. I'll put up
with it a while longer and
see if anything else turns up.KevH

For anyone else who may have this problem,
According to Knowledge base Q322246,
This issue may occur if the manufacturer's drivers for a HighPoint RAID controller type HPT370, HPT370A, or HPT372 are installed. This issue may occur with driver revisions 2.30 and 2.31, which are not digitally signed.
How to deal with it:
http://support.microsoft.com/default.aspx?scid=kb;en-us;q322246KevH

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |