How to Reduce Startup Time in Windows 11

A slow startup needs a location and a repeatable observation before it needs a tweak. This guide helps you separate the wait before sign-in from the wait for a usable desktop, then choose one relevant investigation.

Already know which app you want to stop? Go straight to disabling a startup app. If an app is missing from that list, use Startup folders and Autoruns.

Measure the right part of “startup”

Where the wait occurs	Useful observation	Next direction
At the manufacturer logo, before Windows sign-in	Record the logo or message and connected peripherals.	Check the exact PC model’s support guidance; do not assume sign-in apps are responsible.
Windows reaches sign-in, but desktop apps remain unresponsive	Note which app or action is delayed and whether it settles.	Compare one known optional startup app, or investigate sustained resource use.
Only while an update is finishing	Record the update message and whether the next ordinary restart is also slow.	Complete the update before treating that one run as a baseline.
A boot error, repeated recovery screen or failure to sign in	Record the exact error.	This is a recovery problem, not a startup-app optimisation exercise.

Use a simple endpoint: for example, “after signing in, Start opens and I can open my usual local document.” Keep the document and action the same in later comparisons. If your endpoint is a web page, network and server delays may contaminate what you think you are measuring.

Build a useful before-and-after record

Save work and use Restart for each comparison. Keep power source, peripherals and sign-in method consistent.
Record three ordinary runs before changing anything. Separate the wait to sign-in from the wait after sign-in; exclude time you spend waiting before entering a PIN.
Make one reversible change, then record three comparable runs. Retain the range rather than reporting only the quickest run.

Record	What to write down
Baseline	Restart method; approximate wait to sign-in; wait from sign-in to the chosen usable-desktop endpoint.
Change	One app or setting, its original value and how to restore it.
After	The same observations after the change, plus update, sync or other unusual activity.
Decision	Keep, reverse or investigate further. Record lost functionality as well as any shorter wait.

If your before and after ranges overlap, the observations do not clearly establish an improvement. Avoid claiming that a one-second difference proves a fix. If the delay moves or disappears on its own, record that uncertainty before stacking more changes.

Start with Task Manager

After sign-in, observe Task Manager while the delay is happening. A busy CPU or disk is a clue to investigate the named workload, not permission to end an unfamiliar process. If disk activity remains high, continue with the sustained disk-usage guide.

Disable apps, not everything

If the wait is after sign-in and a recognised optional app is involved, use the startup-app guide for the setting and its undo procedure. Bring the result back to your comparison record. Stop if the improvement meets your goal; a smaller list is not a goal by itself.

Use Settings for the same list

The screenshot below helps identify the normal Startup controls. It is a vendor example, not a recommended set of switches for your PC.

Apps > Startup provides individual switches and startup-impact labels. Leave sync, security and unfamiliar system tools enabled unless you understand their purpose. Screenshot: ASUS Support. Older Windows 11 example; the app list and numbering are vendor examples.

Check startup folders

If the unwanted app is not represented in the list, continue with finding its launch source. Keep that investigation separate from storage or firmware changes so you can tell which action affected the symptom.

Update Windows and drivers

Record whether the slowdown began immediately after a known update. Note the Windows build, app version or driver involved before doing anything else. A timing match is a lead, not proof. Use the driver-update decision guide when a specific driver problem is implicated; do not install every optional update as an experiment.

Check free storage

Record the free space on the Windows drive alongside the timing notes. If it is nearly full, address that condition with deliberate file management and backups before comparing performance. Do not delete unidentified system folders to chase a faster startup.

Do not use msconfig to disable Microsoft services for routine speed-ups

Check whether Fast Startup is relevant

Microsoft distinguishes a Fast Startup shutdown/power-on cycle from a full restart. Do not mix those methods in one comparison or attribute their difference to the app you changed. There is no need to toggle Fast Startup just to perform the Restart-based observation above.

When to stop and ask for help

If the delay remains before sign-in, ordinary app changes do not help, or errors appear, stop adding tweaks. Share the exact model, Windows build, delay location, repeatable timings and one-change results with the appropriate support team. Keep account details and recovery keys out of public screenshots.

Documentation review: 6 October 2026. Checked against the linked primary sources. This is an editorial troubleshooting workflow, not a measured speed-up or a claim that these changes were tested on your PC.

Official references

Microsoft — Startup-app configurationOfficial reference Microsoft — Clean-boot diagnosis and return to normal startupOfficial reference Microsoft Learn — Startup phases and Fast StartupOfficial reference Microsoft Learn — System power states and RestartOfficial reference