Windows App connectivity issues

Question

I've been using the Windows App (formerly RDP) successfully for quite some time to connect my iMac Pro (2017, Sequoia 15.7.7) at home to two remote Windows PCs, one in the same LAN at the iMac and the other at work, through WireGuard. And they still work beautifully.

I now have a Mac Mini M4 Pro (Tahoe 26.4) with the same version of the App (11.3.6 (3024)) with the same credentials and yet the Mac Mini tells me they're incorrect. I use my Microsoft account details to log in to one of them, so I know those details are correct, else I wouldn't have been able to post this here.

The Firewall is disabled on the Mac Mini, and the Microsoft App has full disk access.

I'd be pulling my hair out right about no, but I haven't got much, so any hellp would be appreciated.

Thank you.

Answer 1

Hi Peter

I think hat you’re running into is most likely tied to how the new Mac Mini M4 Pro is handling credential storage and keychain access with the Windows App. Even though you’re using the same version of the app and the same credentials, macOS Tahoe has slightly different security policies compared to Sequoia, and sometimes the app doesn’t properly pick up saved Microsoft account tokens on a fresh machine. A quick fix you can try is to manually remove any saved credentials in the app’s preferences and re‑enter them, making sure you’re signing in with the full Microsoft account email (not just the alias)

Also, double‑check that WireGuard is running with the same config and routes I’ve seen cases where the tunnel works fine on one Mac but needs a re‑import on another. If that still fails, try creating a new user profile in the Windows App on the Mac Mini instead of copying over the old one; it often clears up these “incorrect credentials” errors.

Answer 2

Good day Peter Newman

Glad to hear you managed to get it sorted out even if the path there was a bit messy

Honestly, what you described makes perfect sense: those account tokens can be finicky, especially when moving between machines with different OS builds. WireGuard doing its job but the app still throwing credential errors is a classic sign that the handshake was fine but the token cache wasn’t lining up. Resetting the Mac to avoid Migration Assistant “baggage” was a smart call, even if it made the troubleshooting longer.

Thanks for sharing back what worked for you, even if the steps weren’t crystal clear. That kind of feedback helps others in the same boat

Answer 3

Sorry it took me a while to get back to you.

I've managed to resolve this, but it took a while, and I'm not a techie so my explanation/description may not be completely accurate, so apologies for that, too.

I did get it working after I migrated the app over from my iMac to my Mac Mini, just to prove concept, but I really didn't want to use Migration Assistant because of all the dross it brings with it, so I reset my Mac and started again, and it still didn't work, but I got rid of the dross Migrant Assistant brought over.

One thing, the Windows App I was using is one step behind the latest, and exporting/importing the RDP file didn't work, and setting up as a new connection didn't work either. And oh, how I tried!

It all boils down to what you pointed me to, @HLBui , account tokens. WireGuard was fine and handshaking like a demon, but I kept getting credential errors on both my local Windows PC machine and my remote Work PC from the Mac Mini, but not the iMac.

I'm not going to be able to tell you exact steps that resolved the problem, because I tried lots of them and my head was fizzing by the time I'd finished. I got a lot of help from AI, but definitely had to keep it on point because it can go down a curved path, which was frustrating.

But I got there, so thanks for the pointers.