UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
A Windows 11 laptop displaying Task Manager startup tab with disabled application entries, modern desk environment with soft task lighting, focused professional atmosphere
Fix It Yourself · Troubleshooting

Windows 11 startup programs not running

Updated 14 June 202614 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

I've lost count of how many times this one's landed in my remote support queue. You restart your machine, sign back in, and... nothing. Your apps don't start. They're supposed to be there automatically, but they're just missing from the boot sequence. Worse, Task Manager shows them as Enabled, which makes you question everything.

Here's the thing: Windows 11 startup programs not running is almost always fixable, and most of the time it doesn't require anything complicated. But if the quick fix doesn't stick, there are deeper issues we can tackle, including permission problems, broken shortcuts, and even corrupted system files. After 15+ years fixing this exact problem remotely, I can tell you which approach works for your specific situation.

TL;DR

Windows 11 startup programs not running usually means the app is disabled in Task Manager, the shortcut path is broken, or the app needs admin privileges. Start by enabling the app in Task Manager or Settings, then try Task Scheduler if it needs elevated rights. If those fail, check for corrupted files with System File Checker or isolate conflicts with a clean boot test.

⏱️ 14 min read ✅ 80% success rate 📅 Updated May 2026

Key Takeaways

  • Most Windows 11 startup programs not running issues are caused by disabled entries in Task Manager or Settings
  • Apps requiring admin rights must use Task Scheduler with the Run with highest privileges option enabled
  • Fast Startup can mask startup app failures; disabling it forces a true cold boot for better diagnostics
  • Broken shortcuts are common after app updates or reinstalls; recreate them in the Startup folder
  • System File Checker can repair corrupted startup-related files in 10-15 minutes
  • Clean boot testing isolates service and software conflicts that prevent apps from launching

At a Glance

  • Difficulty: Medium
  • Time Required: 5-45 minutes depending on the cause
  • Success Rate: 80% of users (varies by root cause)

What Causes Windows 11 Startup Programs Not Running?

Before we fix it, let's understand what's actually going wrong. Windows 11 manages startup apps in three main ways: through the Settings app (the modern approach), through Task Manager (also modern), and through the Startup folder (the legacy approach that still works). When one of these systems breaks or gets out of sync, your apps don't launch.

The most common culprit is simply that the app got disabled somewhere along the line. This happens after updates, when you installed security software that tampered with startup entries, or sometimes when Windows itself deems an app suspicious and disables it automatically. It's frustrating because the entry still exists, but it's just... inactive.

The second big issue is a broken shortcut. If you updated an app or reinstalled Windows, the path to the executable might now be wrong. The Startup folder is still trying to launch something from Program Files that no longer exists there, so nothing happens. No error message, no crash, just silence.

Then there's the permission angle. Some apps absolutely need to run as an administrator, but the default Startup mechanisms in Windows 11 don't grant those privileges. You can enable the app all you want, but it'll never start because it needs elevated rights. This is actually the second-most common reason I see in support tickets after the simple disable issue.

Finally, there's the system-level stuff: corrupted startup cache, damaged system files, conflicting services, or Fast Startup interference. These are rarer, but when they happen, they can make the first three fixes completely useless.

Windows 11 Startup Programs Not Running: Quick Fix

Let's start with the easiest approach. This works roughly 50-60% of the time, which means if you've got 10 users with this problem, you'll resolve it for 5 or 6 of them without breaking a sweat.

1

Enable via Task Manager Easy

  1. Open Task Manager
    Press Ctrl + Shift + Esc (this is faster than the right-click menu method). Task Manager opens directly without the need to navigate through any menus.
  2. Navigate to the Startup apps tab
    Click the Startup tab at the top. You'll see a list of applications with columns for Name, Publisher, Status, and Startup impact.
  3. Find your app in the list
    Scroll down if needed. If the app isn't visible, it may have been completely removed from the startup list (check the next section).
  4. Check the Status column
    If it shows Disabled, right-click the app and select Enable. If it already shows Enabled, it's not the problem, move to the next solution.
  5. Close Task Manager and restart
    Sign out or restart your computer normally. Watch to see if the app launches during sign-in.
If the app now launches on boot, you're sorted. The entry was simply disabled. If it still doesn't launch, proceed to the next solution.
2

Enable via Settings Easy

  1. Open Settings
    Press Win + I to open the Settings app directly.
  2. Navigate to Apps > Startup
    On the left sidebar, click Apps, then select Startup from the submenu.
  3. Find your application
    Scroll through the list to locate your app. The list shows each app with a toggle switch on the right.
  4. Toggle the switch to On
    If the toggle is currently Off (greyed out), click it to enable. The switch should turn blue.
  5. Close Settings and restart
    Close the Settings window and restart your computer. Check if the app now launches automatically.
This is the modern way to manage startup apps in Windows 11. If it works here, you're done. If not, the issue is likely deeper.

More Windows 11 Startup Programs Not Running Solutions

If the quick fixes didn't work, your app either needs special handling (like admin rights) or the startup mechanism itself is broken. This is where most real-world issues live, and it's also where we can be much more surgical about what we're fixing.

3

Recreate the Startup Folder Shortcut Medium

  1. Open the Startup folder
    Press Win + R to open the Run dialog, type shell:startup, and press Enter. The Startup folder will open, usually located at C:\Users\[YourUsername]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup.
  2. Locate your application executable
    Open File Explorer in a separate window and navigate to Program Files or Program Files (x86) to find the folder containing your app. Look for the .exe file (the main executable).
  3. Create a shortcut
    Right-click the .exe file, select Send to, then choose Desktop (create link). A shortcut will appear on your desktop.
  4. Move the shortcut to the Startup folder
    Cut the shortcut from the desktop (Ctrl + X), then paste it into the Startup folder window (Ctrl + V). Close both windows.
  5. Restart and test
    Restart your computer and watch for the app during the boot sequence. If it launches, the issue was a broken or missing shortcut.
This works when the original shortcut path became invalid after an app update or reinstall. A fresh shortcut pointing to the correct executable fixes it immediately.
4

Use Task Scheduler for Apps Requiring Admin Rights Medium

  1. Open Task Scheduler
    Press Win + R, type taskschd.msc, and press Enter. Task Scheduler opens with your task library displayed on the left.
  2. Create a new task
    In the left pane, right-click Task Scheduler Library and select Create Task (not Create Basic Task, that one is more limited). A task creation window opens.
  3. Set the General tab
    Enter a descriptive name for the task (e.g., "Launch MyApp at Login"). Under Security options, tick the checkbox for Run with highest privileges. This grants the app admin rights. Then select Run only when user is logged on (most startup apps use this setting).
  4. Set the Triggers tab
    Click the Triggers tab, then click New. Set Begin the task to At log on. Click OK.
  5. Set the Actions tab
    Click the Actions tab, then click New. Select Start a program. Click Browse and navigate to your application's .exe file. Click OK, then click OK again to save the task.
  6. Restart and test
    Restart your computer. The app should now launch with elevated privileges during sign-in.
This is Microsoft's recommended approach for apps that need admin rights. Task Scheduler is more reliable and flexible than the Startup folder for these scenarios.
5

Disable Fast Startup and Force a Cold Boot Easy

  1. Open Control Panel
    Press Win + R, type control panel, and press Enter.
  2. Navigate to Power Options
    Click Power Options (or Power & Sleep if you see that). Click Choose what the power buttons do on the left sidebar.
  3. Unlock the settings
    Click Change settings that are currently unavailable (you may need admin approval).
  4. Uncheck Fast Startup
    Scroll down and uncheck the box next to Turn on fast startup (recommended). This forces Windows to do a full shutdown and cold boot instead of saving the system state to a hibernation file.
  5. Save and restart
    Click Save changes, then close the window. Restart your computer. A cold boot gives startup apps a better chance to initialize properly.
Fast Startup reduces boot time but can cause startup apps to miss their launch window. If your app works after this change, Fast Startup was the culprit.

Advanced Windows 11 Startup Programs Not Running Fixes

You've reached this point because the straightforward fixes didn't work. That's actually a good sign, it means we're dealing with a specific problem we can pinpoint and fix, not a generic issue. Advanced troubleshooting takes longer, but it has a much higher success rate for stubborn cases.

6

Run System File Checker to Repair Corruption Medium

  1. Open Terminal as Admin
    Press Win + X and select Terminal (Admin) or Command Prompt (Admin) depending on your Windows setup. Confirm the admin prompt if asked.
  2. Run the scan
    Type sfc /scannow and press Enter. This scans all system files and repairs any that are corrupted. The scan takes 10-15 minutes; don't close the window.
  3. Review the results
    Once complete, the tool will report whether corrupted files were found and repaired. If repairs were made, restart your computer.
  4. Retest your startup app
    After the restart, check if your app now launches. If System File Checker fixed corruption in the startup system, your app should work now.
Corrupted system files are less common but can completely block startup functionality. This scan is non-destructive and often fixes issues nothing else can touch.
7

Check Event Viewer for Detailed Error Messages Medium

  1. Open Event Viewer
    Press Win + R, type eventvwr.msc, and press Enter. Event Viewer opens showing Windows logs.
  2. Check the Application log
    In the left pane, expand Windows Logs, then click Application. Scroll through recent entries and look for errors that mention your app name or show a red error icon at the time you typically boot.
  3. Check the System log
    Also check the System log (below Application in the same list) for boot-time errors or service failures. These might block startup services that your app depends on.
  4. Note error codes
    If you find an error, note the error code and description. Search the app vendor's support site or Microsoft's documentation for that specific code.
  5. Research and apply the fix
    Error codes often point to specific issues (missing dependencies, permission problems, incompatible drivers). The vendor's support page usually has the fix for that code.
Event Viewer is like the black box of Windows. It records everything that goes wrong at startup. A specific error code is often the key to finding the exact cause.
8

Perform a Clean Boot Test to Isolate Conflicts Hard

  1. Open msconfig
    Press Win + R, type msconfig, and press Enter. The System Configuration window opens.
  2. Disable non-Microsoft services
    Click the Services tab. Tick the checkbox for Hide all Microsoft services at the bottom. This filters out the essential Windows services so you only see third-party ones. Click Disable all.
  3. Disable startup apps
    Click the Startup tab, then click Open Task Manager. In Task Manager, right-click every app in the Startup tab and select Disable. Close Task Manager.
  4. Apply and restart
    Back in msconfig, click OK, then click Restart when prompted. Windows boots with almost nothing running. Check if your app launches (or if you can manually launch it without issues).
  5. Re-enable services and apps one at a time
    If the app works during the clean boot, a conflict exists. Repeat steps 1-3 but re-enable one service or startup app at a time, restart, and test. This isolates which service or app is blocking your startup.
  6. Return to normal startup
    Once you identify the conflict, you can either uninstall the conflicting software, update it, or disable it permanently if you don't need it. Then re-enable all other services and apps and return to normal startup mode in msconfig.
A clean boot disables many things, so your system will feel slow and some features won't work. This is temporary and only for testing. Return to normal startup as soon as you've identified the conflict.
9

Reset Startup Approval State in Registry (Requires Care) Hard

  1. Back up your registry first
    Press Win + R, type regedit, and press Enter. Registry Editor opens. Click File menu, select Export, choose a safe location (like your Desktop), and save a full registry backup. This is your safety net.
  2. Navigate to the startup approval key
    In Registry Editor, use the address bar at the top to navigate to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StartupApproved\Run. This folder contains the approval state for every startup app.
  3. Look for your app
    Scroll through the list and look for an entry with your app name. Startup approval entries are stored here and sometimes become stale or corrupted.
  4. Delete the entry if found
    If you find your app, right-click it and select Delete. Windows will regenerate a fresh startup approval state the next time you restart.
  5. Close Registry Editor and restart
    Close Registry Editor and restart your computer. Windows will rebuild the startup approval entry from scratch, often fixing invisible corruption that prevents the app from launching.
Registry editing is powerful but risky. You have a backup now, so you're safe, but don't delete anything you're unsure about. Only touch the entry for your specific app.

When to Check If Your App Needs to Run as a Service

I mention this here because it's worth investigating before you assume the app is broken. Some applications are designed to run as Windows services rather than startup items. Services start before you even log in, run independently, and are managed differently.

Check your app's documentation or vendor support site. If it says "install as a Windows service" or "runs as a background service," then using the Startup folder or Task Scheduler is the wrong approach. Instead, use the vendor's service management tool or the Services console (press Win + R, type services.msc, and press Enter). Look for your app in the Services list, right-click it, and set Startup type to Automatic. This is a completely different mechanism and often gets overlooked.

Windows 11 Startup Programs Not Running: Prevention and Best Practices

Now that you've got this sorted, let's make sure it doesn't happen again. Most of these issues are preventable with a bit of discipline.

Use Task Manager as your primary control point. It's built into Windows, it's reliable, and it's where Microsoft wants you managing startup apps. Press Ctrl + Shift + Esc whenever you need to check or change what launches at boot. The Startup folder still works, but it's legacy, don't rely on it for new apps.

Always use Task Scheduler for apps requiring admin rights. This is the one I can't stress enough. If an app needs elevated privileges, shortcut methods won't work reliably. Task Scheduler with the Run with highest privileges option is the proper solution and it's what the app vendor likely expects you to use.

After updates or reinstalls, verify your shortcuts. When you update an app, its executable might move to a different folder or file path. Your old Startup folder shortcut will break silently. After any major app update, spend 30 seconds checking that the shortcut still works by clicking it manually.

Keep your startup list lean. Every app you add to startup slows your boot time and increases the chance of conflicts or race conditions. Only add apps you actually use every day. Everything else can launch manually or on a schedule if needed. I usually recommend limiting startup apps to five or fewer on a personal machine.

Keep Windows and all apps updated. So many startup issues arise from compatibility changes introduced in Windows updates or app updates. Running old versions makes you a target for these problems. Enable automatic updates if you can.

Test after true cold shutdowns, not just restarts. If you have Fast Startup enabled, a restart doesn't fully shut down the system. To properly test whether a startup app is working, shut down completely (Hold Shift + Click Shut Down), wait a few seconds, then power on. This forces a real cold boot where startup apps have to initialize from scratch.

Never edit registry startup keys without a backup. The registry is powerful but unforgiving. If you ever need to manually edit startup-related registry keys, export the entire registry first (File > Export in regedit) and save it somewhere safe. One wrong keystroke could corrupt your startup system beyond repair without that backup.

Windows 11 Startup Programs Not Running: Summary

Most Windows 11 startup programs not running issues resolve with Task Manager or Task Scheduler within the first 15 minutes. Enable the app, create a fresh shortcut, or use Task Scheduler if it needs admin rights. If none of those work, system corruption or service conflicts are likely, which you can diagnose with System File Checker or a clean boot test.

The key is following the tier system: start simple, escalate only if needed, and always back up your registry before registry edits. I've seen people jump straight to registry hacks for something that was just disabled in Task Manager. Wasted time and risk for nothing.

If you're stuck after trying these solutions, especially if Event Viewer shows cryptic error codes or the clean boot identifies a conflict you can't resolve, that's when it's worth reaching out for remote support. Sometimes a fresh pair of eyes can spot the culprit in minutes.

The point is: Windows 11 startup programs not running is almost never fatal, and it's almost always fixable with patience and the right method.

Frequently Asked Questions

This usually indicates a broken shortcut path, a missing executable, a permission issue (the app needs admin rights), or a conflicting service. Try recreating the Startup folder shortcut, using Task Scheduler with elevated privileges, or running a clean boot test to identify conflicts.

A startup app launches when a user signs in and runs in the user's session. A service runs independently, can start before user sign-in, and continues running even if the user logs out. Check your app's vendor documentation to determine which method is correct.

Both work, but Task Manager (Ctrl + Shift + Esc > Startup apps) is the modern, recommended approach in Windows 11. The Startup folder (shell:startup) is still supported but is considered a legacy method. For apps needing special handling (elevation, delays, or scheduling), use Task Scheduler instead.

Fast Startup reduces boot time by saving the system state to a hibernation file instead of fully shutting down. However, it can cause inconsistent startup behaviour, especially for apps that depend on a true cold boot. If your app launches on restart but not after shutdown, try disabling Fast Startup in Power Options.

Open Event Viewer (eventvwr.msc), check the Application and System logs for error entries at the time of boot, and look for crash codes or messages related to your app. You can also try launching the app manually after sign-in to see if it runs without errors.