OBS Version 32.0.0 removed --disable-shutdown-check

[ClosedTicket69]

Hi,

I’ve been using OBS for a while to run microphone filters and output to VB Cable as my input device. My setup relies on OBS running silently in the background every time I start my PC, so I had a shortcut in shell:startup with the flag --disable-shutdown-check.

With this setup, OBS launched minimized and bypassed the “OBS didn’t shut down properly” popup that happens every single time I restart my computer. Without that flag, OBS now stops on the crash prompt, which breaks the automation and forces me to manually click it every reboot.

After updating to 32.0.0, I found that --disable-shutdown-check has been removed. This essentially ruins the ability to have OBS auto-run in the background for anyone using it as a virtual mic with VB Cable or similar workflows or people who just find the pop up redundant and annoying.

There are several existing posts on this forum where users discovered and used --disable-shutdown-check as a solution to avoid the popup on restart. By removing the flag, all of those setups are now broken as well:

https://obsproject.com/forum/threads/always-asks-to-boot-normally-or-safemode.171124/

https://obsproject.com/forum/thread...function-on-off-toggle-add-to-setting.171047/

https://obsproject.com/forum/threads/error-obs-did-not-shut-down-properly.171003/

I understand the flag was removed in 32.0.0, but for those of us who rely on automated OBS startup, this breaks an important use case. If the shutdown check is needed for stability reasons, could there at least be an official setting or supported flag for users who intentionally run OBS in the background like this?

As of now my current solution is to just use version 31.1.2 and turn off "Automatically check for updates on startup".

 

[suynad]

Hi, I hope I can help you since I had the same problem after the v32 update.
I used a bash script on windows that force close and start a new instance of obs, in my case using taskkill. After this update, obviously, every time I use this script to restart OBS I have this dialogue box.
I found that deleting an hidden folder (.sentinel, under %appdata%\obs-studio "C:\Users\YOURUSERAME\AppData\Roaming\obs-studio\.sentinel") before start a new instance prevents OBS to show that dialogue box.
In my case, my script is: KILL OBS --> delete .sentinel folder --> start OBS

I hope this helps you.

 

[CaDuSiMs]

Essa atualização quebrou minha automação também.

Porque foram inventar de tirar o --disable-shutdown-check ? Infeliz decisão.

 

[LeeseTheFox]

Registered here just to reply. My app was relying on that flag to get rid of the warning. Because it has been removed, I had to code a new way of suppressing that warning (automatic deletion of the .sentinel folder).

 

[valeriya-cyka-bylat-valis]

NOT GOOD!!! NOT GOOD!!!!

 

[valeriya-cyka-bylat-valis]

can someone write a script please? delete .sentinel before shutting down or right after OBS had been "killed"

Hi, I hope I can help you since I had the same problem after the v32 update.
I used a bash script on windows that force close and start a new instance of obs, in my case using taskkill. After this update, obviously, every time I use this script to restart OBS I have this dialogue box.
I found that deleting an hidden folder (.sentinel, under %appdata%\obs-studio "C:\Users\YOURUSERAME\AppData\Roaming\obs-studio\.sentinel") before start a new instance prevents OBS to show that dialogue box.
In my case, my script is: KILL OBS --> delete .sentinel folder --> start OBS

I hope this helps you.

 

[nexk52]

I'm the author of the past thread you mentioned. I am also experiencing inconveniences with the current version, and as previously argued, I think there should be a toggle switch for the feature in the settings. It seems to be a recurring problem with every version upgrade.

 

[nexk52]

If OBS can run purely on its own without any additional plugins, then the --safe-mode parameter still works, and in this case no warning appears. However, if you need to use VST plugins, this method is useless.

 

[Playjunkie]

OBS 32 broke StreamDeck, broke Aitum Vertical Canvas... Uninstalled so fastt, and still now 31 isn't working correct either. Just what happened?

 

[sjain]

Auto-start OBS with Windows and bypass shutdown check
I have setup this guide so it:

1. Does not require creation of any scripts/files
2. Works for users without admin rights
3. Allows you to directly copy-paste values.

Task 1 - Disable Shutdown Check

Spoiler: Click to expand instructions

1. Open Start Menu
2. Type Task Scheduler
3. Right click on the first result and click Run As Administrator
4. Click Create Basic Task on the right
5. Name: OBS Disable Shutdown Check then Next
6. Click When I log on then Next
7. Click Start a program then Next
8. Program/script: cmd.exe
9. Add arguments: /c "rd /s /q %APPDATA%\obs-studio\.sentinel"
10. Check Open the Properties dialog...
11. Click Finish
12. Click Conditions tab
13. 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.
    Otherwise, click OK on every open dialog, keep Task Scheduler open, and skip to Task 2.
    
    
14. Click Change User or Group...
15. Type the username of the account you want to start OBS on when it logs in
16. Click Check Names, then double-check the result
17. Click OK
18. Click Triggers tab
19. Double click the only entry
20. Click Specific user
21. Click Change User...
22. Repeat Steps 17-19 here
23. Click OK on every open dialog, but keep Task Scheduler open

Task 2 - OBS Autostart

Spoiler: Click to expand instructions

1. Click Create Basic Task on the right
2. Name: OBS Autostart then click Next
3. Click When I log on then click Next
4. Click Start a program then click Next
5. Program/script: C:\Program Files\obs-studio\bin\64bit\obs64.exe
6. [Optional] Add arguments: --startreplaybuffer --minimize-to-tray (delete as per your preferences)
7. Start in: C:\Program Files\obs-studio\bin\64bit\ (do NOT add quotes or remove the final backslash)
8. Click Next
9. Check Open the Properties dialog...
10. Click Finish
11. [Optional] Tick Run with highest privileges if you wish to use OBS' hotkeys in games you run as administrator (not recommended)
12. Click Conditions tab
13. Uncheck the two checked options
14. Click Settings tab
15. Uncheck Stop the task if it runs longer than
    
    The following steps are optional.
    Only proceed if you are setting up OBS to auto-start on a non-administrator account.
    Otherwise, click OK on every open dialog then close Task Scheduler.
    
    
16. Click Change User or Group...
17. Type the username of the account you want to start OBS on when it logs in
18. Click Check Names, then double-check the result
19. Click OK
20. Click Triggers tab
21. Double click the only entry
22. Click Specific user
23. Click Change User...
24. Repeat Steps 17-19 here
25. Click OK
26. Check Delay task for and paste 15 seconds into the dropdown text-box
27. Click OK on every open dialog then close Task Scheduler

 

[valeriya-cyka-bylat-valis]

Auto-start OBS with Windows and bypass shutdown check
I have setup this guide so it:

1. Does not require creation of any scripts/files
2. Works for users without admin rights
3. Allows you to directly copy-paste values.

Task 1 - Disable Shutdown Check

Spoiler: Click to expand instructions

1. Open Start Menu
2. Type Task Scheduler
3. Right click on the first result and click Run As Administrator
4. Click Create Basic Task on the right
5. Name: OBS Disable Shutdown Check then Next
6. Click When I log on then Next
7. Click Start a program then Next
8. Program/script: cmd.exe
9. Add arguments: /c "rd /s /q %APPDATA%\obs-studio\.sentinel"
10. Check Open the Properties dialog...
11. Click Finish
12. Click Conditions tab
13. 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.
    Otherwise, click OK on every open dialog, keep Task Scheduler open, and skip to Task 2.
    
    
14. Click Change User or Group...
15. Type the username of the account you want to start OBS on when it logs in
16. Click Check Names, then double-check the result
17. Click OK
18. Click Triggers tab
19. Double click the only entry
20. Click Specific user
21. Click Change User...
22. Repeat Steps 17-19 here
23. Click OK on every open dialog, but keep Task Scheduler open

Task 2 - OBS Autostart

Spoiler: Click to expand instructions

1. Click Create Basic Task on the right
2. Name: OBS Autostart then click Next
3. Click When I log on then click Next
4. Click Start a program then click Next
5. Program/script: C:\Program Files\obs-studio\bin\64bit\obs64.exe
6. [Optional] Add arguments: --startreplaybuffer --minimize-to-tray (delete as per your preferences)
7. Start in: C:\Program Files\obs-studio\bin\64bit\ (do NOT add quotes or remove the final backslash)
8. Click Next
9. Check Open the Properties dialog...
10. Click Finish
11. [Optional] Tick Run with highest privileges if you wish to use OBS' hotkeys in games you run as administrator (not recommended)
12. Click Conditions tab
13. Uncheck the two checked options
14. Click Settings tab
15. Uncheck Stop the task if it runs longer than
    
    The following steps are optional.
    Only proceed if you are setting up OBS to auto-start on a non-administrator account.
    Otherwise, click OK on every open dialog then close Task Scheduler.
    
    
16. Click Change User or Group...
17. Type the username of the account you want to start OBS on when it logs in
18. Click Check Names, then double-check the result
19. Click OK
20. Click Triggers tab
21. Double click the only entry
22. Click Specific user
23. Click Change User...
24. Repeat Steps 17-19 here
25. Click OK
26. Check Delay task for and paste 15 seconds into the dropdown text-box
27. Click OK on every open dialog then close Task Scheduler

very nice. however a delay would be mandatory like
- start PC
- execute OBS Disable Shutdown Check right after login
- wait 2-3 minutes (i don't need OBS that fast in background/RAM)*
- execute OBS Autostart.

*I don't think 15 seconds would be enough.

 

[jayjay1818]

I do hope they reinstate this flag, it's much simpler than the workaround as per above. I currently use three OBS instances on a VM (One native installed and two portable), so setting up the above for all is a bit of a pain. It's a lot easier for automation using a flag, less reliance on tasks to run. For sure holding fire with the upgrade for the time being..

 

[Wild Thing]

9. Add arguments: /c "rd /s /q %APPDATA%\obs-studio\.sentinel"

Not to be a nitpicker but quotations need to start and end on the directory, like:

/c rd /s /q "%APPDATA%\obs-studio\.sentinel"

had me stumped for a minute lol.

 

[xamspanda]

Hi all,

The OBS team is aware of this issue. They've got a PR to fix the unclean shutdown.
If you go to the Windows x64 Build you can Download the Artifact and test signing out/shutting down while OBS is recording, and it should start without the safe mode crash dialog.

 

[ClosedTicket69]

Hi all,

The OBS team is aware of this issue. They've got a PR to fix the unclean shutdown.
If you go to the Windows x64 Build you can Download the Artifact and test signing out/shutting down while OBS is recording, and it should start without the safe mode crash dialog.

Is this expected to be in the next hotfix? I'll look out and test any new updates that mention the unclean shutdown in the changelogs but until then, or if nothing works in the future, I'll just keep using 31.1.2.

Wish we knew why they don't want --disable-shutdown-check anymore. Hopefully going forward we won't even have to worry about it. I always used it as a workaround for OBS thinking it crashed after I restarted my PC.

 

[AsmadiGames]

This is such an awful decision - devs should have fixed the unclean shutdown issues BEFORE removing the command line option. Our automation is broken now too. Who the heck even wanted safe mode?

 

[PaiSand]

Simple reinstall the previous OBS version you all where using and all works again.
Then wait until a new version of OBS with the fix is released and you can first test it and then deploy it to the production environment. Never update or change anything without testing it first.

 

[AsmadiGames]

Unless the fix is reinstating the command line option (or allowing the suppression of safe mode), this renders OBS more or less unusable for launch automation going forward. Software crashes - it's a constant throughout the history of development. It takes a lot of hubris to assume your software will never crash. There's no value lost by allowing people who need to suppress safe mode to do so.

Aside from that, I'm going to guess a power outage or other unexpected shutdown will result in the sentinel file remaining intact as well (and thus spawning the safe-mode dialog box). So even if they do fix some of the core forced-shutdown issues, a bunch of needless manual intervention will be required if anything at all goes wrong.

Obviously we can revert to 31.1.2, but it's disappointing to think we have to do that long-term or even permanently.

 

[SpectrumTechOps]

Hi,

I’ve been using OBS for a while to run microphone filters and output to VB Cable as my input device. My setup relies on OBS running silently in the background every time I start my PC, so I had a shortcut in shell:startup with the flag --disable-shutdown-check.

With this setup, OBS launched minimized and bypassed the “OBS didn’t shut down properly” popup that happens every single time I restart my computer. Without that flag, OBS now stops on the crash prompt, which breaks the automation and forces me to manually click it every reboot.

After updating to 32.0.0, I found that --disable-shutdown-check has been removed. This essentially ruins the ability to have OBS auto-run in the background for anyone using it as a virtual mic with VB Cable or similar workflows or people who just find the pop up redundant and annoying.

There are several existing posts on this forum where users discovered and used --disable-shutdown-check as a solution to avoid the popup on restart. By removing the flag, all of those setups are now broken as well:

https://obsproject.com/forum/threads/always-asks-to-boot-normally-or-safemode.171124/

https://obsproject.com/forum/thread...function-on-off-toggle-add-to-setting.171047/

https://obsproject.com/forum/threads/error-obs-did-not-shut-down-properly.171003/

I understand the flag was removed in 32.0.0, but for those of us who rely on automated OBS startup, this breaks an important use case. If the shutdown check is needed for stability reasons, could there at least be an official setting or supported flag for users who intentionally run OBS in the background like this?

As of now my current solution is to just use version 31.1.2 and turn off "Automatically check for updates on startup".

Yes I am afraid I have had to take the same action. Caused us a lot of grief last week so had to revert to 31.1.2.

 

[sjain]

Not to be a nitpicker but quotations need to start and end on the directory, like:

/c rd /s /q "%APPDATA%\obs-studio\.sentinel"

Interesting. Did it not work for you? It works fine for me without this change. There are no spaces in the path, so I don't see why quotes are required there. Its more impoortant that the entire command is wrapped in quotes so it appears as one to the /c argument.

very nice. however a delay would be mandatory like
- start PC
- execute OBS Disable Shutdown Check right after login
- wait 2-3 minutes (i don't need OBS that fast in background/RAM)*
- execute OBS Autostart.

*I don't think 15 seconds would be enough.

I fixed this in my guide on Github, but editing posts is not allowed here. I've reported the post with my edit request. I believe 15 seconds should be fine for SSDs and HDDs as its an empty folder. Others may also not want to wait 2-3 minutes.

Auto-start OBS with Windows and disable shutdown check.md

GitHub Gist: instantly share code, notes, and snippets.

gist.github.com