micky wrote:
Using Win 7 I have a USB dock, and it worked fine before, under win10
and maybe under Vista. Never got this message. Now, maybe because I'm
using win7, every time I plug in the dock, I get this message for every
data partition as it starts up (except an empty partition on a different
drive).

The drive has 4 partitions, 3 that it gives this warning for (not the
smallest one with no partition letter) and I've run the scan like it
suggested for the tiny partition and the smaller one, but it keeps
asking. (The dock has USB3 but the laptop only has USB2. and the large
parttion was taking forever so I stopped it. )

Is there really a problem, or are they being super-careful, or is this a
bug in windows 7. The warning says:


"Do you want to scan and fix [this drive]? There might be a problem
with some files on this disc. This can happen if you remove the disc
before all files are written to it. [But I never do that, and certainly
not since the last time I used this dock and ran this scan..]

_ Scan and fix (Recomended). This will prevent future problems when
copying files to this device or disc

_ Continue without scanning.


Can I just routinely continue without scanning?

You were using Windows 10, and at a minimum, it
could have upset $MFTMIRR on one of the partitions.

Windows 7 CHKDSK will fix that. And silently, so there's
no entry in the log after the run is finished and you've
ticked the box to fix it.

Then, once the partitions are fixed, keep rebooting into
Win7 and everything will be fine.

Then, boot into Windows 10, then boot back to Windows 7
and see what happens. And the problem may come back.
Maybe while in Win10, you can create a new text file on
each NTFS partition, just to give a "stimulus".

Macrium Reflect Free knows there's a problem. I tried
to do a 6.1.1196 backup using th CD and got "Error 9".
It knows something isn't right.

Linux LiveCD will show "$MFTMIRR" errors in "dmesg" output.

Windows 10 can damage $MFTMIRR and Volume Bitmap on NTFS
partitions.

Windows 10 custom reparse points cannot be read by Linux.
On older distros, attempts to poke stuff in System32 might
give "I/O Error", whereas a very recent distro will correct
the error to indicate that Linux is not able to parse
the info. Which is a better sort of error message,
because most punters freak out when they see "I/O Error"
and immediately buy new hard drives :-)

All of the NTFS file system versions are Version 3.1. This
means there should have been *zero* issues if they were
really compatible. However, Microsoft has this bad habit
of pooch screwing - $MFTMIRR, Volume Bitmap, Reparse points
(for custom compression format used for system files to
make the Windows tree smaller), the behaviors aren't backward
compatible. They also do something with Extended Attributes
that I still haven't figured out.

"Windows 10 is the gift that keeps on giving." Like the clap.

If you're not seeing problems when booting back to
Win7, then something must be wrong...

Paul