Share via

RDP Credentials - Always have to hit "More Choices" to enter credentials

Question

Monday, September 26, 2016 6:43 PM | 3 votes

I just received the latest Windows 10 update and the RDP prompt has changed. Now, everytime I go to Remote Desktop into a server, it defaults to trying to use "app" credentials from one of my VPN apps, rather than just prompting me for a user name and password as it did before. 

I now have to hit "More choices" every time in order to get to the point below where I can enter my username and password:

Is there anyway to get around this other than uninstalling that VPN app? Or is there a way to go back to the old RDP functionality (registry, default.rdp changes, etc.)?  I manage many different clients using various VPNs, that software (Palo Alto GlobalConnect) being one of them, so this is quite the annoyance to have to hit More Choices many times a day. 

All replies (10)

Tuesday, September 27, 2016 1:01 PM | 1 vote

Hi Josh,

I just configure the logon user name on RDP window, there's no such Windows security pop-up:

Would you please let me know how you remote and if you just try to remote the computer which require VPN connection to make access?

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Monday, October 10, 2016 12:03 PM

I use a variety of VPNs as we support all of my clients remotely (Cisco Anyconnect, Sonicwall, Citrix Access Gateway, Palo Alto GlobalProtect, native Windows VPN, and so on). This behavior occurs whether I'm connected to VPN or not. Most RDP sessions do not support saving of credentials so that wouldn't work for a majority. This extra security prompt has only occurred since the Windows 10 Anniversary update. It seems to be automatically trying to use that saved credential from Palo Alto for every RDP session, regardless of whether or not I'm actually connected to it. 

Friday, October 14, 2016 10:40 AM

Hi,

What kind of the credential does it like in Palo Alto GlobalProtect? Email or others?

Windows security window will abstract the Microsoft account, local user account for Windows to make sure that RDC has enough permission to run and access local recourses.

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
If you have feedback for TechNet Subscriber Support, contact [email protected].

Tuesday, October 18, 2016 5:24 AM | 1 vote

Yep this is to do with the windows 10 anniversary update and not to do with any VPN software and it is bloody annoying. With the old interface you could just hit the down arrow and throw in the new credentials but now you have to go back to the mouse hit more choices, its only a single click but is a massive pain.

Wednesday, October 19, 2016 12:26 PM | 2 votes

Josh,
This too has been bugging me ever since the 1607 update. I couldn't find anything on the internet so I did an mstsc /? from the run prompt and tried a few of the new switches. I found that if you use "mstsc /public" it runs RDP in public mode and has a more simplified credentials screen so you don't even have to mouse to anything. You just start typing your credentials. also, switches can be saved in shortcuts. I always run MSTSC from the run prompt anyway so this works for me.

Monday, August 14, 2017 7:51 PM

I have the same issue.  REALLY driving me crazy!  Palo Alto Global Protect causes this.  I uninstall it, RDP works normal.  when it's installed, RDP tries to use it's credentials.  SO annoying.  There has to be a registry hack to fix this!

Monday, August 14, 2017 8:19 PM | 5 votes

I think I fixed this!

I went into the registry (using regedit), and found the authentication providers and followed a TechNet article on how to disable the Palo Alto provider.

Open RegEdit, then browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers.  Find the one with the provider "PanV2CredProv".  Create a new DWORD in that one called "Disabled", with a value of 1.

Vwalla.  Fixed.

I have tested other GlobalProtect functionality, all seems to work OK still.

Here's the article I found, and I used 'method 2' using the registry. https://social.technet.microsoft.com/Forums/office/en-US/9c23976a-3e2b-4b71-9f19-83ee3df0848b/how-to-disable-additional-credential-providers?forum=w8itprosecurity

Wednesday, September 13, 2017 9:41 AM

Thank you!  It works for me.

Thursday, September 21, 2017 10:24 AM | 1 vote

great find with the /public option. Seems like this might be my new msts default option. However, you lose the option to accept the server certificate permanently.

That clicking on "more choices" was driving me crazy as I often RDP to servers with other credentials than those on the client I'm working on.

Wednesday, November 1, 2017 7:06 PM

THANK YOU! This worked for me. Was bugging the heck out of me.