CHKDSK & sfc /scannow not consistant.

Widows 10 pro



When using the system HDD and applying chkdsk C: /f /r /x

& sfc /scannow, I get errors that cannot be fixed.

Yet when I do this from the duplicate Windows10 (referring to K (the
C: on the main OS)) on the same MB there are no problems at all!
Why?

Peter Jason wrote:
Widows 10 pro



When using the system HDD and applying chkdsk C: /f /r /x

& sfc /scannow, I get errors that cannot be fixed.

Yet when I do this from the duplicate Windows10 (referring to K (the
C: on the main OS)) on the same MB there are no problems at all!
Why?

Windows does not want to CHKDSK C: while
the OS is running. There are "busy" files.
The partition cannot be dismounted. Think
about it.

Whereas your case where one OS (as C scans
the OS partition of another OS (as F, that's
going to work, because the F: partition is virtually
a data partition at that point. Practically
nothing is open/busy on it.

For C: to request a scan/repair of C: , Windows will
set the BootExecute key. And it will do the CHKDSK function
when the OS is rebooted. BootExecute is early enough
in the boot process, that a CHKDSK can be safely done.
The results of the CHKDSK can be written as a Winlogon
event to Event Viewer. That allows you to check the
CHKDSK results later. If you specify the repair option
that reads every sector, expect a large drive to be
tied up for a few hours while that happens. Whereas if
you're just scanning the actual "structure" and not
every sector, that can finish in a minute or two.

Paul