J
Juerg Reimann
Guest
I ran into a mystery with chkdsk that I could verify with a dozen
different Windows XP systems. Chkdsk seems to always find some errors on
the C: drive that need to be fixed with the /F switch while rebooting.
During the reboot chkdsk usually finds nothing but as soon as the system
is up and chkdsk is run against die C: drive again, the game starts from
new.
I bet if someone tries this on a system with all the recent updates, it
will result in the same. But I know it used not to be so, usually if
chkdsk would find errors, after repair it should report a clean file
system.
Does anybody know why chkdsk all over sudden behaves like this?
Thanks, Juerg
different Windows XP systems. Chkdsk seems to always find some errors on
the C: drive that need to be fixed with the /F switch while rebooting.
During the reboot chkdsk usually finds nothing but as soon as the system
is up and chkdsk is run against die C: drive again, the game starts from
new.
I bet if someone tries this on a system with all the recent updates, it
will result in the same. But I know it used not to be so, usually if
chkdsk would find errors, after repair it should report a clean file
system.
Does anybody know why chkdsk all over sudden behaves like this?
Thanks, Juerg