Skip to main content

Hard-Coded Paths in Script-Based Custom Actions

AdminStudio 2025 R2 | 30.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 hard-coded paths inside script-based custom actions.

Test Group/Test Category​

  • 2826—Operating System Compatibility/Windows 10-1809 (and 2019 LTSC) (32-Bit)

  • 7026—Operating System Compatibility/Windows 10-21H2 (32-Bit)

  • 7226—Operating System Compatibility/Windows 10-22H2 (32-Bit)

  • 2926—Operating System Compatibility/Windows 10-1809 (and 2019 LTSC) (64-Bit)

  • 7126—Operating System Compatibility/Windows 10-21H2 (64-Bit)

  • 7326—Operating System Compatibility/Windows 10-22H2 (64-Bit)

  • 7426—Operating System Compatibility/Windows 11-22H2 (64-Bit)

  • 7526—Operating System Compatibility/Windows 11-23H2 (64-Bit)

  • 7626—Operating System Compatibility/Windows 11-24H2 (64-Bit)

  • 0526—Operating System Compatibility/Windows Server 2012

  • 0626—Operating System Compatibility/Windows Server 2016

  • 1026—Operating System Compatibility/Windows Server 2019

Severity​

Warning

Messages​

  • This Windows Installer database contains a hard-coded path [PATH] in a script-based custom action [CUSTOM_ACTION_KEY] stored in property [PROPERTY] (Table: CustomAction, Key: [CUSTOM_ACTION_KEY]; Table: Property, Key: [PROPERTY]).

  • This Windows Installer database contains a hard-coded path [PATH] in a script-based custom action [CUSTOM_ACTION_KEY] (Table: CustomAction, Key: [CUSTOM_ACTION_KEY]).

  • This Windows Installer database contains a hard-coded path [PATH] in a script-based custom action [CUSTOM_ACTION_KEY] stored in a binary stream [STREAM] (Table: CustomAction, Key: [CUSTOM_ACTION_KEY]; Table: Binary, Key: [BINARY_KEY]).

  • This Windows Installer database contains a hard-coded path [PATH] in a script-based custom action [CUSTOM_ACTION_KEY] installed within this product (Table: CustomAction, Key: [CUSTOM_ACTION_KEY]; Table: File, Key: [FILE_KEY]).

Background​

During migration to a new environment, some paths might have changed or became obsolete, eventually causing hard-coded values in script-based custom actions to no longer be valid. This could result in installation failures or functionality issues.

note

ICE48 checks for directories that are hard-coded to local paths.

Resolution​

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

Manual Fix​

All hard-coded paths in script-based custom actions should be replaced with Windows Installer properties or environment variables.

Basic Auto Fix​

No resolution is available.

Advanced Auto Fix​

No resolution is available.

See Also

ICE48

Windows Installer Internal Consistency Evaluators