Как отменить проверку диска во время проверки?
Во время запуска Windows вам будет предоставлено несколько секунд, в течение которых вы можете нажать любую клавишу , чтобы прервать запланированную проверку диска. Если это не помогает, отмените CHKDSK, нажав Ctrl + C, и посмотрите, подходит ли это вам.
Как выйти из режима проверки диска?
Во время следующей загрузки нажмите Esc, Enter или соответствующую клавишу, чтобы остановить запуск ChkDsk.
Как отключить проверку диска при запуске системы?
Нажимаем комбинацию клавиш Win-R или Пуск => Все программы => Стандартные => Выполнить => вводим команду cmd -> нажимаем OK. В открывшемся окне вводим команду chkntfs /X C: (где C: — имя диска, который постоянно проверяется). Теперь проверка отключена.
Как пропустить проверку диска Windows 10?
- Запустить полную проверку диска. Откройте «Мой компьютер» => кликните правой кнопкой по диску, который постоянно проверяется => из контекстного меню выберите «свойства» => затем на вкладке «сервис» нажмите кнопку «Выполнить проверку» .
- Отключить проверку диска.
Что будет если остановить проверку диска?
Утилита проверяет каждый файл на вашем компьютере, и чем объёмнее диск, тем больше времени на это уйдёт. Прервав этот процесс, вы не позволяете программе выполнить свою работу.
Как отменить проверку диска при загрузке Windows?
Отключить проверку диска
Нажимаем «Пуск» > «Выполнить» > вводим cmd > нажимаем «OK». В открывшемся окне вводим команду: chkntfs /X C: * где С — имя диска, который постоянно проверяется.
Как отменить проверку диска Windows 7?
Для отключения проверки диска с помощью командной строки, открываем командную строку. В Windows Vista, 7, 8 запускать от имени Администратора. В командной строке пишем: chkntfs D: /x – в данном случае отключаем проверку диска D. Для того чтобы вернуть значение по умолчанию, вводим в командной строке chkntfs /d .
Как долго может длиться проверка диска?
Для системы с жестким диском емкостью 1 ТБ CHKDSK может занять до 5 часов, а с увеличением размера жесткого диска время также увеличилось. Но если в случае ЧКДСК застрял на 10%, 11% или в каком-то другом проценте, должно быть что-то, о чем вам нужно позаботиться.
Как отключить проверку смарт?
Как отключить проверку SMART
Если Вы по какой-то причине решите отключить функцию проверки жёсткого диска, то для этого необходимо будет зайти в BIOS материнской платы и в расширенных параметрах поискать раздел SMART Settings . В нём нужно найти раздел SMART Self Test и поставить ему значение Disable .
Как отключить проверку файлов в реестре?
Откройте параметр DisableArchiveScanning => в поле “Значение” введите 0 и нажмите на “ОК”, если вы хотите включить проверку архивов, или в поле “Значение” введите 1 и нажмите на “ОК”, чтобы отключить проверку архивных файлов.
Как отключить в биосе проверку системы?
Чтобы отключить дополнительную проверку, нужно в BIOS Setup найти опцию под названием «Init Display First», также в зависимости от версии БИОС она может называется «Primary VGA BIOS» или «VGA Boot From».
Как запустить проверку жесткого диска через биос?
Проверка через BIOS
При включении компьютера нужно нажать соответствующую клавишу вызова экранного меню (обычно это Del, F2, Esc или F8). Далее с помощью клавиш влево-вправо нужно переключиться на вкладку, где располагается «Primary Hard Disk Self Test» (нужный нам автотест).
Что делать если chkdsk зависает?
- проверьте целостность файловой системы утилитой sfc /scannow.
- проверьте своевременность обновлений для вашей копии Windows.
- немедленно проведите дефрагментацию системного диска
- воспользуйтесь утилитой по очистке системы от любых временных файлов
Как запустить командную строку?
Нажмите Win+X на клавиатуре. Выберите: Командная строка, чтобы запустить командную строку.
How to safely stop a `chkdsk /r /f C:` on Windows 10?
I started a chkdsk /r /f C: on Windows 10, but now that it’s running I want to cancel it. Just powering down the computer risks corruption, so how can I safely abort it?
Ctrl+C isn’t an option: I’m running chkdsk /r /f on the drive that has Windows installed. This cannot be done while Windows is running, but only during startup (outside of CMD). This doesn’t respond to ctrl+c.
Note: the linked duplicate question is NOT the same. That question is about running chkdsk without parameters, and that is safe because it runs in read-only mode. The /r /f flags causes chkdsk to run in read-write mode, so then it’s not generally safe to just kill the process. It needs to be terminated gracefully. Some implementations of fsck (linux equivalent) can be stopped gracefully — even in repair mode — so theoretically it should definitely be possible to safely stop a chkdsk procedure. The main question is: did the Windows devs actually implement a graceful cancellation procedure, and if so how do I trigger it?
7 Answers 7
Not sure since which version of Windows or of chkdsk itself this has been the case, but the Microsoft Learn page about it says
canceling or interrupting chkdsk should not leave the volume any more corrupt than it was before chkdsk was run
- used Sysinternals’ Process Explorer to first Suspend the chkdsk process (and listen for an end to all HDD noises) just for some added peace of mind, then
- opened another cmd window with elevated privileges and did a "chkdsk /x e:" (use your own driver letter) because I saw this suggested elsewhere, and /x:
Forces the volume to dismount first, if necessary. All open handles to the drive are invalidated.
- and finally pressed Del in Process Explorer to actually kill the original chkdsk process.
No big catastrophe ensued, the disk had a few kB of corruption here and there, but overall only in proportions I already expected because I hadn’t been refreshing most of the data for over 1-1.5 decades. (But I also have a second copy I could restore anything from after comparing everything with Beyond Compare.)
Ideally don’t stop chkdsk, even Microsoft don’t seem so sure of their own answer as you can see from their choice of words: "should not" leave the volume any more corrupted. But if risk/benefit analysis forces you to, I would say try to be as unabrupt about it as possible, try to separate the process into some stages like pause/suspend/dismount/etc. (for example now I’m thinking I should’ve tried a Windows shutdown after suspending the process, instead of killing it myself, maybe that would take more care to "deactivate more stuff" in a civilized way and somehow create better conditions for finally killing the process and also getting the HDD’s own controller do some cleanup of its own before being powered down).
Как безопасно остановить `chkdsk / r / f C:` в Windows 10?
Я запустил chkdsk /r /f C: Windows 10, но теперь, когда он работает, я хочу отменить его. Простое выключение компьютера может привести к повреждению, так как я могу безопасно прервать его?
Ctrl + C не вариант: я запускаю chkdsk / r / f на диске, на котором установлена Windows. Это невозможно сделать во время работы Windows, но только во время запуска (вне CMD). Это не отвечает Ctrl + C.
Примечание: связанный дубликат вопроса НЕ является тем же. Этот вопрос касается работы chkdsk без параметров, и это безопасно, поскольку он работает в режиме только для чтения. Эти /r /f флаги причины chkdsk для запуска в режиме чтения-записи, так, то это вообще не безопасно просто убить процесс. Это должно быть прекращено изящно. Некоторые реализации fsck (эквивалентные Linux) могут быть корректно остановлены — даже в режиме исправления — поэтому теоретически должно быть возможно безопасно остановить chkdsk процедуру. Главный вопрос: разработчики Windows действительно реализовали процедуру постепенного отмены, и если да, то как мне ее запустить?
Can you cancel chkdsk while it is running?
I have an on-site tech who against my direct order started a chkdsk /r on a 2TB hard drive for a system we are trying to get back in production right away. Waiting the 2-3 hours for the scan to run is not palatable, and I would prefer not to just shut the PC off.
I had him try Control-C and the pause break key, but it just keeps going.
My Google luck is dry, and I’m only seeing a) don’t b) how to cancel from running.
Does anyone here know how to cancel, other than the power switch?
Tim7139 
Printonomics: Understand the Real Costs of Printing
36 Replies
Krizz
Highly unsafe even if you kill the chkdsk process (taskkill /f /im chkdsk.exe). Chkdsk locks the volume for exclusive access and termination of chkdsk may lead to unforeseen problems. Do it on your own responsibility.
Only when it is about to start. Once it starts your SOL.
OP Tim7139
Highly unsafe even if you kill the chkdsk process (taskkill /f /im chkdsk.exe). Chkdsk locks the volume for exclusive access and termination of chkdsk may lead to unforeseen problems.
This is a boot time scan, so this does not apply.
I would agree with the previous. You will be risking losing some data by simply restarting and there is no other way to abort it once it has started running.
If you can not wait for it to finish the it is up to you to decide if you should risk damage to the data on the disk versus letting it runs its course.
AIUI there is not and stopping it with a lack of power would be a bad idea.
SDA
Krizz
Krizz wrote:
Highly unsafe even if you kill the chkdsk process (taskkill /f /im chkdsk.exe). Chkdsk locks the volume for exclusive access and termination of chkdsk may lead to unforeseen problems.
This is a boot time scan, so this does not apply.
Ah so. In this case the result would be exactly the same as hard reset.
OP Tim7139
Data on the disk is not too worries some. The disk itself is, and given the head movement durring a scan, It’s a high pucker factor.
Almost up to 75% Some days I hate to be right.
TheSteward
In that case tell the employee (s)he’s responsible for any damage to the disk. Then dole out some punishment, like making patch cables all day
OP Tim7139
In that case tell the employee (s)he’s responsible for any damage to the disk. Then dole out some punishment, like making patch cables all day
3rd party contractor, who will not be paid for his added time waiting for the PC to boot.
Unfortunately the 38 effected staff and 180 clients were my bigger concern.
Krizz
Lie it was absolutely necessary 😀
Ouch. Bringing down a production server for that long is hard. While I agree chkdsk can do wonders for a machine having problems, it rarely can justify the time it takes to run to fix the problems.
How much was he charging if you don’t mind my asking?
Hopefully you were able to get things going the way you need now.
OP Tim7139
Hopefully you were able to get things going the way you need now.
We have manual systems, so it was sucky, but not life ending.
It’s a quasi rural centre, so were are running at $150/hour, plus travel, meals, etc.
Darn it. I should not have asked. I wish I could get that much an hour for running chkdsk on a computer.
Oh well at least I get lots of time off with school vacations.
OP Tim7139
Darn it. I should not have asked. I wish I could get that much an hour for running chkdsk on a computer.
Oh well at least I get lots of time off with school vacations.
He got paid for a lot of. poor steps. before having me walk him though the resolution, then deciding chkdsk /r was a good idea.
Robert762
We had to run it with /r on a production server yesterday and it took almost 4 hours to complete. Then had to copy all of the files over to a newly spun up VM. We lost the whole day here for much of the staff. In this case we didn’t have a choice but to run it as we had severe corruption happening. Looks like all is good for us today.
Hope that your system got fixed. In this case you might never know if it needed the /r or not!
OP Tim7139
Hope that your system got fixed. In this case you might never know if it needed the /r or not!
I already know it was not needed, and this was confirmed by it not finding errors!
It is a great tool when it is needed, but like al things when it is known to be unnecessary it is just a time suck.
3rd party contractor, who will not be paid for his added time waiting for the PC to boot.
Unfortunately the 38 effected staff and 180 clients were my bigger concern.
I’d not only NOT pay him for the additional time, but I’d also charge him for the additional down time. 38 employees not able to work X $10 an hour (whatever your average is) X 4 hours of unnecessary downtime = oh look, you owe me money for letting you work on this.
Besides, if you had to walk him thru the resolution, you shouldn’t be paying him at all.
OP Tim7139
Tim7139 wrote:
3rd party contractor, who will not be paid for his added time waiting for the PC to boot.
Unfortunately the 38 effected staff and 180 clients were my bigger concern.
I’d not only NOT pay him for the additional time, but I’d also charge him for the additional down time. 38 employees not able to work X $10 an hour (whatever your average is) X 4 hours of unnecessary downtime = oh look, you owe me money for letting you work on this.
Besides, if you had to walk him thru the resolution, you shouldn’t be paying him at all.
If only life worked that way.
Without hearing everyone’s opinions on what it might do, how do you stop it if you can after its already running?
JerryMays wrote:
Without hearing everyone’s opinions on what it might do, how do you stop it if you can after its already running?
If it’s running pre-startup: Pull the power cord out, or hold the power button to force it off. Cross fingers and restart.
If it’s running in Windows: Run cmd, taskkill /f /im chkdsk.exe Cross fingers and restart.
Norman Picard
If it is running in the pre-startup and you are past Stage 3, meaning it is on 4 of 5 or 5 of 5. then you can just re-start your machine. I have done it on stage 5 of 5, which is the stage of checking the free space, and it started up just fine. If you re-start your machine during stages 1 to 3, you run the risk of loosing data.
We were getting eminent HD failure alarms from the server. We tried doing a /f but it fixed nothing. When we tried backing the disk up, it failed due to sector errors. We really had no choice.
Finally, someone answered the question. Thanks!
Norman Picard you are absolutely correct; thank you!
Thank you Norman Picard!
I ran a Chkdsk on a volume that uses a RAID 5 array we have in a Windows 2008 file. Each disk is about 3TB giving us a total of about 11GB of actual storage. I started a Chkdsk on Saturday evening thinking it would have enough time (had to wait so late since our backups start Friday night). I checked on Sunday night and it was about roughly 20% through the files in Stage 4. Since I had to get our main file server back online before Monday morning I figured I would have to stop it. I stopped it on stage 4 and the files weren’t harmed in any way.
With that being said there were some issues with it once it came back up. I had trouble connecting to it via our mapped network drives (via GPO) and just connecting to it via RDP. However this may have been related to the fact that the RPC service was not started after restart. I came in early this morning to check on it before everyone else and everything was working just fine. I just wanted to inform the community of my behavior in case someone else runs into it.
Thanks again Norman.
Hello, I scheduled a chkdsk before start up because my labtop has been freezing a lot lately. It is currently stuck at Stage 5(verifying free space) and has been stuck for about 6 hours now. Since the hdd light is blinking, i assume it’s still working so I am going to head to bed and see what happens in the morning. But if it is still stuck by morning, should I attempt a hard reboot? Please let me know.