The startup folder in Windows 11 lives at C:\Users<YourName>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup for your user account, and at C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp for every account on the PC. You can open either in about five seconds without touching File Explorer: press Win+R, type shell:startup or shell:common startup, and press Enter. The window that appears is the folder, shown as a normal directory you can drop shortcuts into.
Mechanism: what the startup folder actually triggers
The startup folder is not a scheduler and holds no timing logic of its own. It is a watched directory that Windows Explorer reads during sign-in, looking for shortcuts and other executables to launch. When you sign in, the shell enumerates the folder's contents and starts each item it finds, so the folder functions as a launch list, not a program.
Location matters because Windows merges two scopes. Your per-user startup folder loads only after your account signs in, which means another user's sign-in does not trigger your entries. The all-users folder loads for every account, including a shared kiosk or family PC, so an entry placed there fires for everyone who logs on.
Two details explain most behavior people misread. First, startup items do not fire at boot; they fire at sign-in, so a machine that sits at the lock screen has not yet run them. Second, order is not a fixed queue. Windows starts the known list but does not guarantee a strict launch sequence, so do not rely on one startup app loading before another. Plain language version: the folder is a guest list for sign-in, not a rigid assembly line.
There is also a newer wrinkle. Windows 11 has been migrating some startup entries into the Settings app's Startup page, and entries can appear there even when no shortcut sits in either folder. For example, a Store app or a publisher-managed component can register itself through the registry instead of the folder. The folder and the Settings list are related views, not the same list, which is the single most common source of confusion this article exists to untangle.
Quantified context: two folders, dozens of entries, real risk
Windows 11 ships with a Settings startup manager under Settings > Apps > Startup. That page shows each entry's status and an estimated impact rating, commonly phrased as Low, Medium, or High, based on how much CPU and disk time the entry consumed during a short measurement window. The rating is a rough gauge, not a benchmark, but it is the fastest signal for trimming a slow sign-in.
The two folder paths differ in scope and count. The per-user folder typically holds zero to five shortcuts on a fresh profile. The all-users folder usually holds zero to three, often empty on consumer machines. When either list grows past roughly ten items, sign-in can stretch by several seconds, and the delay compounds because each program may spawn its own background processes.
| Location | Scope | Path (Windows 11) | Typical entries | Opened by |
|---|---|---|---|---|
| Per-user startup | One account | %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup | 0-5 | shell:startup |
| All-users startup | Every account | %ProgramData%\Microsoft\Windows\Start Menu\Programs\StartUp | 0-3 | shell:common startup |
| Settings > Apps > Startup | Registry + folder | Settings app | 5-20 | Settings |
| Task Manager startup tab | Mixed sources | Task Manager | 5-20 | Ctrl+Shift+Esc |
| Registry Run key | Registry | HKCU...\Run | variable | Regedit |
The numbers rarely match exactly because each location surfaces a different slice of the launch picture. A folder with two shortcuts can coexist with a Settings list of fifteen entries, and that gap is normal.
Edge cases: why the folder looks empty or disobedient
Several situations make the startup folder behave unexpectedly, and each has a mechanical cause.
The folder appears empty. You may be viewing a different account's profile, or the shortcut may have been migrated to the registry. Check both shell:startup and shell:common startup before assuming nothing loads.
An entry does not run. Windows 11 can silently delay or skip startup items when a setting disables them, when the app was uninstalled but left a dead shortcut, or when the path in the shortcut points to a moved executable. A broken shortcut looks present but fires nothing.
The item runs but closes. Shortcuts to installers, updaters, or command prompts often exit immediately after finishing, which looks like a failure but is normal behavior for one-shot programs.
Your startup item is blocked or flagged. Windows may require elevation for some apps, and a non-elevated shortcut cannot launch an elevated process cleanly, so the app may fail silently or prompt repeatedly.
Red-flag warnings worth respecting:
Startup folders are not sandboxes. Anything placed there runs with your account's permissions, so only add shortcuts you wrote or trust. The all-users folder affects every account, and an entry there can slow or disrupt a shared machine for people who never installed the app. Editing the registry Run keys by hand can break sign-in if a value is malformed, so prefer the folder or Settings page. Do not move system components into the startup folder to "fix" them, because you will likely duplicate or corrupt their normal launch path. Clean uninstalls remove startup entries; deleting a shortcut without uninstalling leaves the program installed but silent, which can confuse future troubleshooting.
A counterintuitive detail: emptying both startup folders is not the most thorough cleanup. Much startup load now lives in the registry and in Task Scheduler, so a clean-looking folder can still hide a dozen launch points. The folder is the simplest layer to inspect, not the whole system.
Timeline: what happens between button press and desktop
Startup order explains why some programs appear before others during sign-in. The table below is qualitative, because exact timings vary by hardware and configuration.
| Stage | What occurs | Where the startup folder fits |
|---|---|---|
| Boot | Firmware and kernel load | Not involved; folders have not been read |
| Sign-in | Credentials accepted | Not yet; shell has not launched |
| Shell init | Explorer starts and builds the user session | Folder enumeration begins |
| Launch phase | Registered and folder items start | Folder shortcuts fire here |
| Settling | Apps draw windows and spawn background work | Delayed items may start last |
| Desktop ready | Shell reports idle | Everything listed has been invoked |
The practical takeaway from that sequence: startup folder items are invoked during the launch phase, after boot and sign-in, so the fix for slow sign-in is measured at sign-in, not at power-on. If boot feels slow but sign-in is fast, the startup folder is unlikely to be the bottleneck. If sign-in drags, the folder and the Settings list are the first places to audit.
Misconceptions: the folder is not a boot trigger or a vaccine
Several widely repeated claims do not survive contact with how Windows works.
Claim one: the startup folder launches programs at boot. It does not; it fires at sign-in, and the distinction matters for shared machines and remote access.
Claim two: removing a folder shortcut uninstalls the app. It only removes the launch point, leaving the program installed and runnable manually.
Claim three: the Settings startup toggle is the same list. The Settings page aggregates folder shortcuts and registry entries, so toggling there may affect items that never appear in the folder.
Claim four: the folder is a security sandbox. It is not. Everything in it runs with your privileges.
Claim five: emptying the folder speeds up boot. It can speed sign-in, but boot time is governed by firmware, drivers, and services, not the startup folder.
The professional caveat: some applications re-add their shortcut after you delete it, often during an update or first-run setup. If an entry returns, check the app's own preferences for a supported "launch at sign-in" switch and turn it off there, rather than fighting a losing battle against a self-repairing shortcut. That behavior is a feature of the app, not a Windows bug, and treating it as a bug wastes hours.
Practical actions: inspect, audit, and trim in order
Work from the least invasive layer outward. Each step is reversible, and none requires third-party tools.
First, open the per-user folder. Press Win+R, type shell:startup, press Enter, and note what appears. Do the same with shell:common startup for the all-users scope.
Second, cross-check the Settings view. Open Settings > Apps > Startup and compare entries and status. Items present there but missing from both folders are almost certainly registry- or app-managed.
Third, decide per item. Disable from Settings first, since it is reversible and leaves the entry visible. Delete from the folder only when you are confident the shortcut is unwanted and the app does not need it to launch.
Fourth, for an app that keeps reappearing, open the app itself and look for a "start with Windows" or "launch at login" preference, then turn it off in the app.
Fifth, if sign-in is still slow after trimming, inspect Task Manager's startup tab and Task Scheduler for hidden launch points, since these cover what folders do not.
Threshold to act: if the Settings startup list has more than roughly ten enabled items, or if sign-in takes more than a few seconds beyond a clean baseline, trim the list before troubleshooting anything else. Fewer than five enabled items with a fast sign-in is a normal, healthy configuration.
Limitations: what this article cannot tell you
This explanation covers the built-in folder paths and behavior that have held stable across Windows 11 releases, which is why it favors mechanism over version-specific screenshots. It does not cover enterprise group-policy overrides, custom shell replacements, or third-party startup managers that inject their own entries, because those vary by environment and vendor.
It also cannot tell you which specific apps to remove, because that depends on what you installed and use. Estimate-based impact ratings are useful for ranking but are not a precise performance measurement, so treat them as a filter rather than a verdict. Start with what you recognize, disable what you do not need at sign-in, and verify the result on your own machine rather than assuming a fixed number of entries guarantees a faster start.