And that is to say nothing of hardware issues such as amount of system memory, the speed of the CPU, the speed of the disk or disks, and so on. To verify a volume correctly, the volume must be in a static state, and the only way to guarantee that state is to lock the volume. Also, Autochk.exe runs in a different environment than Chkdsk.exe. Thus, while Autochk.exe would usually be expected to run faster than Chkdsk.exe, systems with relatively low amounts of RAM may see longer times for Autochk.exe than for Chkdsk. Fixing corruption adds to the time required.
Cycles are a very rare form of corruption in which a subdirectory has itself for an ancestor.
The later case is another form of orphaning. The file represented by the FRS may be intact in all ways except for the fact that it is invisible to all Win32 applications-including backup applications. When disk corruption is detected on a volume, you have three basic choices Do nothing. For a mission critical server that is expected to be online 24 hours a day, this is often the choice of necessity. This option repairs all file system data, restoring all user data that can be recovered by means of an automated process.