Windows 7 CHKDSK breaks Windows 10?

[shamrin]

We had a W10 machine here that was having some strange NTFS errors in the event log. The SMART data was fine and the HDD appears to be working OK. We decided to pull the drive and run a CHKDSK /R on it while slaved to a Windows 7 machine. The scan corrected some non-specific errors and terminated normally.

After 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. 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. 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.

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. I can't find anything on the web to support this. Just wondering if anyone else has any insight or experience similarly.

 

[PBComputer]

I am having simular issues. A laptop came in for a screen replacement, we checked the drive and it was failing upsold a SSD upgrade. cloned the drive and all working fine. notice a few bits of malware clean it all up working fine. see on of the drives is very small so go to resize it. I pull the drive out of the laptop plug it in to my Window 7 bench pc. and it runs a chkdsk on boot. Now when I try and boot into Windows 10 i get the error message 0xc0000225.

 

[Matthew Bradley]

Were these Win10 machines GPT? We've had similar issues but they were always on GPT / UEFI formats. That stop error I believe is a bootmgr error. We've been able to rebuild the BCD store to fix it but yes - it's always after a chkdsk.

 

[Markverhyden]

All I can say is I always run checkdisk with the same OS version as the target drive.

 

[nlinecomputers]

https://blogs.msdn.microsoft.com/b8/2012/05/09/redesigning-chkdsk-and-the-new-ntfs-health-model/

 

[altrenda]

https://blogs.msdn.microsoft.com/b8/2012/05/09/redesigning-chkdsk-and-the-new-ntfs-health-model/

TL;DR version - Updated OS, Updated File system = need for updated tools.

 

[Altster]

All I can say is I always run checkdisk with the same OS version as the target drive.

Ditto! And why wouldn't you (not necessarily YOU, Mark) run "CHKDSK" from the affected machine? It (Chkdsk) is supposedly still compatible between W7, 8 & 10.

 

[Diggs]

Every time I mount a Win10 disk in a Win7 USB drive dock I Win7 wants to correct it's errors. I obviously won't let that happen, have others?

 

[glennd]

Every time I mount a Win10 disk in a Win7 USB drive dock I Win7 wants to correct it's errors. I obviously won't let that happen, have others?

you probably shouldn't be doing that. evidently win10 is doing stuff to the hard disk that win7 doesn't recognise and thinks is wrong. probably should use a late model linux.

 

[PBComputer]

I don't normally run it. It only ran as I got distracted by a phone call and a client when it must of come on the screen.