based on others experience, if you have HP PC, try to remove simple pass software

https://social.technet.microsoft.com/Forums/windows/en-US/7313cec3-9e04-4d3b-8ecf-f197cd6f9ad3/windows-81-pro-remote-app-crashes-connecting-to-2012-remote-desktop-web-access-published?forum=winserverTS

• Edited by britishdhez Tuesday, June 16, 2015 7:18 AM

based on others experience, if you have HP PC, try to remove simple pass software

https://social.technet.microsoft.com/Forums/windows/en-US/7313cec3-9e04-4d3b-8ecf-f197cd6f9ad3/windows-81-pro-remote-app-crashes-connecting-to-2012-remote-desktop-web-access-published?forum=winserverTS

• Edited by britishdhez Tuesday, June 16, 2015 7:18 AM

based on others experience, if you have HP PC, try to remove simple pass software

https://social.technet.microsoft.com/Forums/windows/en-US/7313cec3-9e04-4d3b-8ecf-f197cd6f9ad3/windows-81-pro-remote-app-crashes-connecting-to-2012-remote-desktop-web-access-published?forum=winserverTS

• Edited by britishdhez Tuesday, June 16, 2015 7:18 AM

based on others experience, if you have HP PC, try to remove simple pass software

https://social.technet.microsoft.com/Forums/windows/en-US/7313cec3-9e04-4d3b-8ecf-f197cd6f9ad3/windows-81-pro-remote-app-crashes-connecting-to-2012-remote-desktop-web-access-published?forum=winserverTS

• Edited by britishdhez Tuesday, June 16, 2015 7:18 AM

based on others experience, if you have HP PC, try to remove simple pass software

https://social.technet.microsoft.com/Forums/windows/en-US/7313cec3-9e04-4d3b-8ecf-f197cd6f9ad3/windows-81-pro-remote-app-crashes-connecting-to-2012-remote-desktop-web-access-published?forum=winserverTS

• Edited by britishdhez 23 hours 55 minutes ago

Thanks for the quick reply, and yes, the PC is HP brand.
I will test this ASAP, and will keep you informed for all future details.
Thank you in advance for the help.

Hi DKarov,

How about the issue, is there anything to update?

To isolate the third party service conflict issue, we can perform a clean boot to have a troubleshoot.
How to perform a clean boot in Windows
https://support.microsoft.com/en-us/kb/929135

Best regards

Hello together.

Description of my problem is very simple: I have Win8.1x64, and I`m using RDP to Win2012R2. Recently my RDP (mstsc.exe) start crashing after few second in freeze state. Nothing of the following helped (turn off local resources, printers audo, ports , etc), remove and delete from local PC all printers, sfc /scannow, Full Win update, System restore to previous system state.
Here the description of the error (it is always the same).

Faulting application name: mstsc.exe, version: 6.3.9600.16384, time stamp: 0x5215e2b5

Faulting module name: ntdll.dll, version: 6.3.9600.17114, time stamp: 0x53649e73

Exception code: 0xc0000005

Fault offset: 0x000000000006361a

Faulting process id: 0x1520

Faulting application start time: 0x01d0a44a9e1e79a6

Faulting application path: C:\Windows\system32\mstsc.exe

Faulting module path: C:\Windows\SYSTEM32\ntdll.dll

Report Id: f43e87f2-103d-11e5-8297-64510604ee83

Hello together,

Problem is solved for now. Resolution in my case was System Restore from the date before, last window updates installation. Obviously some drivers or system files are changed during the last update. Now I start complete check for all updates in this set, after check procedure i will make full list with affected drivers and files and will start test them one by one. When i`m done, I will post the results here. Hope that this will help.

Best Regards.

Hello together,

Problem is solved for now. Resolution in my case was System Restore from the date before, last window updates installation. Obviously some drivers or system files are changed during the last update. Now I start complete check for all updates in this set, after check procedure i will make full list with affected drivers and files and will start test them one by one. When i`m done, I will post the results here. Hope that this will help.

Best Regards.

• Marked as answer by Bruce WoodingModerator Friday, June 26, 2015 6:06 PM

Hello together,

Problem is solved for now. Resolution in my case was System Restore from the date before, last window updates installation. Obviously some drivers or system files are changed during the last update. Now I start complete check for all updates in this set, after check procedure i will make full list with affected drivers and files and will start test them one by one. When i`m done, I will post the results here. Hope that this will help.

Best Regards.

• Marked as answer by Bruce WoodingModerator Friday, June 26, 2015 6:06 PM

Hi DKarov,

I am glad the issue has been resolved and thanks for updating. It will be very useful for the person who will come across the similar issue in the future.

Best regards