An Eror Occured While Launching Your Workspace Please Try Again

Troubleshoot WorkSpaces customer bug

The following are mutual issues that you might have with your WorkSpaces client.

I didn't receive an email with my Amazon WorkSpaces registration lawmaking

Contact your WorkSpaces administrator for assistance.

The Amazon WorkSpaces Application Manager client application isn't appearing on my Windows WorkSpace desktop

The Amazon WAM shortcut should be installed on the Windows WorkSpaces client desktop. If the shortcut isn't on the client desktop, see Troubleshooting Amazon WAM Issues in the Amazon WAM User Guide.

I don't meet whatever applications listed in the Amazon WorkSpaces Application Manager client application

Choose MY APPS to see the applications that your admin has specified to install by default on your WorkSpace. Choose Discover to see the applications that your admin has fabricated bachelor for you lot to install.

Later logging in, the Windows customer awarding displays only a white page and I cannot connect to my WorkSpace

This trouble can be caused past expired Verisign/Symantec certificates on your customer reckoner (non your WorkSpace). Remove the expired certificate and launch the client application once again.

To observe and remove expired Verisign/Symantec certificates

In the Windows Control Panel on your customer estimator (not your WorkSpace), choose Network and Internet.
Cull Internet Options.
In the Internet Properties dialog box, cull Content, Certificates.
In the Certificates dialog box, choose the Intermediate Document Government tab. In the list of certificates, select all certificates that were issued past Verisign or Symantec that are also expired, and cull Remove. Do not remove whatsoever certificates that are not expired.
On the Trusted Root Certificate Authorities tab, select all certificates that were issued by Verisign or Symantec that are also expired, and choose Remove. Do non remove any certificates that are not expired.
Close the Certificates dialog box and the Internet Properties dialog box.

My WorkSpaces client gives me a network fault, but I am able to use other network-enabled apps on my device

The WorkSpaces customer applications rely on admission to resource in the Amazon Cloud, and crave a connectedness that provides at least i Mbps download bandwidth. If your device has an intermittent connection to the network, the WorkSpaces client application might written report an issue with the network.

WorkSpaces enforces the utilise of digital certificates issued by Amazon Trust Services, as of May 2018. Amazon Trust Services is already a trusted Root certificate authority (CA) on the operating systems that are supported by WorkSpaces. If the Root CA listing for your operating organisation is not upwards to date, your device cannot connect to WorkSpaces and the client gives a network error.

To recognize connection bug due to certificate failures

PCoIP nil clients — The following mistake message is displayed:

Failed to connect. The server provided a certificate that is invalid. Run across below for details: - The supplied certificate is invalid due to timestamp - The supplied certificate is not rooted in the devices local certificate store

Other clients — The health checks fail with a red alert triangle for Internet.

To resolve certificate failures

Apply ane of the post-obit solutions for certificate failures.

For the Windows customer, download and install the latest Windows client awarding from Amazon WorkSpaces Client Downloads . During installation, the client awarding ensures that your operating system trusts certificates issued past Amazon Trust Services. If updating your client does non resolve the event, contact your Amazon WorkSpaces administrator.
For all other clients, contact your Amazon WorkSpaces ambassador.

It sometimes takes several minutes to log in to my Windows WorkSpace

Group Policy settings that are gear up by your system administrator can crusade a delay on login subsequently your Windows WorkSpace has been launched or rebooted. This filibuster occurs while the Group Policy settings are existence applied to the WorkSpace, and is normal.

When I effort to log in, the Amazon WorkSpaces Windows customer gets stuck on the "Preparing your login folio" screen

When starting versions 3.0.iv and 3.0.v of the WorkSpaces Windows customer awarding on a Windows 10 machine, the client might go stuck on the "Preparing your login page" screen. To avoid this outcome, either upgrade to version 3.0.6 of the Windows client awarding or practice not run the Windows client application with administrator (elevated) privileges.

When I endeavour to log in, I get the error message: "No network. Network connexion lost. Check your network connection or contact your ambassador for help."

When you try to log in to your WorkSpace using some three.0+ versions of the Windows, macOS, and Linux WorkSpaces client applications, yous might receive a "No network" fault on the login folio if yous have specified a custom proxy server.

Windows client — To avoid this effect with the Windows client, upgrade to version 3.0.12 or subsequently. For more than information near configuring the proxy server settings in the Windows client, see Proxy Server for Windows Client.
macOS customer — To work around this issue, apply the proxy server that's specified in the device operating organization instead of using a custom proxy server. For more information about configuring the proxy server settings in the macOS customer, meet Proxy Server for macOS Client.
Linux client — To avert this consequence with the Linux client, upgrade to version 3.1.5 or after. If you lot can't upgrade, yous can work around this outcome by using the proxy server that's specified in the device operating arrangement instead of using a custom proxy server. For more data about configuring the proxy server settings in the Linux client, come across Proxy Server for Linux Client.

The Amazon WorkSpaces Windows client application login page is very tiny

Running the WorkSpaces Windows client with administrator (elevated) privileges might upshot in viewing issues in high DPI environments. To avoid these problems, run the customer in user fashion instead.

I encounter the post-obit error message: "WorkSpace Status: Unhealthy. We were unable to connect you to your WorkSpace. Please try over again in a few minutes."

If you merely started or restarted your WorkSpace, wait a few minutes, and so try to log in again.

If y'all proceed to receive this fault message, you can try the following actions (if your WorkSpaces administrator has enabled you to do them):

Restart your WorkSpace
Rebuild your WorkSpace

If you are unable to restart or rebuild the WorkSpace yourself, or if you continue to see the fault message after doing so, contact your WorkSpaces ambassador for assistance.

Sometimes I am logged off of my Windows WorkSpace, even though I airtight the session, but did non log off

Your system administrator applied a new or updated Group Policy setting to your Windows WorkSpace that requires a logoff of a disconnected session.

I forgot my countersign and tried to reset it, but I didn't receive an electronic mail with a reset link

Contact your WorkSpaces administrator for assistance.

I tin't connect to the internet from my WorkSpace

WorkSpaces cannot communicate with the net by default. Your Amazon WorkSpaces administrator must explicitly provide internet access.

I installed a tertiary-political party security software bundle and now I can't connect to my WorkSpace

You tin can install any blazon of security or firewall software on your WorkSpace, but WorkSpaces requires that sure inbound and outbound ports are open on the WorkSpace. If the security or firewall software that you install blocks these ports, the WorkSpace might not function correctly or might become unreachable. For more data, meet Port Requirements for WorkSpaces in the Amazon WorkSpaces Administration Guide.

To restore your WorkSpace, rebuild your WorkSpace if you nevertheless accept access to it, or ask your Amazon WorkSpaces administrator to rebuild your WorkSpace. You lot then have to reinstall the software and properly configure port admission for your WorkSpace.

I am getting a "network connection is slow" warning when continued to my WorkSpace

If the circular-trip time from your client to your WorkSpace is longer than 100ms, you can all the same use your WorkSpace, simply this might event in a poor experience. A tiresome round-trip time tin can be caused by many factors, but the post-obit are the most common causes:

You are too far from the Amazon Region that your WorkSpace resides in. For the best WorkSpace experience, yous should exist within 2,000 miles of the Amazon Region that your WorkSpace is in.
Your network connection is inconsistent or tedious. For the best experience, your network connection should provide at least 300 kbps, with capability to provide over 1 Mbps when viewing video or using graphics-intensive applications on your WorkSpace.

I got an "invalid certificate" error on the client application. What does that mean?

The WorkSpaces customer application validates the identity of the WorkSpaces service through an SSL/TLS certificate. If the root certificate authority of the Amazon WorkSpaces service cannot be verified, the client application displays an error and prevents any connectedness to the service. The virtually common cause is a proxy server that is removing the root document authority and returning an incomplete document to the client application. Contact your network ambassador for aid.

I see the following error message: "Device can't connect to the registration service. Bank check your network settings."

When a registration service failure occurs, you might see the following mistake bulletin on the Connectedness Health Check page: "Your device is non able to connect to the WorkSpaces Registration service. Yous will not be able to annals your device with WorkSpaces. Please check your network settings."

This fault occurs when the WorkSpaces client awarding tin can't achieve the registration service. Contact your Amazon WorkSpaces administrator for help.

I skipped an update to my client application and am having problem updating my client to the latest version

If y'all've skipped an update to your Amazon WorkSpaces Windows client application and now want to update to the latest version of the client, see Update the WorkSpaces Windows client awarding to a newer version.

If you've skipped an update to your Amazon WorkSpaces macOS customer awarding and at present want to update to the latest version of the client, see Update the WorkSpaces macOS client application to a newer version.

My headset doesn't work in my WorkSpace

If y'all're using the Android, iPad, macOS, Linux, or Windows customer awarding for Amazon WorkSpaces, and you're having trouble using your headset in your WorkSpace, endeavor the following steps:

Disconnect from your WorkSpace (choose Amazon WorkSpaces, Disconnect WorkSpace).
Unplug your headset, and then plug it back in. Verify that it works on your local computer or tablet. For a USB headset, make sure that it shows upward as a playback device locally on your calculator or tablet:
- For Windows, bank check the devices listed in the Command Panel nether Hardware and Audio > Sound. In the Sound dialog box, choose the Playback tab.
- For macOS, choose the Apple menu > System Preferences > Sound > Output.
- For iPad, open the Control Center and tap the AirPlay button.
Reconnect to your WorkSpace.

Your headset should now piece of work in your WorkSpace. If you're nonetheless having trouble with your headset, contact your WorkSpaces administrator.

Audio currently is not supported on Linux WorkSpaces using the WorkSpaces Streaming Protocol (WSP).

I'g getting the incorrect characters when I blazon; for example, I get \ and | when I try to type quotation marks (' and ")

This behavior might occur if your device is not set to the same language every bit your WorkSpace, or if you're using a language-specific keyboard, such as a French keyboard.

To resolve this issue, see Amazon WorkSpaces linguistic communication and keyboard back up.

The WorkSpaces client application won't run on my Mac

If you lot endeavor to run older versions of the WorkSpaces customer application on your Mac, the client application might non offset, and yous might receive security warnings such equally the following:

"WorkSpaces.app volition damage your computer. You should motility it to the Trash."

"WorkSpaces.app is damaged and can't be opened. Yous should movement it to the Trash."

If you lot use macOS 10.15 (Catalina) or later, you lot must apply version 3.0.ii or later of the macOS client.

Versions two.5.11 and earlier of the macOS customer can no longer be installed on macOS devices. These versions likewise no longer work on devices with macOS Catalina or later on.

If you are using version ii.v.11 or before and you upgrade from an older version of macOS to Catalina or later, you volition no longer be able to utilise the 2.five.11 or earlier client.

To resolve this issue, nosotros recommend that affected users upgrade to the latest version of the macOS client that is available for download at Amazon WorkSpaces Client Downloads .

For more information most installing or updating the macOS client, see Setup and installation.

I'yard having trouble using the Windows logo key in Windows WorkSpaces when working on a Mac

By default, the Windows logo key on a Windows keyboard and the Command cardinal on an Apple keyboard are both mapped to the Ctrl primal when you're using the Amazon WorkSpaces macOS customer application. If you desire to alter this beliefs so that these 2 keys are mapped to the Windows logo key, see Remap the Windows logo key or the Control key for instructions on how to remap these keys.

My WorkSpace looks blurry on my Mac

If your screen resolution in WorkSpaces is depression and objects expect blurry, you demand to turn on high DPI mode and accommodate the brandish scaling settings on your Mac. For more data, see WorkSpaces high DPI display support.

I'm having trouble copying and pasting

If you are having trouble copying and pasting, ostend the post-obit to help solve your effect:

Your administrator has enabled clipboard redirection for your WorkSpace.
The uncompressed object size is nether the maximum of 20 MB.
The information type that you copied is supported for clipboard redirection. For a listing of supported data types, see Agreement Cloud Access Software Copy/Paste Feature in the Teradici documentation.

My screen is flickering or not updating properly, or my mouse isn't clicking in the right place

If yous're using a version of the Amazon WorkSpaces Windows customer application prior to version iii.1.4, you might experience the post-obit screen update issues, caused by hardware acceleration:

The screen might take 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.

To address these issues, we recommend upgrading to version iii.1.4 or afterward of the Windows customer awarding. Starting with version 3.ane.4, hardware dispatch is turned off by default in the Windows client application.

Nevertheless, if you need to enable hardware acceleration in version 3.ane.four or subsequently, for instance if y'all're experiencing slow performance when using the client, meet Manage hardware dispatch.

If you need to use version 3.1.three or before of the Windows client application, yous can disable hardware acceleration in Windows. To disable hardware acceleration for version iii.1.3 or before, see Managing Hardware Dispatch. Disabling hardware dispatch in Windows might affect the performance of other Windows applications.

givenagdocany.blogspot.com

Source: https://docs.amazonaws.cn/en_us/workspaces/latest/userguide/client_troubleshooting.html