Windows Remote Desktop on Windows 10 cannot connect to client

[Jacob Klein]

When I try to use Remote Desktop to connect to a running VM, I am getting the error below, even when the Windows Firewall is turned off, using Oracle VirtualBox 4.3.29 r101039. Note that I can connect fine on a Windows 8.1 host, but a Windows 10 host will always return the error below.

Can you please fix it?

---

[Window Title] Remote Desktop Connection

[Content] This computer can't connect to the remote computer.

Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator.

[OK] [Help]

---

[mizzao]

I am also getting this error from the Windows 8.1 mstsc client now. It may have something to do with an update to the protocol?

[sunlover]

Please test:

https://www.virtualbox.org/download/testcase/Oracle_VM_VirtualBox_Extension_Pack-4.3.31-101730.vbox-extpack

This should fix the problem. Thanks!

[Jacob Klein]

I tested that version of the Extension Pack. It appears to fix the RDP connection problems on my Windows 10 machine. Thanks! Any idea what caused this? Some sort of Oracle code regression, or some change Microsoft made?

[sunlover]

MS changed a capability field in the client, and the VRDP server was too strict in checking it.

[Jacob Klein]

Thank you for fixing it, and thank you for explaining it!

[Ayylmao]

This issue is still a problem for VirtualBox 5.0. Can you make a fix for the latest version of VirtualBox? Thanks!

[GimmiLFactorY]

Holy crap, I've been looking for a solution to this issue. I even just rolled back to windows 8.1 on my laptop to see if that would fix it, apparently it has been an issue for a while, I just never knew until I got rid of Windows 7 on my desktop, I am about to do a fresh install so we'll see; seeing as it was fine on there. So I thought I broke my servers when they're just fine and it is this angering bug? Good Game me!

Confirmed, very annoying, spent two days trying to figure this out.

I can not install that version of extpack with VB5, I get the following:

0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to install "/home/gimmil/Oracle_VM_VirtualBox_Extension_Pack-4.3.31-101730.vbox-extpack"
VBoxManage: error: Failed to load the main module ('/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxPuelMain.so'): VERR_FILE_NOT_FOUND - /usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxPuelMain.so: undefined symbol: RTLogRelDefaultInstance
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ExtPackManagerWrap, interface IExtPackManager
VBoxManage: error: Context: "RTEXITCODE handleExtPack(HandlerArg*)" at line 1158 of file VBoxManageMisc.cpp

[NginUS]

I'm having the same problem on VirtualBox 5 & Windows 10. Would like to implement a fix ASAP.

Hopefully this can get bumped up in priority with Win10 being rolled out to the masses now...

[dresta2]

Same issue. Any ETA on a fix?

[Frank Mehnert]

The fix is already available in the latest builds on this page. It will be part of the next 4.3.x / 5.0.x maintenance releases. It's sufficient to install the new Extension Pack.

[NginUS]

Replying to frank:

The fix is already available in the latest builds on this page. It will be part of the next 4.3.x / 5.0.x maintenance releases. It's sufficient to install the new Extension Pack.

VirtualBox-5.0.1-101908-Win with Oracle_VM_VirtualBox_Extension_Pack-5.0.1-101880 works, thank you.

[GimmiLFactorY]

I installed it and it isn't working, going to do another reformat, I think I messed with too many things while trying to diagnose it; LOL oops.

*Edit 12 hrs later at 11am...YAY IT WORKS. Thank you vbox for fixing this.

[DThimsen]

Any chance that a new 4.2 extension pack will be created to fix this problem. We have lots of test VMs that use VirtualBox 4.2, and Windows 10 RDC can't access the VMs.

[Frank Mehnert]

DThimsen, to be honest there is currently no plan to backport this fix to 4.2.x. The official support for 4.2.x will end in 12/2015 and we encourage all users to switch to 5.0 or at least to 4.3.x.

[Frank Mehnert]

Fix is part of VBox 5.0.2.