Program Compatibility Assistant Service
This service supports the Program Compatibility Assistant (PCA).
since 0.9.8.11
Purpose
Identifier: PcaSvc
Setup Foundry sets the startup type to Manual; the service remains installed and can still be started on demand.
This service supports the Program Compatibility Assistant (PCA). PCA monitors installed and executed desktop programs for known compatibility problems. When Windows detects such a problem, the assistant can notify the user and recommend or apply appropriate compatibility settings.
This is particularly relevant to older applications and installers that, for example, expect an earlier Windows version, request privileges incorrectly, or fail because Windows system behavior has changed.
Notes
Additional effects
Microsoft states that both PcaSvc and the Diagnostic Policy Service (DPS) must be running for Program Compatibility Assistant to operate.
The broader Windows application-compatibility infrastructure includes other components and databases. PcaSvc should therefore not be confused with the complete compatibility assessment performed by Windows Setup or Windows Update.
Privacy and security
Program Compatibility Assistant processes information about installed or executed programs, detected failures, and compatibility settings. Microsoft’s Windows 8 documentation also described telemetry—subject to the diagnostic and CEIP settings used at that time—which could include information about the application, its installer, the detected issue, and the compatibility settings applied.
That historical description should not be assumed to apply unchanged to current Windows releases. Diagnostic transmission on current versions depends on the Windows release and its configured diagnostic-data settings. Microsoft’s service documentation does not identify a separate network destination that PcaSvc always contacts.
Setting the service to Manual does not reliably prevent this processing or transmission. Windows or an application can start the service on demand, after which it can perform its normal work.
Effects of the change
The service is not disabled. It is no longer started merely as an automatic-start service, but Windows components and applications can still request it through the Service Control Manager. Once started this way, Program Compatibility Assistant can generally operate normally.
While PcaSvc is not running, Program Compatibility Assistant cannot monitor programs as intended. Notifications about known compatibility problems and suggested or automatically applied mitigations may therefore be delayed or absent. This is most likely to be noticeable with older desktop applications, installers, and uninstallers. An affected program might continue to fail instead of being run again with suitable compatibility settings.
Applications that do not encounter a compatibility condition handled by PCA are normally not directly affected. Changing the startup type alone also does not terminate applications that are already running.
Notes
Changing the startup type does not automatically stop an instance of the service that is already running. The effect therefore becomes apparent after that instance stops or after Windows restarts.
Microsoft’s detailed catalogue of PCA scenarios applies to Windows 8. The service’s general role remains documented, but individual detection and mitigation mechanisms can differ in newer Windows releases.
Microsoft documentation
Microsoft Learn: Security guidelines for system services – Program Compatibility Assistant Service
Microsoft Learn: ADMX_AppCompat Policy CSP – Turn off Program Compatibility Assistant
Microsoft Learn: Program Compatibility Assistant scenarios