AmCache
Amcache
is a replacement of the RecentFileCache
(that was linked to DLL version 6.1.7600
)
forensic interest:
A good place to start is looking at the
InventoryApplicationFile
key, which contains:Data available (depending on the
Amcache
libraries version):executable full path -
LongCaseLongPath
program size -
Size
SHA1
of the first 31.4mb of the executable in theFileId
valueVersion number
description and publisher
binary type (x86 versus x64),
the compilation date of the program (PE Headers) in the
LinkDate
value
Linked to
ProgramId
names within theInventoryApplication
keyEntries confirm presence on device not execution
InventoryDeviceContainer
andInventoryDevicePnP
:Data available:
device type (usb; Bluetooth, media, etc.),
device friendly name,
self reported description,
manufacturer,
associated driver, etc.
Data about installed drivers.
Data is logged in AmCache
upon the following:
executed (and shimmed) GUI apps
file/exe's that were copied as part of app execution
exes present in directory scanned by Microsoft Compat appraised Scheduled task
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.
Parse:
Outputs into:
fileEntries and unassociated_fileEntries - this is
InventoryApplicationFile
split into two unassociated = apps that aren't directly linked to installed apps - forensics interestShortcuts,
DriverPackages/DriverBinaries (look for drivers not in
C:\Windows\System32
),DevicePnPs,DeviceContainers
Last updated