Remote desktop connection protocol error 0x112F: usually is lack of memory on the server side, try connecting with a lower resolution
Posted by jpluimers on 2024/08/19
Usually I work at high resolution monitors and sometimes I got error 0x112F when doing Remote Desktop.
After a reboot of the target machine, that error always goes away, but I wanted to know the underlying reason.
[Wayback/Archive] windows server 2012 – Remote desktop connection protocol error 0x112f – Stack Overflow got me in the direction, and the next time I got a 0x112F error, I tried connecting at 800×600 which worked (and uses far less memory server side at the cost of far less resolution). For now that has worked every time I got that error.
- After few tries with this error, RDP managed to get a connection to the server and I was able to stop a bogus service consuming too much memory. This can be done also with sysinternals or sc.
- Might not be a solution for all but I found that if I reduced the screen resolution of the RDP session, I was able to get in. The server was at 95% capacity I went from 3 high res monitors to 1 800×600 window.
- If the server accessible with RPC (basically, if you can access a shared folder on it), you could free some memory and thus let the RDP service work properly. The following windows native commands can be used:To get the list of memory consuming tasks:
tasklist /S <remote_server> /V /FI "MEMUSAGE gt 10000"To kill a task by its name:
taskkill /S <remote_server> /IM <process_image_name> /FTo show the list of desktop sessions:
qwinsta.exe /SERVER:<remote_server>To close an old abandoned desktop session:
logoff <session_id> /SERVER:<remote_server>After some memory is freed, the RDP should start working.
So for my that’s enough empirical evidence it is a memory problem on the server side.
These seem to confirm this:
- [Wayback/Archive] protocol error code 0x112f on local machine, solved when logged onto – Microsoft Q&A confirms this:
-
I found 2 possible solution might solve this issue:
-
This may due to resolution conflict between monitor and RDP client, so just change resolution in RDP settings.
-
Disable the option “Use all my monitors for the remote session” on the Display tab of the client settings.
Hope this could help! -
- HOWEVER, after some deeper digging this evening, I found one additional setting that ALLOWS me to use ALL My Monitors again. Setting the Display->Color to “High Color 16bit” seems to allow me to have all my monitors
-
This may due to resolution conflict between monitor and RDP client, so just change resolution in RDP settings.This sometime works c. 50%, but only on the lowest resolution available (15 bit)
-
- [Wayback/Archive] RDP protocol error code 0x112f – Microsoft Q&A
- Please try to use the group policy editor (Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment. Then disable “Use the hardware default graphics adapter for all Remote Desktop Services sessions”).
- The problem is solved! I have connected a physical monitor to the computer that I try to connect to. And changed the resolution. Now I am able to use 2 monitors again.
-
Found another workaround….
-
Go into Display settings & change ‘Multiple displays’ to ‘Show only 1’ or ‘Show only 2’, whichever you prefer
-
RDC with ‘Use all monitors for the remote session’ checked
-
Minimise the RDC session, go back into Display settings & change ‘Multiple displays’ back to ‘Extend these displays’
-
Now maximize your RDC session & all should be well ;)
-
- Not exactly an answer, but a work around. What works for me is to just keep trying the RDP connection, it eventually just connects as normal, it just takes a number of attempts usually. It is very annoying though.
- [Archive] Windows10 updates, RD Dual Monitor and Last Opened Windows issues – Microsoft Community shows another solution if memory is not the problem:
A Google search suggested a lack of memory but this was not the case here as the system has about 8 GB free after booting. There were also suggestions about modifying the “Experience” settings in the Remote Desktop connection utility on the client. Turning most of these off seemed to help a little but inconsistently.
The real solution was to use the group policy editor (
Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment. Then disable “Use the hardware default graphics adapter for all Remote Desktop Services sessions”).Doing this shifts the graphics work to the CPU (as can be seen using, for example,
hwinfo).
Via [Wayback/Archive] remotedesktop error 112f – Recherche Google.
–jeroen
The Wiert Corner - irregular stream of stuff 
Leave a comment