Share via

Protocol Error when connecting MacBook (Sequoia and iPad via Remote Desktop/Windows App for Mac

Anonymous
2025-03-26T15:16:15+00:00

My MacBook and iPad have both worked great using Remote Desktop for Mac - on various Mac devices for years - now Windows Update (I updated) for Mac - Host is Windows 10 Pro - until last week. Now neither the MacBook or iPad works - with various error messages, mostly "Your session ended because of a protocol error. Error code: 0x100d". I have reinstalled Windows Update, checked IP connection, tried adding a different user, various Terminal commands suggested by Apple support without effect.I have Sequoia 15.3.2 on the MacBook (Apple M2) purchased in January 2025), updated around the time the problem started - which could be the problem, except my iPad is also not working - no recent update there. also tried on a different MacBook with Sequoia 15,3,2, Any way to figure out what the protocol error might be, how to fix it, or anything else as signing in remotely is important to my clinical practice.

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2025-03-28T07:39:02+00:00

    Dear Philip Drum,

    Thank you for reaching out with your question regarding the protocol error you're encountering when trying to connect your MacBook and iPad using Remote Desktop.

    While I am happy to assist you, this issue involves Remote Desktop Services (RDS), which falls outside the typical scope of Microsoft Community Support. Since this pertains to specific troubleshooting related to Mac device and Remote Desktop, I highly recommend posting your question on Microsoft Q&A.

    Ask a question - Microsoft Q&A

    Microsoft Q&A is a more specialized platform, with dedicated sections for topic like RDS. You'll find support staff and community experts there who can provide more in-depth guidance for resolving protocol errors like the one you're experiencing.

    Thank you for your understanding. I'm confident that you'll be able to find the right expertise and solutions within the Microsoft Q&A community to address this issue.

    Best Regards,

    Martin | Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments No comments