This page explains a decision you will otherwise wonder about: the engine underneath the program is deliberately frozen, and cannot update itself.
What is pinned
During installation the engine’s own updater is removed and automatic updates are switched off. It stays on the version the setup installed until a new setup replaces it.
Why
The program and the engine belong to one generation. They share libraries, and a mismatch is not a small problem: the program simply does not load, the branded interface never appears, and the operator is looking at something that is not the program they know.
An engine that updated itself overnight could produce exactly that, on a Sunday morning, with nobody who knows why.
And more generally: a broadcast machine should be boring. Nothing changes between last week and this week unless somebody decided it should.
What that means for you
You do not have to do anything. No update prompts, no “restart to finish installing” while a service is starting.
A new engine version arrives with a new setup, chosen and tested by whoever builds the release — not by the machine.
Your own OBS is unaffected and can keep updating as it likes; it is a different installation entirely.
Checking which one you have
Settings → Info → Engine. Quote that together with the program version when reporting a problem: those two together identify the combination you are running.
When it does change
Running a newer setup replaces everything under engine except the configuration folder, so files from two versions can never end up mixed while your settings, scenes and designs survive.
That is also why a second run of the same setup is quick: the engine is already at the pinned version and the step is skipped.