When i click defrag - an error message comes up: "disk defragmenter has detected that Chkdks is scheduled to run on the volume C: please run chkdsk /f. what is this -- i tried check disk - >>right click C: drive, properties> and tools tab >- then error checking, it does about 3/4 then reports "windows was unable to complete the disk check" What is going on... please help!!
ok - i found another thread - tried what they said -- still no go i cant even run chkdsk /f it says cannot run because the volume is in use by another process - wouild u like to do at next restarrt - i tried this and still will not chkdsk??
has anyone got a solution to this? im having the same problem and i did a search in all forums here and this is the closest thread i found to solving my problem. but it doesnt really tell how to fix it. any help???
I need to know what version of windows you guys are running, there is a lot of fixes for the problem, but nothing I could easily find to cover all os's. Be glad to research for you. CD.
EDIT>Always remember something after I post. Look in the event viewer, look for red x's after the defrag, or check disk fails. Click on the red x and then the blue link, it will send a error code to ms, and they will tell of a specific fix. It only takes a minute or two. This following is from the help and support center. If you have done all of this, maybe try to repair windows, but if you have upgraded to sp2 and don't have a disk it won't let you. Sometimes, backing up and doing a clean install is the best way to go. When windows xp starts to go down it can really get screwed up. System restore is only as good as the last restore, the bad info gets stored and there's nothing stable to go back to. Well here's some tips. I tried to filter out the junk and post only what relates to xp. To run Chkdsk at the command prompt 1. Click Start, and then Run. 2. In Open, type cmd, and then press ENTER. 3. Use one of the following procedures: • To run Chkdsk in read-only mode, at the command prompt, type chkdsk, and then press ENTER. • To repair errors without scanning the volume for bad sectors, at the command prompt, type chkdsk volume:/f, and then press ENTER. Note If one or more of the files on the hard disk drive are open, you will receive the following message: Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N) Type Y, and then press ENTER to schedule the disk check, and then restart your computer to start the disk check. • To repair errors, locate bad sectors, and recover readable information, at the command prompt, type chkdsk volume:/r, and then press ENTER Note If one or more of the files on the hard disk drive are open, you will receive the following message: Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y/N) Type Y, and then press ENTER to schedule the disk check, and then restart your computer to start the disk check. To run Chkdsk from My Computer or Windows Explorer 1. Double-click My Computer, and then right-click the hard disk drive that you want to check. 2. Click Properties, and then click Tools. 3. Under Error-checking, click Check Now. A dialog box that shows the Check disk options is displayed, 4. Use one of the following procedures: • To run Chkdsk in read-only mode, click Start. • To repair errors without scanning the volume for bad sectors, select the Automatically fix file system errors check box, and then click Start. • To repair errors, locate bad sectors, and recover readable information, select the Scan for and attempt recovery of bad sectors check box, and then click Start. Note If one or more of the files on the hard disk drive are open, you will receive the following message: The disk check could not be performed because the disk check utility needs exclusive access to some Windows files on the disk. These files can be accessed by restarting Windows. Do you want to schedule the disk check to occur the next time you restart the computer? Click Yes to schedule the disk check, and then restart your computer to start the disk check. The following table lists the exit codes that Chkdsk reports after it has finished: Exit code Description 0 No errors were found. 1 Errors were found and fixed. 2 Disk cleanup, such as garbage collection, was performed, or cleanup was not performed because /f was not specified. 3 Could not check the disk, errors could not be fixed, or errors were not fixed because /f was not specified. Detecting and repairing disk errors You can use the Error-checking tool to check for file system errors and bad sectors on your hard disk. Open My Computer, and then select the local disk you want to check. On the File menu, click Properties. On the Tools tab, under Error-checking, click Check Now. Under Check disk options, select the Scan for and attempt recovery of bad sectors check box. Notes To open My Computer, click Start, and then click My Computer. All files must be closed for this process to run. If the volume is currently in use, a message box will appear prompting you to indicate whether or not you want to reschedule the disk checking for the next time you restart your system. Then, the next time you restart your system, disk checking will run. Your volume will not be available to perform other tasks while this process is running. If your volume is formatted as NTFS, Windows automatically logs all file transactions, replaces bad clusters, and stores copies of key information for all files on the NTFS volume. SYMPTOMS When you start your computer to a command prompt and then run Chkdsk.exe, you may receive the following error message: Errors found, F parameter not specified. Corrections will not be written to disk. CHKDSK cannot check the validity of this drive because the following path is too long: <Path> To run CHKDSK, the drive must not contain paths that are longer than 67 characters. To shorten the path, use the MOVE command to rename some of the directories in the path. Back to the top CAUSE This behavior can occur if the command line you type contains more than 67 characters. Back to the top RESOLUTION To work around this issue, use ScanDisk instead of Chkdsk to check your hard disk for errors. For information about how to use ScanDisk, click Start, click Help, click the Index tab, type scandisk, and then double-click the "ScanDisk" topic. RESOLUTION To test the hard disk, run ScanDisk. To run ScanDisk from within Windows, follow these steps: 1. Click Start, point to Programs, point to Accessories, point to System Tools, and then click ScanDisk. 2. Click the drive you want to examine for errors. 3. Click Thorough, and then click Start. Running ScanDisk with the Thorough option selected examines the hard disk for physical damage. If damaged data is detected, ScanDisk gives you the option to save the damaged data to a file or to discard the data. The ScanDisk surface scan may take a considerable amount of time on large hard disks. To run ScanDisk from a command prompt outside of Windows, follow these steps: 1. Click the Start button, click Shut Down, click Restart The Computer In MS-DOS Mode, and then click Yes. 2. Type the following command at the command prompt, and then press ENTER scandisk <x>: where <x> is the letter of the hard disk you want to check. 3. When ScanDisk finishes its initial check, it prompts you to perform a surface scan on the drive. Click Yes or press ENTER. If ScanDisk is unable to repair damaged data, or indicates that the hard disk has physical damage, you may need to have the hard disk checked by a qualified service professional.
Thought of something else. Try uphclean.msi. It forces processes to release. I had a problem during shutdown, processes wouldn't release and close. Then the comp would have to save the chunk of memory to hd and deal with it on startup. It may apply to why ckdsk, scandsk, and defrag can't follow through. They have to be able to do their job. If a process won't let go, failure. You can downlaosd it from the microsoft downloads. They are stingy with it, if you can't find it i will send a copy to you.
I have had the exact same problem and spent hours searching the net for an answer that worked. HERE IS HOW I GOT IT TO WORK!!! Boot from the WindowsXP Cd into the Recovery Console. Run the chkdsk from there. The chkdsk should run without any problems. Then reboot back into Windows and check to see if it will Defrag. It should as it did in my case, and trust me, nothing else worked! If it still tries to run a chkdsk on every reboot then all you have to do is edit the following registry: Go to: HKEY_LOCAL_MACHINE System CurrentControlSet Control Session Manager Then in Session Manager you should see the key "Boot Execute" Modify the key so that it only says: autocheck autochk * Remember you do not have to modify the registry unless you are stuck in the continuous chkdsk loop! That is all! Worked for me!
