Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Restoring My Pc


  • Please log in to reply
2 replies to this topic

#1 monteiro

monteiro

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:10:23 PM

Posted 27 June 2007 - 03:59 PM

Hello to you all,

I'm new to the forum.
I've a problem, I can not restore my PC. I take every step, choose a point or use one, the PC reboots and then I get the message restore not concluded!!
I use Norton Anti virus.

Can you help on this one?

Many thanks

Miguel

BC AdBot (Login to Remove)

 


#2 bicycle bill

bicycle bill

  • Banned
  • 339 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:05:23 PM

Posted 27 June 2007 - 06:01 PM

Possible causes for restore point failures:

Low free disk space on a System Restore monitored partition. Every restore process involves System Restore creating a restore point prior to the restore operation so that the user can undo the restore process. If you are experiencing failed restores, ensure that there is sufficient free disk space available on all the System Restore monitored partitions.

During the restore process, files to be replaced, moved, or deleted by System Restore are locked by the system or some application causing the restore to fail. This issue has been addressed in Windows XP Service Pack 1.

A corrupt restore point possibly caused by an inconsistency between the file entries in the System Restores file change log and those that are actually backed up or tracked by System Restore. Common causes for this issue:

An improper shutdown of the computer occurred while System Restore was adding an entry for a file to the System Restore change log for tracking. During the process of the file being copied or moved to the restore point directory or elsewhere in the system, a power outage or improper shutdown may have corrupted the process, creating an inconsistency in the change log. Similarly, an entry for the file exists in the change log but the file itself may be corrupt or missing.

Changes made to files on a system from another OS (in case of dual-boot OS scenarios). For example, changes to a key application or system files or simply moving a file System Restore was tracking from one location to another while logged onto a different OS. As System Restore cannot incorporate this change, an inconsistency exists.

Changes made to a System Restore tracked file on a removable drive for a restore point while the drive was connected to another computer. Similar to the above, System Restore cannot incorporate this change. It is important to note that all restore points are linked, therefore, any restore point created prior to the missing or corrupt restore point will also not function.

#3 zbd

zbd

  • Members
  • 390 posts
  • OFFLINE
  •  
  • Local time:04:23 PM

Posted 27 June 2007 - 07:56 PM

Try chkdsk first.

http://support.microsoft.com/kb/315265




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users