srividyatr
3rd June 2013 05:43 UTC

Installation dialog display after elevation
Hi,

My installer requests for admin privileges using "RequestExecutionLevel admin".
When the installer is run by a non-admin, the UAC dialog requests for admin credentials.
After that is provided, the installer dialog is no longer visible properly (it is just a white window) though it runs.

I saw some discussions that when the UAC plugin is used, the installer runs in the background. But I do not use the UAC plugin.

What is the reason for this behavior? And how can I resolve it.

Thanks in advance for your help.

Regards,
Srividya

Anders
3rd June 2013 06:23 UTC

RequestExecutionLevel admin will request elevation before the .exe even starts to run so I don't understand what you mean by "the installer dialog is no longer visible properly", no longer implies that is was visible?

Can you provide some more information? Windows version, NSIS version etc...

srividyatr
3rd June 2013 08:04 UTC

Hi,

Thanks for the quick response.

It is not visible at all. (Before and after requesting credentials).
(No longer was with reference to the scenario where it is run by an admin where it is visible and everything works fine).

Windows version: Win7 and also windows server 2008.
NSIS version: 2.46

Please let me know if you need any further information.

Anders
3rd June 2013 08:26 UTC

Does it also happen with a really basic script?

RequestExecutionLevel admin
outfile test.exe
page instfiles
section
sectionend

srividyatr
3rd June 2013 09:16 UTC

yes, the same behaviour/problem is observed with the basic script that you have mentioned.

Afrow UK
3rd June 2013 12:08 UTC

I have never seen this problem before. Have you tried reinstalling NSIS?

Also just a note if you aren't already you need to check the user is actually an administrator using UserInfo::GetAccountType.

Stu

srividyatr
4th June 2013 05:50 UTC

Realized that the problem is happening only when running the installer remotely on a win7 machine (connected using mstsc). If I am locally logged in a win7 machine, then it works fine.
Is there some way I can address this problem?

Anders
4th June 2013 07:20 UTC

I don't believe NSIS cares if you are using RDP. It only uses standard controls and basic GDI stuff...

srividyatr
4th June 2013 07:30 UTC

The problem happens not just with an installer created using NSIS but even with installers created using other means. But if there is a way it can be addressed, then it would be great.

Anders
5th June 2013 00:23 UTC

If it happens to non-NSIS application it is probably a Windows issue, drivers maybe?