Helping people with computers... one answer at a time.

Chkdsk checks your disk for errors at a low level. That means chkdsk needs exclusive access to the disk. We'll look at why that is and what to do.

I think I've got a problem with my hard disk, and tried to run chkdsk but I keep getting this "chkdsk cannot run because the volume is in use by another process" error. What's that mean and what do I do to fix it?

Chkdsk is an important and little understood command line utility that comes with every version of Microsoft Windows. Its purpose, as its mangled name implies, is to "check" your "disk".

In order to do its work, chkdsk needs total and exclusive access to the disk it's about to check. If it doesn't have that "chkdsk cannot run because the volume is in use by another process" results. ("Volume" in this case really means "the disk that's being checked".)

I'll look at why, what to do, and what it looks like as it happens.

Chkdsk Cannot Run

Here's the scenario we're talking about:

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

To have gotten this far, we'll have had to:

  • Start a Windows Command Prompt - in Windows Vista or Windows 7 doing so with administrative privileges (right click on the Start, All programs, Accessories, Command Prompt shortcut and click on "Run as Administrator")

  • Run the command CHKDSK, including the "/F" (fix) or "/R" (repair) options.

Exclusivity

"... you can't run chkdsk with a fix or repair option on the drive from which Windows was loaded. At least, not while Windows is running."

In order for chkdsk to be able to fix or repair a disk it needs to be the only program accessing the hard disk - the only program. If any other program has a file open on that disk, then it's considered to be "in use", and chkdsk can't get the exclusive access it needs.

"But I have no programs running!?" I hear you say.

Yes, you do. Windows is running. In fact, Windows has several files open including the files containing the registry, the system paging file, as well as the executable files that make up Windows itself.

Put another way, you can't run chkdsk with a fix or repair option on the drive from which Windows was loaded.

At least, not while Windows is running.

Other Disks

While getting this error on the Windows drive is the most common, it's certainly not the only case. Let's say you have a drive "D:". If you have Windows Explorer open on drive D:, or perhaps have a word processing document open that lives on that disk the same situation applies.

The solution is easier though: close those programs. Make sure nothing is accessing the contents of that drive and try again. You should be good to go.

Unless, of course, you happened to move your paging file to D:, in which case you're back in the "can't do it while Windows is running" situation as the paging file is always open while Windows is running.

Chkdsk on C:

The "magic answer", so to speak, is actually part of the very error message we see:

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)

Answer the question with a "Y" for yes, followed by Enter, and chkdsk will run the next time you reboot Windows, before Windows itself begins to run. That's the only time that chkdsk can have the exclusive access to the system disk that it needs.

This volume will be checked the next time the system restarts.

When you reboot, the reboot will proceed normally until the screen changes to include this message:

Chkecking file system on C: - The type of the file system is NTFS. A disk check has been scheduled. To skip disk checking, press any key within 10 second(s).

As the message indicates you have 10 seconds to press any key on the keyboard to skip the disk check. After 10 seconds chkdsk proceeds.

As chkdsk runs you'll see information updating on the screen:

Chkdsk progress as it runs at reboot

Finally chkdsk completes, pausing for a moment with a summary report left on your screen as seen in this composite log:

Composite log of chkdsk operation on reboot

Your specifics of course will be different, but the general idea is the same. As you can see here, chkdsk actually fixed a couple of problems that it found.

The computer should then reboot and load Windows normally.

Bottom Line

"Chkdsk cannot run because the volume is in use by another process" simply means that in order to fix your hard disk chkdsk needs to be the only program accessing it. For some drives, that's as simple as closing programs which are using the drive in question. For the system drive from which Windows was loaded, it means a special step needs to be taken such that chkdsk runs when you reboot.

Article C4507 - October 28, 2010 « »

Share this article with your friends:

Share this article on Facebook Tweet this article Email a link to this article
Leo Leo A. Notenboom has been playing with computers since he was required to take a programming class in 1976. An 18 year career as a programmer at Microsoft soon followed. After "retiring" in 2001, Leo started Ask Leo! in 2003 as a place for answers to common computer and technical questions. More about Leo.

Not what you needed?

Recent Comments
13 Comments
Tony
December 27, 2011 4:40 PM

Leo, thanks for your detailed information on chkdsk, running chkdsk finally allowed me to delete a folder on my desktop that had been haunting me for some time.

I run a dual boot system Windows 7 64 bit alongside Linux Ubuntu 11.04, I believe my issue was that I copied some files from Linux into a Windows folder which had special characters in their names. I believe this is the case since I can access drives on the Windows side from Linux but not the other way around.

I had trouble running chkdsk because I would enter Windows before my Linux grub menu would time out which was always before the 10 second chkdsk bypass message (I would hit enter on the Windows operating system in the grub menu). After letting the grub menu time out, the chkdsk message appeared and I let it run with the /f command to fix, it fixed the files (actually removed them) and allowed me to delete the folder. (I should note that I have changed my grub menu to load Windows 1st and also have a 30 second delay instead of the default 10 second)

Thanks again.

Chris
July 11, 2012 7:27 PM

I am trying to reset my computer to an earlier date but I receive an error message as follows, system in use also I have tried to do command prompt as described in your blog but comes up error not alowing fix or repair disk after already saying yes to repair upon reboot what can I do. i also do not have a Windows 7 disk my computer came preloaded with windows 7 home premium 64 bit with 2 point touch please can you help me.

rohit pundeer
January 30, 2013 11:05 AM

how to fix the drive on which windows exist??????
i have errors with c drive which include windows,please help...

Martha
February 2, 2013 3:52 PM

hi, I've run into the same problem, but in my case when it boots after "windows will now check....", it says:

cannot open volume for direct access.
autochk cannot run due to an error caused by a recently installed software package.

here's the problem... I haven't installed any software for the last 6 months.

thanks

T.J.G.
April 1, 2013 2:11 PM

For any other readers coming across this who may have a similar issue to Martha when running chkdsk on Windows 7: "cannot open volume for direct access. autochk cannot run due to an error caused by a recently installed software package."

Try booting from external media (like a CD ROM drive or a USB drive) and then running chkdsk using the /X option to dismount the drive. Then nothing is running off your main hard drive, and chkdsk will be more likely to run without this error. It worked for me.

A good way to do that is to create a system repair disk, boot from the system repair disk, and then run chkdsk from the system repair disk instead of running chkdsk from your harddrive.

Here are instructions how to do that:

{Copyrighted material removed. It's all at the link below.}

http://www.ehow.com/how_7517460_create-bootable-chkdsk.html