When renaming files manually to the yyyyMMdd_hhmmss format it is easy to mistype this as yyyyMMdd-hhmmss, with a hyphen rather than an underscore.

To address this add yyyyMMdd-hhmmss as a pattern match.

Add an option to scan for and report files that would be renamed if the script was run, without making any changes, e.g. -DryRun.

Tested Command

Get-ChildItem -Recurse -File | where { $_.Name -notmatch "^[0-9]{8}_[0-9]{6}(-[^/\\?%*:|`"<>. ]+)?\.[a-z
A-Z0-9]+$" }

When exporting files from iCloud Photos using the desktop application files are downloaded into year folders and named IMG-[seq], where [seq] is a sequential number. The EXIF data is stripped by iCloud, however, when the desktop application downloads files it sets the Date Created, Date Modified and Date Accessed values on the file to the data the image was taken/uploaded?

• Date Created is changed if a file is copied,
• Date Accessed is updated when the file is accessed by certain applications, however,
• Date Modified should remain unchanged (unless of course the file is edited).

Add a -DateModifiedFallback parameter to fallback to the Date Modified value on files where EXIF and Pattern Matches fail, rather than reporting an error and skipping the file, to allow iCloud Photos exports to be processed successfully.

Describe the bug

When files are renamed with -DateModifiedFallback they are named yyyyMMdd-HHmmss (with a hyphen) not yyyyMMdd_HHmmss (with an underscore).

To Reproduce

Steps to reproduce the behavior:

1. Create a folder with a file with no EXIF Data call test1.txt
2. Run `DateFix.ps1 -Path .\Test -DateModifiedFallback
3. See error

Expected behaviour

All renamed files should follow the convention yyyyMMdd_HHmmss (with an underscore).

Screenshots

n/a

System

• OS (e.g. Windows 10): Windows 10
• OS Build (e.g. 17134): 17134
• OS Architecture (e.g. x64): x64
• DateFix Version (e.g. v1.2): v1.7

Additional context

n/a