Microsoft Remote Desktop Keeps Crashing On Mac
Shay Silvertooth
Step 5. Remove the Windows installation CD/DVD, and reboot your PC from its system hard drive. Then, run RDP to see whether Remote Desktop can work normally after login. If you have backup Windows via professional backup software, you can choose to restore the OS to its previous status.
Note: AnyViewer has also released apps for mobile devices. You can download it from Google Play on Android devices or App Store on iOS devices to access computers from mobile devices.
After a while, you can see the desktop of the remote computer and use it as if you were physically present. If you want to connect the remote computer in privacy mode, it's required to upgrade your account to Professional or Enterprise. And you can get other rights, including faster file transfer, high-quality image, assigning more devices for secure one-click access, etc.
One-click unattended remote access is more suitable for accessing your own computer frequently. To access a remote computer for offering one-time support, you can choose to send a remote control request.
Now, I guess you already address RDP keeps closing issue through the above ways, like scanning, running Startup Repair, and so on. Of course, if all the ways cannot make sense for you, you can also try the third-party remote access software, AnyViewer, which can rapidly and safely solve your problem.
@AyanPalit That's great! I'm actually looking to create a remote desktop set up at home to connect a laptop to my personal computer. Being that I'd be the only user remotely accessing my own home set up, do you know if I need to go about putting together this complicated set up with VMware and GPU management system?
Or can I just get a desktop computer with the robust specs that ArcGIS Pro calls for and then remote access via my laptop using the Microsoft Remote Desktop app?
I am still having issues with Pro crashing when my RDP is disconnected. We have some issues with our VPN disconnecting and when I reconnect, if Pro was running it will crash. We had F5 as our VPN, but now have Cloudflare and the issue is still present. I finally gave in and opened a support ticket, but they found nothing. I am working with our IT Team to see if anything about my setup is causing that issue. I am running 3.2 I did remove an ArcGIS Hydro add-in and also our organization screen saver. It is hard to test this issue as it only happens when the disconnect happens. I am hoping that recent changes may have helped. Time will tell
@MeleKoneya Thanks for the update. The behavior reported is weird; my best guess it's the setup. I recall a few issues where VPN/RDP tries to connect the host machine drives to the remote machine for file transfer etc. Connect/disconnect of the mapped drives in this situation seem to upset some applications. This is usually a setting that can be disabled. Just one more item to review and rule out.
I have 2 users out of about 20 that are using Jabber for Windows 10.5 and it keeps crashing out for them. I cannot isolate anything that is causing it on their 2 systems. One user is running windows 7 64bit and the other is using remote desktop services on our windows 2008 R2 server. All other RDS users are not having the issue just this one user. Also I do not see anything that looks funny in the logs at all. Unless I am looking at the wrong ones. I am attaching the log from the windows 7 user for the last time it crashed. I dont see any hints to anything though.
My problem started after i received a forced weekly update, and my computer rebooted the only change i noticed was a update to Firefox then issue continued until i received the next weekly update that also updated Firefox. I may be shooting in the dark here but compare the version of Firefox of the two users with the issue to a few users without the issue. This is of course only if Firefox is allowed in your environment. I was about to open a TAC case Im using version 10.5.2 and jabber consistently crashed before i was able to send an IM to anyone
I tried removing firefox and rebooting/reinstalling Jabber with no luck. I reimaged my machine and loaded 10.5.2 fresh install with no previous versions and still getting the random crash. Also, I have users who say it has crashed on them during a WebEx and have had installation problems when upgrading from 9.x to 10.5.x. Version 9 is very solid, sticking with 9.7.5. I have about 10% of my test users having varying problems with version 10.5.x, waiting till the next release. Hopefully Cisco will spend a few more weeks testing the next one before publishing it on their site.
Also, when you finally get frustrated and want to downgrade, Jabber 10.5.x doesn't uninstall completely and you end up with an error like the image attached when you try to install v9.7.5 for example and can't install Jabber even after rebooting. I had to run Microsoft Fix It install/Uninstall option and tell it to uninstall Jabber before Windows allowed me to install an older version of Jabber. Not too happy with this release. Strange enough though, some of my users have the exact same laptop I do, same windows build, same patches, etc, and it works fine for them. Anyway, not deploying this one. Good luck.
This isn't the experience we want you to have when using QuickBooks Desktop Enterprise, @ckritt3. I'm here to assist you and provide some troubleshooting actions to resolve this crashing issue in QuickBooks Desktop and get back to business in no time.
I am having the exact problem... it just freezes and the only way to close it out is to use the task manager. I am using Windows 11 ver 23 Manufacturing and Wholesale. I have had the complete reinstall and that has not worked either. There is no rhyme or reason... it may go 10 min and freeze or it may not freeze for a couple hours but it irritating to be looking at a statement and then start to make the change and it has frozen.
I understand that you have already taken some steps to address the freezing problem you are experiencing with QBDT. Allow me to suggest additional troubleshooting measures to help restore your QuickBooks to its normal functioning.
However, I'd advise getting in touch with our Customer Support Team if the problem still exists after performing the suppressing steps. If other users report the same issue, they can look into it further and open an investigation ticket. To reach them, you may follow the steps shared by Rea_M above or click this link: Contact QuickBooks Desktop support.
This random freezing issue started for us early last week, I believe. I had thought that it was an update that went wrong and would be fixed, but it has not been. I also thought that since we were still using QB Desktop Enterprise 21, that it was time to do the upgrade and proceeded. Now we are current, at 23. Still same issues. 2 hour phone call with support due to database server manager not working with new install. Everything seemed fine, but we are still having a couple of random freezes a day per user on their own work stations, which is better, but not right. Tool hub fix my program seemed to have helped with the frequency also.
To follow up on Fiat Lux - ASIA's clarifying question, I'm also curious whether you're using QuickBooks on Windows 11. If that's the case, make sure your operating system and hardware are in line with the system requirements of QuickBooks Desktop 2023 to ensure a seamless experience. Feel free to check this article for more details: System requirements for QuickBooks Desktop 2023. Then, update QuickBooks to the latest release.
However, if your QuickBooks isn't operating within Windows 11, please inform me of the specific operating system you are using. This information will enable me to offer more precise guidance on the necessary steps to address the issue of random freezing.
We're also experiencing this. It's followed the same progression: began with random, "silent" crashes to desktop without an error or hang. After about a month, it now hangs and must be closed with task manager. Can occur 10 minutes after opening or 2+ hours, the timing is random. The related Windows event viewer error messages are difficult to decipher and seem to point towards some kind of printer driver issue, but that may be an illusion.
I recognize you're facing a similar issue with random crashes and software hang-ups, which can occur at any time. While Windows event viewer errors may point to a printer driver problem, we're here to help find the cause further, and thank you for your patience.
Upon reading the answers in the previous responses, I can see the Carneil_C's answer explained a lot. He has provided the necessary troubleshooting steps that we can advise from here. For this reason, I'm encouraging you to contact our QBDT Support so they can check this further using more tools.
Relevant PC specs are Intel i7-13700k CPU, 32GB DDR5 RAM. Up to date on Windows Updates, etc. Other threads suggested that a reinstall of .NET framework could fix the issue, so I tried that, but the problem persists.
I didn't get a chance to try your suggestion, but I did manage to experience a true crash-to-desktop without a program hang (requiring task manager to close) for the first time in some time. This also generated a new error in Event Viewer - pointing to a problem with .NET framework ver. 4.0.30319. Two error logs were generated. Here are the details:
I have a similar setup here that I admin. Windows 10 Pro box with 8Gb or ram (upgrading to 24 tomorrow). This box houses the company file as well as a local install of QB Enterprise Mfg and Wholesale 23 for the remote users to connect to it via an remote desktop VM session. Several of the other users in the physical office also connect to this box with local installs of the same software on their computers as they need to provide updates to records or input data.
With all that in mind, from time to time I kept having the same issues I have seen on this page. Often it would hard lock and silent crash to the desktop. Sometimes it would throw an abort error. I narrowed it down to the Sleep Timer being set on the host box to 20 minutes. I turned this off and it basically resolved all my issues. Then, a month or so later, they came back. Turn out that when I ran the Windows Updater on the host computer, the updates it installed reset that sleep timer back to 20 minutes. I had to go back and turn it off again. Problems solved for now again. I'm guessing the host computer going into sleep mode is severing the network connections to it.