On Mar 7, 3:46 pm, "Good News!" wrote:
> "
> Windows will now check the disk.
>
> Cleaning up minor inconsistencies on the drive.
>
> Cleaning up 8 unused index entries from index $SII of file 0x9.
>
> Cleaning up 8 unused index entries from index $SDH of file 0x9.
>
> Cleaning up 8 unused security descriptors.
>
> CHKDSK is verifying Usn Journal...
>
> Usn Journal verification completed."
>
> As you can see, during reboot with chkdsk/f, nothing of any significance is
> detected! What is causing the problem?
Running chkdsk on the drive on which Windows is installed usually
gives error messages, apparently because chkdsk has interrupted some
background disk-writing operation. This has been my personal
experience also. If chkdsk is repeated once or twice, the error is no
longer seen. AFAIK, this is nothing to worry about, and I have also
seen that faithfully obeying the instruction to run chkdsk /f at
boottime does not show up any errors..
>> Stay informed about: File system errors