birdman
Topic Starter
OS: XP Home (sp2)
CHKDSK (with the /r prompt) found a bad sector in Windows. Apparently it was unable to fix it because the same error showed up again on consecutive CHKDSK scan results. The "bad" file is called SimilarityTable_2 (system file - 8,338,608 KB in size) and is located in the following:
C:/ Documents and Settings > Owner > Local Settings > Application Data > Microsoft > Messenger > ([removed]) > SharingMetaData > Working.
Since this is a "system file" (also large in size)….I didn't want to delete it or mess with it.
What's weird is that this particular system file ONLY shows up in that one MSN user account. I have 4 total created accounts/user names…..but NONE of them contain a "SimilarityTable_2" system file.
I even deleted that one MSN user name, but the folder (w/ the system file) still remains in the Messenger folder (see above for location).
Is this SAFE to delete? Can this "bad sector" be repaired? Is there another fix/solution to this matter?
Any help/info would be greatly appreciated. Thanks.
CHKDSK (with the /r prompt) found a bad sector in Windows. Apparently it was unable to fix it because the same error showed up again on consecutive CHKDSK scan results. The "bad" file is called SimilarityTable_2 (system file - 8,338,608 KB in size) and is located in the following:
C:/ Documents and Settings > Owner > Local Settings > Application Data > Microsoft > Messenger > ([removed]) > SharingMetaData > Working.
Since this is a "system file" (also large in size)….I didn't want to delete it or mess with it.
What's weird is that this particular system file ONLY shows up in that one MSN user account. I have 4 total created accounts/user names…..but NONE of them contain a "SimilarityTable_2" system file.
I even deleted that one MSN user name, but the folder (w/ the system file) still remains in the Messenger folder (see above for location).
Is this SAFE to delete? Can this "bad sector" be repaired? Is there another fix/solution to this matter?
Any help/info would be greatly appreciated. Thanks.