Chkdsk cannot run because the volume is in use by another process

First of all:: I was expecting that 'while on 'C:\Windows\System32', I can run ' 'chkdsk c: /f /x'since '/F Fixes errors on the disk.' and '/X Forces the volume to dismount first if necessary. I really tried running this command 'chkdsk c: /f /x' while on 'C:\Windows\System32'. However, I found that same error. However, I think I can never be able to force a dismount and full scan/fix of C drive using "chkdsk C: /f /x"

    Correct, while most other disks can be dismounted for a repair/scan, C: cannot because Windows is using it.  The current directory is only used by chkdsk to determine what partition to scan; it does not scan individual folders by request, only complete partitions (drive letters).

first:: @If you just want to scan for errors without rebooting, use "chkdsk C:".  You can usually force a dismount and full scan/fix of other drives using "chkdsk D: /f /x".@ WHAT BENEFIT IS THERE FROM RUNNING THAT COMMAND ON DRIVERS NOT HAVING OS INSTALLED?

    Other drives (if connected) can get corrupted too.  The benefit of running chkdsk D: /f /x is that you can scan and repair these drives without rebooting your computer.  Very helpful if the computer loses power or crashes during file writing, as NTFS will frequently zero out files, truncate files, or start cross-linking files if such corruption is not fixed promptly.  Ironically, without the /f flag, chkdsk often says that there are no errors on such disks.

Second:: Do you think that I can use all these options for commands all together ?

'chkdsk c: /f /x /r

    Absolutely.  chkdsk C: /f /x /r will dismount the drive (/x), fix (/f), and check for bad sectors (/r).  If you want to do a thorough evaluation of bad sectors, add /b too.

    For the user, it's nice to see all those flags.  However, chkdsk implicates other flags when certain flags are used; so you could accomplish a dismount, fix, and full evaluation of bad sectors using either chkdsk C: /f /r /b /x or chkdsk C: /b /x (/x implies /r, which implies /f).  You can see all chkdsk's commands by typing chkdsk /? in the command window.

Finally: Since that command didn't list any errors when I scanned my hard disk C with that command

'chkdsk C: /r /f ' after scheduling in a boot-time scan, I really fairly still think that my hard disk has some bad sector(boot sector).

Some newer BIOSes have hard disk diagnostic tests that you can run from the BIOS that work well at testing the hard drive. I don't remember exactly how to do it, and I don't know for sure if my BIOS supports it. Do you think I should download the Ultimate Boot CD and run one of its many hard disk diagnostic programs. Burn it to a CD (using the Burn Disk Image option in my CD Burning program.

    If you're concerned that your HDD is failing, it would be better (and easier) to check its SMART data.  I recommend using Crystal Disk Info for this (link to ad-free portable version).  Just take a screenshot, post it here and I'll take a look.  Make sure that the window is tall enough to show all the values.

Thanks a lot,

Despite my lacking of knowing any things of those results shown in that screen shot, I would be saying there is no thing with which I scanned my computer. Thus, I am awaiting your reply to confirm for me if there are somethings need to be scanned by Ultimate Boot Cd or not.

First of all:: I was expecting that 'while on 'C:\Windows\System32', I can run ' 'chkdsk c: /f /x'since '/F Fixes errors on the disk.' and '/X Forces the volume to dismount first if necessary. I really tried running this command 'chkdsk c: /f /x' while on 'C:\Windows\System32'. However, I found that same error. However, I think I can never be able to force a dismount and full scan/fix of C drive using "chkdsk C: /f /x"

    Correct, while most other disks can be dismounted for a repair/scan, C: cannot because Windows is using it.  The current directory is only used by chkdsk to determine what partition to scan; it does not scan individual folders by request, only complete partitions (drive letters).

first:: @If you just want to scan for errors without rebooting, use "chkdsk C:".  You can usually force a dismount and full scan/fix of other drives using "chkdsk D: /f /x".@ WHAT BENEFIT IS THERE FROM RUNNING THAT COMMAND ON DRIVERS NOT HAVING OS INSTALLED?

    Other drives (if connected) can get corrupted too.  The benefit of running chkdsk D: /f /x is that you can scan and repair these drives without rebooting your computer.  Very helpful if the computer loses power or crashes during file writing, as NTFS will frequently zero out files, truncate files, or start cross-linking files if such corruption is not fixed promptly.  Ironically, without the /f flag, chkdsk often says that there are no errors on such disks.

Second:: Do you think that I can use all these options for commands all together ?

'chkdsk c: /f /x /r

    Absolutely.  chkdsk C: /f /x /r will dismount the drive (/x), fix (/f), and check for bad sectors (/r).  If you want to do a thorough evaluation of bad sectors, add /b too.

    For the user, it's nice to see all those flags.  However, chkdsk implicates other flags when certain flags are used; so you could accomplish a dismount, fix, and full evaluation of bad sectors using either chkdsk C: /f /r /b /x or chkdsk C: /b /x (/x implies /r, which implies /f).  You can see all chkdsk's commands by typing chkdsk /? in the command window.

Finally: Since that command didn't list any errors when I scanned my hard disk C with that command

'chkdsk C: /r /f ' after scheduling in a boot-time scan, I really fairly still think that my hard disk has some bad sector(boot sector).

Some newer BIOSes have hard disk diagnostic tests that you can run from the BIOS that work well at testing the hard drive. I don't remember exactly how to do it, and I don't know for sure if my BIOS supports it. Do you think I should download the Ultimate Boot CD and run one of its many hard disk diagnostic programs. Burn it to a CD (using the Burn Disk Image option in my CD Burning program.

    If you're concerned that your HDD is failing, it would be better (and easier) to check its SMART data.  I recommend using Crystal Disk Info for this (link to ad-free portable version).  Just take a screenshot, post it here and I'll take a look.  Make sure that the window is tall enough to show all the values.

If you don't specify a partition to scan, chkdsk assumes the drive letter in your "current directory" (the command-prompt path).  That's why it behaves the same way with or without the "C:" in the command.

    In addition, C: cannot be dismounted because of numerous OS files being open while Windows is running.  That's why chkdsk asks whether you want to schedule a boot-time scan.  If you just want to scan for errors without rebooting, use "chkdsk C:".  You can usually force a dismount and full scan/fix of other drives using "chkdsk D: /f /x".

    However, in my experience, without the "/f" (fix) flag, chkdsk frequently ignores file/folder corruption caused by power loss, saying that no errors were found, and yet a file that was being written to during power loss is 0 KB.  After running chkdsk with the "/f" flag, the file regains its proper size and is usable again.

The message  'cannot lock current drive' is not an error as such.  That will always be the case when you try to run the disk check on the system drive.

 re. "why ''chkdsk /r /f' ran"  - If you don't specify a drive letter chkdsk will use the current default drive as the target.   In your case, with the command prompt open on the c drive that is equivalent to typing chkdsk C:   /f  /r

Although many people harmlessly use /f and /r together, it is redundant.  /r runs the same disk checks as /f and then ADDITIONALLY runs a check for bad sectors.