Updater filename changes each time, unable to unblock in Windows Defender Controlled Folder Access as a result.

[JWatersMeet]

Describe the bug
When using the Simple64 auto-update functionality, the updater executable is downloaded each time an update is needed, and it is given a filename which appears to be a random unique GUID, that changes each time an update is requested, across the same update versions.

For users with Windows Defender Conrolled Folder Access turned on for the drive on which Simple64 is located, the continually changing and unpredictable filename means it can't be unblocked and permitted access to the drive (i.e. one you've unblocked the filename and run again, the filename changes).

To Reproduce
Enable Windows Defender Controlled Folder Access for the drive on which Simple64 is stored.
Run the updater from within the SImple64 GUI
The updater executes, but failes to deploy the update due to a write access failure
Windows Defender pops up a notification asking if the action should be permitted for this executable
The action is permitted and the rule added to Defender
The updater is run again from the GUI, the filename GUID changes, the update fails in the same way and the defender alert pops up again.
Repeat.

Expected behavior
It should be possible to permit the update executable write access to the drive once, which will be valid for future update sessions. To do this, it needs a non-changing filename.

Desktop (please complete the following information):

• OS: Windows 11 23H2
• GPU: RTX 3080 Mobile