Symptoms

• Windows 10 Rdp Remotefx
• Windows 10 Rdp Disable Remotefx
• Windows 10 Disable Remotefx
• Windows 10 Rdp Enable Remotefx
• Configure Remotefx Windows 10

Deprecation: RemoteFX vGPU was removed with the release of Windows 10, version 1809 and Windows Server 2019. Disablement: RemoteFX vGPU was 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 April 2021 Windows. RemoteFX is new age Remote Desktop Protocol and enables the GPU (GPU card) virtualization which means sharing a physical graphics adaptor among the multiple virtual machines The virtual machines can offload rendering of graphics information from the processor to the dedicated graphics processing unit (GPU card) attached to the host. As you might know the RDP protocol in Windows 10 consists of different type of codecs (both proprietary and standardized video compression codecs). They belong to a broader set of technologies also known as RemoteFX. There are currently 2 type of codec configurations possible in Windows 10.

RDP Connection attempts to a RemoteFX enabled Terminal Server fail, resulting in the following error on the client:

'The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator.'

The Terminal Server logs the following event:

Event ID: 1152

Source: TerminalServices-RemoteConnectionManager

Windows 10 Rdp Remotefx

Message: The Remote Desktop Virtualization Host server cannot issue a client license. It was unable to issue the license due to a changed (mismatched) client license, insufficient memory, or an internal error.

Cause

This problem occurs when standard RDP security is used by the client to connect to the RemoteFX server.

This can occur under the following conditions:

1. The client is a custom application using the Remote Desktop active control. This control uses standard RDP security by default.

2. The client is 3rd party or Windows Remote Desktop client that is configured to use standard RDP security. Windows XP SP3 and newer Remote Desktop clients use Enhanced RDP security by default and will not exhibit this problem. Older client operating systems use standard RDP security by default, and will exhibit the symptoms listed in this article.

Resolution

The client must be configured to use Enhanced RDP security.

If the client is a custom application using the Remote Desktop ActiveX control, the client must use minimum control version IMsRdpClientAdvancedSettings4 interface and set the AuthenticationLevel property to either 1 or 2 (default level is 0).

Windows XP SP2 clients running MSTSC.exe can work around this licensing problem by using RDP enhanced security (by selecting the 'Attempt authentication' Drop down in the security tab properties of the Remote Desktop Connection client.

Specifies the Remote Desktop Protocol: RemoteFX CodecExtension, which uses a lossy image codec to encode screen images withefficient and effective compression.

This page and associated content may beupdated frequently. We recommend you subscribe to the RSSfeed to receive update notifications.

Published Version

Previous Versions

Preview Versions

From time to time, Microsoft maypublish a preview, or pre-release, version of an Open Specifications technicaldocument for community review and feedback. To submit feedback for a previewversion of a technical document, please follow any instructions specified forthat document. If no instructions are indicated for the document, pleaseprovide feedback by using the Open Specification Forums.

Windows 10 Rdp Disable Remotefx

The preview period for a technical document varies.Additionally, not every technical document will be published for preview.

A preview version of this document may beavailable on the WindowsProtocols - Preview Documents page. After the preview period, themost current version of the document is available on this page.

Development Resources

Findresources for creating interoperable solutions for Microsoft software,services, hardware, and non-Microsoft products:

Plugfestsand Events, Test Tools,DevelopmentSupport, and Open SpecificationsDev Center.

Intellectual Property Rights Notice for Open Specifications Documentation

Windows 10 Disable Remotefx

• Technical Documentation. Microsoft publishes OpenSpecifications documentation (“this documentation”) for protocols, fileformats, data portability, computer languages, and standards support.Additionally, overview documents cover inter-protocol relationships andinteractions.

• Copyrights. This documentation is covered by Microsoftcopyrights. Regardless of any other terms that are contained in the terms ofuse for the Microsoft website that hosts this documentation, you can makecopies of it in order to develop implementations of the technologies that aredescribed in this documentation and can distribute portions of it in yourimplementations that use these technologies or in your documentation asnecessary to properly document the implementation. You can also distribute inyour implementation, with or without modification, any schemas, IDLs, or codesamples that are included in the documentation. This permission also applies toany documents that are referenced in the Open Specifications documentation.

• No Trade Secrets. Microsoft does not claim any tradesecret rights in this documentation.

• Patents. Microsoft has patents that might cover yourimplementations of the technologies described in the Open Specificationsdocumentation. Neither this notice nor Microsoft's delivery of thisdocumentation grants any licenses under those patents or any other Microsoftpatents. However, a given Open Specifications document might be covered by theMicrosoft Open Specifications Promiseor the Microsoft CommunityPromise. If you would prefer a written license, or if thetechnologies described in this documentation are not covered by the OpenSpecifications Promise or Community Promise, as applicable, patent licenses areavailable by contacting iplg@microsoft.com.

• License Programs. To see all of the protocols in scopeunder a specific license program and the associated patents, visit the Patent Map.

• Trademarks. The names of companies and products containedin this documentation might be covered by trademarks or similar intellectualproperty rights. This notice does not grant any licenses under those rights.For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.

• Fictitious Names. The example companies, organizations,products, domain names, email addresses, logos, people, places, and events thatare depicted in this documentation are fictitious. No association with any realcompany, organization, product, domain name, email address, logo, person,place, or event is intended or should be inferred.

Reservation of Rights. All otherrights are reserved, and this notice does not grant any rights other than asspecifically described above, whether by implication, estoppel, or otherwise.

Windows 10 Rdp Enable Remotefx

Tools.The Open Specifications documentation does not require the use of Microsoftprogramming tools or programming environments in order for you to develop animplementation. If you have access to Microsoft programming tools andenvironments, you are free to take advantage of them. Certain OpenSpecifications documents are intended for use in conjunction with publiclyavailable standards specifications and network programming art and, as such,assume that the reader either is familiar with the aforementioned material orhas immediate access to it.

Configure Remotefx Windows 10

Support.For questions and support, please contact dochelp@microsoft.com.