References:
- obsproject/obs-studio#12650
- https://obsproject.com/forum/threads/obs-version-32-0-0-removed-disable-shutdown-check.190590/
For Windows users looking to workaround this change, here's my setup consisting of two Task Scheduler tasks.
I have setup this guide so it:
- Does not require creation of any scripts/files
- Works for users without admin rights
- Allows you to directly copy-paste values.
Note
The --disable-shutdown-check flag was removed to encourage reporting of cases where OBS does not shutdown cleanly.
Please consider investigating the cause behind your case and reporting relevant details via the appropriate channels.
Warning
Working around the shutdown check is considered bad practice and could result in data loss.
Use it at your own risk.
To setup OBS Autostart without bypassing the shutdown check, simply skip Task 1.
First, open Task Scheduler.
- Open Start Menu
- Type
Task Scheduler - If you wish to use OBS' hotkeys in games you run as administrator (not recommended), right click on the first result and click
Run As Administrator. Otherwise, just click on the result normally.
π Click to expand instructions
β- Click
Create Basic Taskon the right - Name:
OBS Disable Shutdown CheckthenNext - Click
When I log onthenNext - Click
Start a programthenNext Program/script:cmd.exeAdd arguments:/c "rd /s /q %APPDATA%\obs-studio\.sentinel"- Check
Open the Properties dialog... - Click
Finish - Click
Conditionstab - Uncheck the two checked options
The following steps are optional.
Only proceed if you are setting up OBS to auto-start on a non-administrator account,
with the ability to use OBS' hotkeys in games you run as administrator (not recommended).
Otherwise, click OK on every open dialog, keep Task Scheduler open, and skip to Task 2.
- Click
Generaltab - Click
Change User or Group... - Type the username of the account you want to start OBS on when it logs in
- Click
Check Names, then double-check the result - Click
OK - Click
Triggerstab - Double click the only entry
- Click
Specific user - Click
Change User... - Repeat Steps 13-14 here
- Click
OKon every open dialog, but keep Task Scheduler open
π Click to expand instructions
β- Click
Create Basic Taskon the right - Name:
OBS Autostartthen clickNext - Click
When I log onthen clickNext - Click
Start a programthen clickNext Program/script:"C:\Program Files\obs-studio\bin\64bit\obs64.exe"- [Optional]
Add arguments:--startreplaybuffer --minimize-to-tray(delete as per your preferences) Start in:C:\Program Files\obs-studio\bin\64bit\(do NOT add quotes or remove the final backslash)- Click
Next - Check
Open the Properties dialog... - Click
Finish - [Optional] Tick
Run with highest privilegesif you wish to use OBS' hotkeys in games you run as administrator (not recommended) - Click
Conditionstab - Uncheck the two checked options
- Click
Settingstab - Uncheck
Stop the task if it runs longer than - Click
Triggerstab - Double click the only entry
- Check
Delay task forand paste15 secondsinto the dropdown text-box
The following steps are optional.
Only proceed if you are setting up OBS to auto-start on a non-administrator account,
with the ability to use OBS' hotkeys in games you run as administrator (not recommended).
Otherwise, click OK on every open dialog then close Task Scheduler.
- Click
Specific user - Click
Change User... - Type the username of the account you want to start OBS on when it logs in
- Click
Check Names, then double-check the result - Click
OK - Click
Generaltab - Click
Change User or Group... - Repeat Steps 21-22 here
- Click
OK - Click
OKon every open dialog then close Task Scheduler
It's nutty how OBS devs refuse to fix this. Its like they are so thirsty for bug reports, they disable the ability to remove the annoying and debilitating popup. Huge fail on their attitude and understanding of how people use OBS. One excuse for refusing to fix it is that OBS is meant to be used as a UI for direct user interaction. Indeed, so make a UI OPTION TO DISABLE THIS. Also, it's not like the community is requesting a new feature here, its that devs accidently removed the (--disable-shutdown-check) feature and are now pretending like it happened for good purpose, even though the community is negatively affected by the change. They also gaslighted the community in the comments for not shutting down their PC correctly, and tried to blame the affected users for improper usage. Yuck. This project is here because of us, not them, the naughty devs need reminding in this case. The correct and professional behavior would be for them to commit to fixing the issue they caused, and not deny and deflect (or whatever this is). Rant over.
Thank you for this. I did a .bat file to delete the garbage .sentinel directory and launch OBS. Worked.