Mstsc.exe keeps crashing (0xc0000005 error code)

2016-07-06

Question

_{Wednesday, July 6, 2016 1:45 PM}

Hello,

Today I was helping a colleague upgrading from Windows 8.1 to Windows 10 to see if that solved his problem when running mstsc.exe.

Sadly the problem still exists and I went to the log files to see if I could discover anything out of the ordinary:

Despite the log file being Dutch, I see that there is an error code 0xc0000005 which points to many things like faulty RAM, Anti Virus software blocking certain ports etc.

What I have tried so far:

-Getting the latest Windows 10 updates
-Running *scf /SCANNOW
*-Upgrading to Windows 10

If there are ways to solve or workaround it, I would be very grateful.

All replies (4)

_{Thursday, July 7, 2016 11:35 AM ✅Answered}

Hi SP-Brown,

Since the log file is Dutch, I cannot find many information to troubleshoot this issue. We could refer to refer to S.Sengupta's suggestion to use "DISM.exe /Online /Cleanup-image /Restorehealth" to scan and repair the system components at first.

In addition, please boot into clean boot environment and run Mstsc.exe again to have a test, in case it is caused some third party applications and services.
How to perform a clean boot in Windows.
https://support.microsoft.com/en-sg/kb/929135

Please also uncheck the all local redirect resources in the MSTSC then connect again to see if the same issue still exists. Click Options, navigate to Local Resources>Local Devices and resources to check them.

Best regards

Please mark the reply as an answer if you find it is helpful.

If you have feedback for TechNet Support, contact [email protected]

Hello Rick,

I managed to circumvent the problem by installing Remote Desktop Connection Manager, creating a session within RDCMan and after that, in mstsc.exe.

It is very cumbersome to be honest but at least my co-worker can continue where he left off.

13-07-2016: My co-worker got the same error after a few days after it did work for two days. I ultimately resorted to restoring the factory settings. That resulted into mstsc.exe working as it should.

If there are any changes, I'll let you know asaop.

_{Wednesday, July 6, 2016 4:46 PM}

The correct command will be :

sfc /scannow

Type the following command, and then press Enter.
It may take several minutes for the command operation to be completed.

DISM.exe /Online /Cleanup-image /Restorehealth

_{Thursday, July 7, 2016 7:30 AM}

Hi SP-Brown,

Since the log file is Dutch, I cannot find many information to troubleshoot this issue. We could refer to refer to S.Sengupta's suggestion to use "DISM.exe /Online /Cleanup-image /Restorehealth" to scan and repair the system components at first.

In addition, please boot into clean boot environment and run Mstsc.exe again to have a test, in case it is caused some third party applications and services.
How to perform a clean boot in Windows.
https://support.microsoft.com/en-sg/kb/929135

Please also uncheck the all local redirect resources in the MSTSC then connect again to see if the same issue still exists. Click Options, navigate to Local Resources>Local Devices and resources to check them.

Best regards

Please mark the reply as an answer if you find it is helpful.

If you have feedback for TechNet Support, contact [email protected]

_{Friday, July 8, 2016 1:12 AM}

Hello SP-Brown,

It is glad that to hear that you have found a workaround, thanks for sharing your experience and solution here. It will be very beneficial for other community members who have similar problem.