API Reference: Analyzing Windows Amcache Artifacts
Amcache.hve Location
Registry Keys
| Key Path |
Contents |
| Root\InventoryApplicationFile |
File execution evidence with SHA-1 |
| Root\InventoryApplication |
Installed application metadata |
| Root\InventoryDevicePnp |
PnP device connection history |
| Root\InventoryDriverBinary |
Driver binary metadata |
regipy Python Library
AmcacheParser (Eric Zimmerman)
Output CSV Columns
| Column |
Description |
| Name |
Application/file name |
| LowerCaseLongPath |
Full lowercase path |
| Publisher |
Software publisher |
| FileId |
SHA-1 hash (prefixed with 0000) |
| Size |
File size in bytes |
| LinkDate |
PE compilation timestamp |
| Version |
File version string |
| ProgramId |
Associated program GUID |
Forensic Value
| Artifact |
Evidence |
| SHA-1 hash |
File identification even after deletion |
| LowerCaseLongPath |
Execution path including USB/temp |
| LinkDate |
PE compile time (timestomping detection) |
| Publisher |
Legitimacy verification |
| Last Modified |
Registry key update timestamp |
Suspicious Indicators
| Pattern |
Concern |
| Path contains \Temp\ |
Execution from temp directory |
| Path contains \Downloads\ |
User-downloaded execution |
| Missing Publisher |
Unsigned/unknown binary |
| LinkDate far from file date |
Possible timestomping |
| Known tool names (mimikatz, psexec) |
Attacker tooling |