We have just shipped a beta feature that allows you to try out new update behavior which should hopefully address most of the grievances posted here.
This is a multipart change that currently only has any effect on Windows. When we finish support for Mac, it will be available through the same beta feature. If you’re on Mac, you can go ahead and enable the beta feature if you want to automatically opt-in to the feature once it’s live on Mac.
The exact breakdown between the new / old behavior is:
Old
When a new Studio instance is opened and an update is available, Studio immediately begins to update. The new instance never finishes opening, preventing you from opening any new instances (test servers, other places in the game, etc) until Studio is updated, and the updater attempts to close all places to update Studio. (Because of a bug with the updater, sometimes it would force-kill Studio instead of prompting the user to close all places. Team Create instances would always immediately shut down)
If you did not update Studio for 22 hours after an update became available, the updater would automatically pop up and update Studio, even if you were in a fullscreen game.
New
Studio will only ever automatically update if it is being launched for the first time with no existing instances opened, as it is the only point in which we can shut down for update without losing work. If you open a Studio instance while an update is available now, we will honor your request to open that instance, prompting you with a cancellable dialog asking if you want to shut down & update, instead of preventing the new instance from being opened. If you leave Studio open for 48 hours after an update becomes available, you will receive the same cancellable dialog. It will only pop up if you are using that instance of Studio (so never while you’re using a fullscreen game, browsing the internet, etc). You will never receive this dialog when opening test servers / detatched play solo.
If you cancel the dialog, however, it will continue to pop up once an hour from then on. If the dialog is excessively annoying, please provide feedback so we can continue to look into the issue. The recurring dialog allowed us to release these changes sooner rather than later since it’s annoying enough that we didn’t have to investigate the impact of an excessive increase in old versions, but we are open to changing it. Even with the spammy dialog though, the new behavior should be all-around better (you can actually use Studio longer than 22 hours / opening a new instance now)
NOTE: This change only applies to Studio. If you launch Studio via RobloxStudioBetaLauncher.exe (what usually gets pinned to the start menu / taskbar / desktop), it will still try to forcefully shut down all instances to update. If you are opening from Studio (e.g. test server, Game Explorer, File > Open From Roblox) you’re fine, but otherwise use RobloxStudioBeta.exe or switch to Studio and File > Open From Roblox.