QUOTE(cmcc @ 3.09.2013 22:25)
Argh! I want to run "chkdsk /f" on Win XP (because KIS hung the PC). However, I find that "chkdsk /f" will not run [on restarting the PC]. The reboot process blithely ignores the fact that a chkdsk had been scheduled.
As I haven't done anything else new to the computer, and as the disabling of chkdsk is unconscionable by any sane process other than by a very dictatorial antivirus (or by a virus itself, which KIS reports I do not have), I assume that KIS 2014 has somehow managed to disable running "chkdsk /f" upon reboot. Is my assumption correct? And if so, how do I get around it, so that I can, in fact, run chkdsk?
Confirmed! I uninstalled KIS 2014, and suddenly I can once again do a "chkdsk /f" upon reboot!
Which leads me to ask: What the ^&%^%#$^&%$ are you doing -- blocking chkdsk ??? Do you really think that is wise? Does it somehow prevent some sort of virus trickery? And even if so, can you not find some way to enable the user to actually accomplish a chkdsk? It is, after all, a somewhat fundamental need, on a Windows system. (Esp. if your own program is causing hangs.)
(I would, however, love it if you came back with a fix.)