Remote Desktop on Surface Pro 12" with Snapdragon to Win11 Workstation

AlexHRZ 0 Reputation points
2026-05-20T18:34:01.16+00:00

Hi everyone,

I recently purchased a new Surface pro Tablet, expecting to be able use either the classic Remote Desktop Connection app or the newer Windows App from the store.

Unfortunatley both habe their own issues:

  1. With the mstsc app is not able to establisb a connection. Error code 0x3000008 0x0. Various fixes have been tried.
  • NLA registry change HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp UserAuthentication = 0
  • Rdp security layer HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp SecurityLayer = 0
  • CredSSP - compadability HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters AllowEncryptionOracle = 2
  1. Windows app from the storestore does bot bot allow setting of a gateway on the Tablet. For my smartphone the app works well, but for some reason the Windows Windows Version does not have that feature.

What other posibilities are there that do not require admin access on the Workstation that is to ne the Remote-PC?

It is slightly disappointing that it is easier to connect to the pc by android Smartphone than a windows Surface Tablet

Thanks for your assistance.

Alex

Surface | Surface Pro | Network

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. S.Sengupta 31,626 Reputation points MVP Volunteer Moderator
    2026-05-23T00:01:54.34+00:00

    In Start Search type gpedit.msc and hit the Enter key.

    Locate:

    Computer Configuration

    → Administrative Templates

    → Windows Components

    → Remote Desktop Services

    → Remote Desktop Connection Client

    Set:

    Turn Off UDP On Client = Enabled

    Reboot

    Then test mstsc again.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-05-20T18:34:39.06+00:00

    Remote Desktop on the Surface Pro (Snapdragon) is supported, but there are some current limitations and differences between the classic Remote Desktop Connection (MSTSC) and the new Windows App that explain the behavior.

    1. Windows App gateway limitation on Windows

    Windows App on Windows currently has specific support and limitations depending on what is being connected to:

    • On Windows, Windows App supports connecting to:
      • Azure Virtual Desktop
      • Windows 365
      • Microsoft Dev Box
      • Remote PC (preview)
    • On Windows, Windows App does not yet support connecting to Remote Desktop Services (RDS) with a gateway; for RDS on Windows, the guidance is to continue using the classic Remote Desktop app.

    From the documentation:

    • Windows App on Windows does not yet support connecting to Remote Desktop Services; to connect to RDS on Windows, continue to use the Remote Desktop app (MSTSC).
    • Remote PC connections in Windows App on Windows are still in preview; for a generally available solution to connect to a remote PC, use the built-in Remote Desktop Connection (MSTSC).

    This explains why the Windows App on the Surface does not expose the same gateway options that appear on Android: the Windows client is focused on Azure Virtual Desktop, Windows 365, Dev Box, and preview Remote PC, not full RDS gateway scenarios.

    1. MSTSC not connecting (0x3000008) and RDP listener checks

    For MSTSC, the problem is on the Windows side of the Remote Desktop stack, not specific to Snapdragon. The registry changes already tried are low-level and may not address the actual cause.

    The supported troubleshooting path focuses on verifying that the RDP listener and services on the target workstation are healthy. These checks can be done on the workstation without changing its overall configuration beyond what is required for RDP to function:

    1. Verify the RDP-TCP listener:
      • On the workstation, open an elevated Command Prompt and run: 
             qwinsta
      • Confirm that there is a line like: 
             rdp-tcp                    65536 Listen
      • If rdp-tcp is not present or not in Listen state, the listener is not working and RDP connections (including from the Surface) will fail.
    2. Check key registry values for the listener:
      • In Registry Editor on the workstation:
        • Ensure fEnableWinStation = 1 under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
        • Ensure fDenyTSConnections = 0 under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server and, if configured by policy: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services
      • Policies override defaults; if both exist, both fDenyTSConnections must be 0.
    3. Check required services on the workstation:
      • Confirm these services are running:
        • Remote Desktop Services (TermService)
        • Remote Desktop Services UserMode Port Redirector (UmRdpService)
      • If they fail to start, add the Network Service account to the local Administrators group and restart TermService: 
             Add-LocalGroupMember -Group Administrators -Member "Network Service"
    4. Verify the machine is not in Sysprep state:
      • In HKEY_LOCAL_MACHINE\SYSTEM\Setup, confirm:
        • SystemSetupInProgress = 0
        • OOBEInProgress = 0
    5. If the RDP-Tcp key is corrupted:
      • Export HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp from a working machine with the same Windows version.
      • Back up and then replace the key on the workstation.

    These steps are the supported way to restore a healthy RDP listener. If the listener is not in Listen state, MSTSC from any client (Surface, Android, other PCs) will fail regardless of client-side registry changes.

    1. Options that do not require admin access on the workstation

    Given the constraints (no admin access on the workstation), options are limited because enabling and fixing RDP itself requires administrative rights on that machine. From the documented capabilities:

    • For Remote Desktop Services scenarios from Windows, the supported client is still the classic Remote Desktop app (MSTSC). Windows App on Windows does not yet support RDS.
    • For Remote PC scenarios from Windows, Windows App support is in preview and assumes network connectivity and a working RDP endpoint.

    Without admin access on the workstation, it is not possible to:

    • Enable or repair the RDP listener.
    • Adjust RDP-related registry keys on the workstation.
    • Change firewall rules or NLA settings on the workstation.

    In such a case, the practical path is:

    • Ask the workstation administrator to:
      • Verify the RDP listener and services using the supported steps above.
      • Ensure Remote Desktop is enabled and allowed through the firewall.
      • Confirm that the account used from the Surface is allowed to connect.
    • Once RDP is healthy on the workstation, use MSTSC on the Surface Pro to connect, as that is the supported and fully featured client for RDS/gateway on Windows.

    The difference in experience between Android and Windows in this scenario is due to the current feature set of Windows App on Windows and the health of the RDP endpoint, not a limitation of the Surface hardware itself.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.