- Aug 14, 2018
- 3
- 0
- 10
Edit:
Solved. Look at my comment: http://www.tomshardware.co.uk/answers/id-3764838/disk-scan-boot-skip-completes.html#21232155
Hi,
I'm using Windows 8.1
Last night windows tried to scan & repair the disk on boot, since it takes too long to complete, I simply skipped it by pressing any key when asked.
After I logged in the system, I scanned the disk manually with CHKDSK, and it found some errors. Then I restarted the computer and let it to proceed. After a very long waiting, it completed its job and restarted automatically.
This time, Windows entered the Advanced System Startup Options. I simply tried the "Exit and Continue to Windows" button, but it also restarts the computer, and system tries to scan & repair the disk again.
So then I decided to run Command Prompt from Advanced System Startup Options, and run CHKDSK again manually. This time it found no errors. I also checked with CHKNTFS command, it seems there is no any scheduled task and dirty flag is not set.
But Windows continues to scan and repair the disk on every boot, while there is no errors, scheduled task, and dirty flag is not set.
However, I cannot skip the scan this time by pressing any key. Even though I do it, it enters the scanning.
Over the night, I let it to proceed several times. After the first scan, it takes shorter to complete in second time and later. However, windows still enters disk scan on boot and I cannot skip
1. I'm pressing a key (to skip) for sure in the given time, but it does not work. I'm using a laptop, so its not a USB or wireless keyboard.
2. Since I cannot access the Windows, I'm using the Command Prompt from the Advanced Startup Options. Checks (chkdsk, chkntfs) I listed above made by this prompt. I'm telling this because as far as I understand, some changes made in this mode does not affect the system.
Because, I tried to edit AutoChkTimeout registry to adjust the given time of skipping (currently its 1 second), I was thinking maybe if I extend this time the keyboard may work. After editing, the change does not affect and I saw 1 second again. Registry also was returned its original state when I check.
Solved. Look at my comment: http://www.tomshardware.co.uk/answers/id-3764838/disk-scan-boot-skip-completes.html#21232155
Hi,
I'm using Windows 8.1
Last night windows tried to scan & repair the disk on boot, since it takes too long to complete, I simply skipped it by pressing any key when asked.
After I logged in the system, I scanned the disk manually with CHKDSK, and it found some errors. Then I restarted the computer and let it to proceed. After a very long waiting, it completed its job and restarted automatically.
This time, Windows entered the Advanced System Startup Options. I simply tried the "Exit and Continue to Windows" button, but it also restarts the computer, and system tries to scan & repair the disk again.
So then I decided to run Command Prompt from Advanced System Startup Options, and run CHKDSK again manually. This time it found no errors. I also checked with CHKNTFS command, it seems there is no any scheduled task and dirty flag is not set.
But Windows continues to scan and repair the disk on every boot, while there is no errors, scheduled task, and dirty flag is not set.
However, I cannot skip the scan this time by pressing any key. Even though I do it, it enters the scanning.
Over the night, I let it to proceed several times. After the first scan, it takes shorter to complete in second time and later. However, windows still enters disk scan on boot and I cannot skip
1. I'm pressing a key (to skip) for sure in the given time, but it does not work. I'm using a laptop, so its not a USB or wireless keyboard.
2. Since I cannot access the Windows, I'm using the Command Prompt from the Advanced Startup Options. Checks (chkdsk, chkntfs) I listed above made by this prompt. I'm telling this because as far as I understand, some changes made in this mode does not affect the system.
Because, I tried to edit AutoChkTimeout registry to adjust the given time of skipping (currently its 1 second), I was thinking maybe if I extend this time the keyboard may work. After editing, the change does not affect and I saw 1 second again. Registry also was returned its original state when I check.
Facebook
Twitter
Instagram