IgorMundstein
Fixing the UAC window on launch problem
Checklist
- [X] I have used the search function to see if someone else has already submitted the same feature request.
- [X] I will describe the problem in as much detail as possible.
- [X] This issue only requests one feature, not multiple (related) features.
App version
2.8
Problem you are trying to solve
I experienced the same problem as in Issue #80
You can check my comment/suggestion on there, but since the topic is already closed, I'm creating a new, shorter one, to make sure it will be seen.
Suggested solution
The trick is to create/edit the task and set the active user/group for the task to the built-in "Users" group. After that, the program launched at start silently with no UAC window. Also, the program seemed to work well, I can optimize RAM and get the notification of how much was free'd.
The task is created via command line, all that's needed is to edit the command line and add the "/RU" parameter with the value "[MachineName]\Users" (maybe plain "Users" could work too).
Screenshots / Drawings / Technical details
No response
Thanks for the report.
I noticed that the User Account Control (UAC) is also triggered due to the startup registry entry located at SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Run.
I believe this method is no longer necessary if the application utilizes the Task Scheduler. I've also changed the task to run under the built-in administrator group. It's safer since Windows prevents the user from deleting this group. I don't anticipate any issues with this change; however, if problems arise, we can revert to using the built-in users group instead.
The app will remove the startup registry and recreate the task in the next release. Let's monitor this change.