Solved Remote Desktop Internal Error has occured

[redhook]

Hello, I can't use Windows Remote Desktop Connection because everytime I do it says "An Internal Error Has Occured". I was using it about a week ago and there have been no major hardware changes so i can't figure it out.

I am using Windows 10 and HMA! Pro VPN (still doesn't work when I disable this)

Are there any other simple RDP's like Microsoft's that I could try if I can't fix this error?

Any help would be greatly appreciated thanks.

 

[GokAy]

Checkout TeamViewer, it is free for personal use.

 

[redhook]

I use Team Viewer but how do you access a PC remotly when it's just a IP address user name and password. TeamViewer uses these stupid "partner ID" codes.

 

[UsernameIssues]

GokAy is correct to point you to TeamViewer's excellent tool; however, TeamViewer is not an RDP tool. It does not use Microsoft's proprietary Remote Desktop Protocol.

You must have TeamViewer installed on each remote computer as well. For unattended access, TeamViewer must be configured to run all of the time on each remote computer of interest. On your end, you will need to keep a list of the TeamViewer ID (and password) for each remote computer. If desired, you can create a free account with TeamViewer and keep the list of TeamViewer credentials in the TeamViewer client on your computer (and/or smart phone).

TeamViewer creates a connection between your computer and TeamViewer's servers. The remote computer does the same. Once a connection is requested and authentication completes, a direct connection is established between your computer and the remote computer. You won't need a VPN tool. However, I'm pretty sure that TeamViewer automatically use the VPN tool's connection if it is already there. It has been a while since I looked at my VPN traffic while connected to a remote computer via TeamViewer and a VPN tool at the same time.

TeamViewer has its own VPN tool. I've never used it.

In my opinion, TeamViewer's authentication method is better than RDC/RDP and many other remote control tools.

Sadly, TeamViewer cannot be used for free by the non-profits that I support... and TeamViewer is way too expensive to purchase.

 

[GokAy]

Agreed it is expensive for licensing. By the way, TeamViewer has a LAN option (no need to go through net connection)
https://www.teamviewer.com/en/help/40-Can-TeamViewer-be-used-within-a-local-network-LAN-only

 

[UsernameIssues]

Agreed it is expensive for licensing. By the way, TeamViewer has a LAN option (no need to go through net connection)
https://www.teamviewer.com/en/help/40-Can-TeamViewer-be-used-within-a-local-network-LAN-only

That might indeed be what the OP needs

 

[GokAy]

By the way, I have few ideas that you can try on either/both machines:
- Try a clean startup - http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html
- Run RDC as admin in case it is trying to change a registry or something.

 

[redhook]

By the way, I have few ideas that you can try on either/both machines:
- Try a clean startup - http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html
- Run RDC as admin in case it is trying to change a registry or something.

Tried that didn't work. Also tried installing LogMeIn and that gives me a 1920 error on install. After looking for hours online the conscious is it's either a firewall, antivirus, malware, or registry issue, or a windows background process called WMI.

Here's what I have done:

1)I turned off windows firewall and antivirus.
2)Ran malwarebytes
3)messed around in the regedit and followed this instruction:"Go to HKEY_CLASSES_ROOT\AppID registry >Right Click on the folder > Permissions > Add > Type = NETWORK SERVICE > OK > Check Full Control > Apply > OK"
4)turned WMI to automatic and started it.

All still not working in Windows Remote Desktop or LogMeIn.

It's must be some kind of incoming or outgoing network problem, that's all I can think.

 

[GokAy]

Did you try RDPing in with another PC or perhaps your phone?

 

[redhook]

Thanks guys for helping me but I fixed it the old fashioned way that I should have used from the start. I used System Restore and set it back a week and now it's working. What went wrong I'll never know.

 

[GokAy]

That works too