Albert Garinni
New Member
Consider this scenario:
-start OBS with -portable command line parameter;
-there are updates available;
-agree on installing updates;
-after update completes a "Launch OBS" button appears;
-after clicking/tapping it, OBS will run as admin and will not use the portable settings.
Conclusion: The updater loses the command line arguments originally passed to OBS.
Also for zipped version of OBS there is no reason for updater to request admin privileges.
Ideally would be for updater to store the user name who originally launched OBS and re-launch it in context of that user.
-start OBS with -portable command line parameter;
-there are updates available;
-agree on installing updates;
-after update completes a "Launch OBS" button appears;
-after clicking/tapping it, OBS will run as admin and will not use the portable settings.
Conclusion: The updater loses the command line arguments originally passed to OBS.
Also for zipped version of OBS there is no reason for updater to request admin privileges.
Ideally would be for updater to store the user name who originally launched OBS and re-launch it in context of that user.