Windows Application Compatibility (Standard 7 Package Reference)
7/8/2014
This package is a Feature Pack in the category Management. The name of the package as it appears on disk and for use with some command-line tools is WinEmb-Installers-AppCompat.
This package includes the Microsoft Windows Application Compatibility Infrastructure (frequently referred to as the Shim Infrastructure), which is used to help with application and driver compatibility on newer editions of Windows. An application compatibility database (with supporting APIs) of applications, drivers, BIOS versions, and Plug and Play devices is included in this package, although many of the optional, supporting packages include additional shims. Including the optional Windows Installer package provides the user interface of the Compatibility tab for an application's property page.
Settings
No settings provided.
Services
- Program Compatibility Assistant Service
Dependencies
Package Dependencies
No package dependencies.
Group Dependencies
No group dependencies.
Optional Supporting Packages
You can select any number of packages from the following list:
- .NET Framework 2.0 Client Profile
- Active Directory Rights Management
- Common Diagnostic Tools
- Graphics Platform
- Windows Installer
You can use the optional packages to enable the following functions:
To do this |
Use these packages |
---|---|
Use the Compatibility tab provided by the Windows Application Compatibility package. |
|
Provide mitigation functionality that lets certain applications run in compatibility mode. |
.NET Framework 2.0 Client Profile
Important:
The user must test the application using one of the above packages at a time to determine which package enables their application to run.
|
Use the User Action Recorder tool. |
|
Use the Program Compatibility Assistant user interface. |
Common Uses
Notes
On devices using File-Based Write Filter (FBWF), Enhanced Write Filter with HORM (EWF), or Registry Filter to protect volumes, folders, or files, any mitigation information (shims) added to the application compatibility database might not be persisted after a system restart.