View a markdown version of this page

WorkSpaces Windows client application - Amazon WorkSpaces

WorkSpaces Windows client application

The following information will help you get started with the WorkSpaces Windows client application.

Requirements

Setup and installation

Download and install the latest version of the Amazon WorkSpaces client application from Amazon WorkSpaces Client Download.

You have two choices for how to install the Amazon WorkSpaces client application:

  • Install just for you. If you choose this option and you share your local machine with other users, the WorkSpaces client application is available only to you. If other users on the machine also want to use the WorkSpaces client application, they must install the application for their own use.

  • Install for all users of this machine. If you choose this option, the WorkSpaces client application is available to anyone who logs on to the local machine, including those with Guest accounts.

Installing the WorkSpaces client application for all users requires you to have administrator privileges on your local machine. Depending on how your local machine is configured, you might not have such privileges. In that case, you can install the WorkSpaces client application just for yourself. If you have questions about which option to choose, ask your WorkSpaces administrator for guidance.

Installing the USB redirection driver

To use your local USB devices on the remote session, you will need to install the USB redirection driver. To install this driver, you will need to install the WorkSpaces application for all users, and then check the box to Install driver for USB redirection.

Determine your client version

To see which version of the WorkSpaces client you have, choose Amazon WorkSpaces, About Amazon WorkSpaces, or click the gear icon in the upper-right corner and choose About Amazon WorkSpaces.

Client application updates

The Amazon WorkSpaces client application on Windows will automatically check for available updates, and when new versions become available, will install them in the background when you’re not using it. Once the installation is complete, you simply need to open the client to begin using the latest version. This will provide you with faster access to the latest features, enhancements, and bug fixes without interrupting your productivity.

Client updates maintain the same installation context as the original installation. This means if the Amazon WorkSpaces client was originally installed for all users on the local machine, future automatic updates will apply to all users. Similarly, if the client was installed for a single user, future updates will only apply to that specific user. Should you need to change this behavior, you can uninstall the client application and reinstall it under your preferred installation context.

Note

Automatic client updates are only applied when your client application is used to connect to WorkSpaces in the following regions.

AWS Region Address

US East (N. Virginia)

us-east-1

US West (Oregon)

us-west-2

Africa (Cape Town)

af-south-1

Asia Pacific (Mumbai)

ap-south-1

Asia Pacific (Seoul)

ap-northeast-2

Asia Pacific (Singapore)

ap-southeast-1

Asia Pacific (Sydney)

ap-southeast-2

Asia Pacific (Tokyo)

ap-northeast-1

Canada (Central)

ca-central-1

Europe (Frankfurt)

eu-central-1

Europe (Ireland)

eu-west-1

Europe (London)

eu-west-2

Europe (Paris)

eu-west-3

Israel (Tel Aviv)

il-central-1

South America (São Paulo)

sa-east-1

In any other regions not listed above, the Amazon WorkSpaces client application on Windows will not update automatically; you will instead see an message when a new version is available, and will have the option to install it.

Opting out from automatic updates (Windows client only)

We encourage you to take advantage of the new automatic client update feature so you always have access to the latest features, security patches, and bug fixes. However, if you or your administrator want to manage client updates manually, you can opt out by following these steps for Windows clients.

Note

Opting out from automatic updates is supported for the Windows client application only.

Administrator privileges are required on the local device.

  1. Open the by Type "registry editor" in the Windows search box.

  2. Right-click on Registry Editor and select Run as administrator.

  3. If prompted for permission, choose Yes.

  4. Open a command line.

  5. Navigate to: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Amazon\.

  6. If it does not already exist, create a new Key called "Amazon WorkSpaces Client".

  7. Within this key, create a new String Value named "clientUpgradeDisabled" and set its value to 1.

  8. Either restart your computer or do the following to apply the changes:

    1. Open the Task Manager.

    2. Go to the Processes tab.

    3. Search for one of the following:

      • For an "all users" installation, search for WorkSpacesService.exe.

      • For a "single user" installation, search for WorkSpacesHelper.exe.

    4. Right-click and select End process.

  9. For organizations managing multiple Windows devices, this registry setting can be deployed using Group Policy:

    HKEY_LOCAL_MACHINE\SOFTWARE\Amazon\Amazon WorkSpaces Client\clientUpgradeDisabled Type: REG_SZ Value: 1

IPv6 network settings

The WorkSpaces Windows client application supports connecting to your WorkSpace using IPv4, IPv6, or dual-stack (both IPv4 and IPv6) addresses. By default, IPv4 connections are used for streaming. IPv6 connections are disabled by default, meaning that your client application will exclusively use an IPv4 network for your connection. If you enable IPv6 connections, your client application will prioritize using an IPv6 network, but will fall back to using an IPv4 network if IPv6 is not available.

Note

IPv6 connections are supported on the WorkSpaces client application version 5.30.1 or later.

You cannot change IPv6 connection settings if you are connected to your WorkSpace. Change the setting before connecting to your WorkSpace.

Use the following procedure to enable IPv6 connections.

  1. In the WorkSpaces client application, navigate to Settings >, Manage Connection Settings.

  2. Under General Connection Settings, choose Prefer IPv6-enabled communications.

Alternatively, you can also enable IPv6 connections by using the following registry key:

  1. On the Windows client, enter registry editor in the Windows search bar.

  2. Right-click on Registry Editor and select Run as administrator.

  3. If prompted for permission, choose Yes.

  4. In the Registry Editor, navigate to: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Amazon\Amazon WorkSpaces Client\

  5. Within this key, create a new DWORD (Double Word) Value named WSUseDualStackIPv6.

    1. Set its value to 1 to enable IPv6 preferred connections.

      Set its value to 0 to disable IPv6 preferred connection, and enable IPv4 connections exclusively.

  6. Changes you make will take effect the next time you launch the WorkSpaces client application. Users can modify this setting, but it will revert to the default registry key value when the client is relaunched.

Connect to your WorkSpace

To connect to your WorkSpace, complete the following procedure.

  1. The first time that you run the client application, you are prompted for your registration code, which is contained in your welcome email. The WorkSpaces client application uses the registration code and user name to identify which WorkSpace to connect to. When you launch the client application later, the same registration code is used. To enter a different registration code, launch the client application, and then choose Change Registration Code at the bottom of the login page.

  2. Enter your sign-in credentials in the login screen and choose Sign In. If your WorkSpaces administrator has enabled multi-factor authentication for your organization's WorkSpaces, you are prompted for a passcode to complete your login. Your WorkSpaces administrator will provide more information about how to obtain your passcode.

  3. If your WorkSpaces administrator has not disabled the Keep me logged in feature, you can select the Keep me logged in check box at the bottom of the login screen to save your credentials securely so that you can connect to your WorkSpace easily while the client application remains running. Your credentials are securely cached up to the maximum lifetime of your Kerberos ticket.

    After the client application connects to your WorkSpace, your WorkSpace desktop is displayed.

An interruption of network connectivity causes an active session to be disconnected. This can be caused by events such as closing the laptop lid, or the loss of your wireless network connection. The WorkSpaces client application for Windows attempts to reconnect the session automatically if network connectivity is regained within a certain amount of time. The default session resume timeout is 20 minutes, but this timeout can be modified by your network administrator.

Manage your login information (3.0+ clients only)

You can view your registration code and what Region your WorkSpace is in. You can specify whether you want the WorkSpaces client application to save your current registration code, and you can assign a name to your WorkSpace. You can also specify if you want Amazon WorkSpaces to keep you logged in to a WorkSpace until you quit or your login period expires.

To manage your login information for a WorkSpace
  1. In the WorkSpaces client application, go to Settings, Manage Login Information.

  2. In the Manage Login Information dialog box, you can see the registration code and Region information for your WorkSpace.

  3. (Optional) If you want the WorkSpaces client to remember your current registration code, select the Remember Registration Code check box.

  4. Under Saved registration codes, select the WorkSpace that you want to name.

  5. In the WorkSpace name box, enter a name for the WorkSpace.

  6. (Optional) If you want WorkSpaces to keep you logged in until you quit or your login period expires, select the Keep me logged in check box.

  7. Choose Save.

Client views

You can switch to full screen mode by choosing View, Enter Full Screen (3.0+ clients) in the client application menu.

While in full screen mode, you can switch back to window mode by moving the pointer to the top of the screen. The client application menu is displayed, and you can choose View, Leave Full Screen (3.0+ clients) in the client application menu.

You can also toggle full screen mode by pressing Ctrl+Alt+Enter.

Client language

You can select the language displayed by the client by performing the following steps.

Note

The WorkSpaces client applications support Japanese. However, Japanese WorkSpaces are available only in the Asia Pacific (Tokyo) Region.

To select the client language
  1. Depending on which client you're using, do one of the following.

    If you're using... Do this

    3.0+ client

    In the WorkSpaces client application, go to Settings, Change Language.

  2. Enter your desired language in the Select a language list and choose Save.

  3. Restart the client.

Display support

WorkSpaces WorkSpaces Value, Standard, Performance, Power, PowerPro, and GPU-enabled bundles support a maximum of four displays and a maximum resolution of 3840x2160 (ultra-high definition, or UHD). The maximum supported resolution depends on the number of displays, as shown in the following table.

Displays Resolution

2

3840x2160

4

1920x1200

Note
  • You can only extend the display. You cannot duplicate the display. Duplicating the display will cause your session to be disconnected.

The WorkSpaces client application extracts the Extended Display Information Data (EDID) of all attached displays and determines the best compatibility match before starting the session. If you have a high pixel density (high DPI) display, the client application automatically scales the streaming window according to your local DPI settings. For better maximum resolution with high DPI displays, see Enabling high DPI display for WorkSpaces.

To use multiple monitors with WorkSpaces
  1. Configure your local machine to use multiple monitors. For more information, see How to use multiple monitors in Windows 10 in the Microsoft documentation.

  2. Start the WorkSpaces client application and log in to your WorkSpace.

  3. Depending on which client you're using, do one of the following:

    If you're using... Do this
    3.0+ client Choose View, Enter Full Screen On All Displays. You can also toggle full screen mode by pressing Ctrl+Alt+Enter.

Your WorkSpace should now be extended across your displays. Whichever display you have designated as your primary display is also the primary display in WorkSpaces when you enter full screen mode.

Note

Using full screen mode on only some of the displays in a multiple monitor setup isn't possible. You can, however, press the Windows logo key + Up Arrow or use the maximize button in the upper-right corner of the WorkSpaces window to maximize the WorkSpaces client window on a display without extending the WorkSpace to the other displays.

Proxy servers

If your network requires you to use a proxy server to access the internet, you can enable your WorkSpaces client application to use a proxy for HTTPS (port 443) traffic. The WorkSpaces client applications use the HTTPS port for updates, registration, and authentication.

Note
  • The desktop streaming connections to the WorkSpace require ports 4172 and 4195 to be enabled, and do not go through the proxy server.

  • Proxy servers that require authentication with sign-in credentials are not supported.

By default, the 3.0+ Windows clients use the proxy server that's specified in the device operating system settings. The first time the client is launched, the device operating system proxy server setting is used. If you select another option for the proxy server, that setting is used for subsequent launches of the client. If a proxy server is specified at both the operating system level and in the WorkSpaces client, the client setting is used.

Starting with version 3.0.12 of the Windows client, you can also choose not to use a proxy server.

Note

In versions 3.0.0 through 3.0.11, if you specify a custom proxy server, a "No network" error might appear when you attempt to log in to your WorkSpace. If you want to use a custom proxy server with the Windows client, we recommend upgrading to the latest version.

  1. In the WorkSpaces client application, go to Settings, Manage Proxy Server.

  2. In the Set Proxy dialog box, select the appropriate options, depending on which version of the 3.0+ client you have.

    • Windows client version 3.1.3 or later — To disable usage of a proxy server, select Don't use proxy server. If you select Don't use proxy server, no proxy server is used when you access the internet.

      To use a proxy server, choose one of the following options, and then choose Save:

      • Use your device operating system settings — This option uses the proxy server settings for your operating system.

      • Customize proxy server for WorkSpaces — Enter the URL or IP address and the port for your custom proxy server.

    • Windows client versions 3.0.12, 3.1.0, and 3.1.2 — To enable or disable usage of a proxy server, select or deselect Use proxy server. If you deselect Use proxy server, no proxy server is used when you access the internet.

      If you've selected Use proxy server, choose one of the following options, and then choose Save:

      • Use your device operating system settings — This option uses the proxy server settings for your operating system.

      • Customize proxy server for WorkSpaces — Enter the URL or IP address and the port for your custom proxy server.

    • Windows client version 3.0.11 or earlier — By default, these versions of the client use the proxy server specified in the device operating system settings. To use a custom proxy server, choose Use proxy server, enter the URL or IP address and the port for the proxy server, and then choose Save.

Command shortcuts

The WorkSpaces Windows client supports the following command shortcuts:

  • Ctrl+Alt+Enter—Toggle full screen display

  • Ctrl+Alt+F12—Disconnect session

Disconnect

To disconnect the Windows client application, you have several options:

  • In the Amazon WorkSpaces client application, go to Amazon WorkSpaces, and then choose Disconnect WorkSpace. Your WorkSpace session ends, but the client application continues running in case you want to log in again.

  • In the Amazon WorkSpaces client application, go to Amazon WorkSpaces, and then choose End Session.

    When ending the session, you'll be prompted to save open documents. Selecting End Session in the prompt will disconnect you from the WorkSpaces client user session.

    Note

    This option is available only for WorkSpaces Pools.

  • In the Amazon WorkSpaces client application, go to Amazon WorkSpaces, and then choose Quit Amazon WorkSpaces. Your WorkSpace session ends, and the client application closes.

  • In the Amazon WorkSpaces client application, close the WorkSpaces client window by clicking the close (X) button in the upper-right corner. This disconnects the session and returns you to the application homepage.

  • You can also log off of the WorkSpace. In the Amazon WorkSpaces client application, go to View, and then choose Send Ctrl+Alt+Delete. Choose Sign Out. Your WorkSpace session ends, but the client application continues running in case you want to log in again.

Clipboard support

The clipboard supports a maximum uncompressed object size of 20 MB. For more information, see I'm having trouble copying and pasting.

Note

When copying from a Microsoft Office app, the clipboard only contains the last copied item, and the item is converted into standard format. If you copy content larger than 890 KB from a Microsoft Office app, the app might become slow or unresponsive for up to 5 seconds.

Manage hardware acceleration

Starting with version 5.0.0, hardware acceleration is enabled by default when you're using the Amazon WorkSpaces Windows client application.

Note

If you plan to upgrade to a version between 3.1.4 and 5.0.0, and if you've disabled hardware acceleration for version 3.1.3 or earlier by using the procedure described later in this section, make sure that you re-enable hardware acceleration in Windows by setting the DisableHWAcceleration registry key to 0. Then you can upgrade to a version between 3.1.4 and 5.0.0 of the WorkSpaces Windows client application.

If you're experiencing high CPU usage or slower performance when using the client, you might want to enable hardware acceleration in the client.

Note

If you enable hardware acceleration in the Windows client, the following issues might occur with a few video driver versions:

  • The screen might have flickering black boxes in some places.

  • The screen might not properly update on the WorkSpaces login page, or it might not properly update after you log in to your WorkSpace. You might see artifacts on the screen.

  • Your mouse clicks might not be lined up with the cursor position on the screen.

  1. Choose Settings, Manage Hardware Acceleration.

  2. In the Manage Hardware Acceleration dialog box, select Enable Hardware Acceleration for Amazon WorkSpaces, and then choose Save.

  3. For this change to take effect, choose Amazon WorkSpaces, Quit Amazon WorkSpaces to close the Windows client application.

  4. Restart the WorkSpaces Windows client application. Hardware acceleration should now be enabled.

    After you've enabled hardware acceleration in the Windows client, if the screen and mouse issues described earlier occur, clear the Enable Hardware Acceleration for Amazon WorkSpaces check box to disable hardware acceleration, and then restart the Windows client application.

WorkSpaces administrators can enable hardware acceleration in version 3.1.4 or later of the WorkSpaces Windows client by using the following commands in a Command Prompt or PowerShell window.

  1. Use the following command to check for the EnableHwAcc registry key.

    reg query "HKCU\SOFTWARE\Amazon Web Services. LLC\Amazon WorkSpaces" /v EnableHwAcc
  2. Use the following command to add the EnableHwAcc registry key.

    reg add "HKCU\SOFTWARE\Amazon Web Services. LLC\Amazon WorkSpaces" /v EnableHwAcc

    This registry setting takes effect after the WorkSpaces Windows client is closed and restarted.

If needed, use the following command to delete the EnableHwAcc registry key.

reg delete "HKCU\SOFTWARE\Amazon Web Services. LLC\Amazon WorkSpaces" /v EnableHwAcc /f

This registry setting takes effect after the WorkSpaces Windows client is closed and restarted.

  1. Choose Settings, Manage Hardware Acceleration.

  2. In the Manage Hardware Acceleration dialog box, unselect Enable Hardware Acceleration for Amazon WorkSpaces, and then choose Save.

  3. For this change to take effect, choose Amazon WorkSpaces, Quit Amazon WorkSpaces to close the Windows client application.

  4. Restart the WorkSpaces Windows client application. Hardware acceleration should now be disabled.

  1. On your Windows computer (not your WorkSpace), open the Windows search box, and enter registry editor to open the Registry Editor (regedit.exe). Choose Run as administrator. (If you don't have permission to run the Registry Editor as an administrator, contact your system administrator for assistance.)

  2. When asked "Do you want to allow this app to make changes to your device?", choose Yes.

  3. In the Registry Editor, navigate to the following registry entry:

    HKEY_CURRENT_USER\SOFTWARE\Amazon Web Services. LLC\Amazon WorkSpaces

  4. Select Amazon WorkSpaces, and then choose Edit > New > String Value.

  5. For the registry key name, enter EnableHwAcc.

  6. Close the Registry Editor.

  7. Close and restart the WorkSpaces client application.

    After you've enabled hardware acceleration in the Windows client, if the screen and mouse issues described earlier occur, delete the EnableHwAcc registry key to disable hardware acceleration, and then restart the Windows client application.

WorkSpaces administrators can enable hardware acceleration in version 3.1.4 or later of the WorkSpaces Windows client by using the following commands in a Command Prompt or PowerShell window.

  1. Use the following command to check for the EnableHwAcc registry key.

    reg query "HKCU\SOFTWARE\Amazon Web Services. LLC\Amazon WorkSpaces" /v EnableHwAcc
  2. Use the following command to add the EnableHwAcc registry key.

    reg add "HKCU\SOFTWARE\Amazon Web Services. LLC\Amazon WorkSpaces" /v EnableHwAcc

    This registry setting takes effect after the WorkSpaces Windows client is closed and restarted.

If needed, use the following command to delete the EnableHwAcc registry key.

reg delete "HKCU\SOFTWARE\Amazon Web Services. LLC\Amazon WorkSpaces" /v EnableHwAcc /f

This registry setting takes effect after the WorkSpaces Windows client is closed and restarted.

If you need to use version 3.1.3 or earlier of the Windows client application, you can disable hardware acceleration in Windows through the Windows registry. Disabling hardware acceleration in Windows might affect the performance of other Windows applications.

  1. On your Windows computer (not your WorkSpace), open the Windows search box, and enter registry editor to open the Registry Editor (regedit.exe). Choose Run as administrator. (If you don't have permission to run the Registry Editor as an administrator, contact your system administrator for assistance.)

  2. When asked "Do you want to allow this app to make changes to your device?", choose Yes.

  3. In the Registry Editor, navigate to the following registry entry:

    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Avalon.Graphics

  4. Do one of the following:

    • If the DisableHWAcceleration registry key exists, select it and choose Edit > Modify. In the Value data box, enter 1 (to disable hardware acceleration), and then choose OK.

    • If the DisableHWAcceleration registry key doesn't exist, do the following:

      1. Select Avalon.Graphics, and then choose Edit > New > DWORD (32-bit) Value.

      2. For the registry key name, enter DisableHWAcceleration.

      3. Select the new DisableHWAcceleration key, and then choose Edit > Modify.

      4. In the Value data box, enter 1 (to disable hardware acceleration), set Base to Hexadecimal, and then choose OK.

  5. Close the Registry Editor.

  6. Close and restart the WorkSpaces client application.

Note

If you need to enable hardware acceleration to improve the performance of other Windows applications, set the DisableHWAcceleration key to 0.

Diagnostic log upload

Enabling diagnostic log uploads

To troubleshoot issues with the WorkSpaces client, you can enable diagnostic logging. The log files that are sent to WorkSpaces include detailed information about your device and connection to the AWS network. You can enable diagnostic log uploads before or during WorkSpace streaming sessions so that these files are sent to WorkSpaces automatically.

To send log files
Note

You can send log files before and during WorkSpaces streaming sessions.

  1. Open your Amazon WorkSpaces client.

  2. At the top of the WorkSpaces sign-in page, choose Manage Diagnostic Logging Settings.

  3. In the pop-up dialog box, choose Enable Diagnostic Logging for Amazon WorkSpaces and click Save.

    Important

    When you report an issue to AWS support, ensure you keep track of the device ID of the client who is experiencing the issue. This device ID can be found in the diagnostics logging menu, in the WorkSpaces client navigation bar, and it helps the support team identify logs associated with your specific device. Ensure you include the device ID in the tickets that you create regarding this specific issue.

Release notes

The following table describes the changes to each release of the Windows client application. As a general security best practice, we recommend that WorkSpaces customers update client software as relevant patches become available to obtain the latest updates. For additional information on all the supported WorkSpaces client versions, see WorkSpaces client application end of life policy.

Release Date Changes
5.33.0 June 8, 2026
  • Fixed an issue that prevented logging in via SAML 2.0 when the client was launched with Administrator privileges.

  • Fixed an issue that prevented transferring files with multibyte file names (common for some non-English languages).

  • Added support for URL redirection, enabling administrators to configure certain websites to be redirected from the streaming session to the local device's web browser.

  • Added the display of battery level from the local device inside the streaming session, helping you know when your battery is running low when on-the-go.

  • Fixed an issue with the username not being pre-populated in the new user login flow when "Remember me" is selected.

  • Fixed an issue that prevented changing the registration code when there is no network connectivity.

  • Updated the DCV SDK.

  • Additional bug fixes and enhancements.

5.32.2 May 21, 2026
  • Fixed an issue with Microsoft Teams optimization not working as expected.

5.32.1 May 14, 2026
  • Fixed an issue where, under certain conditions, the client may not launch correctly on Windows 11 devices with the April 2026 cumulative update (KB5083769) installed.

5.32.0 April 20, 2026
  • Updated the keyboard shortcut to help users navigate from the client application to their local operating system, from Ctrl+Alt+DownArrow to Ctrl+Alt+Shift+DownArrow.

  • Added support for connecting to WorkSpaces in the US East (Ohio) and Asia Pacific (Malaysia) regions.

  • Fixed an issue where, in certain display configurations, not all valid displays were able to be selected.

  • Fixed an issue where the new client update banner was persisting after a client update in certain configurations.

  • Updated the PCoIP SDK.

  • Updated the DCV SDK.

  • Bug fixes and enhancements.

5.31.0 January 21, 2026
  • Added advanced printing support for DCV-based WorkSpaces using native local printer drivers, enabling features such as two-sided printing, page selection, and layout options.

  • Fixed an issue with the automatic client update functionality that was preventing automatic updates in certain scenarios when VBScript is not present.

  • Added improved error messaging in the case of a SAML session timeout.

  • Other bug fixes and enhancements.

5.30.0 October 21, 2025