default VNC on W2003 64-bit fails to start

Hi,

it's been quite a long time since I've found a real bug in 11.1, but this seems to be one:

I've created a VNC session in default mode. That works fine on a Windows 7 workstation. On my W2003R2 64-bit server (which I still use as a workstation) the default VNC will ..... and will add two entries to the application log:

System.Threading.ThreadAbortException: Thread was being aborted.
at Devolutions.RemoteDesktopManager.Business.HttpBrowserLinker.c36e11a71b2027cacbbca5f70b6ed33df()
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

and

System.DllNotFoundException: Unable to load DLL 'DevolutionsARD': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at Devolutions.Ard.ARDNativeAPI.CreateContext(String host, Int32 port, String username, String password)
at Devolutions.Ard.ArdCustomControl.Connect(String host, Int32 port, String username, String password)
at Devolutions.RemoteDesktopManager.Frames.Embedded.FreEmbeddedAppleRemoteDesktop.Connect()

Also a popup appears, but only once after starting RDM (i.e. not when I try again from the same RDM instance) which says:

Entry Point Not Found
The procedure entry point GetTickCount64 could not be located in the dynamic link library KERNEL32.dll.

This happens on both 32 and 64 bit versions of RDM 11.1. UltraVNC mode (instead of default) works, though.