"DISKEEPER can't run on C: cuz CHKDSK is scheduled"
This is a discussion about "DISKEEPER can't run on C: cuz CHKDSK is scheduled" in the Windows Software category; DISKEEPER 8. 0 PRO won't defrag my C: cuz it states that CHKDSK is scheduled to run upon next reboot. I reboot & nothing happens. I run a read-only CHKDSK and no errors are found. I can't run a CHDSK /F or NORTON DISKDOCTOR without having to reboot.
DISKEEPER 8.0 PRO won't defrag my C: cuz it states that CHKDSK is scheduled to run upon next reboot.
I reboot & nothing happens. I run a read-only CHKDSK and no errors are found.
I can't run a CHDSK /F or NORTON DISKDOCTOR [fix errors] without having to reboot. Nonetheless, no errors are found.
NORTON SPEEDISK will work though.
I even tried SAFEMODE and DIAGNOSTIC START-UP mode to do something but still.... same ol', same ol'.
Any ideas to get it running?
I reboot & nothing happens. I run a read-only CHKDSK and no errors are found.
I can't run a CHDSK /F or NORTON DISKDOCTOR [fix errors] without having to reboot. Nonetheless, no errors are found.
NORTON SPEEDISK will work though.
I even tried SAFEMODE and DIAGNOSTIC START-UP mode to do something but still.... same ol', same ol'.
Any ideas to get it running?
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Feb 24
Feb 25
0
1 minute
Responses to this topic
Check out http://support.microsoft.com/default.aspx?scid=kb;en-us;831426&Product=winxp
I know you said it's not actually running, but there may be a reg key messed up there.
Good luck!
I know you said it's not actually running, but there may be a reg key messed up there.
Good luck!
OP
Quote:Check out http://support.microsoft.com/default.aspx?scid=kb;en-us;831426&Product=winxp
I know you said it's not actually running, but there may be a reg key messed up there.
Good luck!
I appreciate the response but there was no "BootExecute" in the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager" reg. key.
I know you said it's not actually running, but there may be a reg key messed up there.
Good luck!
I appreciate the response but there was no "BootExecute" in the "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager" reg. key.
