Community Newsletter: Q&A: 7/8/05 Stop Chkdsk from running during start-up
- 7/7/05 5:01 PM
7/8/05 Stop Chkdsk from running during start-up
by Lee Koo (ADMIN) - 7/7/05 5:01 PM
A big thank you to all those who participated in this week's topic. Anup, I'm hoping that you would join us in the forums to let us know what worked for you and if you have additional questions to ask about the chkdsk issue.
I encourage all of you who have experience or additional advice in this matter to post your solutions. The more knowledge we exchange, the more we can all learn from each other as a community.
Take care and have a great weekend!!
-Lee Koo
CNET Community
Question:
Recently I have noticed that each time I boot my system, the
operating system (Windows XP Pro SP2) runs ScanDisk on my D:
drive, stating that the computer did not shut down properly,
which is not true. The system then runs a full ScanDisk on
drive D: and gives an error-free report. Then after that,
each time I boot, it runs ScanDisk on my D: drive all over
again, finds no errors. Kindly suggest how to get rid of this
annoyance. (Intel P4 1.4GHz, 256MB RD-RAM, 40GB Seagate
Barracuda with equal partition, C: and D:, C: being the
primary drive). Thanks in anticipation.
Submitted by: Anup J. of West Bengal, India
Answer:
Hello, what you're experiencing is what Windows refers to as "setting the dirty bit" and what you have to do is unset that bit. Every time Windows XP starts, autochk.exe is called by the kernel to scan all volumes to check if the volume dirty bit is set. If the dirty bit is set, autochk performs an immediate chkdsk /f on that volume. Chkdsk /f verifies file system integrity and attempts to fix any problems with the volume. It is usually caused by a hard shut down or a power loss during a read-right operation on that particular drive.
How do I fix it, you ask?
Well, that's easy. First click Start> Run> bring up a command prompt by typing in "CMD" and type " fsutil dirty query d: ". This queries the drive, and more than likely it will tell you that it is dirty. Next, type "CHKNTFS /X D:". The X tells Windows to NOT check that particular drive on the next reboot. At this time, manually reboot your computer, it should not do a Chkdsk and take you directly to Windows.
Once Windows has fully loaded, bring up another CMD prompt and type and now you want to do a Chkdsk manually by typing "Chkdsk /f /r d:". This should take you through 5 stages of the scan and will unset that dirty bit. Finally, type "fsutil dirty query d:" and Windows will confirm that the dirty bit is not set on that drive. Good luck!
Submitted by: Darrin S.
Other suggestions for our community members
by Lee Koo (ADMIN) - 7/7/05 3:02 PM
In reply to: 7/8/05 Stop Chkdsk from running during start-up by Lee Koo (ADMIN)
Answer:
Anup, here are a few things you can try which may help alleviate your problem.
Rule # 1: It is best to have backups of all your data and programs prior to attempting any of the below suggestions. Actually, it is wise to always create backups of your critical data and have your program software at hand in case you encounter any system problems. It is better to be safe then sorry. I have run into similar situations such as the one you are encountering and although it took some time to rebuild I did recover everything on my machine.
Bring up MS DOS and try running Scandisk (before Windows is loaded on your system). You may have to boot from an MS DOS disk (Startup Disk) and running Scandisk from the command line. Although the proper utility to run on Windows XP is CHKDSK/X (where X is the Drive) running Scandisk may clear the “flag” which is telling Windows there is an error on your drive (D: drive in your case).
You can also try the System Restore function / Last Known Good Configuration. To do this you must boot in Safe Mode and use XP’s built-in System Restore function to restore the system to an earlier working configuration. Before you do this I suggest you hit the F8 key during boot up time and try the Last Know Good Configuration. If you haven’t been able to properly log on since you started seeing the Scandisk errors this exercise could restore the last properly working configuration you had.
Note: In order to gain access to the System Restore Wizard in Windows XP: click Start -> Help and Support. Click Performance and Maintenance; click Using System Restore to undo changes, and then click Run the System Restore Wizard.
You can also boot from the Windows XP CD and try the repair option or try fixing the master boot record by typing FDISK /MBR at the DOS Prompt.
Please go back up and read Rule #1 prior to attempting any of the above. Good Luck!
Submitted by: Joe V.
***********************************************************************
Answer:
I ran into this issue a couple of years ago and was able to find a solution on the Internet.
Here are a few resources to go on that helped me.
Chkdsk Runs Each Time That You Start Your Computer
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q316506
Running Chkdsk to Repair File Systems
http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prkd_tro_xudm.asp
Manually resetting AUTOCHK.EXE for a drive
http://searchwin2000.techtarget.com/tip/1,289483,sid1_gci990696_dbg1,00.html
my computer wants to do a scandisk before windows loads. Is there an option to turn that off?
http://forums.sudhian.com/messageview.aspx?catid=81&threadid=63496
Try to cancel checkdisk at every boot up but unsuccessful
http://www.experts-exchange.com/Operating_Systems/WinXP/Q_20698249.html
Good luck.
Submitted by: J.C.
***********************************************************************
Answer:
I would say to this Question
to take the program out of your startup settings so that it does not open, one can open the program manually when needed to do a scan for Problems.
There are probably lots of programs that are opening at startup that
are not needed at that particular time, so a good idea to shut them all down.
Submitted by: Jock of Melbourne. Australia
***********************************************************************
Answer:
Anup,
I am not an expert, however you may try this. My OS is Win 98 SE. I tried it and succeeded.
Even though we shut down the system properly, when we reboot, it says the system was not properly shut down and check for errors in each drive. This is really a pain in the neck. What is the reason for it. My meagre knowledge says that some information from the virtual cache has to be recorded on the hard disk, but, instead it was recorded only on onboard cache. When you shut down the system, what is recorded on onboard cache is erased. So, what is to be recorded on the hard disk is not recorded. Hence when you bootup, the system could not find the information on the hard disk(from virtual memory) while shutting down last, it assumes that the system was not properly shut down and starts the scanning of all partitions.
To avoid this, you have to edit the registry. Open the registry(start>run>regedit) and go to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\
Current Version, on the right you will find 'Cache Write Delay' - there you create DWORD and give its value as 2000. Then you double click it.
Now you will not face the scan disk problem every time you boot. I repeat, this I have tried in Win 98 SE.
I advise you back up your registry and try this.
Wish you good luck.
Submitted by: Bhogaraju R. of Visakhapatnam, India
***********************************************************************
Answer:
Re: ScanDisk running at startup.
The 'error message' you receive may be incorrect.
First, check how you have this program scheduled to run.
It may be scheduled to run each time the system is booted.
Change to another option and hopefully that would solve the problem.
Submitted by: Kathleen K.
***********************************************************************
Answer:
Check to see if you have update KB894391 on your machine. This may NOT come in as part of the automatic update process, and MAY solve your problem.
Submitted by: George O.
***********************************************************************
Answer:
Change the attributes for MSDOS.SYS so it is not 'Read Only', MSDOS.SYS is found in the root directory of your C:\ drive. Open the file using Notepad or another text editor (not Microsoft Word or any word processor).
Change the value of 'AutoScan=' to:
AutoScan=0 : Scandisk is Disabled
AutoScan=1 : Scandisk Prompts First
AutoScan=2 : Scandisk Runs Automatically Changes will take place on the next reboot.
Note: It is advisable to run Scandisk after an incorrect shutdown to avoid file corruption.
Note: This feature is only available on Windows 95 OSR 2 and greater.
Submitted by: Ken S.
***********************************************************************
Answer:
Hi. I suppose that you have a problem with Hard Disk Partitions Definitions in drive D. I suggest that you must backup all important data from your drive D and reformat all Drive (C an D). The format proccess notice you if you have some tracks bad (perhaps it´s containe information about bad partition D) and you may resize your drive for best results.
I hope that it was helpful for you.
Submitted by: Mario S.
***********************************************************************
Answer:
If the user is using Norton SpeedDisk, he may have inadvertently checked View/Global Options/Scan For Errors Before Optimizing NTFS Volumes.
That will lock the C: drive on booting so that the drive can be scanned before Windows boots. If so, unchecking that box should solve his problem.
Submitted by: Norman H. of Azalea, OR
***********************************************************************
Answer:
ou might check the Start-Up Menu ... you may have accidentally dragged the ScanDisk icon into the Start-Up Folder (Start, Programs)
... Best regards,
Submitted by: rix rox
***********************************************************************
Answer:
Scandisk
I’ve had the same problem on my PC (Windows 2000) I cured it by scheduling a check disk on the next boot. After it ran I did not have anymore unwanted disk checks. This has happened a few times and scheduling a check disk always stops the problem. I use Norton Systems works, but the windows check disk also works.
Submitted by: Jim I.
***********************************************************************
Answer:
I don't know how to stop the original problem, but I do know how to stop the scandisc process.
When the scanning begins, hit the "enter" key and the scanning will stop and the normal booting will continue.
But since you do have some sort of problem with the shutdown process, I would allow the scandisc to run to completion every fifth boot or so. It may just find a problem eventually.
P. S.
Do not shut off the computer with the button on the CPU.
Use the "shutdown" in the start menu. If it hangs at the "Windows flag", then you can use the CPU button, at that point. If you do all of this, the scandisc will not start.
P.P.S.
If you do this to the point of pushing the start/off button on the CPU, hold the button till you see and hear it shut off. It takes about five to eight seconds of holding the button in the depressed position before it shuts off.
If you are only using the CPU button to shut down your computer, that is your problem. This will cause the scandisc to run everytime you reboot (restart) the computer.
When you see the message stating that the computer was shutdown improperly, that is what it means. DO NOT just use the button on the CPT to shut off your computer. Use the "shutdown" in the start menu.
I think that is all I have to contribute. Hopefully.
Submitted by: RJT of Fort Lauderdale, FL.
Bad IDE cable or PSU
by Andrew Jackson - 7/8/05 7:26 AM In reply to: Other suggestions for our community members by Lee Koo (ADMIN)
The winning answer treats the symptoms but most likely not the cause. Bad/loose IDE cable or under sized PSU might be the cause. Drives suck more power than anything else. Not having enough juice to spin up can cause all kinds of trouble messages.
Or possibly a hard disk problem!
by cdgoldin! - 7/8/05 9:00 AM In reply to: Bad IDE cable or PSU by Andrew JacksonI experienced this problem with Windows 2000 twice. In the first case, the mobile rack holding a removable hard drive was defective. In the second case, the disk was defective, and eventually failed. Be prepared for this possibility by backing up your data (to tape, cd-rom, dvd, or another hard drive).
Using MSDOS to run Scandisk on XP volumes
by Rob M. Blynde - 7/8/05 7:54 AM In reply to: Other suggestions for our community members by Lee Koo (ADMIN)
DOS does not support NTFS. How is it possible to run Scandisk on an NTFS volume after booting DOS?
Power Supply
by prayerfire - 7/8/05 8:32 AM In reply to: Other suggestions for our community members by Lee Koo (ADMIN)
Hi,
It might even be a Power Supply timing problem. I had a similar incident with Windows 98 some time ago and we eventually found it was actually the power supply shutting down the Hard Disk too quickly on shutdown. Every time the computer was restarted Scandisk ran just as with yours.
Hope this helps.
Chris
utility to disable the automatic running of chkdsk
by ddhamm - 7/8/05 10:12 AM In reply to: Other suggestions for our community members by Lee Koo (ADMIN)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q160963
This is what that article says:
"The Chkntfs.exe utility has been developed by Microsoft and is available in Microsoft Windows NT 4.0 Service Pack 2 and later versions of Windows. It is designed to disable the automatic running of chkdsk on specific volumes, when Windows restarts from an improper shutdown. Chkntfs can also be used to unschedule a chkdsk if chkdsk /f was used to schedule a chkdsk on an active volume on the next system restart. "
DeeDee
discscan starting up everytime you start your pc.
by amlaiki - 7/8/05 1:46 PM In reply to: Other suggestions for our community members by Lee Koo (ADMIN)
Can't you go to msconfig and uncheck it from there?
Booting from the CD to fix the problem
by KitC - 7/11/05 3:26 AM In reply to: Other suggestions for our community members by Lee Koo (ADMIN)
First you need to make sure you have set and know the Administrator password.
If you know the password then skip this section.
There are menu ways of doing this... but I like sureshot methods.
press WINDOWS + R
type compmgmt.msc <press enter>
navigate through the left menu: Local Users and Groups >> Users
In the right panel, Right click on Administrator and choose Set Password...
You may get a warning about losing vital information, mainly you will lose any saved passwords for web sites, file shares. Usually not a problem unless you are constantly logging in as Administrator.
Continue passed this if you are still comfortable.
Set the password.
REBOOT off the XP CD
At the menu, choose to repair using the recovery console
(NOT AUTORECOVERY which shows during the loading phase of CD Boot)
At the DOS window prompt
type chkdsk /p
Let it do it's thing....
if you have multiple partitions, type D: <press ENTER>
then chkdsk /p again
Not sure what partiion your on? type DIR to find out.
Yes, but what is causing Anup's real problem
by joseph whitaker - 7/8/05 5:00 AM In reply to: 7/8/05 Stop Chkdsk from running during start-up by Lee Koo (ADMIN)
Darrin, your answer was thorough and I learned a lot from it.
The only problem is that Anup will have to exercise the "fix" every time he powers his system up. I certainly recognize that the fix is better than having to suffer through CHKDISK.
If it is possible to find out what is setting the "dirty bit" unnecessarily wouldn't that be the thing to fix. That would prevent the problem from happening again and avoid having to fix it every boot time.
Joe
Yes, but what is causing Anup's real problem
by speeddymon - 7/8/05 7:19 AM In reply to: Yes, but what is causing Anup's real problem by joseph whitakerI dont think that the dirty bit is being set unnecessarily. It could be that the dirty bit was failing to be unset, in which case, once it is unset this time, it shouldnt go thru chkdisk next reboot, unless it is shutdown uncleanly.. Now I assume that Windows by design sets the dirty bit when it boots, after autochk runs, but only unsets it as the _very_ last thing it does after unloading the GUI, before rebooting.. SO if windows isnt properly rebooting, that could be due to a driver, a shutdown program, or something else that is causing the computer to reboot before the dirty bit gets unset... So if none of these fix the problem in a do it once fashion, the user needs to merely think back to when it started doing it, figure out what program was installed shortly before that, and remove it..
>>The only problem is that Anup will have to exercise the "fix" every time he powers his system up. I certainly recognize that the fix is better than having to suffer through CHKDISK.
If it is possible to find out what is setting the "dirty bit" unnecessarily wouldn't that be the thing to fix. That would prevent the problem from happening again and avoid having to fix it every boot time.
Joe
Yes, but what is causing Anup's real problem
by shoplift - 11/5/09 6:41 AM In reply to: Yes, but what is causing Anup's real problem by speeddymonI'm experiencin the same problem as Anup.Well it all started today when i found out about the "iexpress.exe" i tried to xtract a .exe file and the iexpress.exe thingy hung up and stopped responding.I tried to delete the process,but on seeing that there was no use tryin to delete the process i pressed the power button and got stuck while it was shutting down( it was displayin "windows is shutting down" for about 5 mins) and i had to manually cut the power supply.And after that when i booted up chkdsk started up and started doing this 5 stage scan thingy everytime i booted up since then
RE Stop Chkdsk from running during start-up
by caridgway - 7/8/05 5:39 AM In reply to: 7/8/05 Stop Chkdsk from running during start-up by Lee Koo (ADMIN)
After you have gone through and cleaned the dirty bit don't you want to set CHKNTFS to scan the drive again so you know if the problem occurs again? How do you tell it to start checking again?
Chkdsk and open files on volume
by tgeery - 7/8/05 5:40 AM In reply to: 7/8/05 Stop Chkdsk from running during start-up by Lee Koo (ADMIN)
One other issue to keep in mind is that if there are ANY open files on that volume, chkdsk will not be able to perform the FIX part of the check (/F)and will error out.
Stop Chkdsk from running during start-up
by maraodette - 7/8/05 5:56 AM In reply to: 7/8/05 Stop Chkdsk from running during start-up by Lee Koo (ADMIN)
My computer doesn't do that.
Thanks
| Forum legend: | |
 |
Locked thread |
 |
Moderator |
 |
CNET staff |
 |
Samsung staff |
 |
Norton Authorized Support team |
 |
AVG staff |
 |
Windows Outreach team |
 |
Dell staff |
 |
Intel staff |
