Forum Discussion
RDP not working on hyper-v server 2022
Ferry001 - I just setup a Server 2022 box on Hyper-V 2019 today, and am having the exact same issue. Did you ever find a resolution?
- Sophos Endpoint Agent is the problem. deinstall it and the problem is gone. I have not found the right setting for sophos yet to solve the problem it. I did find out that changing the setting of the firewall it is working on one server and not on an other.
- We have the same problem, but there is no third-party anti-virus on the Hyper-V server to blame, so it's something.
Did you solve your issue, and if so what was the problem, please?It turned out it was not the anti virus but the amount off processors. You need at least two of them
I use ConnectWise ScreenConnect and have a similar problem on server 2022 physical hosts only, the VMS work fine. This issue started a couple months ago. The issue does not happen on Server 2019.
Both servers are Dell PowerEdge (T430, T550) with different Matrox chips.
The issue occurs whenever I log off my session. I can see my cursor go to the top left of the screen and then I get a message from ScreenConnect that my session was "interrupted and possible UAC prompt."
When the issue occurs the Matrox display driver gets disabled and shows error 43 in device manager with yellow exclamation. After this RDP gives black screen and disconnects with error 0x3 extend 0x10.
After this happens, I can no longer connect to the server via Connectwise or VPN/RDP. After some time (1-2 hours) the T430 recovers but the T550 requires a reboot every time . In the event log I see about 7-10 errors "The Desktop Window Manager process has existed. (Process exit code: 0x800401f0, Restart count: 4, Primary display device ID: Matrox G200eR (Renesas) WDDM 2.0)". I have tried removing the Matrox software and using only the Microsoft Basic Display Driver and it exhibits the same behavior as the Matrox driver just at a crappier resolution.
Like you I do not have 3rd party AV on these servers, but there is still Microsoft Defender. My only solution is to disable Microsoft Defender's Real Time Protection either permanently or just before I log off (tamper protection might re-enable after a few minutes?) so for me it does appear to AV related as others have said. Once I do this, I can log off the server without the ScreenConnect error and without the display driver crashing with error 43 on the T430, the T550 which is a much newer host still crashes and requires a reboot to recover.
I can replicate this scenario at will on both physical hosts.
I have tried older drivers to the newest Matrox drivers, various rdp related GPO settings, dism, sfc, but nothing helps. Any other suggestions would be appreciated. I would open case with MS and may still, but it took them 8 weeks to get back to me when I reported the "effective access" issue, and the support agent did not even know that was already fixed, ugh.
Thank you very much for your detailed response.
We traced the problem back to Splashtop remote access software. Once we uninstalled Splashtop and went back to TeamViewer the black screens stopped and we don’t see the continuous Dwminit errors in the Application logs anymore.
We too only observed this problem on Windows Server 2022. The Hyper-V hosts we manage that run Windows Server 2019 do not suffer from this problem when Splashtop is installed.
We still have the Matrox Display Driver error in Device Manager on the Server 2022 Hyper-V host, but it no longer seems to result in the black screens.
It sounds like our Splashtop problem was a very similar problem to your issues with ConnectWise ScreenConnect. In our case, we are happy to switch back to TeamViewer Host. I suspect it is a GPU driver issue in Server 2022, but we are not going to pursue the problem any further at this stage.
I hope this helps you in some way.
