Failure to add Start Menu asInvoker

[musabio]

I created an install package whose UAC Execution Level is set to "asInvoker" to avoid requiring elevation. (It doesn't install any modules into protected locations, except the Start Menu.) Under Windows 10 it works fine for non-administrator users, but when run by a administrator, it fails to add the Group and Program items to the Start Menu.

Does that make sense? Is there a way around? Can I request elevation only for administrator users?

Thanks,
Jack

[linder]

Jack,

to handle a real asInvoker "per-user" (instead of a "machine wide") install, you can switch the installer into "per-user mode" and this will create the Add/Remove Programs entry and Shortcuts for the current user.

1. Set "UAC Execution Level" to "asInvoker" and make sure you do not install into a "protected" folder.

2. In the Script Editor, use "Set Installer Flag..." to switch the installation into per-user mode (do not mark the "Set Flag" checkbox option for the $SB_ALLUSERFLAG$" flag).



This will create a "per-user" item for the current user.

Does this help?

Friedrich

[musabio]

Friedrich -

Worked like a charm! Thank you!

-Jack

[linder]

Jack,

PERFECT! Thanks for the update.

Friedrich