Chkdsk Disk Defragmenter error.

Similar Questions

• Disk Defragmenter error - CHKDSK /F tried many fixes listed in this site & they do not work - please help! Windows XP

  I have the problem of error Disk Defrag as described in many articles on this site and I tried to use your method of repair twice, both times which could not solve the problem.

  I have a "dirty Bit", as shown in the second line, but your other directions does not solve the problem.  Please note that after your direction to type chkdsk c: /f /r ask Y / N question which you note in your direction.  the system won't let you leave without answering the question. I tried both Y & N responses and both failed to solve the problem.

  My problem started with me updating my Itunes program.  I tried to do the update, but for one reason or another that the update would not take, I took all the update prgrams (new) is installed.  That's when all my problems.

  I lost half of my available disk space on my c: drive even if I removed the additional programs, and more I can't defragment my c: drive as I continue to get the chkdsk /f error code.

  I'm running an old Sony Vaio PC with 60 GB of available disk space. Windows XP.

  Any other suggestions?  I searched around on google and there are all kinds of software "for sale" and repairs that do not also work that supposedely will solve the problem.  I don't want to lose money on something that should be an easy fix.

  Help, please!

  We'll walk though...

  You cannot run the defragmentation on a volume where the dirty bit is set - you must clear the dirty (somehow) bit first before running chkdsk.

  Checking the sale but with fsutil is a good idea and you said that your disk is dirty.

  He probably got the dough to a power interruption (in general), aborted restart or an abnormal termination.  None of this happen or familiar?

  When XP starts, it checks to see if any volume is dirty and if any volume is dirty, XP automatically start chkdsk on it because she would like to fix it for you.

  The only thing that can clear the dirty bit is a successful execution of chkdsk/r.

  The following idea:

  chkntfs /x c:

  That puts a bit in the registry that tell XP to not even check the volume dirty bit... never, so if the disc is dirty, the auto chkdsk will not work on the disk since you already told him not to do so and it remains dirty.  Maybe this isn't a good idea unless you plan to undo it someday.  This part seems to be absent from these instructions (how to cancel it).

  If I were you, I would that result than now because it it really in your best interest to leave XP check the volume and try to fix it if the bit of impurity if she set, right?  Why do you want to tell XP not to check your volumes when they could really need to check?

  To cancel this order, enter the following command:

  chkntfs /d (you don't have so specifies a volume).  That sets everything back to the 'normal' and also removes all pending the command chkdsk, you may have said YES to previously.

  Now your volume is still dirty (you can check it again).

  If your chkdsk to run at reboot and it's not clearing the dirty bit, you can see in the Event Viewer Application log to see what happened:

  When chkdsk runs automatically restart, the results appear in the Event Viewer Application log.  You will need to get there after the disk check performed and XP has finished loading for the results and all the problems. If it looks like nothing, look at the report in the event log Viewer Application.

  To view the logs in Event Viewer, click Start, settings, Control Panel, administrative tools, event viewer.

  A shortcut to the event viewer is to click on start, run and enter in the box:

  %SystemRoot%\system32\eventvwr.msc

  Click OK to launch the event viewer.

  Look in the Application log for a Winlogon event, something as a source (yours may be different):

  Event type: Information
  Event source: Winlogon
  Event category: no
  Event ID: 1001
  Description:
  Checking file system on C:
  The type of the file system is NTFS.

  One of your disks needs to be checked for consistency. You
  may cancel the disk check, but it is strongly recommended
  that you continue.
  Windows will now check the disk.
  CHKDSK checks Usn Journal...
  Audit of the USN Journal is complete.

  976751968 KB total disk space.
  31923620 KB in 81911 files.
  24564 Ko 5968 index.
  0 KB in bad sectors.
  188136 KB in use by the system.
  65536 KB occupied by the log file.
  944615648 KB available on disk.

  4 096 bytes in each allocation unit.
  244187992 total allocation on the drive units.
  236153912 allocation units available on disk.

  Windows has finished checking your disk.
  Please wait while your computer restarts.

  Sometimes it seems that even if XP running chkdsk for you, the dirty bit still is not cleared for any reason, then simply start it yourself from the XP Recovery Console.

  What I do in cases like yours to run chkdsk/r from the XP Recovery Console you can actually see what happens and watch him run (waiting).   When it's done, you can't question the impurity of the RC bit, but you can run chkdsk/r again until he come clean, and if he can, it clears the dirty bit too.  It does not hurt anything either to run chkdsk/r, even when there is no 'need' to be executed.

  You can get in the RC since an authentic Windows XP installation CD, or you can make a CD of bootable XP Recovery Console if you don't know what kind of CD, you have (no XP media required).

  I'd just a console RC bootable CD, so there is no doubt about what you have for a bootable media.  You can always use it again another day (it might be quite useful).

  Here's how:

  Boot into the Recovery Console Windows using an XP bootable installation CD.

  If you have no XP bootable media (or aren't sure you have) create a bootable XP Recovery CD of Console and do not forget.

  This is not the same as recovery disks that might have come with the acquisition of the system store.

  You can make a bootable Recovery Console CD by downloading an ISO file and burn it to a CD.

  The ISO bootable image file you need to download is called:

  xp_rec_con. ISO

  Download the ISO from here:

  http://www.mediafire.com/?ueyyzfymmig

  Use a new CD and this simple and free program to burn your ISO file and create your bootable CD:

  http://www.ImgBurn.com/

  When you install ImgBurn, DO NOT install the Ask toolbar.

  Here are some instructions for ImgBurn:

  http://Forum.ImgBurn.com/index.php?showtopic=61

  It would be a good idea to test your bootable CD on a computer running.

  You may need to adjust the computer BIOS settings to use the CD-ROM drive as the first device to boot instead of the hard drive.  These adjustments are made before Windows tries to load.  If you miss it, you will need to restart the system again.

  When you start on the CD, follow the instructions:

  Press any key to boot from CD...

  Installing Windows... going to pronounce.

  Press 'R' to enter the Recovery Console.

  Select the installation that you want to access (usually 1: C:\WINDOWS)

  You may be asked to enter the password (usually empty).

  You should be in the folder C:\WINDOWS.  It's the same as the

  C:\Windows folder that you see in Solution Explorer.

  The Recovery Console allows base as file commands: copy, rename, replace, delete, chkdsk, fixboot, fixmbr, cd, etc.

  For a list of the commands in the Recovery Console, type help at the prompt of commands or read on here XP Recovery Console:

  http://www.Microsoft.com/resources/documentation/Windows/XP/all/proddocs/en-us/recovery_console_cmds.mspx?mfr=true

  A good idea before you start things must first verify the integrity of your file system by using the chkdsk command.

  In the command prompt window, run the chkdsk command on the drive where Windows is installed to try to fix any problems on the afflicted player.

  Running chkdsk is fine, even if he finds no problem.  It won't hurt anything to run it.

  Assuming your boot drive is C, run the following command:

  CHKDSK C: /r

  Let chkdsk finish to correct the problems, he could find.

  It may take a long time for chkdsk complete or they seem to be "stuck".  Be patient.  If the HARD drive led blinks always, chkdsk is something.  Keep an eye on the amount of the percentage to be sure that it is still making progress.  It may even seem to go back sometime.

  You must run chkdsk/r again until it finds no error to correct.

  Remove the CD, and then type "exit" to exit the RC and restart the computer.

  You have not to set the BIOS to boot the disk HARD since the CD won't be.

• error defragmenting the Disk Defragmenter has detected Chkdsk/f. is supposed to run on this volume, please run chkdsk

  I'm trying to defrag and I get a message saying ' Disk Defragmenter has detected /f. Chkdsk is supposed to run on this volume, please run Chkdsk.»  How am I suppose to do?

  Use my computer to access the list of HDs. right mouse click on the drive in the list. Choose Properties error checking check now.

  Run the check.

  If the drive that contains Windows, the system will restart and check the disc. After rebooting the system, you can run the Defragmenter.

  Tom Ferguson

• I can not defrag.my PC, it is constantly in a X box [Disk Defragmenter has detected that Chkdsk is scheduled

  complete the question was in my title.thank you

  When you try to defragment a volume and Disk Defragmenter reports:

  Disk Defragmenter has detected that Chkdsk is scheduled to run on the volume: (c :))
  Please run Chkdsk /f.

  This means that the volume that you want to defragment was marked 'dirty' XP.  This is not necessarily all of the data has been lost on the volume, it simply means that XP thinks that the volume should be checked to find errors because of something that happened before.

  You won't be able to defragment the volume until the dirty bit has been removed.

  This does not mean that a disk check is scheduled to run, and you can't cancel what needs to happen in this case because this isn't the problem.

  Also the dirty bit is not set on a volume, you can still run a disk defrag with a record of date of arrival in the meantime (try).

  Entry of commands to reset or erase a disc awaiting verification or suggestions for changes to the registry to make changes is a waste of time - that is not the problem.

  A volume can be marked as dirty, if the system underwent a power interruption (power failure, pulling plug, removing the battery, button / stop), abandoned restart or an abnormal termination.  One of these events?

  When XP starts, it automatically checks the bit of impurity on each volume.  You can also tell XP to ignore the bit of impurity on any volume, but this probably isn't a good idea in case there is a real problem that needs to be fixed.  If you have a hard drive where the dirty bit will not disappear, you can tell XP not to check.

  If the starting XP detects that the volume is dirty, it will be automatically run the check disk with error correction (chkdsk/r) and try to fix the problems detected.

  If the chkdsk command succeeds, it clears the dirty bit, and then you can defragment the volume.

  You can check the status of your bit of impurity from a command prompt window.

  To do this, click Start, run and enter in the box:

  cmd

  Click OK to open a command prompt window.

  For example, to query the bit of impurity on drive C, type:

  fsutil dirty query C:

  The sample output:
  Volume c is dirty
  Volume C: is dirty

  Is the volume of your sale or it is not dirty?

  You cannot use fsutil or chkntfs from a command prompt to delete the bit of impurity on a volume.

  The only thing that can clear the bit of impurity on a volume is chkdsk /r (or chkdsk/p).  You could tell XP not to check the bit of impurity on a volume where the dirty bit does not erase, but this probably isn't a good idea since there is some sort of problem on the volume.

  You will be not also solve this problem by editing your registry database (pay attention technical support engineers and moderators of Forum)-is not the problem.

  Once a volume is marked as dirty, the only way to clear the dirty bit is to run "chkdsk/r" or "chkdsk/p" when the volume is not in use.  The only way a volume can not be used while XP is just starting to load or from the XP Recovery Console.

  If XP will not run chkdsk correctly when your system restarts or the dirty bit will not erase as it should, you need to look in the Event Viewer log chkdsk and see what is happening and fix it.

  If XP will not always clear the dirty bit, you need to run chkdsk/r of the XP Recovery Console so you can look and see what works and run it again until it works.  If your hard drive fails, you may never be able to clear the dirty bit, in this case, you can also say XP never check the afflicted volume dirty bit (this will usually do the trick).

  Saying XP not to check the bit of impurity on a volume would be risky behavior because there would always be some kind of problem with your hard drive.

• What is this average, Disk Defragmenter has detected that chkdsk command is schduled to run on the volume: (C). Please run chkdsk /f.

  Been trying to run the defrag on my C drive and this message keeps coming up.

  When you try to defragment a volume of that Disk Defragmenter reports:

  Disk Defragmenter has detected that Chkdsk is scheduled to run on the volume: (c :))
   
  Please run Chkdsk /f.

  This means that the volume that you want to defragment was marked 'dirty' XP.  This is not necessarily all of the data has been lost on the volume, it simply means that XP thinks that the volume should be checked to find errors because of something that happened before.

  You won't be able to defragment the volume until the dirty bit has been removed.

  A volume can be marked as dirty, if the system underwent a power interruption (power failure, pulling plug, removing the battery, button / stop), abandoned restart or an abnormal termination.  One of these events?

  When XP starts, it automatically checks the bit of impurity on each volume.  You can also tell XP to ignore the bit of impurity on any volume, but this probably isn't a good idea in case there is a real problem that needs to be fixed.  If you have a hard drive where the dirty bit will not disappear, you can tell XP not to check.

  If the starting XP detects that the volume is dirty, it will be automatically run the check disk with error correction (chkdsk/r) and try to fix the problems detected.

  If the chkdsk command succeeds, it clears the dirty bit, and then you can defragment the volume.

  You can check the status of your bit of impurity from a command prompt window.

  To do this, click Start, run and enter in the box:

  cmd

  Click OK to open a command prompt window.

  For example, to query the bit of impurity on drive C, type:

  fsutil dirty query C:

  The sample output:
  Volume c is dirty
  Volume C: is dirty

  Is the volume of your sale or it is not dirty?

  Since XP of course already thinking that the volume is dirty, XP will automatically run chkdsk when it restarts to try to clear the dirty bit, in order to plan another running chkdsk can not help you much.  Sometimes the auto chkdsk on a reboot will be not only clear things to the top, but you can try it.

  I would like to start in the XP Recovery Console and run chkdsk /r from there you can actually watch and see what happens and decide what to do about this.  When own running chkdsk/r, it clears the dirty bit unless your HARD drive is somewhat distressed.

• Disk Defragmenter has detected that Chkdsk is scheduled to run on the volume (c)

  My computer is as follows: 2.80 ghz, 4 Pent, Intel, HP d530 SFF (PB603a)

  I am running Windows XP PRO SP3. v2.18

  1. When you try to defrag my computer to speed it up i get: DISK DEFRAGMENTER has DETECTED THAT CHKDSK IS SCHEDULED TO RUN VOLUME C: Please RUN CHKDSK C: /F

  I'll then: run cmd, then type chkdsk C:/f/r and I get: THE TYPE OF FILE SYSTEM IS NTFS. CANNOT LOCK THE DRIVE CURRENT.

  CANOE FOR CHKDSK TO RUN BECAUSE THE VOLUME IS IN USE BY ANOTHER PROCESS. WOULD YOU LIKE TO SCHEDULE THIS VOLUME BE CHECKED THE NEXT TIME THE SYSTEM IS RESTARTED? I selects Y and I roboot system, but nothing happens. I do not get a blue screen or any other people say they get.

  2 error Checking: select two options (Auto trouble & scan and attempt recovery of bad sectors. I get the following error message:

  WINDOWS COULD NOT PERFORM THE DISCK CHECK

  These errors appear when I am logged in SafeMode as well. I'm about to become bald of pulling my hair because of the frustration it causes me. If anyone has any ideas can you please help me.

  Did you insert a space between "C:" and "/ F"?  It is not clear in your answer.
  -JW

• I get an error message whenever I try to run Disk Defragmenter

  original title: I get an error message whenever I try to run the Defragmenter of disck

  It says disck Defragmenter is already programmed to run on volume C please run Chdsk/F I checcked my schedule the task and it does not appear as being planned how to fix this?

  Disk Defragmenter may not work on a drive when it detects errors on the disk.  If you need check your drive for errors.  This is usually by running "chkdsk" even if a disk check can be scheduled graphically as well.  Because the disk check must be performed when nothing else is using the drive, reboot and chkdsk runs before Windows loads on this disc.  For more information:

  "How to perform disk error in Windows XP check"
    <>http://support.Microsoft.com/kb/315265 >

  HTH,
  JW

• Disk Defragmenter has detected that Chkdsk is scheduled to run on the volume HP_Pavillion (C). Please run Chkdsk /f

  When I try to defragment my hard drive a message comes up saying

  Original title: defragment my hard drive

  "Disk Defragmenter has detected that Chkdsk is scheduled to run on the volume HP_Pavillion (C). Please run Chkdsk /f

  I have no knowledge of this annex, or how to make it work, but I need to remove this message before it will allow me to do a defrag, any ideas?

  Ideas:

  • You have problems with programs
  • Error messages
  • Recent changes to your computer
  • What you have already tried to solve the problem

  When I try to defragment my hard drive a message comes up saying

  "Disk Defragmenter has detected that Chkdsk is scheduled to run on the volume HP_Pavillion (C). Please run Chkdsk /f

  I have no knowledge of this annex, or how to make it work, but I need to remove this message before it will allow me to do a defrag, any ideas?

  Ideas:

  • You have problems with programs
  • Error messages
  • Recent changes to your computer
  • What you have already tried to solve the problem

  Restart the computer and let chkdsk to complete its work.

• Disk Defragmenter has detected that Chkdsk is scheduled to run on the Volume: C:. Please run Chkdsk /f.

  I know this question has been asked several times, but I did these steps and still not get Defragmenter to work.  My Disk Doctor said I don't have problems with my Defragler work program - but I don't have a C: drive not 'dirty '.  I have Windows XP Home Edition and do not know how to run an XP Recovery Console.  Y at - it an easy way just to get the Defragmenter to work?... when I run Chkdsk... It goes through stages and then closes and the problem is still there.  Defragmenter just stopped working, my computer everything works fine.  Help, please.

  Hmmm...  It should only take a few minutes for ImgBurn to create the bootable XP Recovery Console CD, then maybe one of the songs that you have downloaded (xp_rec_con.iso or install IgmBurn) won't quite right.

  You want ImgBurn to play a happy tune when it is successful and a "Oh no!" message when it fails, but it shouldn't take hours to burn this ISO file bit.  You can try another system.  You can always uninstall ImgBurn when finished.

  I say 'be patient' when you run the chkdsk /r command because sometimes it seems to be stuck (or even go back), but it should end later.  Depending on the volume size, the amount of data on the volume, the speed of your system and what the chkdsk finds to do, you can watch several hours.

  Look at these words from the mouth of Microsoft:

  If you use chkdsk /f on a drive or drives for very large (for example, 70 gigabytes) with a very large number of files (for example, millions of files), chkdsk may take a long time (for example, over several days) to complete. The computer is not available during this time because chkdsk does not relinquish control until it is completed.

  At the time of this writing, I'm guessing a disc 70 GB was "very large" but it is quite modest by today's standards.

  Now with today's technology, it is unlikely to take days, but it could still take some time!  If your HARD drive is afflicted with a problem material and dying, it can never finish or be unable to fix things.

  To start XP, it automatically checks each volume to see if it is dirty and will try to run chkdsk from the afflicted volumes.  Sometimes, it's good enough to clear the dirty bit, sometimes it isn't.  You will see a message at startup if the volume should be checked for consistency and XP will do the best.

  That's exactly what the message tells you:

  Disk Defragmenter has detected that Chkdsk is scheduled to run on the volume: (c :))

  You can query the dirty bit on a volume from the command prompt window.

  Click Start, run and enter in the box:

  cmd

  Click OK to open the command prompt window.

  To query the bit of impurity on drive C, type:

  fsutil dirty query C:

  The sample output:
  Volume c is dirty
  Volume C: is dirty

  Type "exit" to close the command prompt window.

  If you are suspicious of your HARD drive and think it might be failing, now would be a good time to backup your personal data (documents, pictures, music, etc.) to an external location - a separate attached USB drive or a few clouds on the Internet.

• Message ' Disk Defragmenter has detected that chkdsk is scheduled to run on the evolving: (c) "when I click on either analyze or defragment.»»

  Original title: Disk Defragmenter

  When I click on either analyze or defragment a window appears to indicate that, Disk Defragmenter has detected that chkdsk is scheduled to run on the evolving: (c).

  Please run chkdsk/f. My PC is XP service pack 3 - Pro

  Please tell us the next step that allowed me to start my disk defragmentation. Thank you.

  Hello

  -Did you do changes on the computer before this problem?
   
  I suggest you to follow the steps from the link and check if it helps.
  How to defragment your disk Volumes in Windows XP?
  http://support.Microsoft.com/kb/314848
   
  For reference:
  How to analyze and defragment a Windows XP disk?
  http://support.Microsoft.com/kb/305781
   
  Hope this information helps.

• CHKDSK freezes and Disk Defragmenter does not start

  CHKDSK would not normally start as it says that the hard disk was used?  Asked if I wanted chkdsk to run when you restart the computer.  Selected Yes.  Restarted.  CHKDSK has begun.  A frozen one hour in the audit process and would not move for hours.  Disk Defragmenter does not start also.

  Looks like you need run the diagnostics by the hard drive manufacturer, or
  the diagnostics that came with your computer and see what's happening with
  This hard drive.

  wrote in message
  News: * e-mail address is removed from the privacy... *

  CHKDSK would not normally start as it says that the hard disk was used?
  Asked if I wanted chkdsk to run when you restart the computer. Selected
  Yes. Restarted. CHKDSK has begun. A frozen one hour in the audit
  treat and would not move for hours. Disk Defragmenter does not start also.

• I am unable to run Disk Defragmenter.

  When I try to defragment I get an error message that says: "cannot run because Disk Defragmenter scheduled Chkdsk /f..  If please run Chkdsk and try again. "I tried to run Chkdsk, nothing helps.  Can anyone help?

  It's a shame that we don't know anything about your system, or you would be probably done now (it's not your fault), so the first response to a new problem is a bunch of questions.

  Provide information on your system, the better you can:

  What is your system brand and model?

  What is your Version of XP and the Service Pack?

  Describe your current antivirus and software anti malware situation: McAfee, Symantec, Norton, Spybot, AVG, Avira!, MSE, Panda, Trend Micro, CA, Defender, ZoneAlarm, PC Tools, Comodo, etc..

  The question was preceded by a loss of power, aborted reboot or abnormal termination?  (this includes the plug pulling, buttons power, remove the battery, etc.)

  The afflicted system has a working CD/DVD (internal or external) drive?

  You have a true bootable XP installation CD (it is not the same as any recovery CD provided with your system)?

  If the system works, what do you think might have changed since the last time it did not work properly?

  What usually ends up happening, is that you will need run your chkdsk/r from the XP Recovery Console.  That's the short answer.

  If you do not have a bootable XP installation CD authentic where you can boot into the Recovery Console, you can create a CD of bootable XP Recovery Console and run chkdsk /r from there (no media XP required).

  On your question (simple copy/paste for me and a lot to read, but you will understand things when you're done and prevents you from losing time trying ideas that will not work):

  When you try to defragment a volume of that Disk Defragmenter reports:

  Disk Defragmenter has detected that Chkdsk is scheduled to run on the volume: (c :))
   
  Please run Chkdsk /f.

  This means that the volume that you want to defragment was marked 'dirty' XP.  This is not necessarily all of the data has been lost on the volume, it simply means that XP thinks that the volume should be checked to find errors because of something that happened before.

  You won't be able to defragment the volume until the dirty bit has been removed.

  This does not mean that a disk check is scheduled to run, and you can't cancel what needs to happen in this case because this isn't the problem.

  Also the dirty bit is not set on a volume, you can still run a disk defrag with a record of date of arrival in the meantime (try).

  Entry of commands to reset or erase a disc awaiting review is therefore a waste of time - that is not the problem.

  A volume can be marked as dirty, if the system underwent a power interruption (power failure, pulling plug, removing the battery, button / stop), abandoned restart or an abnormal termination.  One of these events?

  When XP starts, it automatically checks the bit of impurity on each volume.  You can also tell XP to ignore the bit of impurity on any volume, but this probably isn't a good idea in case there is a real problem that needs to be fixed.  If you have a hard drive where the dirty bit will not disappear, you can tell XP not to check.

  If the starting XP detects that the volume is dirty, it will be automatically run the check disk with error correction (chkdsk/r) and try to fix the problems detected.

  If the chkdsk command succeeds, it clears the dirty bit, and then you can defragment the volume.

  You can check the status of your bit of impurity from a command prompt window.

  To do this, click Start, run and enter in the box:

  cmd

  Click OK to open a command prompt window.

  For example, to query the bit of impurity on drive C, type:

  fsutil dirty query C:

  The sample output:
  Volume c is dirty
  Volume C: is dirty

  You cannot use fsutil or chkntfs from a command prompt to delete the bit of impurity on a volume.

  The only thing that can clear the bit of impurity on a volume is chkdsk /r (or chkdsk/p).  You could tell XP not to check the bit of impurity on a volume where the dirty bit does not erase, but this probably isn't a good idea since there is some sort of problem on the volume.

  You also won't solve this problem by editing your registry database - not where is the problem.

  Once a volume is marked as dirty, the only way to clear the dirty bit is to run "chkdsk/r" or "chkdsk/p" when the volume is not in use.  The only way a volume can not be used while XP is just starting to load or from the XP Recovery Console.

  If XP will not run chkdsk correctly when your system restarts or the dirty bit will not erase as it should, you need to look in the Event Viewer log chkdsk and see what is happening and fix it.

  If XP will not always clear the dirty bit, you need to run chkdsk/r of the XP Recovery Console so you can look and see what works and run it again until it works.  If your hard drive fails, you may never be able to clear the dirty bit, in this case, you can also say XP never check the afflicted volume dirty bit.

  Saying XP not to check the bit of impurity on a volume would be risky behavior because there would always be some kind of problem with your hard drive.

  You can manually program the disk with error correction check to run at the next reboot of the system, but if the dirty bit has been set, XP should run check disk automatically with error correction during the next reboot.

  This is usually the case that after a reboot, the problems will be resolved since XP will automatically run check disk on the Sales volumes when it restarts.  If you do not check that the chkdsk results of newspapers after his execution on a restart, you will never know what problems are corrected or remain.

  When you choose to run the check disk with error correction in the Tools menu of disk properties, you will be prompted with a message similar to the following:

  The disk check cannot be performed because the disk check utility needs exclusive access to some Windows files on the disk
  .
  These files can be access only by restarting Windows.  You want to schedule the disk check to occur the next time that you restart Windows?

  Answer Yes, if you want to schedule the check disk on the next reboot of Windows.

  When you choose to run the check disk with error correction in the command prompt window, you will be prompted with a message similar to the following:

  The type of the file system is NTFS.
  Cannot lock the current drive.

  Chkdsk cannot run because the volume is in use by another process.  You want to schedule this volume to be
  check the next time the system restarts? (Y/N)

  Answer Yes, if you want to schedule the check disk on the next reboot of Windows.

  When XP restarts, let the disc over to check and correct the problems, he could find.  Do not interrupt the disk check.  It can take a long time (hours or days) to complete or they seem to be "stuck".  Be patient.  If the HARD drive light flashes, it's something.  Keep an eye on the amount of the percentage to be sure that it is still making progress.  It may even seem to go back sometime.

  Is there a problem with the chkdsk command that works on reboot and it doesn't really seem to do something (too fast) or not to clear the dirty bit (check the dirty bit), the command chkdsk which took to restart results in the Event Viewer Application log.  Look there to see what happened.

  When chkdsk runs automatically reboot, you may wonder where to find the results.  The results appear in the Event Viewer Application log.

  You will need to get there after the disk check performed and XP has finished loading for the results and all the problems.

  To view the logs in Event Viewer, click Start, settings, Control Panel, administrative tools, event viewer.

  A shortcut to the event viewer is to click on start, run and enter in the box:

  %SystemRoot%\system32\eventvwr.msc

  Click OK to launch the event viewer.

  Look in the Application log for a proposed Winlogon event, something like this successful race:

  Event type: Information
  Event source: Winlogon
  Event category: no
  Event ID: 1001
  Description:

  Checking file system on C:

  The type of the file system is NTFS.

  A disk check has been programmed.

  Windows will now check the disk.
  39070048 KB total disk space.
  25151976 KB in 78653 files.
  48256 KB in 10264 index.
  0 KB in bad sectors.
  237080 KB in use by the system.
  65536 KB occupied by the log file.
  13632736 KB available on disk.

  Windows has finished checking your disk.

  If you see errors - same errors that are corrected, you must run the disk checking with correction of error again (chkdsk/r) until you see no error.  You should have no errors.

  If you need help interpreting your event, post it here for analysis.

  If you double-click on an event, it will open a window of properties with more information.  On the right are black up and down arrow keys to scroll through the open events. The third button that looks like two overlapping pages is used to copy the details of the event in your Windows Clipboard.

  When you find an interesting event that occurred at the time of your question, click on the third button at the top and arrows to copy the details and then you can paste the details (right click, paste or CTRL-V) the text in detail here for analysis.  Remove all personal information from your information after you paste If you are forced to do so.

  If the chkdsk command that runs on every reboot XP does not clear the dirty bit, you must run chkdsk/r from the XP Recovery Console and see if that will clear things upward.  It is a good idea because you can watch chkdsk as it works and see the results on your screen instead of looking in the event viewer connects or wondering what happened (she also just 'feels' better when we see that it works).

  If you have no authentic XP bootable installation CD to boot into the XP Recovery Console, you can create a CD bootable XP (no XP media required) Recovery Console, and then run chkdsk /r manually.

  Need instructions on how to create a CD of bootable XP Recovery Console to run chkdsk/r manually?

• For windows XP Disk Defragmenter it please help...

  How can I get my Defragmenter to work after receiving the error message: (c) defragmentation was interrupted because of contradictions that were detected in the file system. Please run CHKDSK or SCANDISK on (c) to repair these inconsistencies, then run Disk Defragmenter. I ran CHKDSK and SCANDISK but I still get the message.

  Have you run "chkdsk" with the /F or/r option?
  If not, start-> Run-> "cmd".
  Then, enter the command:
  CHKDSK c: /R
  It will then complain that it cannot check the drive as it is in use and offers to do the next time.  Answer 'Y' to this request, then restart.  The chkdsk operation will take more than two hours to complete.

  HTH,
  JW

• My disk defragmentation will not start or analyze. What I would do.

  When I press start it will be bot do anything. I tried to go to the drfr.inf press on install that nothing the DCOM thingy is in automatic mode. What should I do?

  Hello

  · Were you able to perform before defragmentation?

  · Do you remember all the recent changes on the computer before the show?

  · What is the service pack installed?

  Check is it y of error codes and error message appears in Event Viewer: how to view and manage the event logs in Event Viewer in Windows XP: http://support.microsoft.com/kb/308427

  Run chkdsk on the drive, and then perform a disk defragmentation. Link, you can refer to the procedure: how to perform disk error checking in Windows XP: http://support.microsoft.com/kb/315265

• Disk Defragmenter won't end

  original title: Disk Defragmenter won't commplete

  defragments up to 12% and rises to 98% and says can not complete

  Hi matthewzabel,

  · What is the full error message that you receive with the error code as appropriate?

  · Were you able to perform before defragmentation?

  · Do you remember all the recent changes on the computer before the show?

  · What is the service pack installed?

  Run chkdsk on the drive, and then perform a disk defragmentation.

  Link, you can refer to the procedure: how to perform disk error checking in Windows XP: http://support.microsoft.com/kb/315265