UILevel may be set incorrectly - Advanced Installer Community
alco
Posts: 80
Joined: Thu Nov 18, 2010 5:02 pm

UILevel may be set incorrectly

In my Win10, when I run the installer w/ full UI, UILevel is set to 5 per the log - this is fine. But if I run the same installer in my Win7 w/ full UI, UILevel is set to 2. Is this a bug?

The installer is built using AI v16.0

This oddity causes my custom action, w/c is only supposed to run when UILevel <= 4, to run even in full UI. As a workaround, I've now set the custom action condition to

Code: Select all

NOT (UILevel = 5 OR CLIENTUILEVEL = 3)
but I'm not sure about CLIENTUILEVEL - I only noticed it being set to 3 when in full UI. Do you have info on CLIENTUILEVEL?
Catalin
Posts: 7852
Joined: Wed Jun 13, 2018 7:49 am

Re: UILevel may be set incorrectly

Hello Albert,
In my Win10, when I run the installer w/ full UI, UILevel is set to 5 per the log - this is fine. But if I run the same installer in my Win7 w/ full UI, UILevel is set to 2. Is this a bug?
To be fully honest with you, I am not sure of whether this is a bug or not, but definitely it is not a normal behavior.

I have tested this just now and the UILevel property is set to "5" on both a Windows 10 and Windows 7 clean VMs, when running the setup with full UI.

In order for me to further investigate this, could you please forward me the following:

- a copy of the .AIP file (you can strip it down to the point where the problem still reproduces - it doesn't have to contain any items)

- a download link for the setup resulted after building the above .AIP file

by e-mail at support at advancedinstaller dot com?

I have tried to do some research on the CLIENTUILEVEL property, but unfortunately I could not find much information about it. It seems to be an internat Windows Installer property, but unfortunately it seems to be undocumented. However, from what I know (and from what I saw in my earlier tests), in case of a FullUI installation, the CLIENTUILEVEL property should be set to "0" (in my logs it appears as "0").

Looking forward to hearing from you.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
alco
Posts: 80
Joined: Thu Nov 18, 2010 5:02 pm

Re: UILevel may be set incorrectly

I rolled back the .aip to before I upgraded to 16.0, rolled back to 15.9, reapplied the changes, rebuild, and UILevel gets set correctly and the custom action no longer gets triggered in full UI.
Catalin
Posts: 7852
Joined: Wed Jun 13, 2018 7:49 am

Re: UILevel may be set incorrectly

Hello Albert,

First of all, thank you for the provided files.

I was indeed able to reproduce the behavior using your setup. I was also able to replicate this in a sample project.

So far, from my investigations, this issue seems to be related to the "Fast installation - optimized file costing and copy, indeterminate progress" option from "Install Parameters" page --> "Minimize Installation Time" section.

With that being said, could you please disable that option, rebuild the project and retest it and let me know the results?

Also, as an additional note, the issue reproduces on both Windows 10 and 7 (with my sample project). The UILevel is set to "2" on both machines.

Looking forward to hearing from you and hope this helps.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
alco
Posts: 80
Joined: Thu Nov 18, 2010 5:02 pm

Re: UILevel may be set incorrectly

Thanks for your help, Catalin!

I reverted to this revision, unchecked the option, rebuilt, & retested and confirmed that the UILevel now works as expected.
Catalin
Posts: 7852
Joined: Wed Jun 13, 2018 7:49 am

Re: UILevel may be set incorrectly

Hello Albert,

Thank you for your followup on this.

I am glad to hear that the workaround did the job.

I will update this thread as soon as this will be fixed.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Catalin
Posts: 7852
Joined: Wed Jun 13, 2018 7:49 am

Re: UILevel may be set incorrectly

Hello Albert,

As a followup to my last thread:

After some further investigations, it seems that this was not actually an issue, but the expected behavior. Please have a look on the following Microsoft article:

FASTOEM property

There, you can see that it states that:
The FASTOEM property is only applicable if all of these conditions are true:

...
- No user interface is displayed during the installation. The user interface level is none.
Hope this information helps somehow.

Best regards,
Catalin
Catalin Gheorghe - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”