Amcache DLL 6.1.7600 and older:
<SYSTEMROOT>\AppCompat\Programs\RecentFileCache.bcf
Overview
Amcache is a replacement for the RecentFileCache (which was linked to DLL
version 6.1.7600).
Very complex artefact, linked to an application compatibility feature that aims
to maintain support for existing software on new versions of the Windows
operating system (like the Shimcache artefact). ProgramDataUpdater (a task
associated with the Application Experience Service) uses the registry file
Amcache.hve to store data during process creation. The Amcache is a
standalone registry hive, with multiple root keys that contain various types of
data.
The Amcache behavior depends on the version of the associated libraries, and
not on the version of the operating system. The Amcache on up-to-date
Windows 7 and Windows 10 systems will thus behave the same way.
For a very comprehensive analysis of the Amcache artefact, and its evolution
across different releases of the underlying DLL, refer to the
ANSSI’s ANALYSIS OF THE AMCACHE v2 white paper.
Information of interest
The Amcache.hve registry hive is split into a number of root keys, with keys
being added, changed, or removed depending on the Amcache DLL version.
An Amcache entry is created whenever a program is executed from a specific
path. However, entries may also be created for files in “scanned” directories.
The following notable root keys can be of forensic interest:
-
FilethenInventoryApplicationFilestarting from version10.0.14913.1002of theAmcachelibraries (AmcacheParseroutputsAssociatedFileEntriesandUnassociatedFileEntries):-
Data about program executions if they are shimmed, programs that are part of an installed application, or programs in scanned directories (without requiring execution of the associated programs).
-
Data available (depending on the
Amcachelibraries version): executable full path, program size,SHA1of the first 30MB of the executable in theFileIdvalue, binary type (x86 versus x64), and the compilation date of the program in theLinkDatevalue. -
Additional data for entries associated with an installed application is available in the
InventoryApplicationkey. TheProgramIdvalue from theInventoryApplicationFilesubkey of a given program matches the subkey’s name under theInventoryApplicationkey of the associated application. TheInventoryApplicationkey provides metadata about the application: name, publisher, install date, etc. -
For non-up-to-date systems still using a
Filekey, the last write time of an entry key under theFilekey coincides with the execution time of an executable that is not associated with an application. For executables that are part of an application, the last write time coincides with either the application installation time or the first execution if the executable needed shimming. For entries under the newerInventoryApplicationFilekey, the last write time of the keys always coincides with an execution ofMicrosoft Compatibility Appraiserand is thus no longer an execution timestamp. -
AmcacheParser’sAssociatedFileEntriesoutput references programs associated with an application, and theUnassociatedFileEntriesoutput references “loose” programs (that are not associated with an installed application).
-
-
InventoryDeviceContainerandInventoryDevicePnp(AmcacheParseroutputsDeviceContainersandDevicePnp):-
Data about devices plugged into the system.
-
Data available: device type (USB, Bluetooth, media, etc.), device friendly name, self-reported description, manufacturer, associated driver, etc.
-
-
InventoryDriverBinary(AmcacheParseroutputDriverBinaries):-
Data about installed drivers.
-
Data available: driver name, full path, size, associated service name, compilation timestamp (
DriverTimestamp), driver file last write timestamp, etc.
-
-
InventoryDriverPackage(AmcacheParseroutputDriverPackages):-
Data about driver package files (INF files), which contain information about the drivers.
-
Data available: driver package file name, path, last write timestamp, etc.
-
-
ProgramsthenInventoryApplication(AmcacheParseroutputProgramEntries):-
Data about installed programs, as referenced in the
Uninstalland/or aRunkey of theSOFTWAREhive. -
Data available: application name, executable full path and SHA1, publisher, install date, etc.
-
-
InventoryApplicationShortcut(AmcacheParseroutputShortCuts):-
Data about the shortcuts (
LNKfiles) that were present at one time (and that may still be present or may have been removed) in a subset of scanned folders (Start Menu and/or Desktop folders). -
Data available: full path of the shortcut. The last write timestamp of the associated subkey can also be a general indicator of when the activity occurred, but does not seem to match any of the
MACBtimestamps of the shortcut file.
-
Tool(s)
-
KAPE’sAmcacheParsermodule.
References
View on GitHub