-
Notifications
You must be signed in to change notification settings - Fork 8
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] "Run at Startup" set wrong path in Windows Registy #125
Comments
On it. |
Regarding setting a value in Either way, I'll build the functionality to do this in, but the actual implementation probably won't use it. |
Should be fixed in 5ed7671 Currently building a test build for you to make sure it works on your end. |
Here is a test build with the fix, and download instructions should you need them. |
The Path is now correct and works but (for me) only if
As you can see in the screenshot below, many 3rd party apps added themself to |
Usually |
As of f9ad6a8 a value in |
Now available in v6.6.1 |
Thank you, i will test it later 😎 |
Version Number
6.5.2
File
Portable (VolumeControl.exe)
Windows Version
Windows 11 22H2 Build 22624.2428
Actual Behaviour
The
Run at Startup
set a wrong or partially wrong path in the Windows Registry.Actual Windows Registry if ```Run at Startup`` is enabled
Screenshot:

Expected Behaviour
But this Registry key should be set
Screenshot:

also you should set this
Screenshot:

Reproduction Steps
No response
Log
Log file does not help (again), but here:
The text was updated successfully, but these errors were encountered: