FIX: chkdsk stuck on an external hard drive

Andrew Wafer
by Andrew Wafer
Author
3 Comments
Download PDF
Affiliate Disclosure

fix chkdsk frozen in Windows 10

If your Windows 10 device is running slow, or if you get force close errors, a good idea is to run a general chkdsk operation. This way you will be able to fix errors and repair any corrupted files, resulting in a more stable and smoother Windows 10 system. This works just as well even if you are running it on an external hard drive.

Many complaints have risen about a chkdsk stuck, as more and more users aren’t capable to fix their Windows 10 problems since the disk check can’t be completed.

As you know, when a disk check is running, it is not recommended to reboot your device as you can end up hard bricking it. So, you should be patient until the check is over – in most cases this can take hours or even a whole day (so there is no problem with the disk check, you just have to let the process do its work).

If you are running a chkdsk on your external hard drive and it is stuck, try to follow the steps from below to fix it.

What can I do if chkdsk gets stuck on an external hard drive?

1. Use the Registry Editor

  1. Use the Windows 10 install CD or a repair CD (recovery image) of Windows 10.
  2. Enter the mentioned CD and reboot your device.
  3. Now, from the CD main window run cmd by pressing and holding Shift + F10 keyboard keys.command prompt window
  4. Next, on the cmd window type regedit in order to open Registry Editor.regedit window
  5. Navigate to HKEY_LOCAL_MACHINE folder and from there select Load Hive.
  6. Go to path C:WindowsSystem32Config and pick System. If a name will be prompted enter something intuitive, such as Disksys, and just press enter to confirm.
  7. Now, you will have to navigate towards DisksysControlSet001ControlSession Manager and select BootExecute.
  8. From there change the autocheck autochk * /rDosDeviceC: line into autocheck autochk *.
  9. Go to your Disksys folder, select unload Hive and exit Registry Editor.
  10. Then in cmd type chkdsk c: /r and wait for the new process to complete.

If you can’t edit your Windows 10’s registry, read this handy guide and find the quickest solutions to the issue.


Can’t access the Registry Editor? Things aren’t as scary as they seem. Check out this guide and solve the issue quickly.


2. Run Disk Cleanup

  1. In the search box on the taskbar, type disk cleanup, and select Disk Cleanup from the list of results.
  2. Select the drive you want to clean up, and then select OK.
  3. Under Files to delete, select the file types to get rid of. To get a description of the file type, select it.
  4. Click OK.

So, if you can’t wait for the chkdsk process to complete or if you think that the disk check is stuck, try to follow the steps from above in order to fix this Windows 10 problem.

If you have any other questions or suggestions, don’t hesitate to leave them in the comments section below and we’ll be sure to check them out.

Editor’s Note: This post was originally published in April 2014 and has been revamped and updated in February 2020 for freshness, accuracy, and comprehensiveness.

Was this page helpful?
Thanks for letting us know! You can also help us by leaving a review on MyWOT or Trustpillot.
Get the most from your tech with our daily tips
Tell us why!
  • Just for clarification: Is this guide meant for people who´se machine always boots into checkdisk and therefore they can’t boot into Windows any more? That’s what you mean by being stuck at checkdisk, right?

    My case is as following:
    When I use the chkdsk /r command, then upon reboot, the checkdisk operation always gets stuck at 16 % and doesn’t move from then onwards. Even if I wait for 24 hours.
    I can, however, after that boot into Windows and use the computer normally. Even though chkdsk is stuck (at 16 %), I am not stuck in chkdsk, so to say.

    Now my question is, whether this article is meant to help me getting beyond 16 % when I execute chkdsk /r, or whether it is not relevant to my issue, since I don’t suffer from not being able to boot beyond chkdsk?

    Would be nice if someone could clarify this for me.
    Thx