Interpret and Export Registry Evidence¶
Your job is to explain what a record supports and keep enough context for another analyst to check it.
Read a value without overclaiming¶
A named value, its type and data, the loaded hive, key path and displayed key time.
A command under a genuine user Run key configures a program to start at sign-in.
The entry alone does not prove the program ran, who set it, or whether its contents are malicious.
The time belongs to the key. If CloudSync and SupportAssist are values under the same Run key, they share that key's last write time. You cannot assign it to a change in SupportAssist alone. Microsoft documents Run key behaviour and the scope of a key's last write time.
Training illustration: both values sit under the same key. Neither has its own last write timestamp.
Save a reviewable export¶
- Select the intended hive and key. Clear or record filters so you know what the visible grid contains.
- Right-click the selected key and choose Export / Values, then a table format such as To TSV. Use your release's labels. Keep this value table separate from a whole-hive or
.regexport. - Save into your outputs folder. Open the exported file and confirm the expected names, types and full data are present. Record the row count and any fields the table omitted.
- Save a screenshot and a short note alongside the table. Include the source hive and original location, working-copy hash, relative key path, key last write time and time zone, tool version, replay/recovery choices, filters and warnings. Hash retained outputs when your workflow requires it.
A short finding is enough
Found: Alex's Run key contains SupportAssist, pointing to a program in Downloads.
Unproven: the entry does not show whether the program ran or when this specific value changed.
Next: check endpoint process records and the acquired file, matching the host, path, time and content identity where possible.
Attach the precise value data and source context as evidence references rather than filling the note with copied paths.
Choose the next source¶
| Lead in the Registry | Useful next evidence | What it can help test |
|---|---|---|
| Program path in Downloads | Browser download records, file records and retained file bytes | Possible download origin, file presence and content identity. |
| Startup command | Endpoint process telemetry and relevant event records | Whether a matching command actually executed during the available interval. |
| User hive or SID | Acquisition notes and SOFTWARE ProfileList | Which Windows profile the settings belong to. |
| Deleted or plugin-decoded record | Raw value, recovery flags, parser notes and another relevant source | Whether the interpretation is reproducible and how complete the view is. |
If something does not look right¶
The application will not open
Confirm you extracted the full package and installed the matching Desktop Runtime. Recheck the executable version and official source. A newer package may not use SUSA's original net9 folder.
The hive will not load, or the expected key is missing
Check that the input is a binary hive, not a .reg text file or a log alone. Confirm the source path, permissions and input hash. Retain parse/replay warnings. Check the user, hive-relative path and search scope before concluding the record is absent.
The same name appears in several places
Compare the hive, complete key path, value type and full data. A machine-wide SupportAssist value can point to a different program from a user value with the same name.
The export has fewer rows or columns than expected
Check the selected key, visible filters, deleted-data settings and export scope. Reopen the saved table. Keep the first export with an explanation if you retry; do not silently replace a failed or incomplete result.