> For the complete documentation index, see [llms.txt](https://legacy.docs.synteq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy.docs.synteq.com/gpu-vds/windows-optimization/enabling-gpu-acceleration-for-rdp-on-windows.md). # Enabling GPU acceleration for RDP on Windows How to enable GPU acceleration for RDP on a Windows GPU VDS ### 1. Connect to your server Start by connecting to your GPU VDS server via RDP. This can be done with the built-in RDP program on Windows, or the [Windows app](https://apps.apple.com/pl/app/windows-app/id1295203466?l=pl\&mt=12) on MacOS ### 2. Enter the registry Enter the Windows run command using the `Windows+R` shortcut, and run `gpedit.msc` \[1], then click on the `OK` \[2] button.

### 3. Enable the following properties In the registry editor, enable all of the propeties under: {% code overflow="wrap" %} ``` Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > RemoteFX For Windows Server 2008 R2 ``` {% endcode %}

### 4. Enable hardware graphics acceleration Start by going to the Control Panel, then go to `System and Security`.

Afterward, go to `System`.

Click on `Advanced system settings`.

Then, under the `Advanced` tab, on `Performance` section, click on `Settings...`.

In here, you can either select: `Let Windows choose what's best for my computer` or `Adjust for best appearance`

### 4. Restart the server Afterward, restart your server.

And just like that, you have enabled GPU acceleration for your RDP sessions! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://legacy.docs.synteq.com/gpu-vds/windows-optimization/enabling-gpu-acceleration-for-rdp-on-windows.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.