Professional Documents
Culture Documents
Sign in
Home
Windows 8
Windows 7
Windows Vista
Windows XP
MDOP
Windows Intune
Library
Forums
Ask a question
Quick access
Answered by:
Question
It appears that the CHKDSK wants to run almost every time I reboot my computers with Windows 7. It happens on desktops and laptops as well. Any help?
1
Sign in to vote
Answers This sometimes worked on XP and should also work on Vista or Windows 7. Click on Start then Run , type cmd and press Enter . Next type fsutil dirty query x: where x: is your boot drive. This queries the drive, and more than likely it will tell you that it is dirty. Next, type chkntfs /x c: . The X tells Windows to NOT check that particular drive on the next reboot. Now manually reboot your computer, it should not do a chkdsk and should take you directly to normal Windows login. Once Windows has fully loaded, bring up another Command Prompt and enter chkdsk c: /r . Reply Y when asked if you want this to happen on the next boot. This should take you through 5 stages of the chkdsk scan and will unset that dirty bit. This can take an hour or more depending on the size of your hard drive, be patient and let it complete. Once booted back to Windows, open another Command Prompt and query the dirty bit again by entering fsutil dirty query c: and Windows will confirm that the dirty bit is not set on that drive. Above from Experts Exchange
15
Sign in to vote
Marked as answer by Ronnie Vernon MVP, Moderator Tuesday, November 10, 2009 1:43 PM Thursday, October 08, 2009 12:42 AM Reply | Quote | Ztruker 1,595 Points
All replies
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
1/12
12/3/13
2
Sign in to vote
Manufacturer diagnostic tools are also useful to run a better 'check' on the drive than Windows provides. If the behaviour is indeed happening as I've described here then it's happening because Windows is perceiving the drive as having bad sectors. Those may or may not be genuine. In some circumstances a corrupted install can cause Windows to perceive a reliable drive as 'bad'. It's best to thoroughly check before assuming that the drive actually is an unreliable one.
Wednesday, October 07, 2009 11:19 PM Reply | Quote | Techwrighter 2,965 Points
This sometimes worked on XP and should also work on Vista or Windows 7. Click on Start then Run , type cmd and press Enter . Next type fsutil dirty query x: where x: is your boot drive. This queries the drive, and more than likely it will tell you that it is dirty. Next, type chkntfs /x c: . The X tells Windows to NOT check that particular drive on the next reboot. Now manually reboot your computer, it should not do a chkdsk and should take you directly to normal Windows login. Once Windows has fully loaded, bring up another Command Prompt and enter chkdsk c: /r . Reply Y when asked if you want this to happen on the next boot. This should take you through 5 stages of the chkdsk scan and will unset that dirty bit. This can take an hour or more depending on the size of your hard drive, be patient and let it complete. Once booted back to Windows, open another Command Prompt and query the dirty bit again by entering fsutil dirty query c: and Windows will confirm that the dirty bit is not set on that drive. Above from Experts Exchange
15
Sign in to vote
Marked as answer by Ronnie Vernon MVP, Moderator Tuesday, November 10, 2009 1:43 PM Thursday, October 08, 2009 12:42 AM Reply | Quote | Ztruker 1,595 Points
Steps provided by Ztruker is worth to have a test. Before that, we can first test to run a Check Disk in Safe Mode. After that, reboot the computer to see if issue still exists.
3
Sign in to vote
Thursday, October 08, 2009 1:47 AM Reply | Quote | Shaon Shan (MSFT CSG) 39,455 Points
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
2/12
12/3/13
It appears that the CHKDSK wants to run almost every time I reboot my computers with Windows 7. It happens on desktops and laptops as well. Any help?
1
Sign in to vote
Udi Burg www.unisfair.com I have a similar issue but it happens after Event Error ID 55 is logged (NTFS). Can you check your logs and see if you have this ominous error occur as well? My subesquent CHKDSK finds no! erros(s).
Monday, November 09, 2009 8:53 PM Reply | Quote | Win7ine 170 Points
Steps provided by Ztruker is worth to have a test. Before that, we can first test to run a Check Disk in Safe Mode. After that, reboot the computer to see if issue still exists.
1
Sign in to vote
How do you run a CHKDSK in Safe mode? You invoke a chkdsk c: (Systemdrive) which runs before Win starts on it. I fail to understand this suggestion.
Monday, November 09, 2009 8:56 PM Reply | Quote | Win7ine 170 Points
get into Safe Mode, input CMD in Search, run it as Administrator. Type: CHKDSK C: /f /r
Tuesday, November 10, 2009 6:27 AM
2
Sign in to vote
Reply | Quote |
39,455 Points
get into Safe Mode, input CMD in Search, run it as Administrator. Type: CHKDSK C: /f /r I still don't get this hocus pocus: It will still only execute CHKDSK C: /f /r on reboot/restart the same.
Tuesday, November 10, 2009 10:32 AM Reply | Quote | Win7ine 170 Points
2
Sign in to vote
0
Sign in to vote
Friday, November 13, 2009 3:02 PM Reply | Quote | Bill_G Self (Partner) 35 Points
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
3/12
12/3/13
1
Sign in to vote
Proposed as answer by Bert Huijben Friday, February 05, 2010 11:11 PM Reply | Quote |
190 Points
I followed all your instructions carefully. It took me more than one hour to complete (with a hard drive of 220 GB) and my problem is solved! Thank you a lot!!!
Thursday, April 29, 2010 6:16 PM Reply | Quote | ndimos 0 Points
0
Sign in to vote
0
Sign in to vote
Reply | Quote |
Elspeth
0 Points
Ztruker I am a relative novice with Windows 7 and have just experienced this problem, but when I run cmd and fsutil dirty query x: I get a message saying I need administrator privileges. Can you tell me how I can make that happen either before I enter the cmd prompt or after?
0
Sign in to vote
Sorry to be dense
Monday, June 07, 2010 9:18 AM Reply | Quote | alittleoldman 15 Points
I'm having the same problem with an Asus netbook running Windows seven, however, when I run the dirty query, I'm told that c: is NOT dirty. Chkdsk doesn't run on every boot, but often enough for it to be really annoying. Every time I let it run the check, no errors are found.
1
Sign in to vote
0
Sign in to vote
Reply | Quote |
10 Points
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
4/12
12/3/13
1
Sign in to vote
This worked for me. Thanks for the help. I was getting really annoyed.
Thursday, July 29, 2010 3:41 PM
0
Sign in to vote
Reply | Quote |
Calstenias
0 Points
I'm having the same problem with an Asus netbook running Windows seven, however, when I run the dirty query, I'm told that c: is NOT dirty.
1
Sign in to vote
Chkdsk doesn't run on every boot, but often enough for it to be really annoying. Every time I let it run the check, no errors are found. Exactly the same situation here. I have recently enlarged my system partition to fill out the entire drive. Since then I have had the same problem, no errors, but still chkdsk on most boots.
Monday, August 16, 2010 6:18 PM Reply | Quote | laconix 5 Points
Ztruker I am a relative novice with Windows 7 and have just experienced this problem, but when I run cmd and fsutil dirty query x: I get a message saying I need administrator privileges. Can you tell me how I can make that happen either before I enter the cmd prompt or after? Sorry to be dense You will need to go to C:\WINDOWS\System32 and then, right click on CMD.exe and hit: Run as administrator. This will do the trick.
Wednesday, August 18, 2010 7:55 PM Reply | Quote | r0ca Borden Ladner Gervais LLP 15 Points
0
Sign in to vote
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
5/12
12/3/13
This sometimes worked on XP and should also work on Vista or Windows 7. Click on Start then Run , type cmd and press Enter . Next type fsutil dirty query x: where x: is your boot drive. This queries the drive, and more than likely it will tell you that it is dirty. Next, type chkntfs /x c: . The X tells Windows to NOT check that particular drive on the next reboot. Now manually reboot your computer, it should not do a chkdsk and should take you directly to normal Windows login. Once Windows has fully loaded, bring up another Command Prompt and enter chkdsk c: /r . Reply Y when asked if you want this to happen on the next boot. This should take you through 5 stages of the chkdsk scan and will unset that dirty bit. This can take an hour or more depending on the size of your hard drive, be patient and let it complete. Once booted back to Windows, open another Command Prompt and query the dirty bit again by entering fsutil dirty query c: and Windows will confirm that the dirty bit is not set on that drive. Above from Experts Exchange
0
Sign in to vote
Hi, I have the same issue as described below but my issue is a little more weirdo than that! I just imaged my HP Z200 with Windows 7 Pro x64. It's a brand new HDD also (500go Seagate) and as soon as I'm finished imaging my HP, I can log in the computer, join it to the domain... etc! I reboot it on first time, chkdsk starts on startup for no reason! Then, it's doing its stuff and then reboot. At reboot, it loops on startup repair for ever and I can't do anything. I tried Bootrec.exe /all_switches_without_luck! I've done some changes to my PC to check for any hardware problem. - I changed the HDD (Samsung 500go for a Seagate 500go) - No luck - Swapped the Video card (nVidia Quadro 580FX for a Radeon EAH4350) I suspect the mobo to be in problem, maybe the HDD controller... Is anybody have seen this before? Thanks so much! David.
Thursday, August 19, 2010 2:48 PM Reply | Quote | r0ca Borden Ladner Gervais LLP 15 Points
I used the first solution and it worked, but now I get BSODs that restart my computer. They have happened when I press the back button in my browser, when I link two items together in Yahoo Pipes, or when I'm away from the computer entirely. Should I try resetting the dirty bit? How would I do that?
0
Sign in to vote
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
6/12
12/3/13
0
Sign in to vote
I can't format it either. It allows me to do all the preliminaries, but it won't erase the HP drive completely as when I reboot, I return to my system as if none of my formatting had taken place. Also, I've run the Malwarebytes, but that yields nothing and two other spyware programs won't update their files to the computer either. All of this seemed to take place when I downloaded Firefox a few months ago. I didn't really notice it much until i wanted to download Skype, which download works, only I can't communicate from the platform to the network on the computer when I enter my password. So, I'm thinking that these communications problems and my problems logging on with software based on my computer, or receiving updates for my windows and firefox are all related. Please advise.
Umm... As I read it, doing the chkntfs /x c: disables chkdsk from *ever* running again at boot. Is this wise? Keith De La Rue
0
Sign in to vote
Friday, January 21, 2011 2:23 AM Reply | Quote | kdelarue AcKnowledge Consulting 0 Points
This sometimes worked on XP and should also work on Vista or Windows 7. Click on Start then Run , type cmd and press Enter . Next type fsutil dirty query x: where x: is your boot drive. This queries the drive, and more than likely it will tell you that it is dirty. Next, type chkntfs /x c: . The X tells Windows to NOT check that particular drive on the next reboot. Now manually reboot your computer, it should not do a chkdsk and should take you directly to normal Windows login. Once Windows has fully loaded, bring up another Command Prompt and enter chkdsk c: /r . Reply Y when asked if you want this to happen on the next boot. This should take you through 5 stages of the chkdsk scan and will unset that dirty bit. This can take an hour or more depending on the size of your hard drive, be patient and let it complete. Once booted back to Windows, open another Command Prompt and query the dirty bit again by entering fsutil dirty query c: and Windows will confirm that the dirty bit is not set on that drive. Above from Experts Exchange
0
Sign in to vote
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
7/12
12/3/13
0
Sign in to vote
0
Sign in to vote
For almost a year I suffered from this problem. Included was Event Error ID 55 is logged (NTFS) in the event logs. On occasion, a day pass without the event. Typically there would be multiple entries on a single day. I was confident it was not a bad drive because it was new. I attributed my problem from using EASEUS Disk Copy to migrate to a larger disk drive. I was beginning to loose the faith in Windows 7 I followed the steps as outlined - CMD , run it as Administrator. Type: CHKDSK C: /f /r Reboot and let it complete. I did this several times but it did not resolve the problem. Last week I found this forum. I then decided to try it in "safe mode" - nothing to loose right ?!?! The computer started in safe mode, It appeared to stop loading the necessary files for safe mode, but I could hear the disk drive working. Kinda funny, it even stopped displaying the sys drivers on MUP.SYS. To my astonishment, the computer had restarted in normal mode, and since I have not had the problem re-occur. It may be my hopeful attitude, but the computer seems to boot much faster now ! I don't know what happened, but I do know the problem has ceased. I Agree with WIN7INE whats safe mode got to do with it when chkdsk is executing before windows starts. I have to give a thanks to the suggestion in safe mode.
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
8/12
12/3/13
0
Sign in to vote
Why am I typing chkntfs /x c: next and go through another reboot, if I'm just going to bring up another Command Prompt and enter chkdsk c: /r ?
0
Sign in to vote
Reply | Quote |
Vivek Sancheti
0 Points
Thanks for that. The safe mode did the same thing for my computer.
Monday, July 11, 2011 4:38 PM
0
Sign in to vote
Reply | Quote |
rmc872
0 Points
I have had the same issue and i tried the command prompt and it tells me not that its dirty, but i need admin privledges. Its my laptop and i did set the admin privledges to my account/the only account on the laptop. I am so frustrated! I just bought this laptop and its acting up :( please help :)
0
Sign in to vote
0
Sign in to vote
I have had the same issue and i tried the command prompt and it tells me not that its dirty, but i need admin privledges. Its my laptop and i did set the admin privledges to my account/the only account on the laptop. I am so frustrated! I just bought this laptop and its acting up :( please help :) When you go to start up Command Prompt or "CMD.exe" Right click it and go run as administrator (If you're in windows 7 that is)
Tuesday, September 13, 2011 9:11 AM Reply | Quote | LiamLemage 0 Points
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
9/12
12/3/13
Hi guys
If you have problem using chkdsk why not try and download a hard drive utility specific to your drive direct from the drive maker like ( SeaTools for Windows ) or maxblast for maxtor,
0
Sign in to vote
these utilities sometimes work when windows crap doesn't im actually doing one now and windows wouldn't do it plus it takes the pain out of trying to direct chkdsk to the drive you wanna do as im sure your aware. these are worth a try that is providing you have a os up and running, that is!. regards CS
Wednesday, September 21, 2011 7:39 PM Reply | Quote | Citizen Smith 0 Points
RickeyV, I don't know if you have looked under "Start > All Programs > Accessories>" but under here you will find the CMD.exe, you can Right Click on this and select "Run As Administrator" then the commands work =) -LMAOIMH
Thursday, October 06, 2011 4:24 PM Reply | Quote | goobs444 0 Points
0
Sign in to vote
0
Sign in to vote
I am having the same issue with the chkdsk problem; however, mine is a little bit different. I cannot get into my Windows at all and cannot get into Safe Mode to attempt to follow the instructions to fix it. Even if I hit a key to cancel the chkdsk, I keep looping around. It does ask me if I want Windows 7 or a previous version (XP) and I choose Windows 7...I shouldn't even have the option as my previous version of XP became corrupted through some viruses and someone installed Windows 7 instead. I had a bunch of errors about some files in Windows 7 and then when I started up the next time, this is all happening!!! I'm stuck and cannot get on my laptop (work computer) at all right now.
Sunday, October 09, 2011 1:43 AM Reply | Quote | kbcouch01 0 Points
I have the same problem now, how did you get it solved?
Monday, February 06, 2012 9:15 PM
0
Sign in to vote
Reply | Quote |
Ihin
0 Points
0
Sign in to vote
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
10/12
12/3/13
I'm having the same problem with an Asus netbook running Windows seven, however, when I run the dirty query, I'm told that c: is NOT dirty.
0
Sign in to vote
Chkdsk doesn't run on every boot, but often enough for it to be really annoying. Every time I let it run the check, no errors are found. This is exactly my situation as well (except I'm using a desktop), Any thoughts?
Edited by heysupersteve
Tuesday, August 07, 2012 5:23 PM
This Happened To Me Everytime, But Then I Found Out That My HardDrive Was Corrupted :( Usayd. Sea
0
Sign in to vote
Wednesday, February 27, 2013 9:38 AM Reply | Quote | Sea5 Sea (Partner) 0 Points
In the past 3 days I have had 4 systems start displaying this behaviour. They are all windows 7 Pro (version 6.1 build 7601) sp1. Various makes and models (HP, Dell, & Lenovo). Update is as of April 12/2013. The fix works but what's triggering it?
0
Sign in to vote
We have another 50 PCs that I don't want to have to fix one at a time! Thanks Garry
Wednesday, April 17, 2013 4:47 PM Reply | Quote | Garry Dodman 0 Points
Hi Garry Dodman - how did you fix it? We have this problems on all Windows 7 Pro computers. It started happening after April 12, 2013. garyli
0
Sign in to vote
Like Garry Dodman and Gary Li I have got this problem with a Windows 7 Pro laptop, also starting on 12th April 2013. Does anybody have any idea as to cause? Thanks
0
Sign in to vote
Donald
Thursday, April 18, 2013 4:00 PM Reply | Quote | DonaldJD 0 Points
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
11/12
12/3/13
0
Sign in to vote
0
Sign in to vote
Today Microsoft released update KB2840149 to replace KB2823324, which was originally made available through MS13-036. Previously KB2823324 was removed from distribution for reasons explained in KB2839011. Customers who have automatic updates enabled will not need to take any further actions to get the new update. For those manually updating, we encourage you to apply this update at your earliest convenience.
Wednesday, April 24, 2013 6:29 AM Reply | Quote | AndricoRus freelance 16,710 Points
social.technet.microsoft.com/Forums/windows/en-US/a7d5c759-c8c6-49cc-80af-589e28f13a65/windows-7-and-chkdsk-on-boot?forum=w7itprogeneral
12/12