Remote Apps: background filling up with garbage

Pieter Huygens 25 Reputation points

Dear, We have RDS farm 2019 with around 100 users using remote apps. We use around 5 remote apps. Since previous month, we are getting reports of users that remote apps background normally should be white in their application, but instead of the white background, the rapp is filled up with garbarage. I've attached a screenshot of this issue: you can see all the repeating items in the middle of the screen: normally that space should be white. screenshotRAPP.png I've drawed some white frames on the screenshot for privacy reasons. When the user uses another computer, the issue is gone. Updated drivers/Windows update on the client and so on > does not solve the problem. We can solve the issue when we reset the local user profile on the users computer. However, this is the 3rth user with the same issue this month. The issue occurs on all the 5 remote apps. All users are using HP Probook series. Does anyone recognize this issue? Any solutions except reinstalling the computer or resetting the local user profile? Many thanks.

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
4,294 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Limitless Technology 44,001 Reputation points

    Hello there, Are you using roaming profiles and do you see and event ID getting generated for these particular users? This might be due to profile corruption or GPO issue. Here's how to view the Operational log for the User Profile Service: In the Event Viewer console tree, navigate to Applications and Services Logs, then Microsoft, then Windows, then User Profile Service, and then Operational. Examine the events that occurred around the time of the Error or Warning events that you noted in the Application log. Hope this resolves your Query !! --If the reply is helpful, please Upvote and Accept it as an answer--

  2. Pieter Huygens 25 Reputation points

    Dear All, Setting this registry key solves our problem: However our symptons does not exactly match with these in the learn article...

    0 comments No comments