How to Install an App for One User on Windows 10

To install a Windows 10 desktop app for one account, run its installer while signed in to that account and choose “Just for me” or “Current user” if offered. If setup lets you choose a destination, a folder under %LOCALAPPDATA%\Programs\Vendor\AppName is a suitable user-profile location. Changing the folder alone does not turn an all-users installer into a per-user install; the setup package must support that scope.

What a per-user installation changes

Windows Installer offers two contexts: per-machine and per-user. The first is designed for all accounts; the second can place installer-managed items such as shortcuts and registrations in the current user’s locations. The package and installation mode determine the context. Copying program files into a profile folder alone does not. Microsoft’s installation-context documentation explains the difference.

Install the app for the signed-in user

1. Sign in to the intended account and download setup from the app publisher or another trusted source. On a managed PC, ask the administrator first. If setup asks for credentials from a different administrator account, check the publisher’s instructions; the prompt may indicate a system component or a machine-level install.
2. Select the current-user scope. Choose a setup option such as “Install for current user,” “Only for me,” or “Just for this user.” Do not choose “All users” or “Anyone who uses this computer.” Wording varies, and many installers do not offer this choice. A Windows permission prompt alone does not identify the install scope.

3. Choose a profile folder if setup supports it. A common destination is %LOCALAPPDATA%\Programs\Vendor\AppName. Press Windows+R, enter %LOCALAPPDATA%, and press Enter to open the current account’s Local AppData folder. In setup, create a separate folder for the app instead of placing files directly in AppData\Local. If the installer does not accept the variable, copy the full path from File Explorer. This is a suitable destination only when the installer supports per-user installation.

4. Complete setup without changing the scope. Leave any all-users option off. If the installer says it requires Program Files, a system service, a driver, or another shared component, do not force it into AppData. Follow the publisher’s requirements or find out whether it offers a per-user version.

5. Check the result in the same account. Open Start and search for the app. For a shortcut check, press Windows+R and inspect %APPDATA%\Microsoft\Windows\Start Menu\Programs, the current user’s Start Menu programs folder. The shared folder is %ProgramData%\Microsoft\Windows\Start Menu\Programs. Microsoft documents that Windows Installer places per-user shortcuts in the user profile and machine-wide shortcuts in the all-users profile. A shortcut’s location is a useful clue, but custom app installers may behave differently.

If there is no “current user” option

Do not assume that selecting an AppData destination makes an app single-user. Some installers support only per-machine setup, and changing the path does not move their registry entries, shortcuts, updaters, or services into a user context. For an MSI package, MSIINSTALLPERUSER works only when the package supports both contexts and uses ALLUSERS=2; otherwise Windows Installer ignores it. A generic command cannot convert an unsupported package. See Microsoft’s MSIINSTALLPERUSER reference and ask the publisher for supported per-user instructions.

MSIX and AppX use a different deployment model. Microsoft describes Add-AppxPackage as adding a signed package to a user account. For an MSIX or AppX download, follow the publisher’s installation steps; avoid admin provisioning methods meant to prepare apps for multiple users. See the Add-AppxPackage documentation.

Limits and quick fixes

• Setup insists on Program Files or an administrator-only component: it may need shared system changes. Check the publisher’s instructions instead of forcing a new path or bypassing a permission prompt.
• Every account sees a shortcut: setup may have created a shared shortcut or installed per-machine. Removing that shortcut will not change the installation scope.
• You want the app to be private: per-user setup does not guarantee that other people cannot run the program or read its files. Access depends on Windows permissions and the app. Use separate Windows accounts and appropriate permissions for privacy.
• Uninstalling: sign in to the same account and use the app’s uninstaller or Windows’ installed-app controls. Do not delete the folder first, or installer and updater records may be left behind.

Windows 10 support note: Microsoft ended support for Windows 10 on October 14, 2025; check the support status for your edition if you continue using it.