Multiple (All) steam accounts launched at once (BUG+SUGGESTION)

[haeLL420]

Hi, so yesterday i downloaded the account switcher, and right after installing it when i wanted to switch the acc it showed me that it needs to rerun with admin rights, so i clicked okay and it restarted with admin rights. Then i chose steam and clicked Log in (i didnt click any account, so the default one was selected but i dont think that matters).
And then magically ALL of my steam accounts were run, and they were all run at the same time, since in the same directory as steam.exe i have steam2.exe file which is the same (copy), but the only difference it its set to always run with avast AV sandbox feature, so all of the accounts were run at the same time every in different window. And it was exactly the same twice in the row, and then i turned off pc

I had default settings since i had just installed it, also if that matters i have on steam the choose account on every launch option turned on and the steam was completely closed (even from tray).

Unfortunately i wasn't able to replicate it today, the closest thing i got: sometimes, but it seems pretty random, i do sometimes (pretty rarely) get the steam run in the sandbox mode (using steam2.exe) but it only runs the selected account instead of all of the accounts possible. I've even tried reinstalling the whole program but I still wasn't able to trigger it.

So after this long story:

1. What do you think can cause this? How to replicate it?
2. Could this be added as a feature? -
   . a) option to choose steam.exe file which i want instead of the default one
   . b) option to run all, or multiple (selected) accounts at once

[haeLL420]

(When i set the main steam.exe file to always run in sandbox, it does always run in sandbox but still only 1 account starts at once. And when its already open and i try to log in into another account it first closes the original steam instance (Which it shouldnt do when the instance is run in sandbox because its defeating the whole multiple steam instances purpose))

[TCNOco]

I'm not too sure what is being requested here... steam.exe is the only application the TcNo Account Switcher interacts with for Steam account switching, that's the only one it should start.
Steam then reads loginusers.vdf to see which user is currently signed in, and logs in with that - That's how the account switcher functions.

Getting multiple Steam accounts to run at the same time would require loginusers.vdf and other files to be referenced by each program differently, somehow, I would assume... This is what you're trying to, or are currently accomplishing with a sandbox?

[haeLL420]

So basically I would like to have the option to choose the .exe file which the program uses to start steam (instead of always steam.exe)
And the option to run second/another steam instance/account without closing the last one (because currently, when i try to log in with another account it closes all the already open steam windows etc.)
And the option to launch multiple accounts at once. (Like select a few accounts and then when click login it would launch all of them or something like that.

Which i somehow achieved, thats why i also reported it as a bug, because I don't think that was a intended feature.

(If that's too much work just for my usage, because its probably pretty niche, then I would be happy if you could just make it be able to run another steam/account without closing the previous one (because when i set the main steam.exe to always run sandboxed, then i can have multiple steam instances at once) because the other two features I can achieve manually with a few more clicks)

Thanks in advance :)

[haeLL420]

Also the multiple steam instances at once is already handled by the Avast AV Sandbox feature, so there's no need for your account switcher to do anything like that.

Also that probably doesn't matter at all, since the account switcher only needs to start the steam.exe (or steam2.exe preferrably) with the correct account, but if you do want to know, I'm pretty sure the Avast Sandbox just isolates resources from each sandboxed program into a separate virtual environment in which that program can read the files from the PC, but it can't write them (in the virtual environment it writes them, but it's not affecting the real system) so the sandboxed steam instances do have all the steam settings, and all the logged in accounts info, because it does have access too all of those steam files.

So it's somewhat like the exe is run in a virtual machine, but has access to the main pc files