Why a Program Is Missing from PCA, and Where Else to Look
Why a program that ran can be absent from PcaAppLaunchDic.txt, and how PCA compares with Prefetch, BAM, Amcache, UserAssist and ShimCache.
TL;DR. PcaAppLaunchDic.txt records GUI shell launches only, on Windows 11 22H2 and later. A program that certainly ran is missing when it was started from a command line, a script, a scheduled task, a service or remotely, when it was a child of another program, when it is a built-in program run from its own folder, or when recording stopped because of the non-ANSI bug, a stopped service or an edited file. A launch can also be hidden behind a later one, since only the last time is kept. For "did it run?", combine sources: Prefetch and BAM see launches PCA does not, UserAssist sees roughly the same GUI launches per user, and Amcache and ShimCache mostly show that a file was there. PCA Parser shows what the PCA traces hold; this article is about what they cannot.
Reasons a program is missing
Check them in this order.
1. The Windows version
The PCA text files exist from Windows 11 22H2 (AboutDFIR found the folder in build 22621 and not in 21H2). Windows 10 and Windows 11 21H2 have none. Read CurrentBuild and DisplayVersion under Microsoft\Windows NT\CurrentVersion in the SOFTWARE hive: build 22621 is 22H2. On older systems, look at the Compatibility Assistant Store key instead, which exists from Windows 8.
2. It was not a GUI shell launch
This site calls a GUI shell launch a program start made through the Windows graphical interface: a double-click in File Explorer, a Start menu, taskbar or desktop shortcut, or a program opened from another program's window. It describes observed behaviour; it is not a Microsoft term. Sygnia's tests give the list:
| How the program was started | Line in PcaAppLaunchDic.txt |
|---|---|
| Double-click in File Explorer, other GUI starts | Yes |
| GUI start inside an RDP session | Yes |
| From Google Chrome's downloads page | Yes |
| From the 7-Zip window | Yes |
| From a command line (cmd.exe, PowerShell) | No |
| By a scheduled task | No |
| Remotely, including with PsExec | No |
| As a child of another program | No line of its own |
Kaspersky describes the scope more narrowly, as launches "executed through Windows File Explorer", and also found no console launches. Launches from the Run dialog (Win+R) go through the shell, but no public test covers them. Services and WMI were not part of the published tests; they are not GUI launches either, so do not expect a line.
The other side of the rule: a line suggests someone started the program interactively, at the screen or over RDP, and a tool you double-click on a suspect system gets a line too.
On FIN-WKS-07, the fictional workstation used on this site, C:\Users\svc_backup\Downloads\tools\PsExec64.exe ran at 10:21:03 UTC from a cmd.exe window. It has no line in PcaAppLaunchDic.txt; BAM, under svc_backup's SID, and Prefetch have it.
3. It was started by another program
A child process gets no line of its own. On FIN-WKS-07, alice's double-click on Invoice_2026-0914.pdf.exe at 09:12:07 is recorded; the powershell.exe it started at 09:12:31 is not. The PcaGeneralDb files are different: public samples show abnormal-exit records for programs that were probably started by other programs, such as git.exe under GitHub Desktop. Search them too.
4. It is a built-in program run from its own folder
Sygnia found that "some built-in applications are not registered when executed from their original directory". The list is not published. Andrew Rathbun's published file does contain C:\Windows\System32\msiexec.exe, so it is not all of System32. A missing line for a Windows program says nothing. On FIN-WKS-07, neither cmd.exe, opened from the Run dialog at 10:02:16, nor mstsc.exe, started at 10:18:40, has a line; BAM, under svc_backup's SID, has both.
5. A later launch replaced it
There is one line per path, with the last launch. If you expect a launch at 10:06 and the line says 10:39, the 10:06 launch may well have happened. On FIN-WKS-07, svc_backup's Windows Timeline shows 7-Zip File Manager open at 10:06:40; PcaAppLaunchDic.txt only keeps 10:39:25.
6. Recording stopped
- A non-ANSI path. Sygnia found that launching a program whose path contains a character outside the ANSI code page writes a truncated line, and that no new program is added after it. Look for a line without a pipe.
- PcaSvc was not running. PcaSvc is the Program Compatibility Assistant Service. Microsoft's service guidance describes it as monitoring "programs installed and run by the user", adds "If you stop this service, PCA stops working", and gives its startup type as Automatic. Rathbun's first write-up says the files populate as long as it runs, and Microsoft's policy documentation adds that PCA also needs the Diagnostic Policy Service. On a live system,
sc query pcasvcandsc qc pcasvcshow its state and start type. On an image, read theStartvalue underServices\PcaSvcin the SYSTEM hive (2 automatic, 3 manual, 4 disabled) and the Service Control Manager events in the System log. A disabled PcaSvc on a workstation is a change worth explaining. Never stop it on a system under investigation. - PCA was turned off by policy. The "Turn off Program Compatibility Assistant" policy sets
DisablePCAunderSoftware\Policies\Microsoft\Windows\AppCompat(Microsoft). Whether it stops the text files is not documented; a recentDisablePCAvalue deserves the same question as a disabled service.
7. The file was changed
The files are plain text. An administrator can delete a line or the whole file. Compare with the USN journal, Volume Shadow Copies and the per-user registry keys.
8. You searched for the wrong path
PcaAppLaunchDic.txt keeps the path as launched, with its drive letter: a tool run from a USB drive is under E:\, not C:\. The PcaGeneralDb files lowercase paths, drop the drive letter and replace user folders with placeholders. Search by file name first.
How PCA compares
| Source | Location | What it records | User | Times | Main limits |
|---|---|---|---|---|---|
PcaAppLaunchDic.txt | C:\Windows\appcompat\pca\ | GUI shell launches (Windows 11 22H2+) | No | Last launch per path, UTC | One time per path; no CLI launches; plain text |
PcaGeneralDb0/1.txt | Same folder | Abnormal exits, failed installers, other PCA events | No | Per record, UTC | Clean exits leave nothing; 2 to 4 MB history |
| Compatibility Assistant Store | NTUSER.DAT | Programs PCA dealt with for that user (Windows 8+) | Yes | Key LastWrite; value data undocumented | Trigger not documented |
| UserAssist | NTUSER.DAT, ...\Explorer\UserAssist | Programs started through File Explorer and the Start menu | Yes | Last run, run count | ROT13-encoded names; GUI only |
| BAM | SYSTEM, Services\bam\State\UserSettings\<SID> | Programs run in a user's session, whatever the launch method (Windows 10 1709+) | Yes, by SID | Last run per path | Last run only |
| Prefetch | C:\Windows\Prefetch\ | Any process start, when prefetching is on | No | Up to eight last runs and a run count (Windows 8+) | Often off on servers; limited number of files |
| Amcache | C:\Windows\appcompat\Programs\Amcache.hve | Programs and files Windows inventoried | No | Various, not run times | Shows presence, not execution |
| ShimCache | SYSTEM, Control\Session Manager\AppCompatCache | Files the compatibility engine checked | No | File modification time | Presence, not execution, on Windows 10 and 11; written at shutdown |
| AppCompatFlags Layers | NTUSER.DAT, SOFTWARE | Compatibility settings chosen for a path | Yes, in NTUSER.DAT | Key LastWrite only | A setting, not a launch |
Two observations from the table:
- PCA and UserAssist overlap (both are about GUI launches), but PCA is machine-wide with one UTC time per path, and UserAssist is per user with a run count. When both record a program, they should broadly agree on the last launch.
- Prefetch and BAM cover the gaps. A tool run from cmd.exe or by PsExec is where PCA is blind and they are not.
A practical order for "did it run?"
- Prefetch, if enabled: any launch method, run count, up to eight times.
- BAM: last run per user.
PcaAppLaunchDic.txt: last GUI launch, machine-wide, with a precise time.- UserAssist and the Compatibility Assistant Store: GUI launches and PCA entries per user.
PcaGeneralDb: whether it crashed or exited with an error.- Process creation events (Security 4688, Sysmon 1) and EDR, when they exist: parent, command line, user.
- Amcache and ShimCache: that the file was there, its hash, when other sources are silent.
Three rules keep a report honest. Absence is weak: every source misses some launches, so say which sources you checked before you say something did not run. Presence is not execution: Amcache and ShimCache list files Windows looked at, and a Layers value is a request, not a run. Two independent sources that agree make a finding; one source alone is a lead. And state the time zone of every time you quote: the PCA text files are UTC according to published research.
FAQ
Why is a program in Prefetch but not in PcaAppLaunchDic.txt?
Most often because it was not started from the graphical shell: from cmd.exe or PowerShell, by a scheduled task, remotely, or as a child of another program. Prefetch records any process start when prefetching is on; PcaAppLaunchDic.txt records GUI launches only. Some built-in Windows programs are also left out when run from their original folder.
Does an empty or missing PcaAppLaunchDic.txt mean nothing ran?
No. Check the Windows version first: the file exists from Windows 11 22H2. Then check whether PcaSvc was running, whether the file was deleted or edited, and whether a non-ANSI path stopped new lines being added.
Does Windows 10 have PCA traces?
Not the text files in C:\Windows\appcompat\pca, which appeared in Windows 11 22H2. Windows 10 has the per-user Compatibility Assistant Store key and the AppCompatFlags Layers key.
Which artifact should I trust for evidence of execution?
None alone. Prefetch, BAM, the PCA launch log and UserAssist each record a different subset of launches, and Amcache and ShimCache mostly show presence. Agreement between two independent sources is what makes a finding solid.
Related articles
Frequently asked questions
Why is a program in Prefetch but not in PcaAppLaunchDic.txt?
Most often because it was not started from the graphical shell: from cmd.exe or PowerShell, by a scheduled task, remotely, or as a child of another program. Prefetch records any process start when prefetching is on; PcaAppLaunchDic.txt records GUI launches only. Some built-in Windows programs are also left out when run from their original folder.
Does an empty or missing PcaAppLaunchDic.txt mean nothing ran?
No. Check the Windows version first: the file exists from Windows 11 22H2. Then check whether PcaSvc was running, whether the file was deleted or edited, and whether a non-ANSI path stopped new lines being added.
Does Windows 10 have PCA traces?
Not the text files in C:\Windows\appcompat\pca, which appeared in Windows 11 22H2. Windows 10 has the per-user Compatibility Assistant Store key and the AppCompatFlags Layers key.
Which artifact should I trust for evidence of execution?
None alone. Prefetch, BAM, the PCA launch log and UserAssist each record a different subset of launches, and Amcache and ShimCache mostly show presence. Agreement between two independent sources is what makes a finding solid.