How can I restrict a user from installing to the C: drive? no admin PW

Hello,

I have two main drives on my comp.: a C: - an SSD, and H: and HDD.
I have multiple user accounts, and another user of this PC never pays attention to where he is installing new software, so puts everything onto the SSD as it is always given as the first suggestion when installing anything (C:\Program Files\...).
And we end up having random games, mini-software, all sorts of stuff, taking up space on the precious SSD.

I do NOT want to completely forbid this user to install anything. The user should have access to everything, and this is why I did not put an admin password (before install wizards open up on non-admin accounts there is a dialog to insert password).

What would be a good solution?
I tried removing all permissions in the security tab on the C: drive properties, but some warnings popped up and I reverted everything back to how it was, as the dialogs suggested.

Also, if it is made invisible, I also want it to not show up in the install wizards (which is the main goal).

I found this quota thing, but would it help if there is no admin password and the user can install to C anyway?

Much thanks in advance.

Only users with admin rights can install programs and trying to restrict what such users can do is an exercise in futility. By design all admin accounts are equal. The built in Administrator account is somewhat different but not relevant to the present situation.

well.. I know this guy and he just isn't listening when I tell him to organize things. He is generally not very organized, and this method does not work.

@LMiller7 I am ok with this person installing anything he likes - there is plenty of space on the H: drive. He won't make a pile of viruses so that's not a problem, but just the C: disk... Putting an admin password is, as I said, not something I want.

@Britton30 PC is shared, but my account is admin and I just sort of take care of the PC.

I Am User said:

The user should have access to everything

This is what makes it a contradicting requirement. By letting him being an admin, you effectively give him access to everything, but also that makes impossible for you to restrict write permissions on him for certain things, as admins have full control over the whole system (or at least the ability to give it themselves).

Playing with permissions in program files may in theory achieve this, but it has two problems: he'll get a rare "access denied" error when trying to do so, not something really descriptive. And also, as he's an admin, he's also able to lift the permissions issue by himself.

Another option would be to use disk quotas. I'm not sure how well they actually work, but by giving him a low limit may restrict installers from using C, opting for the other disk instead. It may create problems when saving to my documents in C too, and like everything else, he's capable of removing the limit himself.

I doubt there can be any effective method of limiting it with him being an admin. That's why standard accounts are for.

I agree. The solution here is clearly to change his to a Standard Account so that when he makes any changes it requires you to insert a password. Just check what he is installing before signing off on it. This will teach him to interact with you about making changes to your PC in the way that you want. If he cooperates then you can promote him to Administrator again. It is a highly optional on your property.