Cambridge PC Support
Well-Known Member
- Reaction score
- 73
- Location
- Cambridge UK
I know it can't just be me, but on XP/Vista/7, quite often I want to run a chkdsk on the system drive as a last check, and also as a first check after cloning a failing system drive.
So the way I run it is to fire up a cmd prompt and type in chkdsk c: /f/r/v, it can't do it on a running drive so hit 'y' for doing it on the bounce, then exit the the cmd prompt and reboot
I'd say about 7 out of 10 times the PC reboots without running the chkdsk at all, or it comes up and instantly declares the drive to be clean. So I have to run thru the whole thing again.
So what I tend to do is type in the chkdsk on the cmd prompt, then wait about 20 seconds, then exit, then wait 20 seconds then reboot. It's almost as if it doesn't register properly.
Anyone else?
So the way I run it is to fire up a cmd prompt and type in chkdsk c: /f/r/v, it can't do it on a running drive so hit 'y' for doing it on the bounce, then exit the the cmd prompt and reboot
I'd say about 7 out of 10 times the PC reboots without running the chkdsk at all, or it comes up and instantly declares the drive to be clean. So I have to run thru the whole thing again.
So what I tend to do is type in the chkdsk on the cmd prompt, then wait about 20 seconds, then exit, then wait 20 seconds then reboot. It's almost as if it doesn't register properly.
Anyone else?
