Server 2022 Logonui.exe error

Hi, yes, we found out that it was some software causing the issue. In our case it was N-able RMM software causing the problem. After removing this software our problem was resolved.

Hi guys, I'm battling this issue since we started to deploy Windows Server 2022. We have only customers with a single VM, no clustering, nothing fancy. If the users disconnect an RDP Session and then try to reconnect, they sporadically get a black or blue blank screen (the users type the credentials into the RDP client). The only thing that is visible are the language/keyboard settings and the ease of access icon in the lower right corner. If you click the icon, the view freezes completely = if you hover with the mouse over those icons, normally the icon gets highlighted, but after clicking on any of the icons, nothing happens, you don't see the highlighted background of the icon anymore or its stuck highlighted, even if you move the mouse away. To fix it, as was mentioned in this thread bevor, you have to log in with another user and kill the running task LogonUI.exe (Windows Logon User Interface Host). If you have background remote management or can ssh to the server, you can kill the task via CMD/Powershell (tasklist | find “ogonu” --> note the PID and then taskkill /F /PID <the PID from above>) Sometimes after killing LogonUI, the user gets logged in to his Windows desktop directly. Sometimes you also need to logout the user, so the session gets logged off. I'm having this issue only with this combination:

• VMWARE ESXi 7 or 8
• Windows Server 2022
• Advanced Monitoring Agent from RMM (N-able)

I installed a couple of physical Windows Server 2022 (without virtualization) and I never experienced it on those machines. If I disable Take Control and reboot, the issue disappears. With take control activated, I had the issue approx. every 3-5 RDP connections. After disabling, I just tried 20 RDP connections to a disconnected session without black screen. I hope this helps someone. I lost a lot of time troubleshooting and looking for workarounds.  

We also have the same issue.
N-able support told us the following:
It is a known bug (NCI-33587) And it is fixed in 7.00.45

uninstal / reinstall take control would fix.
https://documentation.n-able.com/N-central/troubleshooting/Content/kb/How-to-clean-re-install-the-Take-Control-agent-on-N-central.htm

Hi. We have the same issue. Did you find a solution?

We are using the same software. I guess the root of the problem is found. Thank you for your answer. Did you uninstall the whole Agent?