Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, April 11, 2017 11:53 PM
Concerning Windows 10 v1607:
I'm a network administrator who remote controls user's desktops using Remote Assistance and/or Quick Assist. Occasionally, I need to run a program elevated. This causes an elevation prompt on the secure desktop while blanking the helper's screen. I am unable to enter credentials when this happens.
For Remote Assistance, enabling this security option (gpedit.msc) solves the problem:
- User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop
But, for Quick Assist this policy doesn't have any effect.
How do I fix this? Sometimes, I need to enter credentials in the elevation prompt while helping a user via Quick Assist.
Thank you.
P.S. I checked the manifest for quickassist.exe and was surprised to see uiAccess="true". ... Just FYI
-Tony
All replies (11)
Thursday, April 13, 2017 9:36 AM
Hi ,
Disable this group policy to have a test:
User Account Control: Switch to the secure desktop when prompting for elevation
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, April 13, 2017 11:16 PM | 1 vote
Disable this group policy to have a test:
User Account Control: Switch to the secure desktop when prompting for elevation
Yes. This policy works as expected, but it disables the secure desktop for all elevation requests. Using this policy results in a [slightly] less secure computer. For that reason, I don't consider it a proper solution.
Quick Assist should be a UIAccess application and should work with the correct policy. Maybe it's a bug? How do we get confirmation (and fix) from Microsoft development?
-Tony
Friday, April 14, 2017 8:12 AM
Hi ,
Sorry to hear that. But, that is the only solution I could find. In fact, it is not recommended that you start a program as an administrator in a Remote Assistance session. In this situation, the user can disconnect the Remote Assistance session at any time. Then, the user can continue to use administrative rights to run the program. If you have any concern, we could use the built-in Feedback Hub to submit to product team.
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Saturday, April 22, 2017 12:47 AM
It seems that QuickAssist included with Windows v1703 works properly with the User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop policy.
Now, how do I install this version on 2016 LTSB?
-Tony
Tuesday, April 25, 2017 9:47 AM
Hi ,
Copy the "Quickassist.exe" (it is a desktop app) from a Windows 10 version 1703 machine, have a test.
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Sunday, May 14, 2017 12:46 AM
Hi ,
Copy the "Quickassist.exe" (it is a desktop app) from a Windows 10 version 1703 machine, have a test.
I considered this, but SFC would automatically replace the "corrupted" file with a copy from SxS cache.
-Tony
Monday, May 15, 2017 9:39 AM
Hi ,
Copy the "Quickassist.exe" (it is a desktop app) from a Windows 10 version 1703 machine, have a test.
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Hi ,
So, doe this work for you?
If so, do not run SFC command, take it as a temporary workaround.
Best regards
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, July 18, 2017 1:38 AM
It seems that QuickAssist included with Windows v1703 works properly with the User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop policy.
Now, how do I install this version on 2016 LTSB?
-Tony
What exact version of quickassist.exe do you have? I'm running Windows 10 v1703, using quickassist.exe (10.0.15063.0, 3/17/2017) and UIAccess policy still does not let quick assist work with Secure Desktop policy enabled. msra.exe on the same machines does work with UIAccess and Secure Desktop enabled.
Thanks!
Tuesday, July 18, 2017 5:41 AM
-Tony
What exact version of quickassist.exe do you have? I'm running Windows 10 v1703, using quickassist.exe (10.0.15063.0, 3/17/2017) and UIAccess policy still does not let quick assist work with Secure Desktop policy enabled. msra.exe on the same machines does work with UIAccess and Secure Desktop enabled.
Thanks!
The version of quickassist.exe that worked for me was 10.0.15063.0, 3/17/2017. I don't recall doing anything special; it just worked. But, it has been several months since I worked on this project, so it's possible I'm forgetting some little detail. Also, I am using Enterprise Edition.
-Tony
Wednesday, March 25, 2020 4:18 PM
It seems that QuickAssist included with Windows v1703 works properly with the User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop policy.
Now, how do I install this version on 2016 LTSB?
-Tony
I still have this issue with the UIAccess policy inplace and quickassist.exe version 10.0.18362.1. Any idea what else I can do without having to completely disable the secure desktop?
Thursday, March 26, 2020 11:50 AM
We are having the exact same problem; we have windows 1809 / 1909 and the elevation prompt on the secure desktop is still occurring even with the User Account Control: Allow UIAccess applications to prompt for elevation without using the secure desktop policy configured on enabled.