As of the most recent update by Microsoft for Windows 10, KB4571757, Microsoft has decided to discontinue this feature due to a critical vulnerability discovered in Remote Code Execution. Let’s look into the details of the feature, why it was discontinued, and whether or not we can find a way for it to still work.

What is RemoteFX vGPU?

The VMs running on Hyper-V can use the physical GPU on the host computer to run their tasks concerning video rendering and image processing, using the RemoteFX vGPU feature. This allows users to take the load off of their CPU and run heavy image processing on their VMs using the shared GPU.

What is RemoteFX vGPU? Why did Microsoft remove RemoteFX vGPU feature? How to enable RemoteFX vGPU on Hyper-V running on Windows 10 Alternative for RemoteFX vGPU Configure the VM for DDA Dismount the GPU from the host computer Assign the GPU to the VM Closing words

With this feature, a dedicated GPU for each VM is not required and simultaneously provides enhanced scalability and usability of the GPU, as well as the VMs. Head on to Microsoft’s web page to learn more about the feature.

Why did Microsoft remove RemoteFX vGPU feature?

Although the RemoteFX vGPU feature is old as it was introduced in Windows 7, it is now being exploited by hackers to execute remote commands on the host machine. This feature is not capable of authenticating the input of a valid user on the VM. A hacker can exploit this vulnerability to run modified applications on the VM to exploit the drivers of the host GPU and gain access. Once they have access to the host machine, they are able to execute remote commands and scripts. Although Microsoft addresses such vulnerabilities through their regular updates, they were unable to do so as the flaw is architectural. Microsoft started removing this feature for different versions of the OS back in July 2020. However, the Windows 10 cumulative update for September 2020 disabled the feature in all editions of Windows 10 version 2004. Microsoft states that users will still be able to re-enable the feature until February 2021 through special commands, but should start working on alternative methods which will be discussed further down the article. Here is a notification by Microsoft on disabling RemoteFX vGPU.

How to enable RemoteFX vGPU on Hyper-V running on Windows 10

Although Microsoft has greyed out the feature to enable RemoteFX vGPU through Hyper-V on Windows 10, it can still be enabled through a command using PowerShell. Moreover, the Group Policy Settings are still there within the guest Operating Systems (VMs) which can be used to enable the feature on the VM just as before.

You can now start and connect to the virtual machine and it will now use the host machine’s GPU to process its workload. You may also configure multiple VMs to run on a shared physical GPU.

Alternative for RemoteFX vGPU

Microsoft is permanently planning on removing the feature by February 2021. However, they have not left their users stranded. Microsoft has also proposed an alternative solution to directly mount the physical GPU on the PCIe port to a VM through the Discrete Device Assignment (DDA). This method has three phases which need to be completed in order to provide a VM with a dedicated GPU:

Configure the VM for DDA

On the host computer, run the following commands one after the other to configure its settings. Replace (name) with the name of the VM:

Dismount the GPU from the host computer

Firstly, you need to disable the GPU on the PCIe port, and then dismount it. But before that, you are going to need the port’s physical address. This can be determined by performing the following: Now perform the following to dismount the device: Now that the device has been disabled, you need to dismount it. Enter the following command in Command Prompt:Dismount-VMHostAssignableDevice -force -LocationPath $(LocationPath)Replace (LocationPath) with the PCIe path you had noted earlier. Once done, you may proceed to the next phase.

Assign the GPU to the VM

Now all you need to do is program Hyper-V to let the specified VM use the physical GPU. This can be done by running the command below in Command Prompt:Add-VMAssignableDevice -LocationPath $locationPath -VMName (name)Replace (name) with the name of the VM. You may now start the guest operating system and see that the video adapter it is now using will be the physical one on your host computer. If at any time you wish to return the GPU back to the host device, simply run the following two commands in the same order, one after the other, in the Command Prompt while replacing (name) with the name of the VM:Remove-VMAssignableDevice -LocationPath $locationPath -VMName VMName
Mount-VMHostAssignableDevice -LocationPath $locationPath

Closing words

The RemoteFX vGPU hasn’t been around much for the version 2004. However, people liked the idea of it. Seeing it go might not be as troublesome as anticipated unless you put in the cost factor. Although Microsoft has given an alternative for using designated GPUs for each virtual machine, it would not be ideal to place as many GPUs on the motherboard of the host computer as the virtual machines. The costs would be too high, and power consumption would not be ideal. Microsoft needs to find a workaround for the issue as the solution provided is not feasible for most users.