Windows XP SP3 chkdsk will not run at boot

Amathyst

Distinguished
Dec 28, 2010
2
0
18,510
Hello,
One day I set chkdsk to run at the next reboot. Now it will not run at all. It comes up like it's going to start then it cancels automatically without pushing any buttons. What can I do? I tried running it through command prompt, but it would not run because it's scheduled to run at boot. But it never runs and has been doing this everytime I restart for the past 2 months.
 

Amathyst

Distinguished
Dec 28, 2010
2
0
18,510
I'm going to ygive a little more info. I am running Windows XP professional sp3. I'm on a Dell Inspiron E1505 Laptop. I also have Avast anti-virus and Comodo firewall. I do not believe this is the problem. In command prompt I can only run chkdsk in read only mode. It shows that there are errors, but it will not fix them. I get an error message saying that chkdsk cannot run because it is in use by another process. It will not run at startup. It never shows me the count down to cancel chkdisk by pressing any key. It just automatically cancels and then loads windows. I tried this several times. I am an administrator. I figured maybe if I went in through safe mode and signed in under the main administrator account it would work. I still cannot get it to work. I get the same results. I have tried every chkdsk command in cmd. It will scan under read only, find errors, but it will not fix them. My file system type is NTFS. When read only mode is scanning it goes through 3 stages. Then it says it cannot continue in read-only mode. When I run chkdsk /f I get the following message: Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restates? (Y/N)

I have done both. And it still automatically cancels at startup. I tried the /x command as well. I get the same error message I get when I use the /f command. If you need more info let me know. Is there any way to reset chkdsk so there is no scheduled tasks at startup? Then maybe I can try again through cmd.