A Windows-style dashboard highlights Spotify settings, including its app toggle, shortcut, device connection, and scheduled launch.
Your startup apps tab says "Disabled," yet Spotify, a VPN client or the Xbox app pops up in the system tray anyway. Windows isn't broken. Task Manager is only one of several places an app can arrange to start itself.

XDA Developers writer Tanveer Singh described this problem in a recent piece. In his case, apps he had disabled in Task Manager kept showing up after sign-in. His fixes were to check each app's own settings, inspect the Startup folder, and look for helper processes and scheduled tasks. Below are those fixes, checked against Microsoft's documentation and corrected where the original was imprecise.

A Windows-style dashboard highlights Spotify settings, including its app toggle, shortcut, device connection, and scheduled launch. What the Startup apps list actually controls​

How-To Geek makes the same point: Task Manager's Startup apps tab disables only one startup trigger. Microsoft's own documentation agrees. Helper processes and launchers can override your preferences.

Microsoft's support page says that the available controls depend on how an app is installed and registered. In practice, apps registered with Windows as startup apps appear in both Settings > Apps > Startup and Task Manager's Startup apps tab. Microsoft describes these as the same list, and Task Manager adds detail such as startup impact. So the useful split isn't Settings versus Task Manager. It is registered startup entries versus everything else.

Microsoft's developer documentation lists what Windows treats as "startup apps":

  • Run registry keys, including the HKLM, HKCU and Wow6432Node variants
  • RunOnce registry keys
  • Startup folders, both per-user and public

Scheduled tasks, services and in-app launch logic fall outside that list. That gap is where disabled apps tend to come back from.

A conservative troubleshooting order​

This sequence is a practical synthesis, not a Microsoft-prescribed flow. It runs from the lowest-risk check to the highest.

  1. Confirm the baseline. Open Settings > Apps > Startup, or right-click Start, open Task Manager and pick Startup apps. Make sure the app really shows as Off or Disabled.
  2. Check the app's own settings. Open the app and look for wording such as "launch at startup," "open on login" or "start with Windows." Singh found this option enabled in Spotify, Surfshark and Xbox. He also suspects an update flipped it back on. That is his personal account, and I couldn't confirm it for those specific apps. It does fit a wider pattern: one how-to guide notes that some apps re-enable their startup entry during updates. Treat that as a plausible cause, not a documented rule.
  3. Inspect the Startup folders. Press Win+R, type shell:startup and press Enter. For entries that affect every user on the PC, also try shell:common startup.
  4. Look for a helper or scheduled task. Do this only if the app still appears after steps 1 to 3.
  5. Treat the registry and Autoruns as advanced follow-up. They are not first-line fixes.

The Startup folder: a path correction​

Singh's article gives the Startup folder location as %AppData%\Microsoft\Windows\Start Menu\Programs. That leaves off the last folder. Microsoft documents two locations:

  • shell:startup is for the current user. It resolves to %userprofile%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup.
  • shell:common startup is for all users of the device. It resolves to %ProgramData%\Microsoft\Windows\Start Menu\Programs\Startup.

Typing the shell: commands avoids the path problem altogether. Microsoft says that to remove an app from this mechanism, you delete its shortcut from the folder. That removes the launch entry only. It does not uninstall the program, and you can still open the app by hand.

Scheduled tasks and helper processes​

Many apps install an updater or "cloud handshake" component. These can run on a schedule or at logon and may start the main app as a side effect. To check, open Task Scheduler and select Task Scheduler Library in the left sidebar. Look for tasks whose name, publisher or action clearly points to the unwanted app.

Be careful here. Windows runs many of its own maintenance, update and backup jobs from the same library, so only disable a task you can confidently tie to a third-party app. If you can't identify it, leave it alone or ask the software maker. Microsoft documents that scheduled tasks can be disabled through PowerShell's Disable-ScheduledTask cmdlet. That confirms the action is supported. It does not confirm that any particular task is safe to turn off.

Disabling a task is also reversible, which makes it a gentler step than deleting it. If the app breaks or stops updating, you can re-enable the task.

When to bring in Autoruns or the registry​

Microsoft's Sysinternals Autoruns covers far more auto-start locations than Task Manager does, including logon entries, scheduled tasks and services. It suits readers who can't find the trigger by hand. Autoruns' check marks don't always match Task Manager's state. A Microsoft Q&A answer explains that an Autoruns check mark reflects the underlying autostart entry, not the Enabled or Disabled state Task Manager maintains. A ticked item in Autoruns therefore doesn't prove the app will run. The same answer advises that if the process does run while Task Manager shows it disabled, you should look at Autoruns' Scheduled Tasks, Services and other tabs for an additional launch mechanism.

Microsoft also lists the registry Run keys that can start programs at sign-in:

  • HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Run
  • HKLM\Software\Microsoft\Windows\CurrentVersion\Run
  • HKCU\Software\Microsoft\Windows\CurrentVersion\Run

Microsoft cautions that registry changes can have unintended consequences and recommends backing up the registry first. For most people, the earlier steps are enough.

Caveats worth keeping in mind​

  • A process in Task Manager isn't necessarily a launched app. A background component can run without opening a window, and that doesn't make it harmful.
  • One writer's experience isn't a universal diagnosis. Your cause could be any of the mechanisms above. Identify the actual entry before you change settings.
  • Startup impact labels are only a guide. Microsoft bases them on CPU and disk use at startup. For example, Low means under 300 ms of CPU and under 292 KB of disk. They don't tell you whether an app is safe to disable.
  • Re-check occasionally. New installs and updates can add new entries. Revisit the Startup list, folders and task library when your system tray starts to fill up.

Bottom line​

Disabling an app in Task Manager turns off one startup entry and nothing more. If the app still launches, work through four places in order: the app's own setting, shell:startup and shell:common startup, any identifiable helper or scheduled task, and finally Autoruns or the registry. Change only what you can identify. A disabled startup app that still launches is almost always being started by something else on that list.

 

References

  1. My Windows PC keeps launching apps I already disabled, and I finally found the reason why XDA 2026-11-20T18:30:22+00:00
  2. 4 reasons your disabled apps still launch when Windows boots up howtogeek.com
  3. Startup apps - Win32 apps | Microsoft Learn learn.microsoft.com