Salta al contenuto principale

Restore to new drive

Thread needs solution

Suffered a drive failure (C:) which I replaced but was unable to restore a working version of Windows XP to the drive and had to reload everything. I restored some of the data from a backup to a second drive (D) and was successful in getting the data I needed. However, I restored some of the folders from the Windows directory in the process (for fonts, etc) and then tried to delete what was left of the Windows directory and was prevented from doing so when Windows (XP) reported that the folder was corrupted and unreadable (There is no way to delete the folder short of a format). I then made a backup of the D drive without the corrupt Windows folder to a third drive (E) and am now planning to format the D drive with the corrupt Windows folder and all of my data. Then I plan to restore the D drive from my backup on my E drive that does not include the corrupt windows folder. My question is, Does this all make sense? I'm trying very hard not to lose all my data in the restore process from the E drive to the D drive or not be able to access that data and restore to another location. I know this sounds complicated but I am an old guy trying to avoid disaster.

0 Users found this helpful

It does make sense.

Maybe if you run a chkdsk /r on your D drive, this will fix the corrupted folder you are trying to get rid of.

What kind of data do you have on D? Only content files? Do you have system and or application files (like a program folder)? These would be harder to deal with.

BTW, if you have just content files, a file copy might just work as a backup before you format your D drive, in particular if this is a lot of pictures, videos (where compression provided by software like Acronis is not reducing size much).

Ran chkdsk and every other check with no success. I proceed as I planned and recovered everything without the offending folder. Lost no data. Acronis saved the day. The only program that helped at all. I never figured out what was going on and probably never will. I think it had something to do with Windows itself and the various folder protection schemes it employs.