Mistake writing EXIF date into .CR2 files in the 64 bit-Version
Forum rules
READ THIS AND DO IT!!!
Please include the following information:
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).
We strongly recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once, and we won't have to search for that vital information.
When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".
READ THIS AND DO IT!!!
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).
-
admin
- Site Admin
- Posts: 66728
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Mistake writing EXIF date into .CR2 files in the 64 bit-Version
And, fix confirmed?
FAQ | XY News RSS | XY X
-
StewartR
- Posts: 4
- Joined: 17 Aug 2026 16:12
Re: Mistake writing EXIF date into .CR2 files in the 64 bit-Version
Is the issue I reported also solved? I was writing EXIF data into a TIFF file, not a CR2, and my localisation is UK.
But in the screen shot I posted, you can see that the main XYplorer interface interprets the Date Taken as 08/12/2026 whereas the File Properties dialogue interprets it as 12/08/2026. I've updated XYplorer to v28.30.2100 but the behaviour is still the same.
But in the screen shot I posted, you can see that the main XYplorer interface interprets the Date Taken as 08/12/2026 whereas the File Properties dialogue interprets it as 12/08/2026. I've updated XYplorer to v28.30.2100 but the behaviour is still the same.
To see the attached files, you need to log into the forum.
--------------------
XYplorer V28.30.1900 (64-bit) evaluation +++ Windows 11 Home +++ Screen scaling 100%
XYplorer V28.30.1900 (64-bit) evaluation +++ Windows 11 Home +++ Screen scaling 100%
-
admin
- Site Admin
- Posts: 66728
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Mistake writing EXIF date into .CR2 files in the 64 bit-Version
Should be solved, try it.
FAQ | XY News RSS | XY X
-
SL09
- Posts: 58
- Joined: 13 Jun 2009 13:54
- Location: win11 | 100%
Re: Mistake writing EXIF date into .CR2 files in the 64 bit-Version
... I found page 2 of the thread ...
Now, the CR2 get the correct date in Ver. 28.30.2100
Thanks !
Now, the CR2 get the correct date in Ver. 28.30.2100
Thanks !
-
SL09
- Posts: 58
- Joined: 13 Jun 2009 13:54
- Location: win11 | 100%
Re: Mistake writing EXIF date into .CR2 files in the 64 bit-Version
O NOOO ...
I was mistaken. TODAY I cross-checked with Ver. 28.30.2200 - and I got AGAIN the erroneous dates with "08.12.2026" instead of "12.08.2026" !!!?
Same thing after a downgrade to Ver. 28.30.2100
I was mistaken. TODAY I cross-checked with Ver. 28.30.2200 - and I got AGAIN the erroneous dates with "08.12.2026" instead of "12.08.2026" !!!?
Same thing after a downgrade to Ver. 28.30.2100
To see the attached files, you need to log into the forum.
-
SL09
- Posts: 58
- Joined: 13 Jun 2009 13:54
- Location: win11 | 100%
Re: Mistake writing EXIF date into .CR2 files in the 64 bit-Version
... same thing with 'date created' - after I also set it to "EXIF"
File on MS Drive, the old link should still work
File on MS Drive, the old link should still work
To see the attached files, you need to log into the forum.
-
admin
- Site Admin
- Posts: 66728
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Mistake writing EXIF date into .CR2 files in the 64 bit-Version
Hmm, in v28.30.1910 I have reproduced and fixed it. And you confirmed the fix, right?
What exactly are the steps to reproduce the bug now?
What exactly are the steps to reproduce the bug now?
FAQ | XY News RSS | XY X
-
SL09
- Posts: 58
- Joined: 13 Jun 2009 13:54
- Location: win11 | 100%
Re: Mistake writing EXIF date into .CR2 files in the 64 bit-Version
> ... And you confirmed the fix, right?
I cannot reconstruct how this happened. But the next time I tried, the error was there (again: ??), and stays in the 64 bit version. In the 32 bit version all is OK
> What exactly are the steps to reproduce the bug now?
I open the directory in Ver. 28.30.2400
I select
IMG_9012 v28.30.2400.CR2
Datei | Datei speziell > Änderungsdatum auf Jetzt stellen
[as a sort of 'reset']
06.09.2026 13:14:43 = correct time, correct format
Datei | Datei speziell > Änderungsdatum auf EXIF stellen
in the filelist, the date "hops" instantly to 08.12.2026 19:54:35, instead of 12.08.
in 'Eigenschaften' {is this a Windows function ?} shown as "Dienstag, 8. Dezember 2026" 19:54:35
same thing in DOS-Prompt {this IS a Windows function ...} Screenshot 'DOSPrompt.jpg'
Datei | Datei speziell > Erstelldatum auf EXIF stellen
08.12.2026 19:54:35 instead of 12.08.
* in 'Eigenschaften' shown as "Dienstag, 8. Dezember 2026" 19:54:35
* EXIFToolGui shows 'ModifyDate', 'DateTimeOriginal' AND 'CreateDate' "2026:08:12 19:54:35" - on tab 'Exif'
on tab 'ALLE' under '---File:System ---' "2026:12:08 19:54:35+01:00" for all 3 dates - below is an EXIF date
attached: Exiftool 64f.jpg
I copy the file, rename it to IMG_9012 v27.30.1500.CR2
I open the directory in Ver. 27.30.1500
I select IMG_9012 v27.30.1500.CR2
Datei | Datei speziell > Änderungsdatum auf EXIF stellen
instantly > 12.08.2026 19:54:35
Datei | Datei speziell > Erstelldatum auf EXIF stellen
instantly > 12.08.2026 19:54:35
* EXIFToolGui shows the correct dates
attached: Exiftool 32.jpg
Winmerge finds no differences between the files, same thing with FC in a DOS-Prompt - apparently, Date and Time do not belong to the file content ...
I cannot reconstruct how this happened. But the next time I tried, the error was there (again: ??), and stays in the 64 bit version. In the 32 bit version all is OK
> What exactly are the steps to reproduce the bug now?
I open the directory in Ver. 28.30.2400
I select
IMG_9012 v28.30.2400.CR2
Datei | Datei speziell > Änderungsdatum auf Jetzt stellen
[as a sort of 'reset']
06.09.2026 13:14:43 = correct time, correct format
Datei | Datei speziell > Änderungsdatum auf EXIF stellen
in the filelist, the date "hops" instantly to 08.12.2026 19:54:35, instead of 12.08.
in 'Eigenschaften' {is this a Windows function ?} shown as "Dienstag, 8. Dezember 2026" 19:54:35
same thing in DOS-Prompt {this IS a Windows function ...} Screenshot 'DOSPrompt.jpg'
Datei | Datei speziell > Erstelldatum auf EXIF stellen
08.12.2026 19:54:35 instead of 12.08.
* in 'Eigenschaften' shown as "Dienstag, 8. Dezember 2026" 19:54:35
* EXIFToolGui shows 'ModifyDate', 'DateTimeOriginal' AND 'CreateDate' "2026:08:12 19:54:35" - on tab 'Exif'
on tab 'ALLE' under '---File:System ---' "2026:12:08 19:54:35+01:00" for all 3 dates - below is an EXIF date
attached: Exiftool 64f.jpg
I copy the file, rename it to IMG_9012 v27.30.1500.CR2
I open the directory in Ver. 27.30.1500
I select IMG_9012 v27.30.1500.CR2
Datei | Datei speziell > Änderungsdatum auf EXIF stellen
instantly > 12.08.2026 19:54:35
Datei | Datei speziell > Erstelldatum auf EXIF stellen
instantly > 12.08.2026 19:54:35
* EXIFToolGui shows the correct dates
attached: Exiftool 32.jpg
Winmerge finds no differences between the files, same thing with FC in a DOS-Prompt - apparently, Date and Time do not belong to the file content ...
To see the attached files, you need to log into the forum.
-
admin
- Site Admin
- Posts: 66728
- Joined: 22 May 2004 16:48
- Location: Win8.1, Win10, Win11, all @100%
- Contact:
Re: Mistake writing EXIF date into .CR2 files in the 64 bit-Version
Cannot reproduce. Works perfectly here.
FAQ | XY News RSS | XY X
-
SL09
- Posts: 58
- Joined: 13 Jun 2009 13:54
- Location: win11 | 100%
Re: Mistake writing EXIF date into .CR2 files in the 64 bit-Version
> Cannot reproduce. Works perfectly here.
You saw my files ? – in
https://1drv.ms/f/c/06995a52749c96f0/Ig ... E?e=LZ8SiM
In Windows AND Exiftool one sees the differences.
I cannot believe that I am the ONLY ONE in the world with this problem ?? All Germans, French, ?non-US have the scheme DAY:MONTH …
My System: Win11 Version 10.0.26200 Build 26200
“Gebietsschema: Deutschland”
Systemsteuerung: Region ‘Schweiz’, Region für die Geräteeinrichtung ‘Schweiz’ {= was used when Win 11 was installed, cannot be changed]
In all 32-bit versions, the mistake does NOT happen
For now, it is relatively simple: I will continue to use the 32 bit-Version. The mistake is too a momentous with regard to my big collection of photos. But my view of the world is somewhat shattered ...
https://1drv.ms/f/c/06995a52749c96f0/Ig ... E?e=LZ8SiM
In Windows AND Exiftool one sees the differences.
I cannot believe that I am the ONLY ONE in the world with this problem ?? All Germans, French, ?non-US have the scheme DAY:MONTH …
My System: Win11 Version 10.0.26200 Build 26200
“Gebietsschema: Deutschland”
Systemsteuerung: Region ‘Schweiz’, Region für die Geräteeinrichtung ‘Schweiz’ {= was used when Win 11 was installed, cannot be changed]
In all 32-bit versions, the mistake does NOT happen
For now, it is relatively simple: I will continue to use the 32 bit-Version. The mistake is too a momentous with regard to my big collection of photos. But my view of the world is somewhat shattered ...
XYplorer Beta Club