Added WOW6432Node Run Keys and Expanded Edge and Chrome Artifacts#111
Merged
AndrewRathbun merged 1 commit intoEricZimmerman:masterfrom Jan 6, 2026
Merged
Conversation
AndrewRathbun
approved these changes
Jan 6, 2026
Collaborator
AndrewRathbun
left a comment
There was a problem hiding this comment.
Thank you as always 💯
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This adds support for the WOW6432Node Run and RunOnce keys used for 32 bit software on 64 bit systems. This is only present on HKLM and does not work on NTUSER hence only doing HKLM. Additionally I allowed Chrome and Edge keys to be a bit less restrictive to include the different editions of Chrome and Edge such as Dev, Canary and Beta.
Checklist:
Please replace every instance of
[ ]with[X]OR click on the checkboxes after you submit your PRGUIDfor my Batch file(s).\RECmd\BatchExamplesdirectoryThank you for your submission and for contributing to the DFIR community!