Forum Discussion
RDP not working on hyper-v server 2022
I can only connect to any hyper-v server from hyper v manager on the fysical host.
When the connection is up and running i can start MSTSC from my local windows 11 and connect to the server and take over the session.
if i try to connect directly to the server i can logon but the connection gets droped.
when connected from the hyper-v manager the microsoft hyper-v videocard is installed.
when connecting using MSTSC the Microsoft Remote Display Adapter is also installed.
The Vm has all the latest update's installed.
In Hyper-V switching Enhanced Session mode has no results
The problem Exist on all my 2022 Hyper-V VM's
this is in the event log:
The Desktop Window Manager process has exited. (Process exit code: 0x800401f0, Restart count: 8, Primary display device ID: Microsoft Basic Display Driver)
this happens multiple times per second.
The servers i have are all installed afther 8-8-2022.
anybody any sugestions?
In our case, the issue was caused by the software BackupAssist. Uninstalling the software and re-installing version 12.0.4r1 resolved the issue.
Reference:
https://www.backupassist.com/support/en/references/release-notes/current/history.htm
BackupAssist Classic v12.0.4r1
Released August 28th, 2023
Urgent fix release
Urgent: Avoid “black screen” and other Remote Desktop/Team Viewer connection issues after reboots on installations that have applied Windows update KB5028166 on Windows 11 and KB5028171 on Windows Server 2022.
The root cause is a change in the OS that causes some services to fail to start when driver operations are unexpectedly handled as failures (eg. in CryptoSafeGuard Shield, various Anti-Malware drivers, etc).- You just made my day!
Thanks for this information, both servers have Backup Assist. I have tested on our internal lab server which also had the issue described. I installed version 12.05 over the top of the existing 12.03 and the issue is now resolved. I am able to RDP and have also put Screen Connect back on the system and both work flawlessly. No crashed display driver, no black screen, no problem 43 in device manager. I had forgotten this was even on the test server because it did not show in the add/remove programs (was installed under local administrator account when server was built and then was joined to domain, after this it no longer shows in start menu or add/remove), apparently it installs only for current user with no option to change.
Going to tackle client's server later this week but this looks like your solution is the fix for our situation as well.
Again, thank you, your sharing of information is invaluable.
I know this is a little late in response to this, but this issue has just come up for me. In my case this VM doesn't do much, just holds some license servers so I had left it with a low amount of resources. It does have Connectwise Control and Trend Micro Worry Free installed. We were having issues where it would login and then give an error about "Network problem has occurred" and boot us out. Dwminit errors in the Event Logs.
The solution seems to be adding more virtual processors and RAM. Once I did this, the RDP connection logged in successfully (I added 3 processors and another 8GB RAM).
Thanks for the tips!
- 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?
