Remote Desktop Connection has Stopped Working

-

Remote Desktop Connection has Stopped Working


whenever the user RDPs onto a machine it launches but after about 10 seconds mstsc.exe crashes with the error 'Remote Desktop Connection has Stopped Working.

Reason

1)This Remote Desktop Issue related to outdated printer driver installed on your work station which redirected when you login on to remote desktop server.Due to outdated printer driver remote desktop has stopped working.

2)Another reason is outdated Audio driver installed in your Work Station.

Solution

You can try to fix it in two different ways.once you update all printer and audio driver of your work station.And other solution as under below.

1. disable Printer redirect on RDP settings.
2. disable audio redirect on RDP settings.


Popular posts from this blog

How to Reset Terminal license on Windows 2008, 2008 R2 and 2012

-
The RD Licensing grace period has expired and the service has not registered with a license server with installed licenses. A RD Licensing server is required for continuous operation. A Remote Desktop Session Host server can operate without a license server for 120 days after initial start up. The official solution is to Activate the RDS/TS CAL License server and point the Server to License server with User/Device License and will be resolve the problem, but if you want to reset the timer and again avail the 120 days grace time here is the solution: Solution: 1) First open the registry editor with "regedit" command in command prompt. 2)open the registry key from below path HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ Terminal Server \ RCM \ GracePeriod 3)From GracePeriod delete the key " REG_BINARY".don't delete default registry. 4)then Restart the computer and check the grace period with "tlsbln" command from command
Read more

How to remove a static IP configuration for an absent network adapter or uninstall hidden network adapter

-
Image
In a scenario where you have physically removed hardware from a machine you can no longer see it in device manager.  This does not mean that it is gone.  Evidence of that is, if for example you had a network card that had a Static IP address set and you remove the card and add a new one then try to set the IP address to the same as the old NIC you will get an error message. The error might look something like “The IP address 192.168.30.100 you have entered for this network adapter is already assigned to another adapter (Microsoft Virtual machine Bus Network Adapter #3) which is no longer present in the computer.  If the same address is assigned to both adapters and they both become active, only one of them will use this address.  This may result in incorrect system configuration”.  In Windows Server 2008 R2 and Windows 7 it actually gives you an opportunity to “remove the static IP configuration for the absent adapter”. If you say Yes, this will eliminate the IP conflict problem but
Read more