Using the SpecificInstaller Fix
Published: June 11, 2010
Updated: June 11, 2010
Applies To: Windows 7, Windows Vista
This section includes information about using the SpecificInstaller compatibility fix, including the usage and API-related information.
The SpecificInstaller compatibility fix enables you to flag an application to appear as a legacy application installation program. After the file is flagged, the SpecificInstaller compatibility fix can apply Setup mitigations, which include running the application as an administrator and applying the WRPMitigation compatibility fix.
|You can apply this compatibility fix to any application that is not automatically detected by the GenericInstaller function.|
Investigating the Issue
The SpecificInstaller compatibility fix should be considered as a possible resolution if your application is designed to be a setup application, but it is neither manifested nor detected by the GenericInstaller function.
None. This compatibility fix does not intercept any APIs. Instead, it applies a loader flag to the application.
Fixing Your Code
Applications should be modified to use Microsoft® Windows® Installer (.msi file) technology, as defined by the Windows logo guidelines. If however, your application requires an executable (.exe) installation file, you should create a manifest that includes the requireAdministrator function to perform the installation.
|Be aware that validating the signature might take a long time if your application installation file is relatively large and is digitally signed, which is frequently the case for self-extracting executable files. In this situation, you should create a manifest that includes the asInvoker function, with a smaller executable file inside that includes the requireAdministrator function. You can then use the requireAdministrator function to start additional executable files that will inherit the administrator token.|