Skip to content

Load and Examine Registry Hives

Open a working copy, check which hive you loaded, then select a key and read its values. You do not need to edit the live Windows Registry to examine an offline file.

Prepare the evidence

OriginalsKeep the source set

Retain the hive, its available LOG1/LOG2 files, source paths and acquisition notes together.

Working copiesExamine a separate set

Copy the complete set into a working folder. Compare SHA-256 values before opening it.

OutputsSave away from inputs

Put exports, screenshots and notes in a third folder so they cannot replace the hives.

Choose the right file: NTUSER.DAT is a user's hive; SOFTWARE and SYSTEM normally come from Windows\System32\config. A .reg text export is not a binary hive and does not preserve the same forensic metadata. For this guide, use an acquired training hive or the purpose-built hives in the Full Lab.

Load a copied hive

  1. In Registry Explorer, choose File / Load offline hive, then select the working hive. Dragging a copied hive into the application is another supported route.
  2. Read the load messages and record the loaded source path. If the hive is reported dirty, keep its matching transaction logs alongside the working hive and record whether you replayed them, skipped them, or received a warning. Preserve any replayed output separately from the originals.
  3. Check the loaded root in Registry hives. Confirm the profile or system in your case sheet before interpreting its contents. Set and record your time display preference; these exercises use UTC.
What does “dirty hive” mean?

The hive's saved state may need transaction log data to be brought up to date. A replayed view can differ from a view without replay. Keep the input set, the load/replay messages, your chosen settings and any derived file. Do not mix logs from another user or acquisition. If the logs are missing or rejected, retain the warning and state that your view may be incomplete. A missing key is not automatically evidence that the activity never occurred.

Find your way around

Registry hivesNTUSER.DAT› Software› … › Run
ValuesValue name · Type · DataSupportAssist · REG_SZ · command
Type viewerRead the selected value's complete data.

Select a hive on the left, expand its keys, and choose the key you want to examine.

Key means the container on the left. Value means a named item under that key. Value data is the content you investigate. The name of a value can look reassuring even when its command points somewhere unexpected.

Follow a startup lead

1. Navigate to the Run key

Select the user's loaded NTUSER.DAT. Expand Software, Microsoft, Windows, CurrentVersion, then Run. This is a path relative to the user hive root. In a SOFTWARE hive, the corresponding machine Run path starts at Microsoft, without an extra Software level.

Look for: a key name and a Values grid on the right. If Run is absent, record that for this hive and view. Do not create it in evidence.

2. Select a value and read its data

Choose a row in Values. Read its name, type and complete data in the value/type viewer. For a text command such as "C:\Users\Alex\Downloads\RemoteAssistSetup.exe" --background, keep the quoted path and the --background argument separate in your reasoning. Record the original data unchanged; do not launch the program.

Look for: the complete path, arguments and any environment variables such as %APPDATA%. Resolve variables using the examined user's environment, not your analyst account. Keep deleted/recovered flags with the record if the viewer reports them.

3. Use search or bookmarks to find related records

Use the application's search command under Tools to search a distinctive filename or value name. Review whether you searched key names, value names, data, or deleted/slack data. Open a hit and check its hive and full key path. A match from another user or a machine hive can describe a different program.

Bookmarks provide shortcuts to known forensic locations and may show plugin-decoded output. The available list depends on the hive and installed bookmark/plugin versions. Confirm the underlying key and raw value, even when a decoded view looks clear.

Look for: a relevant hit in the intended hive. Zero hits can result from the wrong scope, parser support, encoding, missing data or an incomplete acquisition.

The interface areas, loading, search and bookmark mechanics are documented in the author's Registry Explorer manual (legacy interface reference) and current EZ Tools manuals. Use your release's actual labels and record any differences.