Very strange situation with 'date modified' in Windows and ExifTool

[Arder]

Hello! I'm using ExifTool with GUI. And I see a difference between 'date modified' in ExifTool and in Windows. The difference is one hour.
When I try to change this difference, it become correct in Windows, but in ExifTool metadata (and Android devices) it changes by one our! It happens with about 500 files, other files are fine. How to make 'date modified' the same in Windows and in ExifTool?

Bad file:








And you can see on screenshots that second file is fine - 'date modified' in Windows and in ExifTool are the same.

I'm going crazy with this issue... Please help me. I can share this bad file if it needed.

[Phil Harvey]

Windows sometimes has problems with daylight savings time.  Maybe this old post will give some answers.

- Phil

[Arder]

Thanks for answer.
But restart is useless. Any chances to fix that by other way? And why other files don't have this problem?

[Phil Harvey]

Are the files that don't show the problem in standard time (as opposed to daylight savings)?  (ie. from November to mid March)

[Arder]

Yes, you right. Seems I understand why the problem exists.
Our country changed its clocks to Standard Time on October 26, 2014. And problem files are in period from 2011-11-21 till 2014-10-25.
The cause of the problem is found, but now the question is how to fix this?

[Hayo Baan]

The problem is windows' file system (you're on a FAT file system, I think), it doesn't hold the full time and changes when you change timezone/daylight savings. There is no way around that.  Apart (perhaps) from moving everything to a better file system (I think ntfs does this better). Or, even better, just ignore the modification date and look at the metadata

[Arder]

No, my filesystem is NTFS everywhere.
Ok, there is no way to fix that, and I must live with it?

[Hayo Baan]

No, my filesystem is NTFS everywhere.

Darn, I thought ntfs was better behaving by now.

Ok, there is no way to fix that, and I must live with it?

I'm afraid so
(Linux and Mac don't suffer form this, but changing OS for only this is a bit much , I think)

[Arder]

Regrettable, but I have to put up with it...

[Phil Harvey]

Darn, I thought ntfs was better behaving by now.

This reference from the post I linked specifically mentioned that NTFS has this problem.

- Phil

[Hayo Baan]

Darn, I thought ntfs was better behaving by now.

This reference from the post I linked specifically mentioned that NTFS has this problem.

You're right, I overlooked that (and had hoped MS would have bettered their lives with e.g. Windows 10  by now; this kind of time behaviour is quite ridiculous...)