The following applies to Hyper-V on Windows Server 2012 and 2012 R2.

If you find yourself playing with Hyper-V’s RemoteFX features, you’ll probably find yourself in this particular pickle soon enough…

First, here’s a link to a good article on how to set up Hyper-V with RemoteFX:

Step 14 of Installation and configuration of RemoteFX vGPU is where things go wrong.
After adding a RemoteFX 3D adapter to a VM and hitting apply or OK, an error pops up.


Now, at first I thought this might be due to my tinkering around on a consumer grade laptop with a basic AMD Radeon HD 7600 GPU, which – strictly speaking – isn’t supported. I did however find that this GPU is supported for Windows server 2008 R2 x64. And my laptop hardware configuration does meet the requirements as listed in the Technet article. So what gives?

It’s a bug! It’s been reported by the community (here & here & here amongst others) and it’s been there ever since Windows Server 2012 Release Candidate and it’s still here in 2012 R2 build 6.3.9600.16384.

The solution to use PowerShell instead of the Hyper-V GUI is mentioned in several posts and it works, but I have noticed it carries one little error.

Import-Module RemoteDesktopServices

Add-VMRemoteFx3dVideoAdapter -VMName

The cmdlet to be used is indeed Add-VMRemoteFx3dVideoAdapter, however it is not in the RemoteDesktopServices module. Instead, it’s in the Hyper-V module.


To be fair, when you start a PowerShell session on your Remote Desktop/Hyper-V server, it will load both modules anyway so the whole Import-Module step is a bit irrelevant here. Just so you know, in case you’re using Windows 7 or 8/8.1 to manage your server remotely, there’s no need for the RSAT tools or PowerShell Module for Remote Desktop. Just stick to the guidelines for Hyper-V remote management and you’ll be fine.

Now go and watch some full screen 1080p YouTube streams or make a CAD drawing or something via Remote Desktop. Just because you can 🙂