Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Alternatively, when you install Steam initially you can choose to only install for the current user. Here's a decent guide; however, I've never installed Steam in this manner so can't attest to it's functionality.
https://www.addictivetips.com/windows-tips/install-an-app-for-a-single-user-on-windows-10/
I suppose this will be useful though when I get a new PC later this year.
Well, thanks. Sadly my gaming PC is also the one the wife uses to hunt for her coupons and the kids use for school. Sounds like I need to get them some laptops of their own.
this post from "gagnrad" is the answer.
i'm wondering why OP never bother to read before he go make this post of his
I don't know what they are saying. Log out? I really don't want to log out as it's a pain to log back in involving codes being sent to my phone, etc. Also STEAM just kicks on and logs in as the PC boots up, then updates itself.
I'm not going to say or insinuate that I understand how all this works. The answer I was hoping to find is someone just saying "Go to Settings, Set allowed users equals X, save." But apparently this is more of a WIN 10 issue than a STEAM issue.
It didn't always do that no, normally when a different windows user signs into their own account Steam would attempt to get the login credits that were associated with that account. (I don't know where steam saves this exactly or how)
Its an issue related uniquely to Windows 11 as well.
Here's some windows info:
When an icon exists on a desktop, it is usually actually just a 'shortcut'. A shortcut is a 'link file', a file that ends with .lnk and is actually saying "do this that is stored somewhere else".
Each desktop for each user has their own user access level (security wise).
If you attempt to move something that isn't associated with your user specifically and is actually on Someone Else's desktop or shared through 'all users', then you may need elevated access rights to change it. (that said, you can hide it on your specific desktop per user)
This is because you'd be 'removing' the file from 'all users', not just the logged in user.
I assume "Steam" is not installed on the desktop, so its not an exe file. You can safely remove it.
I did try to just remove the icons from the other users, but it said it required admin rights to 'delete' this. Well I have admin rights of course, but it made it sound like it was going to remove STEAM from my PC altogether, so I stopped.
Like I said I'll be getting a new PC soon. Perhaps at the same time I'll get my wife a new iPad that she can do all her shopping on and there wouldn't be any reason then for her to use the PC. Kids already have their own laptops so they should be good as is.
That was what I was trying to explain. If you access another user's profile and attempt to remove a file that windows flagged 'its theirs', then you need administrative previllages.
You don't need that for removing stuff on your own profile.
and if you're an admin you don't usually get this access level warning because you're an admin.
You have neutral sections on your PC, and most of the default neutral sections require admin access level to change stuff about them. If it is a folder, then unless a specific user made the directory or file in there, they cannot do much with it, unless they are admin.
You have user parts on your pc, which requires user access level. (each user has their own access key). User access level is separated per user, only admins can mess with files belonging to other people. (basically)
and then there is a section for 'system', which is kinda like a separate user. If you mess with files in here you will also get warnings, like in the windows folder.
Anyway, installation packages (which do it automatically) and admins can change stuff about "program files" or "program files (x86)"
Users can change stuff about their own profile. Installations go normally to program files, but if it requires admin access, which it sometimes does and a user is trying to install it, the installation may either go to their own profile instead, which is by default appdata/local (unless shared over multiple computers, then its appdata/roaming) or the user may need to create a new folder somewhere.
Some installation packages prefer the user profile by default (and go to either appdata/roaming or appdata/local) though normally they end up in program files.
Program Files installations are shared only locally on the pc. Yes, I mean shared to all users. each user can use what is installed inside of it, but usually only admins can change stuff within program files. (At least this is true when the admin is the one installing these things) And with change stuff I mean basically rename or remove files. So you may get the warning here as well to let you know 'it will be gone/changed if you do this'
Steam is by default installed into Program Files. The icon on the desktop is a shortcut to Program Files (x86)/Steam/steam.exe
Edit:
So if I had to explain in more depth.
If a regular user (not admin) tries to remove Program Files, they will get a warning that they cannot.
They however can add a file into it, because they have read access to the directory file. The file inside it will have read and write permission.
A regular user usually however cannot even read another user's profile and the folders inside there.
That said, an installation package can sometimes do this however. What's more is that folders made by the installation package, usually automatically get permissions set and if a user installs it, then the user is added to the full permissions list. And yes this also happens when they install something into Program Files. (This is thankfully true so, because it will then also allow the same user to manage and uninstall the program. Its not a bad thing).
That said, if an admin installs something into program files, sometimes regular users will be locked out, out of adminstrating it I mean. They cannot change anything inside there manually.
(windows update, program updates and installation packages still can however)
It's just to delete what you tried. If you tried to delete the shortcut that's all it it'll delete. Do it again and enter you password, Password won't be saved, and they won't see the shortcut