An unsigned test build is available for evaluation.
A SMALL EXAMPLE
Explore an entry
✳
Illustrative examples only—not your computer or an app screenshot.
● REVIEW CLUE
Command in a temporary folder
This example’s startup command points to a temporary folder. That is a reason to look closer, not proof of malware.
Available action: supported current-user Run entries can be disabled or restored; Windows approval can remain unknown.
● SCHEDULED TASK
More than one trigger
A scheduled task may run at sign-in, on a schedule or when another event occurs.
Available action: where permitted, changing the task affects all of its triggers—not just startup.
● READ-ONLY IN THIS BUILD
Background service
A service can support Windows, hardware or another application. The tool cannot tell you with certainty whether it is essential.
Available action: inspect the details; service changes are read-only in this test build.
UNDERSTAND THE ENTRYREVIEW THE EVIDENCECHANGE WHAT IS SUPPORTED
A BETTER LOOK
There’s more than one startup list.
Apps can register in several places. Startup Deep Dive gathers many of them alongside services, drivers and running processes, with a place to inspect the details.
It also shows scan issues when something could not be read. This build includes read-only Active Setup, Windows Time provider, Winlogon and credential-provider registrations; a listing does not mean the component ran. No tool can promise to find every possible way software starts.
01
EXPLORE
Find the entry.
Search, filter and sort a broad inventory of startup registrations and other system entries. A running process is shown separately from a startup registration.
02
UNDERSTAND
Look a little closer.
See the entry type, location and available details. Review clues, inspect a file’s hash and signature status, or choose to search the web for more context.
03
DECIDE
Make a deliberate change.
Find entries with offered controls, then disable or restore supported current-user startup entries or change a scheduled task where Windows permits it. The filter is not a recommendation, and Windows may refuse a change.
CONTEXT MATTERS
Check the entry before you switch.
A useful tool should tell you what it knows—and where the evidence stops.
!
A flag is a clue.
Red or gold highlights mean an entry deserves a closer look. They do not prove malware or tell you that something is safe to remove.
↗
Snapshots are not boot impact.
CPU and RAM show activity at scan time, not per-entry boot impact. When accessible, Windows boot warnings can show historical process timings; these do not measure each startup registration. File size refers to one resolved file.
◇
Some entries stay read-only.
This test build leaves services, drivers and machine-wide entries read-only. A scheduled-task change affects every trigger, not only startup.
TEST BUILD
Try the test build.
We’re still checking usability, compatibility and recovery. Run this unsigned build as a normal Windows user. Services, drivers and machine-wide controls remain read-only.
A few useful details about the current test build.
How would I install the test build?+
Download the test installer above, close older app windows and run setup as a normal user. Do not run this test build as administrator. It is unsigned, so Windows may display an unknown-publisher warning. Keep your recovery records. If an older version disabled machine-wide entries, restore them with that version before upgrading. Open More options → Help & about for guidance.
Does it identify everything I can safely disable?+
No. An entry may be important to Windows, a device or a security product. The tool provides context but cannot determine with certainty what is essential or find every startup method. Investigate unfamiliar entries before making changes.
Where does my scan information go?+
Scan history is stored locally by default and can include paths, commands and extension details. You can pause future snapshots in History & privacy; existing history remains. Web searches send the selected terms to the search provider after confirmation.
Will it check for updates?+
The test build checks a signed update feed and is designed to notify you when a newer release is available. A complete interactive upgrade has not yet been tested, and signed feed information must be renewed before it expires. If a check cannot be completed, the app reports that instead of claiming it is up to date. Version 0.7.2 may time out on slower connections; use the download above to update manually if that happens.