Vista considerations

From ISXKB

(Difference between revisions)
Jump to: navigation, search
(Added a link to the real KB)
(Added Types of Installer)
Line 5: Line 5:
Due to this permission elevation, anything run from the install will also run with full access to the system. Whether your application is "Vista compatible" or not, this is a very bad idea.
Due to this permission elevation, anything run from the install will also run with full access to the system. Whether your application is "Vista compatible" or not, this is a very bad idea.
Unfortunately, Microsoft "forgot" to add the ability for en elevated application to drop them when running anything else so the only way around this is to add the OnlyBelowVersion: 0,6 on the [Run] entry to so the option is not available on vista.
Unfortunately, Microsoft "forgot" to add the ability for en elevated application to drop them when running anything else so the only way around this is to add the OnlyBelowVersion: 0,6 on the [Run] entry to so the option is not available on vista.
 +
 +
== Types of Installer ==
 +
With the changes made in Vista, essentially now only two different "classes" of installer can be used:
 +
* '''Administrative'''
 +
** Runs with admin permissions (use PrivilegesRequired=admin)
 +
** Is expected to make changes to per-machine areas such as Program Files, HKLM, and/or the All Users profile
 +
** ''Must not'' make changes to per-user areas such as HKCU and the current user's profile
 +
** Fully supported by Inno Setup (all versions, although 5.1.9 and above is best under Vista)
 +
* '''Standard user'''
 +
** Runs with standard user permissions (use PrivilegesRequired=none)
 +
** Is expected to make changes to per-user areas such as HKCU and the current user's profile
 +
** ''Must not'' make changes to per-machine areas such as Program Files, HKLM, and/or the All Users profile
 +
** Not currently supported by Inno Setup.
== See also ==
== See also ==
* [http://www.jrsoftware.org/iskb.php?vista Inno Setup KB]
* [http://www.jrsoftware.org/iskb.php?vista Inno Setup KB]

Revision as of 21:33, 7 February 2007

Windows Vista now includes a far stricter LUA system. This pretty much stops all applications making system wide changes without asking the user.

Inno 5.1.9 and later handles this fully for the install, and asks for elevated permissions so it can write anything it needs.

Due to this permission elevation, anything run from the install will also run with full access to the system. Whether your application is "Vista compatible" or not, this is a very bad idea. Unfortunately, Microsoft "forgot" to add the ability for en elevated application to drop them when running anything else so the only way around this is to add the OnlyBelowVersion: 0,6 on the [Run] entry to so the option is not available on vista.

Types of Installer

With the changes made in Vista, essentially now only two different "classes" of installer can be used:

  • Administrative
    • Runs with admin permissions (use PrivilegesRequired=admin)
    • Is expected to make changes to per-machine areas such as Program Files, HKLM, and/or the All Users profile
    • Must not make changes to per-user areas such as HKCU and the current user's profile
    • Fully supported by Inno Setup (all versions, although 5.1.9 and above is best under Vista)
  • Standard user
    • Runs with standard user permissions (use PrivilegesRequired=none)
    • Is expected to make changes to per-user areas such as HKCU and the current user's profile
    • Must not make changes to per-machine areas such as Program Files, HKLM, and/or the All Users profile
    • Not currently supported by Inno Setup.

See also

Personal tools
Ads: