Mac Remote Desktop beta 10.5.1 (1837) freezing with error message from runningboardd

Ernie Beffel 1 Reputation point
2020-12-22T19:36:51.73+00:00

Starting last week, 10.5.0 became very unstable connecting to a W10 desktop over a hw VPN. It crashed every 20 minutes or so.
Looking at the Catalina Console for Remote Desktop errors, every crash coincided with an error message from the OS X dameon runningboardd. The message is always, "Invalidating assertion 413-221-5788 (target:executable<Microsoft Remote Desktop Beta(501)>) from originator 221". Before updating to beta, the error was slightly different.
The beta has decreased the crash frequency to once in two hours or so.
I've searched, but cannot find in any forums reference to this error.
MSFT monitor, what causes this error? Feel free to contact me, for error logs or to discuss. It would be nice if RDP worked again.
Best regards, Ernie Beffel
ps, no Mac tags available

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services
{count} votes

1 answer

Sort by: Most helpful
  1. Jenny Yan-MSFT 9,356 Reputation points
    2020-12-23T06:33:44.413+00:00

    Hi,
    I have removed your phone info for security since this is a public forum.

    Per my understanding that your RDP from Mac got crashed every 2 hours and you checked logs for mac OS. However, we have limited knowledge of Mac and would suggest you to contact Apple support for more assistance about the error info you shared.

    From RDS perspective, is there any error message prompted when you launched RDP client or during your remote session?
    Moreover, please try with another account and remote to a computer in the same network if possible.

    Last but not least, are you capable to check the event logs in windows machine(your target computer) in following paths?
    Event log checking:

    TerminalServices-RemoteConnectionManager and TerminalServices-LocalSessionManager logs to view information about connections.

    Step 1: Press Windows+R to open the Run dialog, enter eventvwr (or eventvwr.msc) and hit OK.

    Step 2: Navigate to Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-*


    Hope this helps and please help to accept as Answer if the response is useful.

    Thanks,
    Jenny

    0 comments No comments

Your answer

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