Skip to content

The Compatibility Assistant Store and Persisted Keys

The per-user Compatibility Assistant keys: Persisted on Windows Vista and 7, Store on Windows 8 to 11, what their values show and what is undocumented.

Published on 6 min read

TL;DR. Before Windows 11 wrote text files, the Program Compatibility Assistant left one trace per user: a value named after the executable's path under Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\ in that user's NTUSER.DAT. The subkey is Persisted on Windows Vista and 7 and Store on Windows 8, 10 and 11. The value name is the path; the data of a Store value is binary and undocumented. What it gives you that the Windows 11 files do not is the user. PCA Parser reads these keys from NTUSER.DAT files and joins them, by path, with the Windows 11 PCA files.

The keys by Windows version

WindowsKey, in NTUSER.DATValue nameValue data
Vista, 7...\AppCompatFlags\Compatibility Assistant\PersistedExecutable pathNot described by the public sources
8, 10, 11...\AppCompatFlags\Compatibility Assistant\StoreExecutable pathBinary, undocumented
11 22H2 and laterThe Store key, plus the files in C:\Windows\appcompat\pca\

The full path is Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store, which is HKCU\... for the logged-on user and HKU\<SID>\... for any loaded profile.

What Microsoft says

Microsoft's Vista-era page on the Program Compatibility Assistant is the only official description of the Persisted key. After explaining where PCA writes compatibility modes, it says that "PCA stores the list of all programs for which it came up" under HKEY_CURRENT_USER\...\Compatibility Assistant\Persisted, for each user, "even if no compatibility modes were applied". Microsoft has not documented the Store key that replaced it.

The same page lists what PCA excludes: programs with an application manifest that declares a UAC run level, programs listed in ExecutablesToExclude under HKLM\Software\Microsoft\Windows NT\CurrentVersion\Compatibility Assistant, programs running from network locations, and programs with fixes in the compatibility databases. That was Windows Vista. Whether the same exclusions decide what reaches the Store key on Windows 10 or 11 is not documented, and the Windows 11 text files clearly record programs that carry manifests.

What researchers observed

Corey Harrell tested both keys in 2013, in Revealing Program Compatibility Assistant HKCU AppCompatFlags Registry Keys:

  • On Windows 7, the Persisted key held the programs he had installed through an installation routine, such as FTK Imager. Programs without an installer did not appear.
  • On Windows 8, the Persisted key was gone and the Store key held third-party programs with and without installers: Process Monitor, Process Explorer, FTK Imager, Foxit.
  • His reading: an entry shows that the program ran, and that it ran under the user account whose hive holds the key.

These were small tests on two releases. Nothing published since has mapped exactly which launches create a Store value on Windows 10 or 11.

The value data

Store values hold binary data. No vendor documentation describes it. What exists:

  • Harlan Carvey's RegRipper appcompatflags plugin has read an 8-byte FILETIME at offset 0x2C of each Store value since 2013, using test data from Eric Zimmerman, and prints it next to the path.
  • No public source states which event that time records, whether it changes on each launch, or whether it is UTC on every release. If you rely on it, test it on a lab machine of the same build.

For Persisted values, the public sources give no description of the data at all. Use the value name, and the key's LastWrite time.

Timestamps you can rely on

The key's LastWrite time is a FILETIME in UTC, set when any value in the key is added or changed. It dates the most recent change to the key as a whole, not each value. Two cases make it more useful:

  • A new account. A profile created during the intrusion has an almost empty hive. On FIN-WKS-07, the rogue account svc_backup was created at 09:57:41 UTC and first logged on at 09:59:28. Apart from anything copied from the default user profile, every value in its Store key was written after that logon.
  • A short key. With few values, the LastWrite time is close to the last one added.

What a Store value proves

It showsIt does not show
PCA dealt with this path in this user's sessionHow many times the program ran
Which user, by the hive it is inWhen each launch happened
That the path existed when PCA saw itThat the file is still there, or what it contained

Uninstalling a program does not remove its value: a user asked about exactly that on Microsoft Q&A in 2023 and got no explanation. For an investigator, a value can outlive the file it names, so the path of a tool deleted after use is worth looking for.

Store key and Windows 11 files together

On Windows 11 22H2 and later you have both. They answer different questions:

PcaAppLaunchDic.txtStore key
ScopeWhole machineOne user
TimeLast launch, per path, UTCKey LastWrite; undocumented data
PathAs launched, with drive letterAs recorded, full path

Join them on the path. A path in the launch log and in one user's Store key gives you a launch time and a user. A path in the launch log and in no Store key leaves the user open: check UserAssist, BAM and the logon sessions. Details in investigating program execution with PCA traces.

Reading the keys

  • On a live system: reg query "HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store" for the current user. For other users, query HKU\<SID>\... while their profile is loaded.
  • Offline: collect each NTUSER.DAT with its transaction logs (collecting the PCA folder and AppCompatFlags keys) and open it in Registry Explorer, RegRipper (appcompatflags plugin) or PCA Parser.

The same parent key, AppCompatFlags, also holds the Layers subkey, where compatibility modes and RUNASADMIN are stored. It is covered in AppCompatFlags Layers.

FAQ

Where is the Compatibility Assistant Store key?

In each user's NTUSER.DAT, at Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store, which is HKCU on a live system. Windows Vista and 7 used a Persisted subkey at the same place instead.

Does a Store value prove that the program ran?

It shows that the Program Compatibility Assistant dealt with that path in that user's session, which in practice means the program was started. Microsoft does not document what triggers an entry, so treat it as strong evidence with user attribution and corroborate it with Prefetch, BAM or the Windows 11 PCA files.

Is there a timestamp in the Store value data?

RegRipper's appcompatflags plugin reads an 8-byte FILETIME at offset 0x2C of each Store value and prints it, based on test data from 2013. Microsoft does not document the binary format and no public source states which event that time records. The key's LastWrite time is reliable but covers the whole key.

Why does a Store value remain after the program was uninstalled?

Uninstalling does not remove it, as a user reported on Microsoft Q&A in 2023 without getting an explanation. For an investigator this is useful: a value can outlive the file it names.

Frequently asked questions

Where is the Compatibility Assistant Store key?

In each user's NTUSER.DAT, at Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store, which is HKCU on a live system. Windows Vista and 7 used a Persisted subkey at the same place instead.

Does a Store value prove that the program ran?

It shows that the Program Compatibility Assistant dealt with that path in that user's session, which in practice means the program was started. Microsoft does not document what triggers an entry, so treat it as strong evidence with user attribution and corroborate it with Prefetch, BAM or the Windows 11 PCA files.

Is there a timestamp in the Store value data?

RegRipper's appcompatflags plugin reads an 8-byte FILETIME at offset 0x2C of each Store value and prints it, based on test data from 2013. Microsoft does not document the binary format and no public source states which event that time records. The key's LastWrite time is reliable but covers the whole key.

Why does a Store value remain after the program was uninstalled?

Uninstalling does not remove it, as a user reported on Microsoft Q&A in 2023 without getting an explanation. For an investigator this is useful: a value can outlive the file it names.

Related articles

How AppCompatFlags Layers stores compatibility modes and Run as administrator per executable, in NTUSER.DAT and SOFTWARE, and how to read it as evidence.
Use the Windows 11 PCA files and AppCompatFlags keys in an intrusion: what to flag, what is missing and why, how to find the user, with a worked example.
What PcaAppLaunchDic.txt records on Windows 11 22H2 and later: one line per program launched from the GUI, its last launch time in UTC, and its limits.