COMING SOON · Q1 2027 Planned releaseGet notified + 10% launch offer ↗
← Acorn overview

Acorn application guide

Registry Analyser

Registered software and application paths can help explain the state of a Windows system. Use that state to choose follow-up questions. A registration entry is not an execution history, and the significance of a value depends on its source and context.

Demonstrated on public training data

What software or application-path registration is recorded in this Windows profile?

Start with

  • Registry data from the public Lone Wolf training scenario.

What you can take away

  • Registered-program and application-path review tables.
The public Lone Wolf scenario shows 24 registered programs and their available versions and installation dates, plus application-path registrations. These records guide follow-up work; registration alone does not prove a program was executed. View full screen
The public Lone Wolf scenario shows 24 registered programs and their available versions and installation dates, plus application-path registrations. These records guide follow-up work; registration alone does not prove a program was executed.

Open the screenshot and choose “View actual size” to read the records at their original resolution.

A practical starting point

How the workflow fits together.

  1. Identify the Registry source being examined and the profile or system context it represents.

  2. Review relevant software registrations, available dates, versions and application paths. Retain the source context needed to locate material entries again.

  3. Check an important entry in the underlying source with a suitable independent method. Use other artefacts when the question concerns execution, user activity or a sequence of events.

Evaluate the workflow

Questions worth bringing to a demonstration.

  • Which hive and record support the displayed software or application-path entry?
  • Is a displayed date explained in context, rather than being treated as the time an application ran?
  • What separate artefact would help test an execution claim suggested by this registration information?

Start with your requirements

Bring a sample question.

Ask us to demonstrate this workflow with suitable public or constructed material. Do not send confidential evidence in an initial enquiry.

Planned for Q1 2027

Be first to hear. Save 10% at launch.

Request Acorn launch news and details of the planned 10% offer. No deposit or purchase commitment.

Notify me at launch ↗

Launch-update requests go to the SQFR team for review. Final offer terms and product availability are still to be confirmed.

About the screenshots and illustrations

Application screens are selected from the September 2026 Acorn screenshot pack. Captions distinguish native setup views, constructed training records and public-corpus results. They are not private client cases, and a displayed control does not establish that every operation was completed.

Relevant public sources include DeepBlueCLI training event logs and Plaso test data. Check the relevant source terms before redistributing an underlying dataset.

Workspace scenes and sector mascot variants are generated illustrations. They do not show actual police, judicial, military or university deployments or endorsements. The original Squirrel Forensics identity is retained.

Zoom in, then scroll to inspect the detail.

Open full-resolution image ↗

A useful first conversation

Let’s look at your workflow.

Tell us what you examine, where you work and what you need to deliver.

Use the enquiry form to outline your role, intended use and potential order quantity. Do not send case material through a general enquiry.

Your enquiry goes to the SQFR team. Please do not include passwords or case evidence.