AdminUser or Privileged Launch Condition

AdminStudio 2023 | 25.0 | Application Manager

Note:This test is not applicable to App-V packages.

For this Operating System Compatibility test, the Windows Installer database is scanned for the presence of launch conditions that use the AdminUser or Privileged properties and that may prevent installation on the specified Windows operating system.

Test Group/Test Category

0349—Operating System Compatibility/Windows 8.1 (32-Bit)
0449—Operating System Compatibility/Windows 8.1 (64-Bit)
0549—Operating System Compatibility/Windows Server 2012
0649—Operating System Compatibility/Windows Server 2016
1049—Operating System Compatibility/Windows Server 2019
2849—Operating System Compatibility/Windows 10-1809 (and 2019 LTSC) (32-Bit)
5649—Operating System Compatibility/Windows 10-20H2 (32-Bit)
5849—Operating System Compatibility/Windows 10-21H1 (32-Bit)
7049—Operating System Compatibility/Windows 10-21H2 (32-Bit)
7249—Operating System Compatibility/Windows 10-22H2 (32-Bit)
2949—Operating System Compatibility/Windows 10-1809 (and 2019 LTSC) (64-Bit)
5749—Operating System Compatibility/Windows 10-20H2 (64-Bit)
5949—Operating System Compatibility/Windows 10-21H1 (64-Bit)
7149—Operating System Compatibility/Windows 10-21H2 (64-Bit)
7349—Operating System Compatibility/Windows 10-22H2 (64-Bit)
6749—Operating System Compatibility/Windows 11-21H2 (64-Bit)
7449—Operating System Compatibility/Windows 11-22H2 (64-Bit)

Severity

Warning

Messages

This Windows Installer database contains LaunchCondition [LAUNCHCONDITION_NAME] using AdminUser property (Table: LaunchCondition, Key: [LAUNCHCONDITION_CONDITION]).
This Windows Installer database contains LaunchCondition [LAUNCHCONDITION_NAME] using Privileged property (Table: LaunchCondition, Key: [LAUNCHCONDITION_CONDITION]).

Background

The Windows Installer properties AdminUser and Privileged may be used to prevent users who do not have administrator or elevated privileges from running the installation. These properties should not be used in the LaunchCondition table because Windows Installer may initially spoof their value during evaluation of the LaunchCondition table and set both to 1 even if the user is not an administrator and has not received elevated privileges yet. This behavior is present because privileges are elevated much later, and the result of authentication is not known when initial launch conditions are evaluated.

Resolution

The following resolutions are available. Note that this issue is not resolved automatically by default.

Manual Fix

A LaunchCondition table entry that uses the AdminUser or Privileged properties should be migrated to a type 19 custom action that uses the following condition:

NOT Privileged

Basic Auto Fix

No resolution is available.

Advanced Auto Fix

No resolution is available.

See Also