1

I'm running into the Windows Vista/7 Program Compatibility Assistant problem described here:

"This program might not have installed correctly" message in Windows 7 RC

The solution (backed-up by similar questions elsewhere, and MSDN), is apparently to add a 'compatibility' section to setup.exe's manifest. InstallShield 10 SP1 does this automatically, but unfortunately I only have InstallShield 2009.

How would I go about editing the manifest? Is there a way to do this programmatically, so I can integrate it into my build?

Community
  • 1
  • 1
DNS
  • 37,249
  • 18
  • 95
  • 132

4 Answers4

2

Look for the files named setupexe.*.manifest (Support or Program subfolder of InstallShield, I think) and edit or replace them. The appropriate one is selected and incorporated into setup.exe during build.

Michael Urman
  • 15,737
  • 2
  • 28
  • 44
  • 1
    Looks like they're in (by default) C:\Program Files\InstallShield\2009\Support, and are called SetupExe..manifest, where is one of Admin, Highest or Invoker. Which one is used depends on what you selected in Release options. http://kb.flexerasoftware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q205850&sliceId= – DNS Jun 01 '10 at 15:54
1

There is this tool from InstallShield that can update the manifest. Or a direct link here: isreman. The provided example manifests do not supply the application compatibility section, though.

Community
  • 1
  • 1
user281806
  • 1,020
  • 9
  • 14
1

Yes, just use mt.exe from the Windows SDK.

saschabeaumont
  • 22,080
  • 4
  • 63
  • 85
0

a manifest file could be outside the exe, in the same path, or inside, in the resources of an exe.

OlimilOops
  • 6,747
  • 6
  • 26
  • 36
  • InstallShield places a manifest in its bootstrap's resources. So since Vista (and possibly XP, I keep forgetting the cutoff) any external manifest will be ignored. – Michael Urman Jun 01 '10 at 12:49