Archive: vista installer detection


vista installer detection
Hi, I have been struggling (to no avail) to find a way to get around Vista's Installer detection (without modifying local computer settings). The problem is that after the installer completes, it pops up a window saying "This Program Might Not Have Installed Correctly.". From what I read here: (http://209.85.165.104/search?q=cache...ient=firefox-a)

this is because my installer doesn't add anything to the Add Remove Programs and thus Vista concludes that the installer failed (brilliant!).

Creating a manifest didn't help, get the same popup.

Does anybody know of a way to get around this or perhaps a way to trick vista into not detecting the installer?

thanks!
Mark


The manifest is the only way to get around it as it disables the compatibility mode. Try it again with RequestExecutionLevel.


Hi Kickik, I'm still getting the problem. Here's the contents of manifest I'm using:

Executable: test.exe
Manifest:test.exe.manifest
Sample application manifest file:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity version="1.0.0.0"
processorArchitecture="X86"
name="test.exe"
type="win32"/>
<description>CCT installer</description>
<!-- Identify the application security requirements. -->
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges>
<requestedExecutionLevel
level="requireAdministrator"
uiAccess="true"/>
</requestedPrivileges>
</security>
</trustInfo>
</assembly>


This is in a test.exe.manifest file residing in the same directory as the test.exe file. Am I doing something wrong?

thanks for your help!
Mark


The embedded manifest probably overrides it. Use RequestExecutionLevel in the script to add the Vista nodes to the embedded manifest.


thanks Kickik, do you know of a good way to inject a manifest file into an existing installer exe?

thanks,
Mark


You can use Resource Hacker to do that.


thanks Kickik,

Using RequestExecutionLevel in my installer script worked perfectly!

-Mark