Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Amcache and ShimCache are Windows compatibility artefacts that record which binaries a system has encountered, giving investigators programme execution evidence that attackers rarely think to clean.

What Are Amcache and ShimCache?
Two Windows registry artefacts appear in almost every intrusion timeline: the Application Compatibility Cache, universally called ShimCache, and Amcache. Both exist because Microsoft needs to keep older software working on newer builds, and both end up recording binaries the operating system has encountered. Neither was designed as an audit trail, which is precisely why attackers so rarely clean them.
ShimCache is a single binary value inside the SYSTEM hive, under ControlSet001\Control\Session Manager\AppCompatCache. Windows holds it in kernel memory and flushes it to disk at shutdown, so the copy on a running machine can be days out of date. Modern builds keep up to 1,024 entries, each holding the full path of a binary and the file system last-modified time that applied when the entry was created.
Amcache is a hive of its own, stored at C:\Windows\AppCompat\Programs\Amcache.hve with transaction logs beside it. The InventoryApplicationFile subkey is the one analysts want: each entry carries a file path, the SHA-1 of the first 30 MB of the file, the PE link date, the publisher and product strings from the version resource, and the last-write time of the key itself.
This is where investigations go wrong. On Windows 8 and later, a ShimCache entry records that the operating system examined the file, not that anyone ran it. Listing a folder in Explorer can be enough. Windows 7 maintained an execution flag and those entries carry more weight, but such systems are now rare. The timestamp inside an entry is the file’s modified time, never the moment of execution; the only sequencing you get is the position in the list, which runs most recent first.
Amcache sits closer to execution evidence, yet entries are also written by the Microsoft Compatibility Appraiser scheduled task as it inventories software. Treat both artefacts as proof that a named binary with a given hash existed on that host before a certain point, then corroborate with Prefetch, Windows event ID 4688, Sysmon event ID 1, or endpoint telemetry before you write the word “executed” in a report.
An intruder who deletes a tool from disk, clears the Security log, and empties the Prefetch folder usually leaves both artefacts intact. The SHA-1 recorded in Amcache frequently identifies a wiped binary outright once you check it against threat intelligence sources, which is the difference between “something unknown ran here” and “Mimikatz ran here on 14 March”. ShimCache retains full paths, exposing staging directories such as C:\Windows\Temp, C:\ProgramData, and user profile subfolders that no legitimate installer would use.
They also help with scoping. During triage across a large estate, the presence of the same unusual path or hash on forty machines maps the intrusion far faster than reading logs host by host.
Eric Zimmerman’s AppCompatCacheParser and AmcacheParser are the standard tools, both of which emit CSV for review in Timeline Explorer. Collect the hives with KAPE or Velociraptor rather than copying them manually, and always take the .LOG1 and .LOG2 transaction logs with Amcache — a hive replayed without them can be missing the most recent entries, which are usually the interesting ones. Volatility can recover ShimCache from a memory image, giving you the live in-memory version instead of the stale copy on disk, which matters on a server that has not rebooted for months.
Because both artefacts are easy to misread, any statement you make about them has to be carefully hedged. In UK proceedings an expert is expected to set out the limits of a technique and the range of reasonable interpretation, so a report that claims ShimCache proves execution invites a straightforward challenge in cross-examination. Record how the hive was acquired, hash it on collection, and keep the chain of custody alongside the parsed output.
At Privia Security, we collect both artefacts on every Windows host we triage as part of our digital forensic incident response services, because they routinely answer the question a client asks first: what did the attacker bring with them?
Not on Windows 8 or later. The entry only shows that the operating system inspected the file, which can happen when a folder is browsed or a compatibility check runs. Windows 7 recorded a separate execution flag, so entries from those systems are stronger. Treat a modern ShimCache hit as evidence of presence and confirm execution with Prefetch, event ID 4688, or Sysmon.
Collect both, but prioritise Amcache if the binary has been deleted. Amcache stores a SHA-1 of the file, so you can identify a wiped tool by hash even though it no longer exists on disk. ShimCache is more useful for mapping staging paths and for hosts that have not rebooted, where the in-memory version can be pulled from a RAM image.
They can, and some tooling does clear the AppCompatCache value or delete the Amcache hive. In practice this is uncommon, and removal is itself suspicious: a missing or newly created Amcache hive on a long-running server is an anomaly worth investigating. Volume shadow copies and backups frequently hold older versions that survive deliberate clean-up.
It depends on activity. ShimCache holds roughly 1,024 entries, so a busy workstation can cycle through them in weeks while a quiet server retains years of history. Amcache usually covers a longer window because it is not capped the same way, though scheduled maintenance tasks prune old entries. Always check the hive last-write times before stating a coverage period.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.