[BUG] Installing on windows new updates from a non-administrator users is taking all the system resources (crash) #2984
Assignees
Comments
|
Having the user and administrator as separate user accounts is not currently supported in the updater, but it should definitely error out instead of getting stuck in a loop. Will look into it. |
|
I am unable to reproduce this. When the non-elevated user account launches the updater, a runas prompt appears asking for administrator credentials. Cancelling the prompt works as expected (ie, the updater exits). Could you describe your user account environment in more detail? |
notr1ch
added a commit
to notr1ch/obs-studio
that referenced
this issue
Jun 16, 2020
In rare cases, "runas" would somehow launch the updater as a non-admin user again, resulting in a loop where the updater constantly spawns processes. Fixes obsproject#2984
Oncorporation
pushed a commit
to Oncorporation/obs-studio
that referenced
this issue
Jun 29, 2020
In rare cases, "runas" would somehow launch the updater as a non-admin user again, resulting in a loop where the updater constantly spawns processes. Fixes obsproject#2984
mv2731
pushed a commit
to ushadow/obs-studio
that referenced
this issue
Jun 29, 2020
In rare cases, "runas" would somehow launch the updater as a non-admin user again, resulting in a loop where the updater constantly spawns processes. Fixes obsproject#2984
Oncorporation
pushed a commit
to Oncorporation/obs-studio
that referenced
this issue
Jul 12, 2020
In rare cases, "runas" would somehow launch the updater as a non-admin user again, resulting in a loop where the updater constantly spawns processes. Fixes obsproject#2984
derrod
pushed a commit
to derrod/obs-updater
that referenced
this issue
Dec 12, 2023
In rare cases, "runas" would somehow launch the updater as a non-admin user again, resulting in a loop where the updater constantly spawns processes. Fixes obsproject/obs-studio#2984
sorenisanerd
pushed a commit
to sorenisanerd/obs-studio
that referenced
this issue
Jan 20, 2024
In rare cases, "runas" would somehow launch the updater as a non-admin user again, resulting in a loop where the updater constantly spawns processes. Fixes obsproject#2984
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Platform
Operating system and version: Windows 10 Pro 64bit - Version 1909 - build 18363.836
OBS Studio version 25.0.4 64bit
Expected Behavior
After launching the update for the new version, as non-admnistrator, the OBS Studio updater warns about the lack of administrator rights and stops or installs the software only for the current user.
Current Behavior
After launching the update for the new version, as non-admnistrator, the Obs Updater goes in loop and opens several new "updater.exe" processes until the whole system is unresponsive.
I needed to kill all the processes several times with
taskkill /F /IM "Updater.exe"
There are no useful informations in the log files.
Steps to Reproduce
https://ibb.co/5B1kh2G
https://ibb.co/MNg8fTv
Additional information
The text was updated successfully, but these errors were encountered: