Locations desk

Windows startup locations

Find Windows startup locations, from folders and Run keys to tasks, services, packages, and event consumers.

A useful sequence

Observe, locate, then change only with a reason.

Name the startup phase you are dealing with.
Use the least destructive inspection tool.
Record the original state before a test.

A location is a question about scope

Windows startup locations answer different questions about who runs something and when. A current-user folder or registry value follows one profile, while an all-users location or service can affect the machine more broadly. Packaged applications and event consumers add their own boundaries. This section groups the routes by the behavior a reader is trying to explain, then links to the focused guides where the exact inspection steps belong.

Read the route before the name

A familiar program name can be launched from several mechanisms, and an unfamiliar name can be perfectly explainable once its path, publisher, and trigger are visible. The location is therefore the first useful fact. Record it with the account, phase, command, or shortcut target before changing anything. That small habit keeps a plausible explanation attached to the evidence that produced it.

What this desk does not promise

The location map is not a security scanner, a registry cleaner, or a complete inventory of every installed application. It brings official descriptions together so a reader can inspect the relevant family with a reversible next step. When the location does not explain the symptom, move to timing, services, or a controlled trace instead of forcing every problem into a startup-folder story.

Reading routes