Update to disable and remove the RemoteFX vGPU component in Windows

[Brink]

Update to disable and remove the RemoteFX vGPU component in Windows

Applies to: Windows 7 Service Pack 1, Windows Server 2012, Windows 8.1, Windows 10, Windows 10 version 1607 all editions, Windows 10 version 1703 all editions, Windows 10 version 1709 all editions, Windows 10 version 1803 all editions, Windows 10 version 1809 all editions, Windows 10 version 1903 all editions, Windows 10 version 1909 all editions, Windows 10 version 2004 all editions

Overview

RemoteFX vGPU makes it possible for multiple virtual machines to share a physical GPU. This feature was first introduced in Windows 7 and was removed as an option for users in Windows Server 2019. The current implementation of RemoteFX vGPU appears susceptible to security vulnerabilities (see the FAQ section for CVE details). Because these newly identified vulnerabilities are architectural in nature, and the feature is already removed from newer versions of Windows, the July 14, 2020 security updates and all superseding Windows Updates will disable and remove the RemoteFX vGPU feature. Starting with the July 14, 2020 security updates, this and all superseding Windows Updates will disable the RemoteFX vGPU feature.\

Although users have the ability to re-enable RemoteFX vGPU until February 2021, we strongly encourage that users seek an alternative vGPU option.

Timeline

• Deprecation: RemoteFX vGPU was removed with the release of Windows 10, version 1809 and Windows Server 2019.
• Disablement: RemoteFX vGPU will be disabled in all applicable Windows platforms in the July 2020 Windows security updates (July 14, 2020).
• Removal: RemoteFX vGPU will be removed from all applicable Windows platforms in the February 2021 Windows security updates (February 9, 2021)

Alternatives

In order to mitigate potential security risks within RemoteFX vGPU, we strongly recommend that users consider using an alternative vGPU technology.

Secure GPU virtualization is available through Discrete Device Assignment (DDA) in Windows Server LTSC releases (Windows Server 2016, Windows Server 2019) and Windows Server SAC releases (Windows Server, version 1803 and later versions).

How to re-enable RemoteFX vGPU

For Windows 10, version 1803 and earlier versions

1. To configure RemoteFX vGPU, add the RemoteFX 3D graphics adapter to the virtual machine (VM). For more information, see Configure the RemoteFX vGPU 3D adapter.
2. To configure the RemoteFX vGPU 3D adapter, use one of the following methods:

Method 1: Configure RemoteFX vGPU with Hyper-V Manager ​​​​​

To configure the RemoteFX vGPU 3D by using Hyper-V Manager, follow these steps:

1. Stop the VM if it's currently running.
2. Open Hyper-V Manager and navigate to VM Settings, and then select Add Hardware.
3. Select RemoteFX 3D Graphics Adapter, and then select Add.

Method 2: Configure RemoteFX vGPU with PowerShell cmdlets

To configure the RemoteFX vGPU 3D adapter, you must use the following PowerShell cmdlets:

• Add-VMRemoteFx3dVideoAdapter
• Get-VMRemoteFx3dVideoAdapter
• Set-VMRemoteFx3dVideoAdapter
• Get-VMRemoteFXPhysicalVideoAdapter

Frequently asked questions

What is the current level of support Microsoft will provide for RemoteFX vGPU?
We will provide technical assistance for users who want to re-enable RemoteFX vGPU until February 2021. We will not continue to ship security or nonsecurity updates for RemoteFX vGPU.

What will happen to my VM with RemoteFX vGPU enabled on July 14, 2020?

• If the VM is in a Saved state, you will see the following error message and will be required to remove the RemoteFX adapter to resume:The virtual machine cannot be started because the server has insufficient GPU resources.
• If the VM is in a Shutdown state, there is no error message.
• If the VM is in a Start state, you will see an error message upon a Restart.

What are the alternatives to RemoteFX vGPU?
Secure GPU virtualization is available through Discrete Device Assignment (DDA) in Windows Server LTSC releases (Windows Server 2016 and Windows Server 2019) and Windows Server SAC releases (Windows Server, version 1803 and later versions). If you are on a Windows version earlier than Windows 10, version 1607, please consider upgrading.

What security vulnerabilities am I susceptible to if I re-enable RemoteFX vGPU?
Please refer to the following CVEs for more information:

• CVE-2020-1032
• CVE-2020-1036
• CVE-2020-1040
• CVE-2020-1041
• CVE-2020-1043
• CVE-2020-1042

Are any other RemoteFX features affected by this disablement?
No. RemoteFX vGPU is the only RemoteFX feature being disabled.

Source: https://support.microsoft.com/en-us...isable-and-remove-the-remotefx-vgpu-component

 

[jim davis]

Thank you Mr. Brink
As I read this on a 7 OS, that no longer receives support, I must ask, will I get a up date that will remove this feature, or must i go in and pick it out, ha ha the latter would not be a good thing, I being a comp idiot, if yes, should i turn updates back ON, as I believe I have them blocked

 

[Brink]

Thank you Mr. Brink
As I read this on a 7 OS, that no longer receives support, I must ask, will I get a up date that will remove this feature, or must i go in and pick it out, ha ha the latter would not be a good thing, I being a comp idiot, if yes, should i turn updates back ON, as I believe I have them blocked

Hello Jim,

No need to do anything since it has been automatically disabled. This was just a status update about it.

 

[AK6DN]

Hello Jim,

No need to do anything since it has been automatically disabled. This was just a status update about it.

How can this feature be 'automatically disabled' if Windows 7 is not receiving updates since January?


Unless of course you happen to be in an enterprise that is receiving Win7 ESU updates.


Not most folks, however.

 

[feetand nches]

Prerequisite:

The Extended Security Updates (ESU) Licensing Preparation Package (KB4538483) released February 11, 2020. The ESU licensing preparation package will be offered to you from WSUS. To get the standalone package for ESU licensing preparation package, search for it in the Microsoft Update Catalog.

Same thing with: July 14, 2020—KB4565539 (Security-only update)