Just wondering if anyone else has any insight or experience similarly. I can't find anything on the web to support this. My conclusion is that somehow the NTFS implementation under Windows 10 is not backward compatible to the extent that you can use CHKDSK from a pre-Windows 10 machine on it. Finally, I ran a Scan and Repair from the Windows 10 GUI and now the errors (except for ones reported on the HDDRECOVERY Partition) have gone away. I tried to track down the errors, both from the System events and Application events and never really came up with anything solid on diagnosing exactly what what going on.

The scan corrected some non-specific errors and terminated normally.Īfter putting the drive back in it's native machine, the error log went crazy with VSS errors complaining about errors in Shadow Copies that were corrupt and unwriteable. We decided to pull the drive and run a CHKDSK /R on it while slaved to a Windows 7 machine. Uses more system resources to speed up verification can have a negative impact on the performance of other tasks running on the system (must be used with /scan) x. The SMART data was fine and the HDD appears to be working OK. Bypasses online repair (must be used with /scan) errors found are queued for offline repair (i.e. We had a W10 machine here that was having some strange NTFS errors in the event log.

Chkdsk windows 10