Windows 10: Robocopy tells me files are modified, but I can't find any difference

Hi,

after a recent upgrade from Windows 7 to Windows 10 I stumbled upon a weird little problem that I don't understand at all.

I do all my backups with Robocopy. All important data is on a local hard drive D:, I use another, identically sized local hard drive E: for internal backups kind of a "manual RAID 1" if you will and additional external hard drives via USB. All of those drives use NTFS.

My Robocopy commandline looks like this:


robocopy D:\ E:\ /E /ZB /COPYALL /PURGE /XD "RECYCLER" "$RECYCLE.BIN" "RECYCLE.BIN" "System Volume Information"


I ran this on Windows 7 with Administrator rights right before the upgrade to Windows 10, so pretty much all data on both drives should be identical, including NTFS-ACLs et cetera.

When I ran this after the upgrade to Windows 10, Robocopy regarded all the files as modified and started to copy everything again. I stopped Robocopy after a couple of files to investigate and run everything with/T to see what was going on without changing anything.

What I figured out so far: /COPYALL equates to /COPYATSOU is the culprit, respectively the attributesS, O and U. If I use /COPYAT, Robocopy will - as expected - not regard the files as modified. If I use any of the other options in any combination e.g./COPYATS, /COPYATO, /COPYATU, Robocopy claims the files were modified. It will however not touch the files that were previously copied again via/COPYALL in my first attempt, so apparently there was a change in the ACLs S, the owner information O and the auditing information U taking place on one of the NTFS volumes at some point during the Windows update.

The thing is: I can't find any difference anywhere. I checked and compared everything I could find in the file properties and had a look at some files and folders withicacls on the command line, absolutely everything seems to be 100% identical.

What am I missing? Is there any other way of getting information about ACL, owner and auditing information of files and folders that might reveal a difference?

Thanks in advance!

:)

 

Repeat RoboCopy batch file in Windows 10 gives different results.

Action taken as suggested.

Same question now exists here
HERE.

 

Windows 10 robocopy ERROR 1392 (0x00000570) file or directory is corrupted

I keep all my personal and business data on a 2TB Passport external drive and back up key parts of it daily to two other external drives using robocopy. I've been doing this for years.

Since I upgraded to Windows 10, however, I keep getting the error I mentioned above (in the subject line). Robocopy complains that some file or directory on the **destination** drive is unreadable, and sure enough, I am unable to delete the file. I've tried
both File Assassin and File Unlocker. File Assassin complains that it cannot see the file. File Unlocker claims to delete it, but I still see it in Windows Explorer, even after rebooting. The only way to get rid of the file is to boot in safe mode and delete
it.

Problem is: this keeps reoccurring in different places in the filesystem !!!

Relevant facts:

* It occurs on *both* of my backup drives, which suggests to my mind that the problem is not with the backup device.

* Again, it occurs with different files in different places. There's no detectable pattern as far as location.

* CHKDSK reports no problems on any of my disks

* SFC reports no problems on any of my filesystems

For now, I've settled on the following work-around: I tell robocopy to ignore read errors:

For EX: robocopy g:\data q:\data /mir /R:0 /W:0

So now robocopy runs to completion instead of hanging, but it reports FAILURES.

I am worried about my data and would appreciate guidance and suggestions.

 

Windows 10 robocopy ERROR 1392 (0x00000570) file or directory is corru


I keep all my personal and business data on a 2TB Passport external drive and back up key parts of it daily to two other external drives using robocopy. I've been doing this for years.
Since I upgraded to Windows 10, however, I keep getting the error I mentioned above (in the subject line). Robocopy complains that some file or directory on the **destination** drive is unreadable, and sure enough, I am unable to delete the file. I've tried both File Assassin and File Unlocker. File Assassin complains that it cannot see the file. File Unlocker claims to delete it, but I still see it in Windows Explorer, even after rebooting. The only way to get rid of the file is to boot in safe mode and delete it.
Problem is: this keeps reoccurring in different places in the filesystem !!!
Relevant facts:
* It occurs on *both* of my backup drives, which suggests to my mind that the problem is not with the backup device.
* Again, it occurs with different files in different places. There's no detectable pattern as far as location.
* CHKDSK reports no problems on any of my disks
* SFC reports no problems on any of my filesystems
For now, I've settled on the following work-around: I tell robocopy to ignore read errors:
For EX: robocopy g:\data q:\data /mir /R:0 /W:0
So now robocopy runs to completion instead of hanging, but it reports FAILURES.
I am worried about my data and would appreciate guidance and suggestions.