checkdisk

at startup I get a message that says checking the file system, one of your files needs to be checked, press any key to skip checkdisk.
I've let it run the checkdisk and everything is fine. I've skipped the checkdisk most times. Neither seems to have any effect on the system but this start up message won't go away.
What's a mother to do?

 

The applet is chkdsk although check disk is exactly what it does.

If you are comfortable looking at and maybe editing the registry,

Start/Run/Regedit and navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
In the list look for "SFCScan ". It should have a value of 0 (zero). If it is set to 1 the scan will happen at every boot so you will need to change it back to zero.

Another possiblilty (usually on upgrades from another OS to XP) is
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
Look for BootExecute which contains commands that will be executed at startup.
The default value is: autocheck autochk * . If you have one set to autocheck autochk /f * the chkdsk scan will run every time so set the top one (you may have only one or maybe lots) back to the default and delete the others.

Partition Magic, if you use it, can also cause this so if you have used PM to partition one or more of your disks, it could be causing the behavior.

If you aren't comfortable messing with the registry, create a restore point before you start with the first regedit so in case of problems you can just revert to the settings you have now. Annoying but working.

 

Thanks, I printed out the first suggestion and ran through it. There was no SFCScan. The closest thing was SFCDisable set to 0.
This machine was bought from Dell with XP Home pre-loaded.
I'll take a look at the other suggestion anyway...stay tuned.

 

Looked at the second suggestion...it is set to the default value: autocheck autochk*

 

xort - just to let you know you aren't forgotten (and to put this back at the top), I'm at work and too busy this evening to research but will do so tomorrow if someone else hasn't already given you more ideas.

I really thought one of those reg entries would be the problem but looks like it isn't quite that simple. Ah well.

 

Newt
Oh well, not a big deal. I've been putting up with this for a few months now, I have some patience with windows.
If I remember correctly, it may have started after a download from Microsoft of Win or IE patches. Remember, this is Win XP home installed by Dell, so no major re-installs or upgrades.