Virtual Desktop Log In

Hi,

1- Specific to Error Code 0x3000064: This error can relate to Remote Desktop Gateway (RD Gateway) issues or misconfigured security settings like Network Level Authentication (NLA). It may indicate a connection failure before credentials are prompted. Ask your admin to:

Verify RD Gateway is online and reachable (port 443).
Check if NLA is enabled on the session host (in System Properties or Group Policy) and ensure your client matches this setting (adjustable in the client’s "Advanced" tab).
Review RD Gateway logs or test disabling NLA to pinpoint the issue.


2- Expired or Changed Credentials: If the server password changed (e.g., for security or policy) but the client’s saved credentials weren’t updated, the connection fails.

3- Compatibility Issues: An old RDP client’s saved credentials might not work with a new server setup (e.g., after switching to Windows App or a server update), blocking login.

4- Automatic Login: If the client auto-uses outdated saved credentials without prompting, you won’t get a chance to enter new ones before it times out.

How to Check and Fix:

Clear Saved Credentials: In Windows, go to "Credential Manager" > "Windows Credentials," find entries for your server (e.g., IP or domain), and delete them. In the Remote Desktop app, edit the connection, remove saved credentials, and save without "Save credentials."
Force New Login: Re-enter the server address manually, uncheck "Remember me" if prompted.
Check Client: If using an old Remote Desktop app, switch to Windows App and set up the connection fresh, without saved credentials.

Feel free to reach out if you more questions 

Please try to fix on below:

1.    Check Session Host Health: Ensure that the session host is online and functioning correctly. You can verify this in the Azure Portal or your Virtual Desktop management tool.
2.    Update Remote Desktop Client: Make sure you're using the latest version of the Remote Desktop client. Outdated versions can sometimes cause compatibility issues.
3.    Network Configuration: Check your network settings to ensure there are no restrictions or firewalls blocking the connection. Sometimes, VPNs or proxy settings can interfere with Virtual Desktop connections.
4.    Rejoin Domain: If the session host is part of a domain, try disconnecting and rejoining the domain. This can resolve authentication or connectivity issues.
5.    Session Host Restart: Restarting the session host can often resolve timeout issues. If you don't have access to do this, you may need to contact your system administrator.
6.    Logs and Diagnostics: Review the logs for more detailed error information. This can provide clues about what might be causing the timeout.