News:

2023-03-15 Major improvements to the new Geolocation feature

Main Menu

Daylight Savings Time Bug of Windows

Started by fkbreitl, October 02, 2013, 04:36:14 PM

Previous topic - Next topic

fkbreitl

Hi Phil,

That's a pity. However, I found these free Windows 7 images offered by Microsoft for testing Internet Explorer:

http://www.modern.ie/en-us/virtualization-tools

Together with VirtualBox 4.3 (https://www.virtualbox.org/) or Virtual PC this could give you a free Windows 7 test environment.

Frank

delerious

Looks like the problem that OP reported still occurs on Windows 10 build 19044.

I ran the following commands:

G:\Documents>exiftool "-filemodifydate#<CreateDate#" sunset.jpg
    1 image files updated

G:\Documents>exiftool -G0 -a -s -FileModifyDate -CreateDate sunset.jpg
[File]          FileModifyDate                  : 2023:02:12 17:30:37-05:00
[EXIF]          CreateDate                      : 2023:02:12 17:30:37

G:\Documents>dir sunset.jpg

 Directory of G:\Documents

02/12/2023  06:30 PM         4,821,484 sunset.jpg

So right now we're in daylight saving time, and the "dir" command shows a modified timestamp that is one hour ahead of the FileModifyDate that ExifTool reports. Although in Windows Explorer, the "Date modified" column for sunset.jpg shows "2/12/2023 5:30 PM".


Phil Harvey

Microsoft is dedicated to maintaining backward compatibility at the expense of progress, which means that bugs like this are "features" that will never get fixed.

- Phil
...where DIR is the name of a directory/folder containing the images.  On Mac/Linux/PowerShell, use single quotes (') instead of double quotes (") around arguments containing a dollar sign ($).

delerious

It looks like maybe the behavior has changed actually. OP reported that the timestamp in his Windows Explorer was one hour off. My Windows Explorer shows a timestamp that matches what ExifTool reports, but the "dir" command is showing a timestamp that is one hour ahead.