OBS Version 32.0.0 removed --disable-shutdown-check

[jeffdyer]

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.

Nope. Breaking changes should not be rolled out in self updating software. Never.

 

[PaiSand]

Nope. Breaking changes should not be rolled out in self updating software. Never.

The change isn't breaking anything.
You shouldn't ever update, change or add anything on a production environment until tested on a test environment. Good practices.

 

[jeffdyer]

The change isn't breaking anything.
You shouldn't ever update, change or add anything on a production environment until tested on a test environment. Good practices.

It is breaking numerous installations where disable-startup-check is required

 

[jwdlm]

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.

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

I get this error.

 

[KittieCatKay]

I would second reinstating this flag. I have automated my obs using the task scheduler. These intentionally kill obs. I do not want to get an error message every time they do this, as that also breaks a few automated scripts I have made.

 

[Wheemer]

Rug pulling on previous working features we've become accustomed to is not cool. There's no conceivably valid reason to disrupt so many working setups.

 

[Akelaphobia]

Really annoyed they removed this..

 

[Robert-S]

Please please please reinstate the disable-shutdown-check argument!!
I regularly use Windows Task Scheduler to start OBS for streaming a church service. It's vital that I also set up a scheduled task to STOP OBS, but there doesn't seem to be any 'clean' way of exiting the program by command line. The only way (that I have been using for years) seems to be to kill the obs.exe process. This works fine - but it is clearly seen by OBS as a bit dirty. So be it! It's vital that the next scheduled start of OBS is not disabled - so it's vital that I disable the shutdown check.
I feel very disappointed that this feature has been removed without apparent consideration for those who use this kind of automation.