Hi kurmbox,
Not to worry, yours is a common complaint for Windows XP and you
should be able to fix it without too much trouble.
1. Make sure CheckDisk is not enabled in your startup list - if it is,
uncheck it:
Start / Run / Msconfig / Startup
2. Clear your BootExecute entry:
Start / Run / regedt32
HKEY_LOCAL_MACHINE / SYSTEM / CurrentControlSet / Control / Session
Manager
BootExecute
-Delete all autocheck entries, especially: autocheck autochk /f *
HKEY_LOCAL_MACHINE / SOFTWARE / Microsoft / Windows NT /
CurrentVersion / Winlogon
-Highlight the Winlogon file.
-Set "SFCScan" to 0 (zero).
Additional Links:
Kelly's Korner:
Registry Edits for Windows XP: "Tweaks and Tips" (see Line 82)
http://www.kellys-korner-xp.com/xp_tweaks.htm
Hopefully one of those will help. If not, or if you have any
questions, please post a clarification request before rating my
answer.
Thank you,
hummer
Google Search Terms:
checkdisk xp startup |
Clarification of Answer by
hummer-ga
on
24 Sep 2003 15:36 PDT
Hi kurmbox,
Thanks to denco for the timely reminder - for sure, back up your
registry first. But don't get too freaky over this, the two registry
fixes I suggested aren't classified as critical red alert.
Reading your question over again, I thought perhaps your "'dirty bit'
is set to 1" comment refers my "Set "SFCScan" to 0 (zero)" fix (it
would be set at "1" to auto scan). However, your best bet is still the
"autocheck autochk /f *".
Please let me know how you make out, ok? hummer
|
Request for Answer Clarification by
kurmbox-ga
on
24 Sep 2003 19:17 PDT
I was able to delete the autocheck entry in SessionManager (there was
only one), however my Winlogon did not have the entry "SFCScan". It
did, however, have "SFCDisabel" which was set to 0 (or OxOOOOOO) (more
on this in a second). So at this point all I have done is delete
autocheck entry from SessionManager. I reboot and when I normally get
the disk-checking screen, I now get a short message saying something
along the lines of "/windows/.../..../autcheck.exe not found, skipping
autocheck". So apparently at this point I have gotten rid of autocheck
but not disabled the key in the system that causes it to run. After
this boot completes, I go back into my registry and find the
"SFCDisable" entry and set it to 1 to see if that would disable SFC
scanning. I rebooted and got the same error message as mentioned
before. So, the problem has been modified, but not yet completely
solved.
|
Clarification of Answer by
hummer-ga
on
24 Sep 2003 20:11 PDT
Hi Kurmbox,
Restore your registry to get back to square one.
Run checkdisk manually.
hummer
|
Clarification of Answer by
hummer-ga
on
25 Sep 2003 05:49 PDT
Good morning kurmbox,
When you do your Checkdisk manually, do the Full version. If there's
something going on with your computer, this may solve it.
Going back to the disabling question, if the full Checkdisk didn't
help, try this (please back up first):
http://www.winguides.com/registry/display.php/907/
HKEY_LOCAL_MACHINE / SYSTEM / CurrentControlSet / Control / Session
Manager
Name: AutoChkTimeOut
Type: REG_DWORD
Value: 0
It's ok to disable Checkdisk at startup but you really need to
determine if something is wrong to avoid bigger problems down the
road. When troubleshooting, it is important to do just one fix at a
time. If it doesn't help, go back to square one before trying another.
Don't add fix over fix over fix - it just multiplies the problem.
So far, you have (individually) -
To disable Checkdisk:
Checked your startup menu
Deleted autocheck autochk /f *
Set "SFCScan" to 0
Set "AutoChkTimeOut" to 0
To troubleshoot system:
Run a full Checkdisk manually
I will wait for your next update. Thanks, hummer
|
Request for Answer Clarification by
kurmbox-ga
on
29 Sep 2003 17:34 PDT
Actually, hummer, I was able to fix my own problem. You see, checkdisk
ultimately wouldn't run because the drive in question had my page file
on it. I disabled this drive as my page file, moved my page file to
another drive, shutdown and restarted, manually ran checkdesk with /f
parameter on drive E:, and then reenabled the page file on this drive.
This fixed my problem, no more booting annoyances. Thanks for your
suggestions anyway, they helped a little.
|
Clarification of Answer by
hummer-ga
on
30 Sep 2003 04:54 PDT
Hi kurmbox,
I'm happy to hear you fixed the problem - good job! However, I wish
you had given me a chance to complete my answer before closing the
question off and rating it. Rather than waste your time and mine by
giving a long list of fixes that may or may not work, it is more
productive to take it alittle bit at a time and learn by each step -
fixing computer problems is often a matter of the process of
elimination. Had you gotten back to me as I had requested, I would've
continued to work through your problem until it was solved. If at any
time I felt I wasn't going to be able to help, I would've withdrawn my
answer in order to let another researcher take over. The number of
clarifications that can be posted is unlimited and all researchers are
more than happy to respond to as many as it takes to ensure the
questioner has received a thorough answer to his/her question.
At any rate, the most important thing is your computer is booting up
normally now and I'm glad I was able to help, even if it was only by a
wee bit.
Take care, sincerely,
hummer
|
