Share via

Windows UI will NOT work

Anonymous
2024-07-18T12:49:51+00:00

Hi,

I am facing a very unusual issue that seems to affect only a few relatively new users who are currently using RDS 2022. The issue is that no matter what you do, the taskbar, search bar, and Windows logo are unresponsive. Clicking on them does nothing. I have tried all the basic troubleshooting steps, such as restarting services, but nothing has helped. I decided to investigate further, and here's what has been done:

  • Reset AppX manifests
  • In-place repair upgrade
  • Replaced the XAML DLLs with those from a working 2022 Standard machine
  • Updated Windows app framework

None of these steps worked. Reinstalling the OS is not a viable option as it is an RDS server.

Does anyone have any ideas on how to fix this issue?

Thank you.

Windows for business | Windows Server | User experience | Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-07-18T22:51:33+00:00

    Hello,

    You can try the following steps to troubleshoot the problem:

    1. Check the installation of the latest patches and updates in Windows Update on the local client and remote server to improve system compatibility and stability.
    2. Use the SFC tool on the remote server to check for software conflicts and system file corruption:

    At the command prompt (admin), type "sfc /scannow", and then restart your computer

    1. Restart Windows Explorer on the remote server:

    Press Ctrl + Shift + Esc to open the task manager. Find "Windows Explorer" in the list. Select it and click the "Restart" button in the bottom right corner.

    1. Use DISM (Deployment Image Service and Management Tool) to try to repair component storage in Windows Server operating system:

    At the command prompt (admin), type "DISM /Online /Cleanup-Image /RestoreHealth" and press Enter.

    5.Start the system in the clean boot state and check whether any third-party applications cause the problem.

    I hope this helps. Please let me know if you require further assistance or have any questions.

    Best regards

    0 comments
  2. Anonymous
    2024-07-22T09:46:46+00:00

    Hello,

    Thanks for sending it, unfortunately it did not solve the problem. The process is physically not running, it gets killed one second after it's started.

    Hello,

    You can try the following steps to troubleshoot the problem:

    1. Check the installation of the latest patches and updates in Windows Update on the local client and remote server to improve system compatibility and stability.
    2. Use the SFC tool on the remote server to check for software conflicts and system file corruption:

    At the command prompt (admin), type "sfc /scannow", and then restart your computer

    1. Restart Windows Explorer on the remote server:

    Press Ctrl + Shift + Esc to open the task manager. Find "Windows Explorer" in the list. Select it and click the "Restart" button in the bottom right corner.

    1. Use DISM (Deployment Image Service and Management Tool) to try to repair component storage in Windows Server operating system:

    At the command prompt (admin), type "DISM /Online /Cleanup-Image /RestoreHealth" and press Enter.

    5.Start the system in the clean boot state and check whether any third-party applications cause the problem.

    I hope this helps. Please let me know if you require further assistance or have any questions.

    Best regards

    0 comments
  3. Anonymous
    2024-07-22T19:42:58+00:00

    Hello,

    At what stage does the process terminate?

    It is advised to check whether the server works properly in the local environment.

    0 comments
  4. Anonymous
    2024-07-23T07:58:03+00:00

    Hello,

    The process doesn't even run when the user logs into their RDS profile, we can manually trigger it to start but gets terminated after 1 second. We made a copy of the server and worked on it in the local environment but it is still the same.

    0 comments
  5. Anonymous
    2024-07-29T08:52:06+00:00

    Sorry to see that your problem still exists. Please focus on the RDS configuration file Settings. Ensure that the user's configuration file path is set correctly. If you are using roaming profiles or redirected folders, make sure that these paths are accessible and that users have sufficient permissions to access the RDS server and their profiles. As a last resort, you can try deleting and recreating the user's RDS profile, but before doing so, make sure you back up the user's data.

    In addition, look for error messages related to remote desktop services in the application log and system log in the Event Viewer. In particular, look at logs during and after user logins. Before viewing the query, enable Display Analysis and Debug logs.

    Regards

    0 comments