Alphrag
commented
1 day ago Hi @imtrobin, the portable version is in fact unpacking inside the temp directory to actually run, so the fact that you see a folder in Username\AppData\Local\Temp is completely normal and this folder has been given the specific name Ferdium-Unpacked for a while now (cf commit 3e0e263) when before it was simply a random set of characters.
So is the problem that Ferdium tries to start 2 distinct instances which then breaks the second one since it cannot unpack properly (the directory name already existing from the first one), or is there another behavior that you are seeing? Did you add one by hand in your startup application or did you only toggle the "Start automatically at startup" button in the Ferdium settings to make it happen?
imtrobin
Avoid duplicates
Ferdium Version
6.7.4 portable
What Operating System are you using?
Windows
Operating System Version
10
What arch are you using?
x64
Last Known Working Ferdium version
No response
Expected Behavior
I'm using portable 6.7.4. When I reboot my machine, there were two ferdium instance that autostarted. I see there were two entries in my startup list, one is the Ferdium.exe AppData\Local\Temp\Ferdium-Unpacked. I believe earlier versions of portable did not create this temp folder.
I force delete Ferdium.exe in AppData\Local\Temp\Ferdium-Unpacked, and it still came back upon starting ferdium. The ferdium.exe also does not start, it shows only purple window.
I've been using portable versions with earlier versions without this problem
Actual Behavior
no second ferdium.exe in temp folder
Steps to reproduce
Reboot
Debug link
https://debug.ferdium.org/fc8919c6-fa57-4f90-9c65-2d8733b88781
Screenshots
No response
Additional information
No response