Microsoft Remote Desktop

[Michele_Centonze]

May I have your feedback please?

Best regards.

Michele

[DennisCJr757]

Hello Michelle Centonze, I do not have the exact answer for you but, possibly some information that may help guide you in the direction of an answer.  

I posed the question of your issue this way to one of the online A.I.-powered Search engines, one I am presently assisting in Beta testing for "use" and "behavior" issues (to quality check the results), and am sharing those actions here with you/on your question:

Prompt:
"On the Apple macOS what is the most likely cause of an error EXC_BAD_INSTRUCTION (SIGILL) while using Microsoft Remote Desktop"

Response:

"The most likely cause of an error EXC_BAD_INSTRUCTION (SIGILL) while using Microsoft Remote Desktop on Apple macOS could be due to a compatibility issue between the Microsoft Remote Desktop application and the macOS version you are using. It is possible that the application is not optimized or fully compatible with the macOS version, leading to the error.

To troubleshoot this issue, you can try the following steps:

1. Make sure you have the latest version of both Microsoft Remote Desktop and macOS installed. Check for updates and install any available updates.

2. Try uninstalling and reinstalling the Microsoft Remote Desktop application. This can help resolve any corrupted files or configurations that may be causing the error.

3. If the issue persists, you can try using an alternative remote desktop application that is known to be compatible with your macOS version. There are several free and paid options available, such as TeamViewer or AnyDesk.

4. If none of the above steps resolve the issue, you can reach out to Microsoft Support for further assistance. They will be able to provide specific troubleshooting steps or updates related to the Microsoft Remote Desktop application.

Remember to always backup your data before making any changes or installing/uninstalling applications."
- - - - - - - -
** Take-aways from me:
I like the idea of using another remote desktop application such as TeamViewer or AnyDesk should be tried, and {possibly} you could TRY one of these while Remote Desktop is 'Uninstalled' in order to see if the macOS is able to establish the connection FREE FROM any "dependency" or inter-connection with the "problematic" Remote Desktop application.

If TeamViewer or AnyDesk works, this would establish the macOS is able to 'make' a connection to a Remote service of another "flavor" from the same vendor.  Okay, good.  Then you could 'Add' Remote Desktop back into the mix and see whether (a.) It now works -- because one of the other Apps loaded one or more 'components' that "healed" the underlying system pieces, or, (b.) the Remote Desktop continues to 'Not work' which would mean ALTHOUGH TeamViewer or AnyDesk is able to function and {for some reason} Remote Desktop is NOT.

I hope that you find some of this guidance helpful and decide to pursue one of the options.
~ Dennis C.
[Also a long-time Contributor over at (the) Experts-Exchange (.com) site]

[DennisCJr757]

If the Application take the entire macOS system "Down" (a forced reboot), this is what used to be referred to as a 'System Bomb' and it indicates a software conflict the O.S. was unable to resolve.

Supporting quote: "A third-party software interacting with macOS that causes the system to halt and forces a reboot is called a kernel panic. A kernel panic is a critical error in the system's kernel, the core of the operating system that manages hardware and software interactions. When a kernel panic occurs, the system is unable to recover and must be rebooted."

[tmariscal]

We are sorry you are running into issues. To discuss issues we recommend to share your problem on our Tech Community forum (https://aka.ms/wvdtc) or open a support ticket after you have reviewed the troubleshooting options in our documentation (Windows Virtual Desktop troubleshooting overview - Azure | Microsoft Docs)

We recommend to review our troubleshooting section first. The other option you have is to open a support ticket through the Azure Portal.