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

Anonymous
2014-12-25T22:56:33+00:00

Hi,

Whenever I turn on my computer or even restarted it, and then tried to run the command 'chkdsk /r /f', I faced the error 'cannot lock current drive', although there are no other process hare running.

I had to schedule it to be running in the next restart.

When I scheduled it to be running in the next system restart , it was running well when it was restarted.

Threads merged.

Duplicate deleted.

Moved from Windows 7 Email and Communications Forum.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2014-12-31T16:14:25+00:00

I personally don't think you'd gain anything from a scan with UBCD.  We can learn all about the HDD's health by looking at its SMART data.  It may pass a diagnostic test with flying colors, and still have corrupted numerous files (in the past) and/or have many (remapped) bad sectors.

    Looking at your HDD's SMART status, I can see that it had 104 (hex 68) bad sectors which have since been reallocated (see Reallocated Sectors Count).  Since Current Pending Sector Count is 0, all suspected bad sectors have been successfully remapped, probably thanks to an earlier chkdsk /r scan.

    Everything else looks good.  I would suggest keeping an eye on the HDD every once in a while to make sure that it isn't developing more bad sectors (Current Pending Sector Count or Read Error Rate increasing from 0 in the far-right column).

    In case you didn't know this, HDDs are quite sensitive to being jostled while in operation.  Setting a laptop down too hard while it's on are is one the easiest ways to kill a laptop's HDD.  If you need a laptop that can be thrown around, it would be a good idea to upgrade to a SSD, since they have no moving parts.  This will also greatly speed up the laptop since the HDD is the biggest bottleneck in practically all laptops made nowadays.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

60 additional answers

Sort by: Oldest
  1. Anonymous
    2014-12-29T03:55:12+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-12-30T10:41:43+00:00

        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.

    Thank you all of you very much indeed,

    First of all:: I was expecting that 'while on 'C:\Windows\System32', I could 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"

    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?

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

    'chkdsk c: /f /x /r

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2014-12-31T01:26:17+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-12-31T11:59:49+00:00

    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.

    Was this answer helpful?

    0 comments No comments