The Startup folder opens from Run with shell:startup, or through the hidden AppData path in File Explorer.
If you want a program to launch each time you sign in, the Startup folder is still one of the neatest ways to set it up on Windows. Many people miss it because the folder lives inside hidden system paths, so it feels like it vanished. It did not. Windows 11 and Windows 10 still include it.
This page lays out the fastest route, the full folder paths, the all-users folder, and the checks to run when an app refuses to open at sign-in. You will also see when the Startup folder is the right pick, and when Windows Startup Apps or Task Scheduler does a better job.
How To Access Startup Folder On Windows 11 And 10
Open Your Personal Startup Folder With Run
This is the route most people want. Press Windows + R, type shell:startup, then press Enter. Windows opens the Startup folder tied to your account, so anything you place there runs when you sign in.
The same folder also sits at this path:
%AppData%\Microsoft\Windows\Start Menu\Programs\Startup
If you paste that path into File Explorer, you land in the same place. That is handy when the Run box is disabled or you want to pin the folder for later.
Open The Startup Folder For Every User
Windows also keeps a second Startup folder for all accounts on the PC. Press Windows + R, type shell:common startup, then press Enter. Items in that folder run for every user who signs in on that machine.
The matching path is:
%ProgramData%\Microsoft\Windows\Start Menu\Programs\Startup
This folder is handy on a shared family PC or a work machine with more than one local user. On a personal laptop, the current-user folder is usually the cleaner pick.
Browse The Folder Manually In File Explorer
If you like seeing the full path, open File Explorer and paste the path straight into the address bar. That skips the hidden-folder hunt through AppData. You can also pin the folder to Quick Access once it is open, which saves a few clicks next time.
Why Windows Has Two Startup Folders
The split exists so Windows can keep personal startup items separate from machine-wide ones. Say you want OneDrive to start only for your account. Put its shortcut in shell:startup. Say you want a shared clipboard tool to open for anyone who signs in. Put it in shell:common startup.
Microsoft also points out that startup entries are not all handled the same way. Some apps appear in the Settings and Task Manager startup lists, while others are better handled through File Explorer and the Startup folder itself. That is spelled out on Microsoft’s startup applications page.
| Route Or Tool | What It Opens | Best Time To Use It |
|---|---|---|
shell:startup |
Startup folder for your account | You want an app to open only when you sign in |
shell:common startup |
Startup folder for all users | You want one shortcut to run for every account |
%AppData%\...\Startup |
The personal Startup path in File Explorer | You want to browse or pin the folder |
%ProgramData%\...\Startup |
The all-users Startup path in File Explorer | You want the machine-wide folder path |
shell:appsfolder |
A list of installed apps | You want to drag an app shortcut into Startup |
| Settings > Apps > Startup | Registered startup tasks | You want a quick on or off toggle |
| Task Manager > Startup Apps | Startup list with impact data | You want to trim slow logins |
Add Or Remove Apps From The Startup Folder
Opening the folder is only half the job. You also need the right thing inside it. In most cases, that means a shortcut, not a random copy of the full program folder. Shortcuts are easier to swap, rename, and delete.
Add A Program The Clean Way
- Press Windows + R, type shell:appsfolder, and press Enter.
- Press Windows + R again, type shell:startup, and press Enter.
- Drag the app from the first window into the Startup folder window.
- Sign out, then sign back in to test it.
That drag-and-drop route comes straight from Microsoft’s Windows startup instructions. If you are adding Word, Excel, Outlook, or another Office app, Microsoft’s Office autostart steps use the same shortcut idea.
Remove A Program
Open the Startup folder and delete the shortcut. That is all. You are not uninstalling the app. You are only removing the sign-in launch trigger. If you are unsure which shortcut belongs to which app, right-click it, open Properties, and read the target path before you delete anything.
What Belongs In The Startup Folder
The Startup folder works best with small daily apps: cloud sync tools, note apps, launchers, chat clients, clipboard managers, and scripts that do one clear task. It is not a great parking spot for heavy apps you open once in a while. Too many startup items slow the desktop down and make sign-in feel sticky.
Startup Folder Problems And Fixes
When the folder opens fine but the app never launches, the fault is usually with the shortcut, the app type, or a second startup rule buried somewhere else. Windows can launch apps from the Startup folder, from Startup Apps, from Run registry keys, and from scheduled tasks. That is why one app may still open even after you cleared the folder.
| Problem | What It Usually Means | What To Try |
|---|---|---|
| The app never opens | The shortcut target is broken | Open Properties and check the target path |
| The app opens for one account only | It sits in the personal Startup folder | Move the shortcut to shell:common startup |
| The app opens twice | It has more than one startup trigger | Check Startup Apps, Task Scheduler, and Startup folders |
| The app appears in Startup Apps but not in the folder | It is registered another way | Turn it off in Settings or Task Manager |
| The app asks for admin approval each time | Its launch rule needs elevated rights | Use Task Scheduler with proper rights |
| Sign-in feels slow | Too many items start together | Disable the ones you do not need at login |
Check The Shortcut Before You Blame Windows
Right-click the shortcut in the Startup folder and open Properties. The target should point to a real executable. If the app moved after an update, the shortcut may still point to an old path. That is common with apps installed from odd download packages.
Check Startup Apps And Scheduled Tasks
If you remove a shortcut and the app still opens at sign-in, the trigger is elsewhere. Open Settings > Apps > Startup or Task Manager > Startup Apps. Turn off anything you do not want. If the app still returns, open Task Scheduler and scan the Library for a logon task tied to that program.
Use A Stronger Inspection Tool When The List Gets Messy
When startup behavior feels tangled, Sysinternals Autoruns gives a wider view than the Startup folder alone. Microsoft says it can show items from startup folders, Run and RunOnce keys, services, shell extensions, and more. That makes it a solid choice when you need to track down a stubborn autostart entry.
Startup Folder Vs Startup Apps And Task Scheduler
The Startup folder is great when you want a visible, easy-to-edit startup rule. You can open it, drop in a shortcut, test it, and remove it in seconds. That is tough to beat for simple desktop programs.
Startup Apps in Settings or Task Manager is better when the app already registers itself with Windows. You get one-click enable and disable controls, plus startup impact data in Task Manager. Task Scheduler is the better pick when an app needs a delay, admin rights, or a launch tied to a trigger other than your sign-in.
- Pick Startup folder for plain shortcut-based startup.
- Pick Startup Apps when Windows already lists the app.
- Pick Task Scheduler when you need timing or elevated rights.
If all you needed was the path, this is the short version: use shell:startup for your account, shell:common startup for every account, and use shortcuts rather than loose files. That gets you to the folder fast and keeps startup items easy to control later.
References & Sources
- Microsoft.“Configure Startup Applications In Windows.”Lists Settings, Task Manager, shell:startup, shell:common startup, and both folder paths.
- Microsoft.“Automatically Start An Office Program When You Turn On Your Computer.”Shows the shortcut method for adding an app to the Startup folder.
- Sysinternals.“Autoruns v14.11.”Shows many autostart locations beyond the Startup folder.
