Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, April 26, 2017 10:08 AM
On a chkdsk scan it displayed:
Windows has checked the file system and found problems.
Please run chkdsk /scan to find the problems and queue them for repair.
On more than thirty web pages I found lots of information on chkdsk syntax, commands and switches but none had any information on chkdsk /scan
Has anyone used the administrative command prompt chkdsk /scan command?
This was the result after the chkdsk /scan command:
Windows has found problems and they were all fixed online.
No further action is required.
When a computer is rebooted it may display the option to click to prevent a scan after boot.
If you don't click on it, it will then perform a scan and delay the boot. How does this scan on boot compare to chkdsk /scan?
How does the scan on boot compare to chkdsk /f or chkdsk /r or chkdsk /spotfix?
If chkdsk /scan repairs an error is the repair any different than a chkdsk /f /r repair?
Are the repairs the same or is one repair better or longer lasting than the other?
Are there any web pages or links that explain specifically what chkdsk /scan does or does not do?
Or how a chkdsk /scan repair may compare to a chkdsk /f repair?
I've been performing a lot of these chkdsk lately and all HD drive tests have passed numerous time. These have included HP bios UEFI extensive tests as well as seagate tools for windows. All smart, short, long, and generic tests have displayed pass multiple times.
One time I had run chkdsk /f /r after an upgrade from 1607 to 1703 and the repair lead to windows did not restart properly and the windows troubleshooting menu. This lead to a clean install. Then moving files from a secondary drive to the desktop displayed errors. These errors were just repaired by chkdsk /scan
This is the full chkdsk that displays the errors found. It also includes the run of chkdsk /scan which fixed the errors. There was no reboot like with /f or /r. The drive did not have to be locked and chkdsk /scan fixed the errors. So I was wondering about the different types of repairs between chkdsk /scan versus chkdsk /f /r and chkdsk /spotfix.
.
.
.
Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.
PS C:\Windows\system32> chkdsk
The type of the file system is NTFS.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
354304 file records processed.
File verification completed.
4461 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
439004 index entries processed.
Index verification completed.
CHKDSK is scanning unindexed files for reconnect to their original directory.
Detected orphaned file 8828F3~1 (103), should be recovered into directory file 1EEBD.
Detected orphaned file 8828F39C7C0CE9A14B25C7EB321181BA_3DF94EB797096674F7793A562A778C5F (103), should be recovered into
directory file 1EEBD.
2 unindexed files scanned.
Detected orphaned file 0972B7~1 (127), should be recovered into directory file 1EEBD.
Detected orphaned file 0972B7C417F696E06E186AEB26286F01_6DEFC1B0F00B73D870DAEE9AD78095DA (127), should be recovered into
directory file 1EEBD.
2 unindexed files recovered to original directory.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
42351 data files processed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has checked the file system and found problems.
Please run chkdsk /scan to find the problems and queue them for repair.
731992063 KB total disk space.
240957136 KB in 271906 files.
161000 KB in 42352 indexes.
0 KB in bad sectors.
484151 KB in use by the system.
65536 KB occupied by the log file.
490389776 KB available on disk.
4096 bytes in each allocation unit.
182998015 total allocation units on disk.
122597444 allocation units available on disk.
PS C:\Windows\system32> winver
PS C:\Windows\system32> chkdsk /scan
The type of the file system is NTFS.
Stage 1: Examining basic file system structure ...
354304 file records processed.
File verification completed.
4461 large file records processed.
0 bad file records processed.
Stage 2: Examining file name linkage ...
439024 index entries processed.
Index verification completed.
2 unindexed files scanned.
Found 2 missing entries (\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content\
8828F39C7C0CE9A14B25C7EB321181BA_3DF94EB797096674F7793A562A778C5F <0x4,0x103>, ...) in index "$I30" of directory "\Windo
ws\SysWOW64\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\Content <0x2,0x1eebd>"
... repaired online.
0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
42361 data files processed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Windows has found problems and they were all fixed online.
No further action is required.
731992063 KB total disk space.
241054324 KB in 272629 files.
161280 KB in 42362 indexes.
0 KB in bad sectors.
444727 KB in use by the system.
65536 KB occupied by the log file.
490331732 KB available on disk.
4096 bytes in each allocation unit.
182998015 total allocation units on disk.
122582933 allocation units available on disk.
PS C:\Windows\system32>
All replies (4)
Thursday, April 27, 2017 11:20 AM
Hi ,
Run chkdsk /?, it will give more detailed information about chkdsk command.
chkdsk /scan can only be used with a NTFS disk. Runs a online scan on the volume.
I found a similar thread online that might give you some hint. Please check it.
In chkdsk, what is an online scan?
https://superuser.com/questions/906222/in-chkdsk-what-is-an-online-scan
NOTE: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites.
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, March 14, 2018 10:36 PM | 2 votes
Please, in the future, to save time for anyone who might read this, answer the question, instead of just tossing a link to go read this......and that.... Seems simple enough a question, and provide links to reference your answer.
Chkdsk /scan differs from Chkdks /f , in that with Windows 8 and higher, some repairs can be performed without dismounting the disk. If a dismount is required, its automatic and will prompt to reboot to run the repairs.
Reference: https://www.neowin.net/forum/topic/1162464-could-someone-explain-the-new-chkdsk-options-whats-an-online-scan/
Rickke
- I do not work for Microsoft.... at least not for money anyhow.... I could be driving a new Lamborghini with the money I have not been able to bill clients because of "Microsoft Gotcha" issues.
Wednesday, March 14, 2018 11:27 PM
On this computer chkdsk /scan and chkdsk /spotfix and chkdsk /x /f /r all had been run at various times and today all failed. Using the computers windows advanced troubleshooting menu they all failed. Using a windows 10 iso X:\Sources they failed. The syntax that worked today in windows recovery was chkdsk /r C:
Running this command on the 750 GB HD typically took 4 hours.
When running chkdsk /x /f /r using administrative command prompt it typically ran up to 11% and remained there until completion.
When running chkdsk /r in the windows recovery environment it displayed ETA of typically 4 hours. Today it never completed and froze with approximately a little more than 2 hours remaining in stage 4.
The freeze followed by power off and power on caused major problems with the HD.
There were many orphaned files. It displayed that there was insufficient free space on the HD to make the full repairs. The drive had 335 GB free space and that was insufficient for the chkdsk repairs on the 750 GB HD.
The computer was powered off from the frozen chkdsk.
The drive had had the following tests that had passed:
1) Crystal Disk
2) HD Tune
3) HD Sentinel
4) Sea Tools for Windows
5) HP UEFI diagnostics extensive tests
HP support was contacted and they said that they only replace drives with hardware failure.
This drive seems to be having logical drive failure.
Currently the plan is to:
1) copy the users folder onto a storage drive
2) run HP sanitization on the drive to overwrite and fix all portions of the drive.
3) reinstall Windows
4) restore the files by copying the users folder from the storage drive to the Windows drive
5) Make a backup image with Macrium (I may need an additional HD for this (this I don't currently have so the step would need to be performed at a later time)
Macrium was not able to be used to backup the drive as it displayed an error message. This error message was present 1 year ago and was ignored as the C: was not having problems. The error message and code when decoded indicated that it had found a problem with the hidden partition. It requested labeling of the hidden partition and then to run chkdsk /r on the partition. So somehow on a 750 GB HD Macrium found a problem on 100 MB that was not detected by the other software drive tests.
6) If there are recurrent problems after disk sanitization the plan is to replace the HD. This would then be a drive that has normal hardware but problems with the logical drive component. Apparently there is no known method to test the logical drive portion with SMART, Benchmarks, Error or Surface scans.
When chkdsk /r C: is run in the recovery environment as far as I know there is no method to get a log file.
Does anyone know how to save log files in the windows recovery files? Or is the only method to use a camera? The displayed results ran off the administrator X:\windows\system32\cmd.exe box. So there was a portion that was in view and a large portion that was no longer able to be viewed. Control A was clicked followed by control C but this did not appear to work. It was unclear how to save this portion but the whole log was preferred. Copy to notepad and then to a flash drive was not attempted.
So it was unclear what had happened.
The problem appears to have been precipitated by an attempted Windows upgrade causing the freeze.
If anybody has any ideas on how to further troubleshoot as sometime later today the users folder will have been copied to the storage drive. Before the windows recovery chkdsk /r C: both administrative command prompt and administrative powershell failed to open so I was guessing that the freeze and power off somehow caused problems with the user or the registry or both. However after the chkdsk /r C: the administrative command prompt opened. No commands were yet run to test it though.
Thursday, March 15, 2018 1:43 AM
The Windows update freeze followed by power off did a lot of damage.
chkdsk /scan now works but after the chkdsk /r C: it found corrupt basic file structure > needs offline scan > did not offer spot fix
sfc /scannow > could not start the repair service
dism /online /cleanup-image /restorehealth > the file or directory is corrupted or unreadable
dism /online /cleanup-image /scanhealth > error 1392 the or directory is corrupted or unreadable
dism /online /cleanup-image /checkhealth > the component store cannot be repaired.
Google chrome > profile error occurred > your preferences file is corrupt or invalid > google Chrome is unable to recover your settings