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

Start Menu and Search functionality in Amazon Workspace is not functioning

0

Most of our Workspaces are built using Microsoft Windows 10 (Windows 2019 Server or Windows 2022 Server) with DCV protocol (this issue is also happening on PCOIP protocol as well).

We ran into an issue lately that points to a user profile corruption that I am not sure how to fix. It does not occur immediately after a system is built, but usually after the first 1-2 minutes of being first logged on, the Workspaces application will close on the host machine and when the user logs back in, is when the issues start. Here are the symptoms:

  • User can no longer open the Start Menu/Search bar. Receives an error "Critical Error - Your Start menu isn't working. We'll try to fix it the next time you sign in"
  • User cannot log in to Microsoft 365 Desktop applications. Receiving an error tag:7Q6ch

At first, we thought that the error was being caused by a Group Policy being applied to all computers in our AD that blocked External USB drives. However, we moved that policy to another OU and not as a default domain policy and we still have issues. Things I have tried:

  1. Running dism/sfc commands on the Workspace as an admin
  2. Restoring and Rebuilding the Workspace
  3. Deleting the user's profile by remoting into the Workspace via RDP and doing so in the Advanced System Properties Control Panel item. This did "fix" the issue because when the user logged back into the Workspace, their user profile was created on the C: Windows system drive and not on the User Profile D: drive. This workaround pointed me to the fact that it is a user profile corruption error on the D: drive.
Topics
End User ComputingCompute
Tags
WindowsAmazon WorkSpacesCompute
Language
English
asked a year ago282 views
1 Answer
0

The issue you're experiencing with Amazon WorkSpaces appears to be related to user profile corruption, specifically on the D: drive where user profiles are typically stored. This problem can manifest in various ways, including Start Menu and Search functionality issues, as well as problems with Microsoft 365 Desktop applications.

Given that the issue occurs after the first 1-2 minutes of being logged on and persists after a restart, it's likely that something is interfering with the proper creation or loading of the user profile. Here are some additional troubleshooting steps and potential solutions you can try:

  1. Check the PCoIP Standard Agent for Windows service: Ensure this service is running and set to start automatically. You can verify this by connecting to the WorkSpace using RDP.

  2. Verify security group settings: Make sure your WorkSpaces security group allows outbound traffic, especially communication with your directory controllers on all required ports over the primary network interface.

  3. Investigate Group Policy settings: Although you've moved the policy blocking external USB drives, there might be other Group Policy settings affecting user profiles. Review your Group Policy settings, particularly those related to user profiles and folder redirection.

  4. Check for disk space issues: Ensure there's enough free space on both C: and D: drives. Low disk space can sometimes cause profile corruption.

  5. Examine WorkSpaces logs: Enable advanced logging on the WorkSpaces client to gather more diagnostic information. This can help identify any underlying issues causing the profile corruption.

  6. Consider profile management solutions: Implement a user profile management solution designed for virtual desktop environments, which can help mitigate profile corruption issues.

  7. Investigate potential conflicts with third-party applications: Some applications or security software might interfere with profile creation or loading. Try temporarily disabling non-essential applications to isolate the issue.

  8. Review recent changes: If this issue started occurring recently, review any recent changes to your WorkSpaces environment, such as updates, new applications, or policy changes.

If these steps don't resolve the issue, you may need to engage AWS Support for further assistance, as there could be an underlying problem with the WorkSpaces service or your specific configuration that requires more in-depth investigation.
Sources
Troubleshoot issues for WorkSpaces Personal - Amazon WorkSpaces
Troubleshooting a Windows WorkSpace marked as unhealthy - Best Practices for Deploying WorkSpaces
Amazon workspaces - No network : Network connection lost. Check your network connection or contact administrator for help. | AWS re:Post

answered a year 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