What is the Program Compatibility Assistant?
The Program Compatibility Assistant (the PcaSvc service) watches programs as they start and stop so that it can offer compatibility fixes. Doing so, it leaves traces an investigation can read: which programs ran, under which user, and sometimes how they ended.
Since Windows 11 version 22H2 it writes plain-text logs in C:\Windows\appcompat\pca. PcaAppLaunchDic.txt keeps one line per executable launched through the graphical shell, with the time of its last launch in UTC. PcaGeneralDb0.txt and PcaGeneralDb1.txt log events about programs: abnormal exits, blocked drivers, failed installers. On every version since Windows 7, it also records executables in each user's registry, and the compatibility settings users apply are kept in the Layers keys.
The files and keys
- PcaAppLaunchDic.txt: <full path>|<YYYY-MM-DD HH:MM:SS.fff>, one line per path, updated in place at each launch. ANSI text (code page 1252, no BOM) on the systems Sygnia, Kaspersky and the public Windows 11 copies show; some write-ups read it as UTF-16, so the tool detects the encoding.
- PcaGeneralDb0.txt and PcaGeneralDb1.txt: UTF-16LE, no BOM, eight fields separated by |: time (UTC), record type, path, product name or description, company, version, program ID, message. Paths are lower case, without the drive letter, often behind a variable (%programfiles%, %USERPROFILE%), and user names may be replaced by %USERNAME% or x's. The two files take turns at about 2 MB.
- Record types, as Sygnia's research names them: 0 installer failed, 1 driver blocked, 2 abnormal process exit (the exit code in hex in the message), 3 PCA resolve called (resolver name and result in the message), 4 unknown. Microsoft does not document them.
- NTUSER.DAT, Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store (Windows 8 and later) and \Persisted (Windows 7): one value per executable path. The value data is not publicly documented.
- AppCompatFlags\Layers, in NTUSER.DAT and in SOFTWARE (Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers): compatibility settings per executable path, such as ~ RUNASADMIN WIN8RTM.
What PCA records, and what it does not
- PcaAppLaunchDic.txt records programs started through the graphical shell: a double-click in Explorer, the Start menu, a shortcut, a program opened from a browser's download list, also inside an RDP session (Sygnia's tests).
- It does not record programs started from cmd.exe or PowerShell, by a script, a scheduled task, a service, or remotely with PsExec. Sygnia also found that some built-in Windows programs are not recorded when run from their own folder.
- So a program missing from PCA may still have run, and that absence says something about how it was started: a tool in Prefetch, Amcache or BAM but not in PcaAppLaunchDic was most likely started from a command line, a script or remotely.
- Only the last launch of each path is kept. A path holding a character outside the ANSI code page is written up to that character with no time, and after it new paths stop being added (Sygnia, Kaspersky).
- The Store key lists executables PCA dealt with for that user; what makes it write a value is not documented. Read it as presence with user attribution, and corroborate execution elsewhere.
How the tool reads them
- Each file is read in your browser, in a Web Worker. The encoding is detected (BOM, UTF-16 without BOM, UTF-8, else code page 1252), both CRLF and LF line ends are accepted, and every line keeps its raw text and number.
- Lines that hold no path are listed as not understood; records with a missing time, extra fields or an unreadable type are kept with what is odd about them. Nothing is dropped silently.
- In the hives, only the AppCompatFlags keys are read, plus what names the user (the profile folder, else the path stored in the hive header). Store data is shown as its size and hex, not interpreted. Layers words are named when a source documents them, and always kept as written.
- Rows are joined per executable path per host. PcaGeneralDb paths are tied to a full path when exactly one fits: system variables are expanded on the system drive, %USERPROFILE% and missing drives are matched against the host's other paths, and redacted user names act as wildcards. When several fit, the event stays on its own row.
- Files are placed on hosts by their collection path (KAPE's C\ folder, Velociraptor's C%3A, a host folder above them); loose files go with the only host when there is one.
Limits
- Microsoft documents none of these files. Field names, record types and behaviours come from public research (Sygnia, Kaspersky, Andrew Rathbun's samples) and may change with Windows builds; the tool shows every field as written.
- The times are documented as UTC on Windows 11 22H2 to 24H2. Sources call the PcaAppLaunchDic time the last launch; one write-up says it is written when the program exits.
- Paths in PcaGeneralDb lack their drive and often their user: an event is tied to a row only when one path fits, and only within the same host.
- Transaction logs (.LOG1/.LOG2) are not replayed: a hive copied while in use may miss its latest changes.
- The Store key's LastWrite time is shared by all its values: it dates the latest change to the key, not each executable.
- A flag is a reason to look, not a verdict.
Questions
Are my files uploaded?
No. The page reads the files in your browser with JavaScript in a Web Worker; nothing is sent to a server. You can disconnect from the network once the page has loaded.
Which Windows versions have PCA files?
PcaAppLaunchDic.txt and the PcaGeneralDb files appear with Windows 11 version 22H2 (Sygnia tested builds 22621 and 22632; Kaspersky describes 24H2). The Store key exists on Windows 8 and later, the Persisted key on Windows 7, and the Layers keys on every version.
Why is a program I know ran not in PcaAppLaunchDic?
Because it was not started through the graphical shell: programs started from cmd.exe or PowerShell, by a script, a scheduled task, a service or remotely (PsExec) are not recorded. Some built-in Windows programs are not recorded either. Look for it in Prefetch, Amcache, BAM and the event logs.
Is the time in PcaAppLaunchDic the start of the program?
Sygnia and Kaspersky describe it as the last execution time, in UTC; one write-up says it is written when the program exits. The tool shows it as the last launch and does not claim more. Compare with Prefetch or BAM when the exact minute matters.
What does the data of a Store value mean?
Its format is not publicly documented. The tool shows its size and hex and treats the value name, the executable path, as the evidence: PCA dealt with that program for that user.
Can it read a disk image?
Export C:\Windows\appcompat\pca and the users' NTUSER.DAT with Disk Image Parser or another forensic tool and drop the folder here. The page also accepts files handed over by Disk Image Parser, tab to tab, without a server.