Multiple Installations of Studio on Windows PC with multiple user accounts causes one or both to be completely broken

Bug Reports Studio Bugs
,
1

On Windows computers with multiple accounts, it seems to be very easy to get into a situation where there is one Roblox Studio installation that is ‘shared’ across user accounts- however, Roblox Studio doesn’t seem to actually support this behaviour. When opening it, you get this error:
image

To fix this, and this isn’t prevented by Roblox Studio’s installer, you might then go ahead and install Roblox Studio on your own user as an installation for that user, however:

  • Roblox will still always open the ‘shared’ studio file when pressing the ‘Edit in Studio’ button from the website
  • Because of the above, the user installation is never updated or prompted to update, so when opened, you get all kinds of weird errors, from saying that the version of studio is outdated and should be updated by going to create.roblox.com (which updates the shared installation), and others like the one below
    image

Expected behavior

Studio should prioritise the installation on the user’s account, and if it doesn’t support ‘universal’/‘shared’ installations, then it shouldn’t allow them in the first place.

Currently I’m just completely unable to use Studio on this computer at all on my own account. It works on the account that installed the original ‘shared’ version of studio, but neither versions work on my account.

1 Like
2

Update: I was able to temporarily fix this by uninstalling the version on my own user, then redownloading studio - when it opened after installing it has worked.

2 Likes
3

Hi, not sure has this reoccurred or not, but we support installation as admin or installation as user. User installs are completely separate, and we’re not aware of a way that it would result in an HTTP error. I’m wondering if in this case it was a really old install? That can happen regardless of the location of the install. But in either case, it still won’t yield a network error, as nothing about the version prevents an outgoing network connection. If the problem is resolved on your end, there’s not much more action we can take here that we’re aware of.