RDP From Mac to Windows: Windows App Setup Guide (2026)

Install Windows App, the new Microsoft Remote Desktop for Mac

In September 2024, Microsoft renamed its Remote Desktop clients: Microsoft Remote Desktop for Mac (version 10) became Windows App (version 11). The change was announced at Ignite 2023 and rolled out to macOS, iOS, and Android in late September 2024. The old Mac App Store listing was updated in place, so existing installs silently became Windows App on their next update. The name is confusing — an app called "Windows" running on macOS — but underneath it is the same RDP client, and direct PC connections survived the transition on the Mac (on the Windows version of Windows App, they initially did not).

Install it from the Mac App Store: search for Windows App, not Microsoft Remote Desktop. It is free and requires macOS 12 or later. On first launch the app suggests signing in with a Microsoft account; that is only needed for cloud services like Windows 365 or Azure Virtual Desktop. For connecting to your own PC or server, skip the sign-in and work from the Devices section.

Prepare the Windows machine first

RDP is disabled by default on Windows, and the Mac client cannot fix that remotely. Before touching your Mac, enable Remote Desktop on the Windows 11 machine you want to reach. Two things to verify while you are there:

• Edition: only Windows Pro, Enterprise, and Server can accept incoming RDP connections. Windows 11 Home ships without the RDP host component.
• Account: the user you connect as needs a real password — a Windows Hello PIN is not enough for RDP — and must be an administrator or a member of the Remote Desktop Users group.

Then note the machine's IP address. On the Windows machine, open a terminal and run:

ipconfig | findstr IPv4

On the same network, the private address (usually 192.168.x.x or 10.x.x.x) is all you need. Across the internet you need either a VPN into that network or a port forward on the router — RDP listens on TCP and UDP port 3389 by default. Do not expose 3389 to the internet from a home connection without a plan: prefer a VPN, and at minimum enforce a strong password and an account lockout policy, because exposed RDP ports get password-sprayed within hours.

Add your PC in Windows App

1. Create the connection

Open Windows App, click the + button and choose Add PC. In PC name, enter the IP address or hostname. If the host listens on a non-standard port, append it with a colon, for example 203.0.113.10:3390. If you are wondering what actually listens on RDP port 3389 and whether moving it is worth it, that guide covers it — short version: a custom port cuts log noise from scanners, but it is not a security measure.

2. Set credentials

The Credentials dropdown defaults to Ask when required, which prompts on every connection. For a machine you use daily, choose Add credentials and store the account. Username formats that work:

• username — plain local account
• .\username — forces a local account on a domain-joined machine
• DOMAIN\username — domain account
• The Microsoft account email — if the PC is signed in with a Microsoft account, use that email with the account's password, not the PIN you type at the Windows lock screen

3. Connect and accept the certificate

Double-click the new entry. On the first connection you will almost certainly see a certificate warning: standalone Windows machines generate a self-signed RDP certificate, and the Mac has no way to verify it. For a machine you own this is expected — confirm you typed the right address, then click Continue, optionally ticking the box so it does not ask again.

Display, clipboard, and folder redirection

Sharp text on Retina displays

Right-click the PC entry, choose Edit, and open the Display tab. Two settings matter on a Retina Mac:

• Optimize for Retina displays — renders the session at the panel's full native resolution and lets Windows handle the scaling. Text becomes as sharp as a native Mac app. The cost is real: roughly four times the pixels to encode, which means more bandwidth and more CPU on both ends. Enable it on fast connections; leave it off on hotel Wi-Fi.
• Update the session resolution on resize — keeps the remote desktop matched to the window as you drag it, instead of stretching a fixed-size framebuffer into a blurry mess.

If you work across several screens, Use all monitors in the same tab extends the full-screen session across them.

Clipboard and devices

The Devices & Audio tab controls redirection: clipboard, printers, smart cards, and microphone. Clipboard is enabled by default and carries text and images in both directions — copy on the Mac, paste in Windows, and vice versa. If paste stops working mid-session, toggling the checkbox and reconnecting resets the shared clipboard channel.

Folders

The Folders tab shares Mac folders into the session. Tick Redirect folders, add a folder such as ~/Exchange, and it appears in File Explorer under This PC as a redirected drive. It behaves like a network share: fine for moving files back and forth, too slow to run applications from.

Performance: keep UDP working

Modern RDP transports the session over UDP whenever it can, falling back to pure TCP when it cannot. UDP is what makes scrolling and video feel fluid on imperfect links, so it is worth protecting:

• If you set up a router port forward, forward both TCP and UDP on 3389 (or your custom port), not just TCP.
• The built-in Remote Desktop rule in Windows Defender Firewall already allows both — do not replace it with a TCP-only rule.

The inverse problem also exists: some VPNs pass TCP cleanly but mishandle UDP, which shows up as a session that connects fine and then freezes for seconds at a time. In that case, forcing the Mac client to pure TCP is more stable:

defaults write com.microsoft.rdc.macos ClientSettings.EnforceTcp -bool true

# revert to automatic TCP/UDP negotiation later:
defaults delete com.microsoft.rdc.macos ClientSettings.EnforceTcp

Windows App kept the bundle identifier of the old Microsoft Remote Desktop client, so this long-standing preference still applies. Quit and reopen the app after changing it.

Mac vs Windows keyboard shortcuts

Inside the session, Windows App maps macOS modifiers onto their Windows counterparts. The mappings that trip people up:

Quick troubleshooting

• Error 0x204 / "unable to connect": the Mac never reached an RDP listener — wrong IP, wrong port, PC asleep, firewall in the way, or Remote Desktop not actually enabled. Work through the checklist in fixing a Remote Desktop connection timeout; every step applies to the Mac client unchanged.
• Credentials rejected in a loop: you are typing a PIN instead of the account password, or the account is not allowed to log on remotely. Use the full password and double-check the username format (.\user versus DOMAIN\user).
• Freezes on Wi-Fi or VPN: usually the UDP problem described above — try EnforceTcp, and test on Ethernet to rule out packet loss.
• Soft or blurry text: enable Optimize for Retina displays and set Windows display scaling to a level that suits the Mac's panel (150-200% is typical).

Alternatives: Jump Desktop and Royal TSX

Windows App is free and covers the standard case well, but it is not the only Mac RDP client. Jump Desktop is a paid client that speaks RDP and VNC plus its own Fluid protocol, with more flexible keyboard remapping than Microsoft's app. Royal TSX targets admins who juggle many servers — RDP, SSH, VNC, and web logins in one connection manager, free for up to ten connections. Both use the same RDP protocol underneath, so everything above about ports, UDP, and credentials applies to them unchanged.

Whichever client you pick, it still needs a Windows machine on the other end — and a home PC that sleeps, reboots for updates, or sits behind a router you cannot configure is a fragile target. If what you really need is a Windows environment reachable from your Mac, rather than remote control of one specific PC, a hosted machine is the simpler route: an RDP server gives you a Windows instance that is always on, with full admin access and dedicated CPU and RAM, ready to accept your first connection about 10 seconds after payment confirms. Add it in Windows App like any other PC, and your Mac has a permanent Windows side.

Frequently Asked Questions

Is Microsoft Remote Desktop still available for Mac?

It was renamed Windows App in September 2024; the client itself lives on.

Yes, under a new name. In September 2024 Microsoft renamed Microsoft Remote Desktop to Windows App on macOS, iOS, and Android. Existing installs were updated in place, so the old app silently became Windows App version 11. All the core features — Add PC, clipboard and folder redirection, multi-monitor — carried over. Search the Mac App Store for Windows App; the old listing name no longer exists.

Can I RDP from a Mac to Windows 11 Home?

Not directly — Home editions cannot accept incoming RDP connections.

No. Windows 11 Home does not include the Remote Desktop host component, so no client — Mac or otherwise — can RDP into it. Your options are to upgrade that PC to Windows 11 Pro, to use a third-party remote access tool instead of RDP, or to connect to a hosted Windows machine such as a Windows VPS, which runs a Server or Pro edition with RDP enabled out of the box.

Is it free to RDP from a Mac?

Yes — Windows App is free and there is no per-connection charge.

The client side costs nothing: Windows App is a free download from the Mac App Store, with no subscription required to connect to your own machines. Jump Desktop is a paid alternative and Royal TSX is free for up to ten connections, but neither is required. The only real cost is the Windows machine itself — either a PC with a Pro or Enterprise license, or a rented Windows server.

Why is my RDP session from Mac slow or laggy?

The usual causes are a blocked UDP path, Retina rendering cost, or Wi-Fi packet loss.

Check three things. First, UDP: if only TCP 3389 is forwarded, or a VPN mishandles UDP, RDP falls back to its slowest mode — forward UDP too, or force TCP with the ClientSettings.EnforceTcp preference. Second, Optimize for Retina displays roughly quadruples the pixels to encode; disable it on slow links. Third, Wi-Fi packet loss hurts RDP badly — test on Ethernet before blaming the remote machine.