What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

If Windows 10 reaches the desktop but a program fails to open after you sign in, troubleshoot the sign-in startup entry—not Windows boot repair. First test the app manually, then check whether it is enabled, whether its launch path still works, and whether it relies on a task, service, or its own startup setting. An entry marked Enabled only confirms that Windows has a registration; it does not prove the app can launch successfully.

First identify what is failing

This guide is for programs that should open after a user signs in. If Windows itself will not boot or you cannot reach the sign-in screen, that is a different problem; Startup Repair is not the usual fix for an app that fails after you reach the desktop.

  • Only one app is missing: Test that app manually. Its installation, startup setting, path, dependency, or security permissions may be the issue.
  • Several or all apps are missing: Check the startup controls and folders, then investigate profile, policy, software conflicts, or Windows components.
  • The app opens but no window appears: Check the notification area, Task Manager’s Processes tab, other monitors or virtual desktops, and the app’s display preferences. Some apps run minimized or in the background.
  • The app starts late: It may be waiting for a network connection, service, cloud sign-in, or another dependency. Distinguish a delayed launch from one that never happens.

Also note whether the app should start before sign-in or after it. A normal Startup-folder shortcut launches in the signed-in user session; it is not a substitute for a service or a task configured to run under a different account.

Test the app and check its startup setting

  1. Open the app from the Start menu or its installed executable. If it errors, crashes, asks for an update, or closes immediately, repair that application before changing Windows startup settings.
  2. Check the app’s own preferences for options such as Start with Windows, Launch at login, or Run in the background. Some apps use their own setting instead of a conventional shortcut.
  3. Press Ctrl + Shift + Esc to open Task Manager. If needed, choose More details, then open Startup or Startup apps—the label varies by Windows 10 build.
  4. Select the app and choose Enable if it is disabled. Sign out and sign back in, or restart, to test.
  5. Alternatively, open Start > Settings > Apps > Startup and turn the app on, then sign out and sign in again.

If the app is enabled but still does not launch, continue below. If it is not listed, that does not prove it has no startup mechanism: it may use a Startup folder, registry Run entry, scheduled task, service, or an app-specific option. Microsoft documents the Settings, Task Manager, and Startup-folder controls in its Windows startup-app configuration guide.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Check or recreate the Startup-folder shortcut

Windows has a Startup folder for the current user and another for all users. Use the current-user folder unless the app should launch for every account and you have permission to configure the all-users folder.

Scope Run command Folder path
Current user shell:startup %USERPROFILE%AppDataRoamingMicrosoftWindowsStart MenuProgramsStartup
All users shell:common startup %ProgramData%MicrosoftWindowsStart MenuProgramsStartup
  1. Press Win + R, enter shell:appsfolder, and press Enter. This opens the applications view.
  2. Press Win + R again and enter shell:startup, or shell:common startup if the shortcut is meant for all users.
  3. Create a shortcut for the affected app and place it in the chosen Startup folder. Put a shortcut there—not a copied program executable—so the installed app remains intact and the shortcut can be removed independently.
  4. Sign out and sign back in to test. If the app requires special arguments, a particular working directory, or administrator elevation, follow the app vendor’s instructions rather than assuming a basic shortcut is sufficient.

These commands and folder paths are documented by Microsoft.

Repair the app or correct a broken launch path

A startup registration can outlive an app that has been removed, moved, or updated. If Windows reports that it cannot find the app, check whether the target executable exists and whether it is on a removable or network drive that is unavailable at sign-in. Microsoft lists a missing path, removable or network drive, and an uninstalled app among possible reasons for a “We couldn’t find this app” entry in its startup-app guidance.

  • Use the app’s built-in Repair or Reset option if Windows offers one, or update the app from its official source.
  • If its executable is missing or its installation is damaged, reinstall it from the vendor’s official site or another trusted official distribution channel.
  • Remove a stale shortcut or invalid entry only after confirming it belongs to the missing app. Do not download replacement executables from unofficial sites.
  • If it opens only when run as administrator, investigate the app’s permissions, installation, or vendor guidance. Making every startup app run elevated is not a general fix and can create security or compatibility problems.

Check other startup mechanisms

Some apps do not use the entry shown in Settings or Task Manager. Cloud clients, VPNs, hardware utilities, and launchers may depend on a scheduled task or Windows service. Microsoft describes startup commands as being stored in multiple locations, while its startup-command documentation covers that broader picture.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Task Scheduler

  1. Open Start, search for Task Scheduler, and open Task Scheduler Library.
  2. Look for a task whose trigger is At log on or At startup. Select it and inspect the Actions tab for the app’s executable path.
  3. Confirm the target still exists. If task history is enabled, review the History tab for a failure at the relevant sign-in time.
  4. Do not disable unfamiliar or Microsoft tasks simply because their names are unclear. If scheduled tasks generally fail, Microsoft’s troubleshooting guidance identifies the Task Scheduler operational log at Event Viewer > Applications and Services Logs > Microsoft > Windows > TaskScheduler > Operational: Task Scheduler service troubleshooting.

Application services

If the app depends on a background service, press Win + R, enter services.msc, and inspect only the service identified by the app vendor. Check its status and startup type; do not change Microsoft services indiscriminately. A stopped or disabled dependency may prevent the app’s interface from opening. For conflict testing, Microsoft recommends selectively disabling non-Microsoft services as part of a clean boot, not randomly altering core Windows settings.

Registry Run entries (advanced)

Applications can also register in these locations:

  • HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionRun for the current user.
  • HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionRun and HKEY_LOCAL_MACHINESoftwareWow6432NodeMicrosoftWindowsCurrentVersionRun for machine-level entries.

Only inspect these if simpler checks fail. Press Win + R, enter regedit, and export the relevant key before making any change. Check whether the value points to an existing executable; remove only an entry you have identified as obsolete or malicious. Do not delete unfamiliar values because their names look generic, and do not use registry-cleaner tools. Microsoft warns that incorrect Registry Editor changes can cause instability, app errors, or prevent Windows from starting: System Configuration tools and registry guidance.

Use a clean boot to find a software conflict

A clean boot starts Windows with essential drivers and a reduced set of startup programs and non-Microsoft services. It is a diagnostic test, not a permanent configuration, and differs from Safe Mode. Save your work first; some functionality may be temporarily unavailable. Microsoft provides the Windows 10 steps in its clean-boot guide.

  1. Sign in as an administrator and search for msconfig. Open System Configuration.
  2. On the Services tab, check Hide all Microsoft services, then select Disable all and Apply. Hiding Microsoft services first is important; do not disable them indiscriminately.
  3. Open the Startup tab and select Open Task Manager.
  4. In Task Manager, disable the enabled startup items, then close Task Manager.
  5. Select OK in System Configuration and restart the PC. Test the affected app.
  • It starts in a clean boot: A third-party service or startup item is likely interfering. Re-enable items in groups, restarting and testing until the conflict returns; then narrow down the item in that group.
  • It still fails: A conflict among disabled startup items is less likely. Return to the app, its task or service, the user profile, permissions, or Windows-file checks.

After testing, restore normal startup: open msconfig, use the General tab’s Normal startup option or Microsoft’s specified return-to-normal steps, re-enable the startup items and services you disabled, and restart. On current Windows 10 layouts, System Configuration’s Startup tab sends users to Task Manager; Microsoft describes the tool’s diagnostic role in its System Configuration guidance.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Repair Windows components with DISM and SFC

Use these built-in repair tools if several Windows functions are malfunctioning, startup entries are disappearing, or the issue followed system-file corruption or an interrupted update. They repair Windows components; they do not repair a damaged third-party app installation.

  1. Open Command Prompt as administrator.
  2. Run DISM.exe /Online /Cleanup-image /Restorehealth and wait for it to complete.
  3. Then run sfc /scannow.
  4. Restart Windows and test the startup behavior again.

Microsoft recommends running DISM before SFC because DISM can provide files needed to repair corrupted Windows components. Interpret SFC’s result as follows:

  • No integrity violations: SFC did not find corrupted protected system files.
  • Corrupt files repaired: Restart and retest.
  • Corrupt files found but not repaired: Review Microsoft’s repair guidance and CBS log details.
  • The scan cannot run: Retry in Safe Mode or address pending servicing issues.

Microsoft documents the sequence, result messages, and log guidance here: Use System File Checker to repair missing or corrupted system files. To extract SFC entries from the CBS log to a desktop file, run:

findstr /c:"[SR]" %windir%LogsCBSCBS.log >"%userprofile%Desktopsfcdetails.txt"

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Check security controls and compare another profile

Security software, application allowlists, account restrictions, and organization policies can block a program at sign-in. Check the security product’s detection or quarantine history. Restore a file only after confirming it is legitimate; add an exception only when the vendor or your security administrator supports it. Do not turn off antivirus permanently. On a work-managed device, contact IT; policy may also restrict System Configuration changes.

If the app works for a different Windows user, the problem is more likely tied to the original profile’s Startup folder, registry hive, permissions, or configuration than to the app itself. Testing another account is diagnostic, not a quick repair: moving to it can require transferring files, settings, credentials, and licenses.

When to stop changing Windows settings

If the app still fails manually or its installer reports errors, use the vendor’s repair or support guidance rather than continuing to add startup entries. If manual launch works but every startup mechanism fails, check relevant Event Viewer entries and account or organization policy before considering a Windows repair installation; back up important files before any major repair. Startup Repair is intended for serious boot problems, not a program that fails after you can sign in.

Quick Recap

Bestseller No. 1

Use this order to keep diagnosis focused:

  1. Confirm the app opens manually and check its own startup preference.
  2. Enable its entry in Task Manager or Settings, then test after sign-in.
  3. Verify or recreate the correct Startup-folder shortcut and confirm its target exists.
  4. Check a related scheduled task or service when the app uses one.
  5. Use a clean boot to test for a third-party conflict, then restore normal startup.
  6. Run DISM followed by SFC if Windows components may be damaged.
  7. Check security controls and compare another user profile if needed.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.