-
-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Autostart option does not work when Ueli is installed via Microsoft Store #1137
Comments
Possible workaround:
|
The issue is still happening on version 9.3.2 (Win 10) Thanks. |
Sorry for the confusion. This is still an issue and as far as I know there is no workaround that you can apply. You have to wait until we fix this (with the workaround mentioned above) in the code. |
Hello. |
I also have this issue. I think the problem is, that the autostart entry directs to a directory my user has no access rights for: When I try to run it via cmd I get an access denied error. With this command I can open ueli:
|
@oliverschwendener: Calling |
I just found it out, it's the publisher id. So this should be constant and I think we can hard-code it. What do you think? |
The next release contains a fix for this. |
@tkohlmeier This still doesn't work for me. The shortcut is being created and it works when I open it manually, but Ueli won't start automatically when I log in. |
It does work on my machine. Do you see an error in the Windows event log (eventvwr.msc)? |
No, no errors. Does it show up in the task manager under "Startup apps" for you? |
Are you using Windows 11 or 10? I'm using Windows 11. |
Yes, it does show up under "Startup apps". I cannot open its properties though. I'm using Windows 11. I even checked it on another computer, also Windows 11. It does also work. Strange. |
Autostart option does not work when Ueli is installed via Microsoft Store
To Reproduce
Steps to reproduce the behavior:
Expected behavior
That the app is added/removed to/from the autostart apps when toggling the "Autostart" option
Environment
The text was updated successfully, but these errors were encountered: