A lot of software installation dialogs on Windows throw up a query to the installing user asking if this software should be installed for all users or the current user.

Why do they do this? Why not just install for all users? What is the real technical difference between the two options? I would like to know the difference in aspects like the registry, file execution permissions, files in the file system, start menu shortcuts and such.


In a nutshell...

Install For All Users would be used when you want the program to be "active" for anyone who logs on to the computer with their personal account (if there is more than one login). A good example would be an antivirus program, that you would want to be available while any user is logged in.

Install for Current User is normally used under an Administrator account for something that handles disk operations and other admin-type functions, such as Acronis True Image, a keylogger (to track what non-admin users are doing while logged on), and other disk-related or sensitive software.

  • 5
    It mainly controls in which start menu the links to that program appear (the current [Administrator] user's or the All users one). You don't want a keylogger to be admin-only. Actually you don't want a keylogger at all, but that's jut my opinion :-) – Joey Nov 3 '09 at 6:27
  • 1
    I will also point out that Install for Current User is often used to install regular programs when a user does not have admin rights. A lot of programs now have options that will allow standard users to install a program for their account only if they are not an administrator. Generally, administrative rights are required to install a program for all users but not always for just the current user. – InterLinked Apr 26 '18 at 16:51

Take a look at the following web site, it goes into pretty good detail on the differences of all users and current user:

Installation types

Edit: This is for a particular type of installation setup software, but the information here is valid for most installers with variations in their options prior to the compile stage.


I think that there are two ways to answer this question:

For a system admin

  • You've got applications that you don't want anyone to use other than yourself--current user, admin--,
  • you've got bs/bloatware apps that you don't want launching in admin mode but somehow monetize things for your company--current user, guest/non-admin--,
  • you've got applications that you're going to control with their built-in security measures, like AV (mentioned by NC Phantom), which has internal password protection--all users--, and then
  • you've got applications that you're going to monitor--any.

For an every-day user

  • You've got applications you want everybody to be able to use because they're awesome--all users--,
  • you've got applications you want your kids to use but don't want your friends to suddenly think you're using (like Candy Crush)--current user, guest/non-admin--, and
  • you've got applications you don't want your kids to mess up or your wife to know you're using--current user, admin.

For an advanced every-day user

Make an extra non-admin account for your friends, brother, etc., so they don't get on the guest account, start playing Candy Crush, and annoy the crap out of you.


I think the only difference is whether it'll put a shortcut in the all user start menu folder, or in the current user's start menu folder.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.