The change in UAC in SC small exe Update 2013

[lwc]

Regarding this latest update, [DIS_UAC] acts differently (as in worse).

Until now it presented the yes/no UAC question before trying to connect. If the user chose no, the connection never took place.
It now presents the initial yes/no popup after the remote session is already active. Not only is it user unfriendly, but the session continues even if the user chose no. The only difference in choosing "no" is that there's another yes/no popup question when the connection is over. Obviously it doesn't matter what the user chooses at this point, but it causes a crash to their active window (as in it freezes until they force close it).

[Rudi De Vos]

Then just don't use the option.

The option is only if you want to avoid that remote users need to press the UAC OK each time you open a system window.
But indeed, you need to allow that after startup and changed resuire UAC.

When i'm correct, the old version needed admin permission and the new also run as guest.
That's why the old prompte UAC on start and closed as you refused to become admin.

The popup on close is indeed not needed if you answered no. If you answerd yes it's done in background as
UAC isn't blocking.

[lwc]

I have to use the option because I obviously don't want my users to get the UAC popup each time.

What happens if they choose "no" and run as guests? What will be the functions that won't work?

Please remove the unneeded closing popup.

[Rudi De Vos]

Then you can only control normal apps.

The OS security block keyboard/mouse injection from non elevated windows to
elevated windows.
WIth a SC started as guest ( non elevated) your input is locked as soon as a elevated window become the foreground.

[Rudi De Vos]

winvnc.exe updated, to avoid regsitry reset when no changes was made.
"UAC popup after no question"

[lwc]

Thanks for the fix!

Can you make the initial question disappear after a few seconds? The users may not notice this question now.