Capture and Compare with RegShot¶
Take the first shot before the action. Take the second after it. Changing the test conditions between shots makes the result harder to explain.
Set up one small test¶
Use the same VM, account, tool build, privileges and capture settings.
Record what you change and when. Keep unrelated programs quiet.
Put snapshots and reports outside any folder you ask RegShot to watch.
Use the Full Lab for a harmless test action. RegShot observes the live environment; use Registry Explorer when your task is to examine copied Windows hives offline.
Follow the capture sequence¶
1. Choose the report and scan settings
Select Plain TXT for an easy-to-search text report, or HTML document for a browser view. Set Output path to your case's reports folder. Enter a short comment such as RGS-LOCAL-01.
For a Registry-only test, leave Scan dir unchecked. For a folder test, enable it and choose only your training folder. A broad C:\WINDOWS scan adds time and background changes. Record the selected paths and any skip rules in regshot.ini; the directory box does not restrict the Registry scan to that folder.
Look for: a known output folder and a recorded scan setting before taking the first shot.
2. Capture and save the first shot
Choose 1st shot / Shot and Save. Wait for capture to finish, then save as before in your snapshots folder, keeping the extension offered by RegShot. Unicode shots normally use .hivu.
Shot alone keeps a capture in memory. You can lose that capture when you quit. Load opens a previously saved compatible RegShot shot, not an arbitrary NTUSER.DAT or SYSTEM hive. Keep the same build/encoding for your pair.
Look for: a non-empty saved shot and a completed capture. Record its time, host, user and build in your case notes. Hash saved evidence using your normal workflow.
3. Make one recorded training change
Carry out only the approved action. In this section's Full Lab, a helper changes a uniquely named training setting and creates one harmless note file. Record the action's start and finish time. Do not run unknown software for this beginner exercise.
Look for: the helper's success result. Avoid opening unrelated applications or changing the scan settings during the test.
4. Capture the second shot and compare
Choose 2nd shot / Shot and Save. Save as after in the snapshots folder. Keep the first capture settings unchanged. Then select Compare.
Open the generated report from Output path and confirm it is the report from this run. The comment is a report label, not a replacement for capture notes. Preserve both shots, the report and the recorded action together. The project's 1.9.0 readme explains the saved-shot and report controls; the project notes document the Unicode .hivu extension.
Look for: two shot times and matching machine/user context, then the relevant added, deleted or modified records. Windows background activity can add unrelated differences.
Keep the comparison fair¶
You can observe that the setting differs. You cannot identify the writing process from this pair alone.
I took the second shot too early
Keep the failed run with an explanation. If the first shot is still a valid baseline, clear only the second shot and take it again after the action. Record the retry and do not overwrite saved evidence. If the baseline was taken after the change, restore the training state and begin a new run.
The report is empty, missing or much larger than expected
Check which shots were compared, where the output was written, your privileges, scan paths and skip settings. A zero result can mean no observed difference in the captured scope. It does not prove no activity occurred. A large result may include ordinary Windows activity; search for the exact training identifier.