windows 10 all users startup folder

Windows 10 All Users Startup Folder: The Ultimate Guide to Managing Startup Apps

By Michael Davis
AD

Most Windows 10 users eventually run into a program that insists on launching every time the computer boots, and the trail usually leads to one of two folders: the per-user startup folder or the all users startup folder. The Windows 10 all users startup folder is the system-wide counterpart that applies a program launch to every account that signs in to the machine, which makes it both remarkably convenient for administrators and a frequent hiding spot for unwanted software. Knowing exactly where it lives, how Windows processes it, and how to control it gives you a level of authority over your PC's boot behavior that few people bother to learn.

This guide walks through the folder's location, the difference between the machine-wide and per-user versions, the practical steps for adding or removing entries, and the troubleshooting techniques that solve the stubborn cases. Whether you are setting up a shared workstation in an office, managing a family computer, or simply trying to stop a chat app from hijacking your login, the information below will get you there without guesswork.

Understanding the All Users Startup Folder in Windows 10

Windows has supported startup folders since the earliest days of the Start menu, and the design has barely changed in two decades. The idea is simple: anything placed inside a specific directory is treated as an instruction to run after the user logs in. Windows 10 maintains two of these directories, one tied to a single user profile and one tied to the machine itself. The machine-wide version is what people commonly call the all users startup folder, and it sits inside the ProgramData directory rather than inside any individual user's profile.

AD
Where is the Startup Folder in Windows 11/10 for All Users
Where is the Startup Folder in Windows 11/10 for All Users
How to Move Your User Folders in Windows 10
How to Move Your User Folders in Windows 10
Windows 10 folder icon set
Windows 10 folder icon set

Because the contents of that folder are machine-scoped, they are processed for every account that logs on, including accounts created after the shortcut was placed there. That behavior is what makes it so useful in managed environments, and it is also why Microsoft restricts write access to it by default. A standard user cannot casually drop a file into the folder without an administrator approving the action through a User Account Control prompt.

Where to Find the Folder

The physical path to the Windows 10 all users startup folder is C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp. Notice the capital U in "StartUp" and the capital U in "Programs" — the folder names are not case-sensitive in Windows, but matching the exact spelling avoids confusion when scripting. ProgramData is a hidden folder by default, so it will not appear in File Explorer unless you enable the display of hidden items or paste the path directly into the address bar.

How to Access the Windows 10 Startup Folder? - (GUIDE)
How to Access the Windows 10 Startup Folder? - (GUIDE)
Beauty Salon Secrets Revealed: Navigating the Startup Landscape - Salon Business Boss
Beauty Salon Secrets Revealed: Navigating the Startup Landscape - Salon Business Boss
How to change startup programs in Windows 10, to make your computer start faster
How to change startup programs in Windows 10, to make your computer start faster

Typing a shell command into the Run dialog is far faster than navigating the file tree. Press Windows key + R, type shell:common startup, and press Enter. Windows resolves that shortcut into the all users startup folder and opens it in File Explorer immediately. The per-user equivalent is shell:startup, and remembering the word "common" is the key distinction between the two.

LocationPathRun CommandScope
All UsersC:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUpshell:common startupEvery user account
Current UserC:\Users\<name>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startupshell:startupSigned-in user only

All Users Startup Folder vs Current User Startup Folder

The practical difference comes down to who is affected and who has permission to make changes. An entry in the current user folder runs only when that specific person signs in, and the user can add or delete items freely without administrative rights. An entry in the all users folder runs for every account on the machine, and modifying it requires elevation. If you drop the same shortcut in both places, the program will typically launch twice, which is a common cause of duplicated tray icons and doubled background processes.

AD

Choosing between them depends on intent. A personal password manager, a messaging client, or a sync tool that belongs to one person should live in the current user folder. A VPN client that must be connected before anyone works, a corporate monitoring agent, a shared printer utility, or a kiosk application belongs in the all users folder so it applies consistently to everyone. Mixing these up is one of the most frequent mistakes in workstation setup.

How to Reveal Hidden System Files in Windows 10 & 11
How to Reveal Hidden System Files in Windows 10 & 11
How to Add or Remove Startup Programs in Windows 10 and 11
How to Add or Remove Startup Programs in Windows 10 and 11
How To Make Text Bigger In Windows 10 | Daves Computer Tips
How To Make Text Bigger In Windows 10 | Daves Computer Tips
Fix: File Explorer Icon Missing in Windows 10 Start Menu
Fix: File Explorer Icon Missing in Windows 10 Start Menu
How to Open WindowsApps Folder in Windows 10
How to Open WindowsApps Folder in Windows 10
books stacked on top of each other with the title 6 windows apps that automatically organize files for you
books stacked on top of each other with the title 6 windows apps that automatically organize files for you

Managing Entries in the Machine-Wide Startup Folder

Everything inside the folder is treated as a launch instruction, but the file type matters. Shortcuts with a .lnk extension are the normal case, and they point to an executable somewhere else on disk. Batch files, scripts, and even .url internet shortcuts can also live there, and Windows simply executes them in alphabetical order during the logon process. There is no built-in priority setting, so ordering is determined purely by filename.

The folder itself contains no registry entries and no configuration file. Whatever you see listed is exactly what will run, which makes it a refreshingly transparent way to manage startup behavior compared with the more opaque Run keys in the registry. If you can see it, you can predict it.

AD

Adding Programs to the All Users Startup Folder

The cleanest method is to locate the executable in File Explorer, right-click it, choose Send to and then Desktop (create shortcut), and finally move that shortcut into the all users startup folder. Copying and pasting an existing shortcut works equally well. Because you are writing to ProgramData, Windows will prompt for administrator credentials if your account is not already elevated, which is expected and harmless.

How To Turn Off Annoying File Explorer Ads in Windows 10
How To Turn Off Annoying File Explorer Ads in Windows 10
Fun With Windows Folders 2
Fun With Windows Folders 2
How to move your user folders to another drive in Windows 10 & Windows 11
How to move your user folders to another drive in Windows 10 & Windows 11
How To Take Ownership Of Folder In Windows 10 By Yourself - MiniTool
How To Take Ownership Of Folder In Windows 10 By Yourself - MiniTool

For repeatable deployments, command-line approaches save time. A PowerShell session running as administrator can copy a shortcut with a single line such as Copy-Item "C:\Shortcuts\App.lnk" -Destination "$env:ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp". The %ProgramData% environment variable is preferable to a hardcoded path because it stays valid across Windows installations and localized folder names.

Removing and Troubleshooting Startup Entries

Deleting a shortcut from the all users startup folder is usually enough to stop the program from launching at logon, but you should confirm the change by signing out and back in rather than assuming it worked. Some applications recreate their own shortcuts during an update cycle, particularly updaters and license managers, so a deleted entry can quietly reappear weeks later. If that happens, look for a setting inside the application itself that controls launch-at-login behavior and disable it there first.

AD

When a program still starts despite an empty startup folder, the cause lies elsewhere. Check Task Manager's Startup tab, the Settings app under Apps and Startup, and the registry keys at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run and HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run. Scheduled Tasks and Windows services are other common persistence points, and a startup entry that resists deletion from the folder is often actually a scheduled task triggering the executable.

Suspicious entries deserve special attention. Malware frequently plants itself in the all users startup folder precisely because it runs for every account and survives profile changes. If you find an unfamiliar shortcut, right-click it, open Properties, and inspect the target path and digital signature before deleting it. Legitimate software almost always points to a signed executable inside Program Files, while unwanted code tends to reference obscure paths in AppData or Temp directories.

Administrative Control and Advanced Considerations

In business environments, administrators rarely rely on the folder alone. Group Policy offers a setting called Run these programs at user logon, which can push a curated list of applications to every machine in a domain, and it effectively supersedes anything a user might place in the all users startup folder. Group Policy can also disable the legacy run list entirely, which prevents both the startup folder contents and the registry Run keys from executing, a useful hardening measure for locked-down kiosks and shared terminals.

Folder redirection is another lever. The startup folders can be redirected to a network share through Group Policy, allowing a central location to control what launches on hundreds of machines at once. This approach requires care, since a network outage at logon can slow the sign-in process dramatically while Windows waits for the redirected folder to become available.

Permissions, Hidden Folders, and Windows Explorer Quirks

If the all users startup folder appears empty in File Explorer but programs still launch at logon, you may be looking at a permissions or visibility problem rather than a missing entry. The ProgramData directory is hidden, and some administrators further restrict the startup folder's access control list so that only specific security groups can read it. Running File Explorer as an administrator, or opening the folder through an elevated Command Prompt, will reveal the actual contents.

Another quirk involves the 64-bit versus 32-bit file system redirection. On 64-bit Windows, some legacy installers write shortcuts into a redirected location, which can make an entry seem invisible from certain tools. Using the shell command rather than a manually typed path usually sidesteps this entirely, because Windows resolves the shortcut to the correct real directory.

Best Practices for Keeping Logon Fast and Clean

Startup entries have a direct cost. Every shortcut in the all users startup folder adds to the time between entering your password and seeing a responsive desktop, and heavy applications compound that delay. Keeping the list short, ideally under five items, produces a noticeably faster sign-in on older hardware and on machines with traditional spinning drives.

Before adding anything, ask whether it truly needs to launch at logon or whether it could be started manually when required. For services that must run in the background, a scheduled task with a logon trigger is often more controllable than a startup shortcut, since it supports delays, condition checks, and retry logic. Where an application offers a built-in "start with Windows" toggle, use that instead of creating a shortcut, because the application will manage its own lifecycle more reliably. Audit the folder once or twice a year, remove what no longer serves a purpose, and your machine will reward you with a cleaner boot every time you press the power button.

AD