How to troubleshoot System Restore issues in Windows XP.

Question

I recieve... application has problem needs to close , when I try useing system restore.these are the first two things listed [there are more] from the error report ....appname rstru.exe , modname srrstr.dll. how can I fix this?

Answer

This question was answered on June 10, 2005. Much of the information contained herein may have changed since posting.

To troubleshoot System Restore issues, use one or more of the following methods:

• If you receive an error message that is related to System Restore, always make sure that you first record the error message, and then follow the instructions that the error message contains to try to resolve the issue.

Most System Restore issues generate an error message that contains a description of the issue and suggestions for how to resolve the issue.

• Make sure that you have sufficient disk space on all the drives where System Restore is enabled.

• Make sure that the System Restore service is running. To do this, use one of the following methods:

• Look in Control Panel. To do this, follow these steps:

1. Click Start, click Run, and then type compmgmt.msc in the Open box.

2. Expand Services, and then click System Restore Services.

• Open a command prompt window. To do this, follow these steps:

1. Click Start, click Run, and then type CMD.

2. Press ENTER, and then type Net Start at the command prompt to make sure that the System Restore service is up and is running.

• Make sure that System Restore is enabled on the drives where you want System Restore enabled.

• Try to run System Restore in Safe Mode.

• If you suspect that you do not have as many restore points as you should have, make sure that the data store is the size that you want the data store to be.

• View the event logs to investigate System Restore service errors. To do this, follow these steps:

1. Click Start, click Control Panel, and then click Performance and Maintenance.

2. Click Administrative Tools, click Computer Management, double-click Event Viewer, and then click System.

3. Click the Source tab to sort by name, and then look for "sr" or "srservice." Double-click each of these services, and then evaluate the event description for any indication of the cause of the problem.

GOOD LUCK!

Author

Posted by Kisha of Katharine Gibbs School - New York on June 10, 2005