I suggest you do a quick format because a full format can take forever. Then run the cmd command chkdsk /f - that will fix possible bad sectors [. . .]
Always better to not leave incorrect info in a thread, regardless of age. People come here and read these things pretty much forever as a result of their Google search results, and what is past is prologue. Pretty deep huh?
"CHKDSK /F" will not repair bad sectors. It deals with various types of file system integrity errors and can fix logical file system errors, but not bad sectors. Think of the "/f" as meaning "file integrity", and consisting of the first layer of cleanup, CHKDSK "Level 1" if you like.
That's where "CHKDSK /R" comes in... it not only deals with everything "CHKDSK /F" does, it also adds bad sectors to the list, identifying them and attempting to deal with them. Think of the "/r" as meaning "repair" (as in bad sectors) and consisting of a second, more in depth layer of cleanup... it's like CHKDSK "Level 2".
Since the "/r" argument deals with all the same stuff as "/f" plus more, there's no reason to include "/f" with the "/r" argument, even though CHKDSK will let you and won't return an error if you issue both parameters. It's just redundant, because you're saying to it "Do a Level 2 cleaning job, but also do a Level 1 cleaning job."
Last edited:
My Computer
- OS
- Windows® 7 (64-bit)
- CPU
- intel® Core™ i5-4690 @ 3.50 GHz
- Motherboard
- GIGABYTE™ H97-D3H
- Memory
- 8 GB DDR3