Windows 10 remote desktop stuck on configuring remote session
|
This is my last attempt to resolve the issue, before I throw this server out of the window. This problem is absolutely random and Event viewer is absolutely useless, so as Google results for this case. I am connecting to my PC via RDP constantly from different computers.
The PC is running on W10 Enterprise 1909. All updated and all updated drivers. All was working great, till recently it started not to connect from certain computers and to be stuck at "Configuring remote session"
After changing the RDP port to 37879 the problem was resolved, but now very frequently when connecting it will come to a black screen.
Afterwards when trying to connect again it will just be stuck at "Configuring remote session" from any PC. The PC will be stuck completely, also when trying to access it physically. Restart helps. Then this happens again, absolutely randomly.
Happened also that the connection froze and when trying to reconnect it would come to a black screen and then same issue again.. Please help, give me any direction what to check..
Thanks in advance!
0
First of all, don't throw it out the window. It's good hardware with some bad software stuff going on. I use RDP extensively (even using it right now). A lot of times when I get such stuck messages is because something is going on with the host system. With windows constantly updating itself, it can also break itself. I believe this may be the root cause of whatever problem you're having. Trying using vnc and see if you have any issues. I know vnc isn't as seamless as rdp and isn't the same, but if you experience a crash with vnc, it is something on the pc that is running irrespective of rdp. I have also found that I can 'mess up' a host system pretty easily by disconnecting and reconnecting a lot of rdp sessions. Sometimes it is best to leave the session running and let a new session 'take over' an existing one instead. Or the opposite may be true where it is best to disconnect from the session, wait enough time for the system to prepare for another login and then login from another system.
0
Thanks for the advice. It is almost certainly happening when I am connecting via RDP. That is almost all the cases when the black screen will appear. I am using RDP all the time for many years and for many users and working with 10 other RDPs. I never need to wait for anything.. it's a server environment with users and such. It must be stable for me as it used to be..
0
Sounds like a video driver issue. Have you tried connecting at a lower color bit rate to see if you don't get the black screen. Does the rdp control bar appear at the top like normal or is it also missing?
0
Well, the bar does appear, since my computer is not stuck, just the host. Now it got a black screen and now whatever I will do it will not even get to the black screen, but will just stuck on CONFIGURING.. Even when I am trying TeamViewer it will not connect. The computer has completely stuck, though I can ping it..
0
Also, PLEX server running on it is accessible
0
Sounds like something is happening with the rdp server as its running. Do you have a monitor connected locally to the system?
0
Yes, but i tried with or without and it's the same issue. When it's frozen I see a black screen on the physical monitor. It was working fine for a whole week and now it's just started again.. no idea why.
0
I've run into this before as well and it's just something messed up with the system at that point. I recall that usually this was when I ran out of ram. I could reboot the system and all was fine again. Does yours work fine after its rebooted? Page 2 Hi there, I've a new-build PC and the CPU speed is stuck at 800MHz and will not go any higher or any lower. It reads 800MHz in BIOS and 0.79GHz in Task Manager, despite TM listing the base speed as 3.60GHZ. I've run a fresh install of Windows 10 but the problem still appears then as well. Interestingly, if I boot into Safe Mode then the full 3.60GHz appears in Task Manager. I've also updated BIOS to its latest version which hasn't helped and neither does changing any settings within BIOS itself. Here's the specs of my build:
Intel i7-9700k 3.60GHz
ASUS ROG STRIX Z390-H Gaming motherboard
Nvidia RTX 2070 Super Ventus
16GB DDR4 RAM
250GB M.2 Drive
Corsair H80i V2 liquid cooling fan I haven't overclocked anything or even attempted to overclock anything. The motherboard temperature lists at 27 Celsius and the CPU itself at 32 Celsius. I'd really appreciate any advice or help you can give, it's driving me nuts!
Cheers.
0
goto Control Panel check your Power Mgmt profile and your bios settings
0
You have to either load BIOS defaults or go to CPU setting in BIOS and adjust the multiplier in there from 8 to... say 47. And enjoy.
0
Everything is set to ‘Auto’ and greyed out so I can’t change anything sadly. I installed Throttlestop out of interest to see if that would help anything. When I unchecked the ‘BD PROCHOT’ setting, the clock speed kicked into life and started fluctuating between 3.6GHZ and 4.2GHz, seemingly overriding the issue. Does anyone know what this setting relates to and how I might be able to fix it so I don’t need to use Throttlestop? Thanks.
0
That setting supposed to throttle down you CPU when other stuff gets too hot (GPU, VRM, other components). What are other board temperatures? Look for an answer in that direction...
0
See what you show with hwmonitor or similar, it might show more sensors.
0
I flashed it to the latest version this morning, it was released two weeks ago. At least I've found a workaround for it at the moment, I'm just intrigued as to what's causing it to throttle all the time.
0
You could disable this feature in BIOS completely or contact CS about the motherboard. |
