Help needed to remote desktop Win 11 Pro computer from Android tablet

[DennisT]

Hi

My needs are simple: to sit on my lounge with my Lenovo Idea Tab 11 tablet and remote desktop to my Win 11 Pro computer on the other side of the room so I can control my music playing app. I was doing this successfully with my Dell Venue 11 Pro Win 10 computer until Microsoft rendered the device obsolete and demanded I buy a new one. I complied, and now have this brand new Lenovo Idea Tab 11 tablet, TB336FU ZAFR.

I installed the Windows app for Android, which supposedly has RDP capabilities. But I wasn't able to log in to it as it required a school or corporate account, which I don't have. So, after activating the Windows RDP helper on the Windows machine I tried the other connection option on the Windows app.

The machines connected, but there are two issues that need to be solved:
1. The remote desktop image only occupies about a quarter of the area of the Lenovo screen, and nothing I do, such as fiddling with the resolution settings, makes it any bigger, so it is completely useless.
2. After closing the connection, it cannot be opened again, it just comes up with the ox204 error. The only way to get another connection is to uninstall the app and reinstall it.

I also tried installing the app on the Win 11 computer, but it also required a school or corporate account.

Any advice on these issues will be gratefully appreciated.

Thank you for reading.

Dennis

 

[ChatGPT]

Hi Dennis — thanks for the clear description. You were close; this is a common combination of (a) the wrong Android app and (b) a display‑scaling / connection settings mismatch. Below are a concise set of things to try (order matters) plus a couple of easier alternatives if you just want to control music.
Before you start

• Confirm both devices are on the same Wi‑Fi network (home Wi‑Fi).
• On the Windows 11 PC make sure Remote Desktop is enabled: Settings → System → Remote Desktop → turn on “Remote Desktop.” Note the PC name shown there and keep the PC awake during testing (see step 3).

1) Use the correct Android app

• Uninstall the “Windows” app you installed (that asked for a school/corporate account). That app is not the right client for what you want.
• Install Microsoft Remote Desktop (the Android app published by Microsoft Corporation — search “Microsoft Remote Desktop” in Google Play). This is the free RDP client for Android and does not require a school/corp account for home use.

2) Basic connection setup (recommended order)

• On Windows: open Command Prompt and run ipconfig and note the IPv4 address of the PC (e.g. 192.168.1.23). Also make sure power settings keep the machine awake while plugged in: Settings → System → Power & battery → Screen and sleep → set “When plugged in, put my device to sleep” to Never for testing.
• On the tablet (Microsoft Remote Desktop):
  • Add a new Desktop.
  • For PC name use the Windows PC’s IPv4 address (preferred for reliability).
  • Add a user account: either your Windows username and password, or choose “Ask when required” if you prefer to type each time.
  • Save and tap to connect.

3) Fix the “quarter of the screen” / tiny remote window
This is usually a client display setting or a Windows scaling mismatch.
Try these in order:

• In the Android Remote Desktop app: Edit the desktop → Display settings (or Edit → Display). Choose “Use device resolution” or “Fit to screen / Fit to width” (wording depends on app version). That tells the client to scale the remote desktop to the tablet screen.
• If that option doesn’t work or is missing, temporarily change your Windows display scaling to 100%: On the PC right‑click Desktop → Display settings → Scale → set to 100% and reconnect. If that fixes it, you can experiment with other values or leave it at 100% when using from the tablet.
• Alternative (if you know the tablet resolution): in the Android app set a Custom resolution that matches the tablet (e.g. 1920×1200). The client will then use that resolution for the remote session and fill the screen.
• If you see a tiny desktop after reconnecting, try toggling “High quality” / “Use more bandwidth” or “Dynamic resolution” in the app (those options affect scaling behavior).

4) Troubleshooting the 0x204 reconnect error
0x204 on Android usually means the client can’t reach the PC (network, sleep, firewall, wrong address) or cached credentials/config got corrupted.
Try these checks and fixes:

• Make sure the PC did not go to sleep. (See step 2: set sleep to Never while testing.
• Test reachability: from another device on the same Wi‑Fi you can try pinging the PC’s IPv4 address or use another RDP client on a laptop to confirm the PC accepts RDP.
• Firewall: Windows Defender Firewall should allow Remote Desktop. On the PC: Settings → Privacy & security → Windows Security → Firewall & network protection → Allow an app through firewall → verify “Remote Desktop” is allowed on Private networks.
• Use the PC’s IPv4 address in the Android client (not the computer name) to avoid name resolution issues.
• Clear the Android app cache / stored credentials instead of uninstalling every time: Android Settings → Apps → Microsoft Remote Desktop → Storage → Clear cache (and Clear storage if needed). Then re‑enter the connection settings. This often fixes the need to reinstall.
• If the client refuses to connect only after a previous session: open Remote Desktop on the tablet, edit the desktop → open User accounts and remove/re-add the saved Windows credentials (sometimes corrupted credentials cause reconnect failures).
• If you use a local Windows account (not a Microsoft account) ensure the user is allowed: On the PC, open Settings → System → Remote Desktop → select “Select users that can remotely access this PC” and verify your username is listed (Administrators are allowed by default).

5) If you want the simplest “just control music” alternative
If the RDP route keeps being fiddly, consider one of these lighter options:

• Unified Remote (Android) — designed specifically to control media apps and works over your LAN. Very quick to set up.
• Chrome Remote Desktop — easy, uses Google account, full remote access with simpler setup.
• AnyDesk or TeamViewer — easy, reliable remote control and mobile clients (personal use is free).

6) Follow-ups I need from you if those steps don’t fix it

• Which exact Android app did you install earlier (show the Play Store name or a screenshot)?
• Is the Windows account a local account or a Microsoft account?
• Is the tablet on the same Wi‑Fi as the PC?
• After one successful connection, does the PC go to sleep or log out before you try to reconnect?
• If you still get 0x204, please paste the exact error text or a short screenshot and tell me whether you used the PC name or IP address when connecting.

If you like, tell me the tablet’s reported screen resolution and I’ll give the exact display settings to set in the Android app (or a short checklist you can follow).

 

[DennisT]

Thank you for your detailed response, ChatGPT. . I won't have the time to try out all your suggestions until tomorrow, but I question your advice in 1) to install the Microsoft Remote Desktop app on the tablet, my understanding is that it has been replaced by the Windows app, and the Microsoft Remote Desktop app is no longer available on the Play Store: when I searched for it, only the Windows app came up. For more info, see:

Windows App to replace Remote Desktop app for Windows - Windows IT Pro Blog

On May 27, 2025, Remote Desktop app for Windows will no longer be supported. Get ready by transitioning to Windows App.

techcommunity.microsoft.com

Thank you

Dennis

 

[ChatGPT]

Good point — thanks for the link. You’re right that Microsoft has been moving its standalone Remote Desktop client into the new “Windows” app, and that’s the reason you’re seeing the Windows app in the Play Store instead of the old “Microsoft Remote Desktop” listing. The Windows IT Pro blog Microsoft published explains that the Store Remote Desktop app is being replaced by the Windows App (this guidance is for the Store/Windows app lineage). A few important clarifications that explain what you saw on your tablet:

• The Windows App is the new, unified client Microsoft is rolling out to replace the Store Remote Desktop client (and it’s being positioned around Windows 365 / AVD / cloud workspaces). That change went public in 2025 and Microsoft started moving platform clients to the Windows App.
• Microsoft has said older Store Remote Desktop behavior will be phased out; on some platforms the package/name you see in the Play Store has been updated to the Windows App (developers and APK indexes show the same package ID but a new Windows App label). That can make it look like “Remote Desktop” vanished or now asks for a work/school sign‑in (because the Windows App initially focuses on cloud/workspace scenarios).
• There are also device‑compatibility and Play Store filtering quirks (some older/Chromebook devices are hidden from the listing), which explains why you might not find the classic Remote Desktop client on some tablets.

What that means for you right now

• If the Windows App on your tablet is prompting only for a work/school account or missing the classic direct‑RDP features you used before, that’s likely the result of Microsoft’s migration and the Windows App’s initial focus.
• You still have practical choices that will be faster than wrestling with the new Windows App right away:
  • Unified Remote — excellent and very simple for controlling music apps (server on your Win11 PC, app on the tablet). No corporate account required.
  • Chrome Remote Desktop — easy full‑desktop access using your Google account; good for occasional control.
  • AnyDesk or TeamViewer — reliable remote control clients with Android apps that work for home use.

If you want to stick with native RDP from the tablet

• I can help you check whether the Windows App on your tablet can be tuned to allow direct RDP to your Win11 Pro (it depends on the Play Store build and whether the Android client was upgraded to the Windows App preview). If it refuses personal RDP, switching to one of the alternatives above will be much quicker.

Next step
Tell me which approach you prefer and I’ll give step‑by‑step instructions:

• If you want to try Unified Remote (best for music control) I’ll give the server + client setup steps.
• If you want to try to make the Windows App/RDP work, tell me the exact Play Store app name shown on the tablet (screenshot or exact text) and I’ll walk through specific settings to try.

Which would you like to try first?

 

[DennisT]

Hi GPT and anyone else who may be interested

So, first of all Microsoft renders my Windows 10 computer obsolete, then it terminates the remote desktop app and replaces it with one that cannot be accessed by the average user like me. The the Microsoft robot tells us to use third party apps that either don't work, or are not free.

The good news is that I've found one that is free and works. It is called RustDesk.

Dennis

 

[ChatGPT]

Great — thanks for the update, Dennis. Nice find — RustDesk is a very popular free alternative for exactly this kind of home use.
A short checklist and a few tips so you can get the smoothest experience from the lounge:
1) Why RustDesk is a good fit

• Free and broadly used for personal remote control.
• Works in LAN mode so traffic stays local (low latency) or via public relay/rendezvous servers if you need access across networks.
• Option to self‑host the relay/rendezvous servers if you want full control and privacy.

2) Quick setup checklist (basic, LAN or internet)

• On the Windows 11 PC: install RustDesk for Windows (host).
  • Open RustDesk, set an unattended access password (so you can connect without someone at the PC).
  • Allow RustDesk through Windows Firewall when the installer or first run asks, or add an exception in Windows Security → Firewall.
  • Optionally set RustDesk to start with Windows so it’s always available.
• On the Lenovo tablet: install RustDesk from Google Play and enter the Windows machine’s RustDesk ID and the password you set. If both devices are on the same Wi‑Fi, RustDesk should detect the host and connect directly (LAN mode).
• If you need access from outside your home network, you can use RustDesk’s public relays (default) or set up your own relay/rendezvous servers and point both ends at them.

3) Unattended access and reliability

• Use a strong unattended password and check “Start with system” on the Windows host so the PC is reachable after reboots.
• Keep the PC awake or adjust power settings so it doesn’t sleep when you want to control music.

4) Security & privacy notes (short)

• If you care about privacy/security, consider self‑hosting RustDesk relay/rendezvous servers so IDs and traffic don’t rely on public infrastructure.
• Keep RustDesk updated to the latest release.
• Use strong, unique passwords for unattended access. If you must expose a server to the internet, use sensible firewall rules and keep the host OS patched.

5) If you want help I can provide next

• Step‑by‑step Windows host setup (including how to set unattended access and startup).
• Step‑by‑step tablet client setup (how to connect and switch to LAN mode).
• Instructions for self‑hosting the RustDesk server (I can give commands and port notes if you want to host your own relay/rendezvous).
• Troubleshooting tips if it doesn’t connect or if video is too small / resolution problems.

Which of the above would you like detailed steps for — basic setup on Windows/tablet, or instructions for self‑hosting the server?