Skip to content

PcaAppLaunchDic.txt Explained: The Windows 11 Launch Log

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.

Published on 9 min read

TL;DR. C:\Windows\appcompat\pca\PcaAppLaunchDic.txt is a plain-text file that Windows 11 22H2 and later keeps up to date: one line per executable path, in the form path|YYYY-MM-DD HH:MM:SS.fff, holding the last time that program was launched, in UTC. The Program Compatibility Assistant service, PcaSvc, writes it for programs started from the graphical shell, not for programs started from a command line, a scheduled task or PsExec. It has no user, no run count and no earlier runs, and it is written in a single-byte ANSI code page, not UTF-16. PCA Parser reads it in your browser together with the other PCA traces.

This article is the entry point to the series. Each section links to a deeper one.

The Program Compatibility Assistant

The Program Compatibility Assistant (PCA) is a Windows feature introduced in Windows Vista. It watches programs as users run them and offers fixes when it detects a known compatibility problem: an installer that fails, a program that needs administrator rights, an old program that checks the Windows version. Microsoft describes it in its Vista-era documentation and its Windows 8 scenarios page. The work is done by the Program Compatibility Assistant Service, service name PcaSvc, which runs inside a svchost.exe process and starts automatically.

To do that work, PCA keeps records, and those records are what investigators read:

TraceWindowsHoldsCovered in
PcaAppLaunchDic.txt11 22H2 and laterLast GUI launch time per executable path, machine-wideThis article
PcaGeneralDb0.txt, PcaGeneralDb1.txt11 22H2 and laterAbnormal exits, failed installers and other PCA eventsPcaGeneralDb files
Compatibility Assistant Store (Persisted on Vista and 7)Vista and laterPer user: the programs PCA dealt withStore and Persisted keys
AppCompatFlags LayersVista and laterCompatibility modes and RUNASADMIN set per executable, by users or by PCAAppCompatFlags Layers

Where it is and since when

The file sits in C:\Windows\appcompat\pca\, next to two others:

FileContentEncoding
PcaAppLaunchDic.txtOne line per program: path and last launch timeANSI (CP-1252), per Sygnia and Kaspersky
PcaGeneralDb0.txt, PcaGeneralDb1.txtA log of abnormal exits, failed installers and other PCA events (PcaGeneralDb files)UTF-16LE

Andrew Rathbun and Lucas Gonzalez described the folder in January 2023 on AboutDFIR. They found no trace of it in Windows 11 21H2 (build 22000.978) and found it in 22H2 (build 22621.382). The KAPE target AppCompatPCA credits a member of the Digital Forensics Discord with noticing it, and notes that it appears to be Windows 11 only. Harel Segev of Sygnia then documented the format in November 2023 in Diving into the new Windows 11 PCA artifact, from tests and partial reverse engineering on 22H2 and 23H2 builds. Kaspersky's October 2025 overview, Windows 10 EOL and Windows 11 forensic artifacts, describes the same file on 24H2. Microsoft has not documented any of it.

The format

C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE|2026-09-14 08:58:40.517
C:\Users\alice\Downloads\Invoice_2026-0914.pdf.exe|2026-09-14 09:12:07.204
C:\ProgramData\Intel\m64.exe|2026-09-14 10:09:44.118
C:\Users\Public\rclone.exe|2026-09-14 10:47:12.045

These lines come from FIN-WKS-07, the fictional Windows 11 workstation used in the examples on this site. Each line is the full path of the executable, a pipe, and a time. Windows file names cannot contain |, so splitting a line at the pipe is safe.

What the published research and samples show:

  • One line per path, updated in place. Rathbun watched the line for Everything.exe change as soon as he ran it. A second launch of the same path replaces the time; it does not add a line.
  • The path keeps its drive letter and case. Rathbun published the file from his own machine in the DFIRArtifactMuseum repository. It has paths on K:, M:, V: and Z:, and packaged apps under C:\Program Files\WindowsApps.
  • The lines are not in time order. In that same file, lines from May sit between lines from December. Sort by the time column before reading.
  • The time has milliseconds. Sygnia writes the format as YYYY-MM-DD HH:MM:SS.f; the published files carry three decimals.

Encoding

Sygnia and Kaspersky describe the file as ANSI (code page 1252) with Windows line endings. Some write-ups and community parsers describe it as UTF-16LE. The file Rathbun published is single-byte text, which matches Sygnia. Whether a machine set to another ANSI code page, Cyrillic or East Asian for example, writes in that code page instead of 1252 is not documented. A parser should look at the bytes before choosing a decoding. The two PcaGeneralDb files are UTF-16LE: the same folder holds two encodings.

What gets a line

Sygnia's tests give the clearest list:

How the program was startedLine in PcaAppLaunchDic.txt
From the GUI (File Explorer, desktop, Start menu)Yes
From the GUI inside an RDP sessionYes
From Google Chrome's downloads pageYes
From the 7-Zip windowYes
From a command lineNo
By a scheduled taskNo
Remotely, including with PsExecNo

Kaspersky puts it more narrowly, as launches "executed through Windows File Explorer". This site calls the recorded kind a GUI shell launch.

Two consequences follow:

  • A child process gets no line. On FIN-WKS-07, alice double-clicked Invoice_2026-0914.pdf.exe at 09:12:07, and that launch has a line. The powershell.exe it started at 09:12:31 has none.
  • Some built-in programs are missing. Sygnia found that "some built-in applications are not registered when executed from their original directory". Which ones, and why, is not documented. Rathbun's file does contain C:\Windows\System32\msiexec.exe and C:\Windows\SysWOW64\msiexec.exe, so System32 is not excluded as a whole. A missing line for a Windows program means nothing on its own.

All the reasons a program can be absent are in why a program is missing from PCA.

The time

  • Last launch only. Earlier launches of the same path are gone. Prefetch keeps up to eight run times; use it for history.
  • UTC. Sygnia and Kaspersky both say so. No public source has checked every build, so test it on one machine where you know a launch time before you put seconds in a report.
  • Start, not exit, as far as anyone has shown. Rathbun saw the line change when the program started. A 2025 blog post states that the time is written when the process ends, without showing a test. If the difference matters, check it on a lab machine of the same build.

What the file does not tell you

QuestionWhere to look instead
Which user?The path, if it is in a profile; the Compatibility Assistant Store key in each NTUSER.DAT; UserAssist; BAM
How many times?Prefetch run count
Earlier runs?Prefetch, event logs, EDR
Which file exactly (hash, signer)?Amcache, the file itself
Started by what?Process creation events (Security 4688, Sysmon 1), EDR
Did it succeed?PcaGeneralDb abnormal-exit records, the program's own output

How these sources compare is in why a program is missing from PCA.

The non-ANSI bug

Sygnia ran a program whose path contained a character outside the ANSI code page. The line was cut at that character, with no pipe and no time. From then on, no new program was added to the file, while the times of existing lines kept updating. Sygnia calls it a bug rather than intended behaviour. Kaspersky reports the same on 24H2: such a path "breaks" the file.

In practice:

  • Look for a line with no pipe. It marks the point after which new programs stopped being recorded.
  • In that case, the absence of a program says even less than usual, and the file's modification time still moves.

Trust and tampering

The file is plain text under C:\Windows. An administrator can edit a line, delete one, or delete the file, and nothing in it would show. PcaSvc can also be stopped. Check the file against other sources:

  • the file's own times, and $UsnJrnl:$J records for PcaAppLaunchDic.txt;
  • older copies in Volume Shadow Copies (Velociraptor's Windows.System.AppCompatPCA artifact can search them);
  • the per-user registry keys, which an intruder editing the text file may forget.

Microsoft's "Turn off Program Compatibility Assistant" policy (registry value DisablePCA under Software\Policies\Microsoft\Windows\AppCompat) turns PCA off; whether it also stops these text files is not documented. How to check the service and the policy is in why a program is missing from PCA.

Reading it

# Windows PowerShell 5.1: Default is the system ANSI code page
Get-Content C:\Windows\appcompat\pca\PcaAppLaunchDic.txt -Encoding Default

# PowerShell 7: name the code page
Get-Content C:\Windows\appcompat\pca\PcaAppLaunchDic.txt -Encoding 1252 |
  ConvertFrom-Csv -Delimiter '|' -Header Path, LastLaunchUtc |
  Sort-Object LastLaunchUtc

Microsoft's Get-Content reference documents numeric code pages for -Encoding from PowerShell 6.2. Do not use -Encoding Unicode on this file: that is for the PcaGeneralDb files.

PCA Parser reads the file with the two PcaGeneralDb files and the AppCompatFlags keys of NTUSER.DAT and SOFTWARE hives, joins them per executable and shows a timeline. To collect everything, see collecting the PCA folder and AppCompatFlags keys.

FAQ

Does PcaAppLaunchDic.txt record programs started from cmd.exe or PowerShell?

Not in Sygnia's tests: programs started from a command line, by a scheduled task or remotely with PsExec were not recorded, while launches from the GUI, inside an RDP session, from Chrome's downloads page and from the 7-Zip window were. A program started by another program, such as a PowerShell process started by a dropper, does not get a line of its own either.

Is the time in PcaAppLaunchDic.txt UTC?

Sygnia (Windows 11 22H2 and 23H2) and Kaspersky (24H2) both describe it as UTC. No public source has checked every build, so confirm it on a host where you know when a program was started.

Which user launched the program?

The file does not say. There is one file for the whole machine. Take the user from the path when it is inside a profile, or from per-user traces such as the Compatibility Assistant Store key, UserAssist or BAM.

Why would PcaAppLaunchDic.txt stop getting new lines?

Sygnia found that launching a program whose path has a character outside the ANSI code page writes a truncated line with no time, after which new programs are no longer added while existing lines still update. Kaspersky reported the same behaviour on Windows 11 24H2. Look for a line without a pipe.

Frequently asked questions

Does PcaAppLaunchDic.txt record programs started from cmd.exe or PowerShell?

Not in Sygnia's tests: programs started from a command line, by a scheduled task or remotely with PsExec were not recorded, while launches from the GUI, inside an RDP session, from Chrome's downloads page and from the 7-Zip window were. A program started by another program, such as a PowerShell process started by a dropper, does not get a line of its own either.

Is the time in PcaAppLaunchDic.txt UTC?

Sygnia (Windows 11 22H2 and 23H2) and Kaspersky (24H2) both describe it as UTC. No public source has checked every build, so confirm it on a host where you know when a program was started.

Which user launched the program?

The file does not say. There is one file for the whole machine. Take the user from the path when it is inside a profile, or from per-user traces such as the Compatibility Assistant Store key, UserAssist or BAM.

Why would PcaAppLaunchDic.txt stop getting new lines?

Sygnia found that launching a program whose path has a character outside the ANSI code page writes a truncated line with no time, after which new programs are no longer added while existing lines still update. Kaspersky reported the same behaviour on Windows 11 24H2. Look for a line without a pipe.

Related articles

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.
How to read PcaGeneralDb0.txt and PcaGeneralDb1.txt on Windows 11: the eight fields, record types 0 to 4, redacted paths, rotation, and what is still unknown.
How AppCompatFlags Layers stores compatibility modes and Run as administrator per executable, in NTUSER.DAT and SOFTWARE, and how to read it as evidence.