Slow startup: review what launches at sign-in
A slow sign-in can happen before the desktop appears or only when a particular app loads. Locate the platform’s built-in startup list, record enabled entries and any displayed impact, and ask which tools the customer needs immediately. Keep entries unchanged, especially on managed devices or where an item’s purpose is unclear.
Updated November 11, 2026
- Clarify when the delay occurs Ask whether the delay is before sign-in, while the desktop loads, or when the customer opens a particular app. Record their estimate and what they consider ready.
- Open the built-in startup list Read Startup Apps in Windows settings or Task Manager, Login Items in macOS settings, or the desktop environment’s Startup Applications list on Linux.
- Record enabled items and impact Note displayed names, enabled status, and any impact indicator. Do not infer function or safety from an unfamiliar publisher or label alone.
- Ask what the customer depends on Ask which apps, security tools, backup utilities, work services, accessibility features, and device helpers must be ready after sign-in.
- Compare with the reported timing If permitted, observe one ordinary sign-in and note what appears and when. Do not change startup items during this review or make repeated restarts just to collect timing.
- Document questions before a change List items the customer does not recognize and ask their purpose. A proposed change needs clear approval and a way to restore the prior setting.
When does the startup delay happen?
Ask whether the delay is before sign-in, while the desktop loads, or when a required app opens. Record when it began and whether it happens every time. Do not promise that reviewing startup items will resolve it.
Where is the built-in startup list?
On Windows, review Startup Apps in Settings or Task Manager. On macOS, review Login Items in System Settings. On Linux, use the desktop’s Startup Applications or session settings. Record enabled entries and displayed impact. A name or icon alone does not show what an item does.
Which startup items are safe to leave?
Do not disable items during a read-only review. Ask the customer what they use and whether the item supports work, security, backup, accessibility, printers, input devices, or another needed function. An item the customer does not recognize may still be required.
Compare the list against the reported delay and the time when each item appears. If a displayed impact label exists, record it as the system reports it. Treat it as one clue, not a diagnosis or permission to change the setting.
What should I ask the customer?
Ask which applications must be available immediately, which can be opened later, and whether any sign-in helper supports a device or access need. Ask about work-managed tools before proposing changes. Get the customer’s approval for any later action and explain how the previous setting could be restored.
When should I stop?
Stop if an entry might support security, backup, accessibility, work, or a required device and its purpose is unclear. Do not disable or remove entries during review. For a managed computer, record the list and ask the responsible administrator before proposing a change; explain that the delay may need investigation elsewhere if no safe conclusion is available.
CommandGate can collect startup-related evidence for review, while any change to the customer’s launch list remains a separate, explicitly approved action.