legal contact rss

Windows Programm Execution Artefacts

  • Prefetch
    inspired and sourced by Description Increases performance of a system by pre-loading code pages of commonly us...
  • MRU - Last visited or MostRecentlyUsed
    inspired and sourced by Description Tracks the specific executable used by an application to open the files ...
  • SRUM - System Resource Usage Monitor
    inspired and sourced by Description Windows 10 Background Activity Moderator (BAM) Location Win10: SYSTEM\...
  • SRUM - System Resource Usage Monitor
    inspired and sourced by Description Records 30 to 60 days of historical system performance. Applications run, ...
  • Amcache.hve
    inspired and sourced by Description ProgramDataUpdater (a task associated with the Application Experience Se...
  • Jump List
    inspired and sourced by Description The Windows 7 task bar (Jump List) is engineered to allow users to “jump” ...
  • Shimcache
    inspired and sourced by Description Windows Application Compatibility Database is used by Windows to identify ...
  • Windows 10 RecentApps
    inspired and sourced by Description GUI Program execution launched on the Win10 system is tracked in the Rec...
  • Windows 10 Timeline
    inspired and sourced by Description Win10 records recently used applications and files in a “timeline” accessi...
  • UserAssist
    inspired and sourced by Description GUI-based programs launched from the desktop are tracked in the launcher...
05.01.2020 20:15

Windows: Available Artefacts - Evidence of Execution

Adam Harrison
 hast done a great article including the below table of where to look first while forensically examining a windows machine.

The table below details some of the artifacts which evidence program execution and whether they are available for different versions of the Windows Operating System

click me if I'm to small …

Summary of Artifacts

What follows below is brief details on the availability of these artifacts, some useful resources for additional information and tools for parsing them. It is not my intention to go into detail as to the functioning of the artifacts as this is generally already well covered within the references.

PrefetchPrefetch has historically been the go to indication of process execution. If enabled, it can provide a wealth of useful data in an investigation or incident response. However, since Windows 7, systems with an SSD installed as the OS volume have had prefetch disabled by default during installation. With that said, I have seen plenty of systems with SSDs which have still had prefetch enabled (particularaly in businesses which push a standard image) so it is always worth checking for. Windows Server installations also have Prefetch disabled by default, but the same applies.

The following registry key can be used to determine if it is enabled:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters\EnablePrefetcher
0 = Disabled
1 = Only Application launch prefetching enabled
2 = Only Boot prefetching enabled
3 = Both Application launch and Boot prefetching enabled


ShimCacheIt should be noted that the presence of an entry for an executable within the ShimCache doesn't always mean it was executed as merely navigating to it can cause it to be listed. Additionally Windows XP ShimCache is limited to 96 entries all versions since then retain up to 1024 entries.

ShimCache has one further notable drawback. The information is retained in memory and is only written to the registry when the system is shutdown. Data can be retrieved from a memory image if available.


MUICachePrograms executed via Explorer result in MUICache entries being created within the NTUSER.DAT of the user responsible.


Amcache / RecentFileCache.bcfAmcache.hve within Windows 8+ and RecentFileCache.bcf within Windows 7 are two distinct artifacts which are used by the same mechanism in Windows to track application compatibility issues with different executables. As such it can be used to determine when executables were first run.


Microsoft-Windows-TaskScheduler (200/201)The Microsoft-Windows-TaskScheduler log file (specifically events 200 and 201), can evidence the starting and stopping of and executable which is being run as a scheduled task.


LEGACY_* Registry KeysApplicable to Windows XP/Server 2003 only, this artifact is located in the System Registry Hive, these keys can evidence the running of executables which are installed as a service.


Microsoft-Windows-Application-Experience Program-Inventory / TelemetryBoth of these system logs are related to the Application Experience and Compatibility features implemented in modern versions of Windows.

At the time of testing I find none of my desktop systems have the Inventory log populated, while the Telemetry log seems to contain useful information. I have however seen various discussion online indicating that the Inventory log is populated in Windows 10. It is likely that my disabling of all tracking and reporting functions on my personal systems and VMs may be the cause... more testing required.


Background Activity Monitor (BAM)The Background Activity Monitor (BAM) and (DAM) registry keys within the SYSTEM registry hive, however as it records them under the SID of the associated user it is user attributable. The key details  the path of executable files that have been executed and last execution date/time

It was introduced to Windows 10 in 1709 (Fall Creators update).


System Resource Usage Monitor (SRUM)Introduced in Windows 8, this Windows features maintains a record of all sorts of interesting information concerning applications and can be used to determine when applications were running.


ActivitiesCache.db In Windows 10 1803 (April 2018) Update, Microsoft introduced the Timeline feature, and all forensicators did rejoice. This artifact is a goldmine for user activity analysis and the associated data is stored within an ActivitiesCache.db located within each users profile.


Security Log (592/4688) Event IDs 592 (Windows XP/2003) and 4688 (everything since) are recorded within the Security log on process creation, but only if Audit Process Creation is enabled.


System Log (7035) Event ID 7035 within the System event log is recorded by the Service Control Manager when a Service starts or stops. As such it can be an indication of execution if the associated process is registered as a service.


UserAssistWithin each users NTUSER.DAT the UserAssist key tracks execution of GUI applications.


RecentAppsThe RecentApps key is located in the NTUSER.DAT associated with each user and contains a record of their... Recent Applications. The presence of keys associated with a particular executable evidence the fact that this user ran the executable.


JumpListsImplemented in Windows 7, Jumplists are a mechanism by which Windows records and presents recent documents and applications to users. Located within individual users profiles the presence of references to executable(s) within the 'Recent\AutomaticDestinations' can be used to evidence the fact that they were run by the user.


RunMRUThe RunMRU is a list of all commands typed into the Run box on the Start menu and is recorded within the NTUSER.DAT associated with each user. Commands referencing executables can be used to determine if, how and when the executable was run and which user account was associated with running it.


AppCompatFlags Registry KeysReferences/Tools:


Application Experience Program TelemetryReferences/Tools:


Windows Error Reporting (WER)References/Tools:


Various Anti-Virus, Intrusion Detection and Endpoint Detection and Response (EDR) solutions may provide evidence of program execution. It is recommended to identify and analyse any associated logs and note that some logging may be centralised.
Repeating the appeal earlier in this post, feedback, suggested additions and corrections are very welcome!Posted by