Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Desktop Window Manager Causing Session Launch Failures

0

Users are frequently reporting getting stuck at the message "Your WorkSpace will be ready in a few seconds…” WorkSpaces are running Windows Server 2016 with DCV.

Reviewing logs in Event Viewer, under Application, there are entries such as:

  • "Faulting application name: dwm.exe"
  • "The Desktop Window Manager process has exited. (Process exit code: 0x8898009b, Restart count: 1, Primary display device ID: AWS Virtual DOD Driver)"
  • "The Desktop Window Manager process has exited. (Process exit code: 0xffffffff, Restart count: 1, Primary display device ID: AWS Virtual DOD Driver)"

We have been temporarily resolving the issue by running the PowerShell commands found in this post: https://repost.aws/questions/QURTDnXs_vTHyBG5bxmCQBFQ/aws-workspaces-desktop-client-disconnects-after-launching. However, the issue does occasionally reoccur.

Does anyone have suggestions for determining a root cause?

Topics
End User Computing
Tags
Amazon WorkSpaces
Language
English

asked 2 years ago373 views

2 Answers
1

The issue you're experiencing with Amazon WorkSpaces seems to be related to a known problem involving display settings and the Desktop Window Manager (DWM) on Windows Server 2016 WorkSpaces using NICE DCV (Desktop Cloud Visualization).

The root cause appears to be related to a mismatch between the local and remote display layouts. This can occur when display settings on the WorkSpace are changed to "Duplicate," which can happen inadvertently, for example, when using PowerPoint in presenter mode.

While the PowerShell commands you've been using provide a temporary fix by cleaning up the DCV display registry keys, they don't address the underlying cause. These commands essentially reset the display configuration, allowing the WorkSpace to reconnect successfully.

To determine the root cause and find a more permanent solution, consider the following steps:

  1. Monitor for any applications or processes that might be changing display settings, particularly those that use presentation or screen sharing features.

  2. Review any group policies or user settings that could be affecting display configurations.

  3. Check for any recent updates to the WorkSpaces image or NICE DCV that might have introduced this issue.

  4. Consider upgrading to a more recent version of Windows Server if possible, as newer versions might have improved handling of display configurations.

  5. Engage with AWS Support to see if there are any known issues or upcoming fixes for this problem with Windows Server 2016 WorkSpaces.

In the meantime, you might want to create a script that runs the cleanup commands periodically or on startup to minimize disruptions. However, be aware that this is still a workaround and not a permanent solution.

The WorkSpaces client team at AWS is reportedly working on longer-term fixes for this issue. Staying in touch with AWS support and checking for updates to the WorkSpaces service and clients would be advisable.
Sources
AWS Workspaces Desktop Client - Disconnects after launching | AWS re:Post

answered 2 years ago

0

If you have support, I would recommend opening a case for tracking the issue and providing feedback on the severity of the business impact of the issue.

AWS
EXPERT

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content