Built by IT engineers, made for IT teams.
Best PracticesNovember 4, 2026· 5 min read

Slow Windows Startup: Find and Clean Up Startup Programs

Windows takes forever to reach the desktop? Measure startup time, find all startup entries – even the hidden ones – and spot suspicious programs.

Nico Haslberger
Nico HaslbergerCEO & Co-Founder · November 4, 2026
Share
PC startet langsam: Autostart finden und aufräumen

Your PC isn't old. It just starts a pile of programs every morning that you never ordered.

“The device starts slowly, please check it.” After switching on, it takes minutes until the desktop is usable. The Start menu doesn't respond, programs open one after another on their own, the fan runs at full speed.

In the concrete case, a Windows 11 laptop at a tax advisor's office, the very first look at the startup items showed a long list: OneDrive setup twice, VPN client, Copilot, Edge, remote support, audio service – and an entry nobody could place. Here is how to measure the startup time, find all startup locations and recognize suspicious entries.

Why does my PC start so slowly?

In most cases, too many programs load at the same time at sign-in. Every program in startup wants disk, processor and network at the same moment. Other typical brakes:

  • Pending updates that are installed at startup
  • Almost full drive, especially with less than 10–15% free space
  • Conventional hard drive (HDD) instead of SSD – on older devices the biggest single factor
  • Drivers or services that wait for a timeout at startup
  • Network drives that are connected at sign-in but aren't reachable
Slow Windows Startup: Find and Clean Up Startup Programs – at a glance
Slow Windows Startup: Find and Clean Up Startup Programs – at a glance

Step 1: How long does startup really take?

Windows measures the startup time itself and writes it to the event log. That is better than a gut feeling – and later you can see whether your changes made a difference.

Get-WinEvent -LogName 'Microsoft-Windows-Diagnostics-Performance/Operational' -FilterXPath '*[System[EventID=100]]' -MaxEvents 5 |
  ForEach-Object { [pscustomobject]@{ Zeit = $_.TimeCreated; Startdauer_s = [math]::Round(([xml]$_.ToXml()).Event.EventData.Data[1].'#text' / 1000, 1) } }

The commands need a PowerShell with administrator rights. Rough guide: Under 30 seconds is good, 30–60 seconds is normal, and well over a minute is worth looking into.

In addition, Task Manager (Ctrl+Shift+Esc › Startup apps) shows the “Last BIOS time” at the top right – the time before Windows even loads. If that is already 20 seconds or more, the hardware or the BIOS setting is more likely the issue.

Step 2: Which programs start automatically?

Task Manager shows the visible startup programs along with their “Startup impact”. Under Startup apps, look at everything marked “High” and disable whatever isn't needed immediately after sign-in: right-click › Disable.

You get a more complete overview with PowerShell:

Get-CimInstance Win32_StartupCommand | Select-Object Name, Command, Location | Format-Table -AutoSize

In the real case, this list included:

  • OneDrive setup, twice – one entry is enough, the second is superfluous
  • VPN client – only needed if VPN is required right after startup
  • Copilot, Edge – usually unnecessary at startup
  • Remote support software – wanted by the IT service provider – leave active
  • Windows Security, audio service – system components – leave active
  • Script from C:\Temp with no recognizable vendor – suspicious – check, see step 4

Step 3: Where else do startup entries hide?

Task Manager doesn't show everything. Programs can register themselves in several places:

  • Registry, Run keys: HKCU\Software\Microsoft\Windows\CurrentVersion\Run (this user only) and HKLM\Software\Microsoft\Windows\CurrentVersion\Run (all users)
  • Startup folders: Windows+R › shell:startup (user) or shell:common startup (all)
  • Scheduled tasks with the trigger “At log on” or “At startup” (taskschd.msc)
  • Services with startup type “Automatic” (services.msc)

In the real case, that was exactly the trap: The entry in question was not in the startup folder but in the Run key in the registry. Only there could it be removed.

14 days free

IT support that fixes itself.

SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.

Start free trial

For a complete overview of all locations, Autoruns from the Microsoft Sysinternals tools is recommended. It shows every startup entry, flags missing signatures and can disable entries with one click.

Step 4: Is an unknown startup entry dangerous?

Not automatically – but some characteristics are clear warning signs. This is exactly the question the user asked in the real case after the entry had been removed.

  • Program under C:\Program Files with a known vendor name – usually harmless
  • Program from C:\Temp, %TEMP% or directly from %APPDATA% – suspicious
  • Script instead of a program (.bat, .cmd, .vbs, .ps1) – suspicious, look at the contents
  • No digital signature – suspicious
  • Name doesn't match any installed program – suspicious

Here is how to check an entry:

  1. Look at the file: Scripts can be opened in a text editor – don't run them by double-clicking.
  2. Check the signature: Right-click the file › Properties › Digital Signatures.
  3. Check with the antivirus scanner: Right-click › Scan with Microsoft Defender.
  4. When in doubt: Disable the entry instead of deleting it, don't touch the file, and inform IT.
Slow Windows Startup: Find and Clean Up Startup Programs – step by step
Slow Windows Startup: Find and Clean Up Startup Programs – step by step

Step 5: What else helps?

  • Finish updates: Settings › Windows Update – install everything, restart once.
  • Storage space: Keep at least 10–15% free.
  • Fast startup: If it is on, “Shut down” doesn't give a real restart – background in High CPU and RAM usage.
  • Network drives: Disconnect unreachable drives or connect them only when needed.
  • Hardware: Older devices with an HDD benefit more from an SSD than from any optimization.
Example view in SuperSupport – Slow Windows Startup: Find and Clean Up Startup Programs
Example view in SuperSupport – Slow Windows Startup: Find and Clean Up Startup Programs

How does SuperSupport help when the PC starts slowly?

In the case described, the SuperSupport agent read out all startup entries, searched the system logs for startup errors and suggested a selection of which entries could be disabled. The user deliberately chose only the unknown entry. After confirmation, the agent first looked for it in the startup folder, then found it in the Run key, removed it and verified the result. What this looks like for internal IT teams and MSPs is described on their respective pages.

Frequently asked questions

Why does my PC start so slowly?

Usually too many programs load at sign-in, plus pending updates, an almost full drive, an old HDD instead of an SSD, or a driver that hangs at startup.

Where do I find all startup programs in Windows?

In Task Manager under “Startup apps” and in Settings under Apps › Startup. These lists aren't complete, though: more entries are in the registry (Run keys), in the startup folders, in scheduled tasks and in services.

How do I measure how long Windows takes to start?

Windows logs the startup duration in the event log “Microsoft-Windows-Diagnostics-Performance/Operational” as event 100. Task Manager also shows the last BIOS time under “Startup apps”.

How do I recognize a suspicious startup entry?

Warning signs are programs from temp folders or directly from AppData, scripts (.bat, .cmd, .vbs, .ps1), a missing digital signature, and names that can't be matched to any known program.

Can I disable startup entries safely?

Disabling yes, deleting only with care. Disabled entries can be turned back on at any time. Security software, driver services and VPN clients should stay active.

14 days free

IT support that fixes itself.

SuperSupport fixes IT problems right on the device, before they turn into tickets. Try it free for 14 days.

Start free trial
Nico Haslberger

Nico Haslberger is Co-Founder & CEO of SuperSupport.ai. With years of experience as an IT technician, he knows the problems in IT support first-hand: from overloaded help desks to recurring tickets that slow teams down. That knowledge is built into every feature of the platform today. He makes sure SuperSupport.ai solves exactly the problems he experienced himself for years.

Share

This article was created with AI assistance and editorially reviewed.

Related Articles