BUG: 'Start Flow launcher on system startup' does not work where account path contain spaces

[xmichelo]

Checks

• I have checked that this issue has not already been reported.

• I am using the latest version of Flow Launcher.

Problem Description

'Start Flow launcher on system startup' does not work.
I investigated a bit using Sysinternals Autoruns, and I think the issue might be link to the fact that my Windows local account contains a space. The Image path is clearly missing what's after the space character. It lists C:\Xavier when it should be something last C:\Xavier Michelon\...

To Reproduce

Potentially, test the feature with an account that contains a space in it username.

Screenshots

Flow Launcher Version

1.15.0

Windows Build Number

Microsoft Windows [Version 10.0.19045.2965]

Error Log

2023-05-11.txt

[VictoriousRaptor]

#2000. Can't test it now. Will try to investigate later this week. Can you please try to navigate to HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run and add quotes to Flow's entry, then check if it's fixed?

[xmichelo]

It's odd, other entries in the list are double quoted, so it did it. it fixed the path in Autoruns. I logged out and logged it again, but the app did not launch. The path in the registry is correct, i tested it in a "Run" box. Not surprisingly, when Flow launches, it replaces the quoted version by the previous one, but I took care and repeated the test twice without success.
In

[taooceros]

@xmichelo could you take a check on this build? https://ci.appveyor.com/api/buildjobs/7cb1p4hkf72s18xf/artifacts/Output%2FPackages%2FFlow-Launcher-Setup.exe

[xmichelo]

Hi @taooceros .

It works now! Thanks a lot.

Note: I do not have the original setup anymore, as the machine was update to Windows 11, but I still have a Windows 10 VM. I created an account with a space in the username, installed the build, enabled autostart and rebooted. Flow properly started on login.

[VictoriousRaptor]

Hi @taooceros .

It works now! Thanks a lot.

Note: I do not have the original setup anymore, as the machine was update to Windows 11, but I still have a Windows 10 VM. I created an account with a space in the username, installed the build, enabled autostart and rebooted. Flow properly started on login.

Well that's a surprise. I didn't expect it can fix this issue.

[taooceros]

That's nice, then let's get it merged.