My laptop is running Windows 8.1 and since yesterday has starting giving problems when connecting to remote PCs using Remote Desktop Connection.

It asks for the password and then shows 'Configuring remote session' for about 30 seconds and then displays 'An internal error has occurred'.   Another PC on the same network is able to connect to the remote PC without problem.  I've tried connecting to four other PCs with this laptop and two work and three don't.

I've tried changing various settings such as bitmap caching and clipboard sharing etc.  Nothing makes a difference.

I've also used system restore to reverse recent windows updates and that hasn't helped either.

Any ideas?

What can cause 'An internal error has occurred'?  Will it be writing to a log somewhere that I can look at to find further information about the error?

Thanks

Andy

Probably, there is something wrong with your user profile.

You could try to fix this issue by using the method by bokken in the next thread.

https://social.technet.microsoft.com/Forums/windowsserver/en-US/1f64168e-1f65-4917-ae78-3556b3e771a3/rdp-stuck-on-configuring-remote-session?forum=winserver8gen

I'm not sure if you meant there could be a problem with the user profile on the laptop or the one on the server I'm trying to connect to?

However, it seems to be the latter.  I just created a new user account on the server and can now remote into it from my laptop.  If I try the original user account again (Administrator) then I get the internal error message.  Other client PCs can still log-in to the server using the same Administrator account without problem.

Is there something I can do (either to client or server) to clear the fault with the Adminstrator account without wiping that account on the server?

What is the operating system on the server?

You could do the following steps on the server.

Administrative Tools --> Remote Deskotp Services --> Remote Desktop Services Manager

Find the original user account on the list and select Log Off.

Verify that this user is not showing on the list at all.

Then you can test the Remote Desktop Connection again.

• Proposed as answer by Roger LuMicrosoft contingent staff, Moderator Wednesday, January 21, 2015 2:43 PM
• Marked as answer by Yolanda ZhuMicrosoft contingent staff, Moderator Tuesday, January 27, 2015 9:59 AM

I'm having the same problem since I've upgraded to W10.  I'm connected through the Sonic Wall VPN client but I get an internal error from RDC.  I can ping the remote computer and I've cleared the profile and started over.  No luck.

Same problem here since upgraded to Windows 10. Target computer is a Windows 7.

Apparently, my newly upgraded Windows 10 can connect via Remote Desktop to Windows Server 2012 R2 but not to computers running Windows 7.

Other computers running Windows 7 can connect to the target computer (Win7)