Timestamp of copied file is not the same
Hello,
There was already a bugfix with the same subject. But I still have such issues.
Filesystems is exFAT to exFAT with a Copy and Rename rule.
Everything looks fine except that the timestamp is not exact the same.
Scripts to verify the timestamp:
# Original file
powershell
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser
$fileorig = Get-Item .\DSC00136.ARW
$fileorig.LastWriteTimeUtc.ToString("o")
$fileorig.CreationTimeUtc.ToString("o")
$fileorig.LastAccessTimeUtc.ToString("o")
exit
# Output:
2026-06-14T14:25:58.9600000Z
2026-06-14T14:25:58.9600000Z
2026-06-14T14:25:58.0000000Z
# Copied file
powershell
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser
$filecopied = Get-Item .\2026-06-14-16.25.58-Cam1-ILCE-1M2-DSC00136.ARW
$filecopied.LastWriteTimeUtc.ToString("o")
$filecopied.CreationTimeUtc.ToString("o")
$filecopied.LastAccessTimeUtc.ToString("o")
exit
# Output:
2026-06-14T14:26:00.0000000Z
2026-06-16T10:34:37.7500000Z
2026-06-16T10:34:36.0000000Z
Environment is Windows 10.
Advanced Renamer Version is 4.23.
I'm a paid user.
Can you please fix it again.
Thnx.
Gerhard
There was already a bugfix with the same subject. But I still have such issues.
Filesystems is exFAT to exFAT with a Copy and Rename rule.
Everything looks fine except that the timestamp is not exact the same.
Scripts to verify the timestamp:
# Original file
powershell
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser
$fileorig = Get-Item .\DSC00136.ARW
$fileorig.LastWriteTimeUtc.ToString("o")
$fileorig.CreationTimeUtc.ToString("o")
$fileorig.LastAccessTimeUtc.ToString("o")
exit
# Output:
2026-06-14T14:25:58.9600000Z
2026-06-14T14:25:58.9600000Z
2026-06-14T14:25:58.0000000Z
# Copied file
powershell
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope CurrentUser
$filecopied = Get-Item .\2026-06-14-16.25.58-Cam1-ILCE-1M2-DSC00136.ARW
$filecopied.LastWriteTimeUtc.ToString("o")
$filecopied.CreationTimeUtc.ToString("o")
$filecopied.LastAccessTimeUtc.ToString("o")
exit
# Output:
2026-06-14T14:26:00.0000000Z
2026-06-16T10:34:37.7500000Z
2026-06-16T10:34:36.0000000Z
Environment is Windows 10.
Advanced Renamer Version is 4.23.
I'm a paid user.
Can you please fix it again.
Thnx.
Gerhard
Reply to #1:
When you copy a file, the default behavior is to also copy the modified timestamp, but not the created timestamp. Don't know why, this is how the Windows API works. I may be able to add an option to process a second pass to also copy the created timestamp.
When you copy a file, the default behavior is to also copy the modified timestamp, but not the created timestamp. Don't know why, this is how the Windows API works. I may be able to add an option to process a second pass to also copy the created timestamp.
Reply to #2:
You can look at the source code of FAR manager. It copies timestamps reliable for many years.
https://github.com/FarGroup/FarManager
If necessary the timestamp should be updated after each copy and not at the end in a "second pass".
You can look at the source code of FAR manager. It copies timestamps reliable for many years.
https://github.com/FarGroup/FarManager
If necessary the timestamp should be updated after each copy and not at the end in a "second pass".