protocol error code 0x112f on local machine, solved when logged onto

mhanson 31 Reputation points

I have two desktop machines (one windows 10 home and one windows 10 professional). I routinely use remote desktop connection to access the windows 10 pro machine from the windows 10 home machine. Lately I have been getting a protocol error code 0x112f whenever I try to log on in the morning. Plugging in a monitor, mouse, and keyboard and logging onto the windows 10 pro machine seems to resolve whatever problem is occurring. The windows 10 pro machine is set to never sleep or turn the screen. Any tips?

  1. Douglas Araujo 11 Reputation points

    confirma em gpedit.msc

    Configuração do computador -> Modelos Administrativos -> Componentes do Windows -> Serviço da Area de Trabalho Remota -> Host da Sessão da Area de Trabalho Remota -> Ambiente da Sessão remota -> Prioriza o modo gráfico H.264/AVC 444...

    deixa como não configurada

    erro 0x904

  2. Tom Petzold 31 Reputation points

    I just shut off the second monitor's power. I log in, and then turn the second monitor on.

    Works everytime.!!

  3. mhanson 31 Reputation points

    I have personally solved this problem by transitioning to Linux and using the Remmina desktop client. I believe this client is also available for windows, so that might help. Bit frustrating that connecting to a windows machine works better from linux than windows... shrug

  4. Danilo Almeida 1 Reputation point

    Actually i get similar errors when connecting through Remmina too :-)

Sign in to comment

12 answers

  1. Reuven Jackson 61 Reputation points

    I've been having the same problem, the solution that I found was in the comments at https://stackoverflow.com/questions/31402343/remote-desktop-connection-protocol-error-0x112f#comment117915095_61203653

    An update to this: I have found that if you connect using only one monitor first (uncheck "Use all my monitors for the remote session" in the "Display" tab before connecting), and then connect using all monitors while still being connected with one monitor, the multi-monitor connection will "take over" and successfully connect without the 0x112f error. Hope this helps! –
    Adrian Wiik Mar 19 at 8:29

    1. John Hubert 6 Reputation points

      ReuvenJackson-9177 you are awesome. I actually figured this out and came here to post the same solution and was happy to see you already found it. It doesn't permanently fix it for me, but i can go days without having to do it again so it's good enough for now.

    2. Chad Henke 6 Reputation points

      This worked for me! Thank you so much!

    3. Terease McCormick 0 Reputation points

      wooo! success!

    4. Matthew Beck 0 Reputation points

      Just saved my keester!

    5. David Branca 0 Reputation points

      Thank you for being so determined [frustrated] to make this work that you thought of overtaking a working rdp session. 4 years later still a savior.

    Sign in to comment
  2. JW 46 Reputation points

    I've been suffering from this problem for quite a while now.

    Something that worked for me:

    1. Open gpedit.msc
    2. Goto Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Remote Session Environment
    3. Change the policy "Use WDDM graphics display driver for Remote Desktop Connections" to Disabled
    4. Reboot

    For everyone trying this out, please do share your results, positive or negative doesn't matter.

    1. RL 1 Reputation point

      THIS WORKS ! Thanks!

    2. Daniel Barth 0 Reputation points

      This works perfectly! I don't know why, but don't care. Thanks!

    3. Chasity Myers 0 Reputation points

      Worked perfectly at first, or so I thought. I log on to a remote server in a steel mill. After I made this change, I was able to load my Remote Desktop with no issues, until I tried to log onto my FactoryTalk client. it would not let me. So, I had to change it back.

    4. Rob of the Mountain 0 Reputation points

      I use both Remote Desktop Client (RDC) and Remote Desktop Connection Manager (RDCM).

      I only get the protocol error code 0x112f if the monitors of the remote PC have been turned off.

      If I connect to the remote PC using RDC, then I can no longer connect to that same PC using RDCM (unless I reboot the remote PC first).

      Disabling the setting "Use WDDM graphics display driver for Remote Desktop Connections" solved the problem for me. I can now connect to the remote PC with both RDC and RDCM interchangeably, even if the remote monitors are turned off.

      Thanks for sharing the solution!

    5. Anonymous

      Didn't do it for me.

    Sign in to comment
  3. DocB 6 Reputation points

    This worked for me.

    1. Open gpedit.msc
    2. Go to Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Remote Session Environment
    3. Change the policy "Use WDDM graphics display driver for Remote Desktop Connections" to enabled.
    4. Change the policy "Limit number of monitors" to however many monitors you plan to use. I am currently only using 2.

    Reboot if necessary.

    I did option 3 and it still gave the same error code. Once I completed option 3 and then 4 and restarted RD no more error code.

    0 comments No comments
    Sign in to comment
  4. Todd Seiler 6 Reputation points

    I turned off/unchecked "persistent bitmap caching" under the "Experience" tab.

    1. Jon S 1 Reputation point

      I beleive this is the correct solution. :)

    Sign in to comment
  5. Anonymous

    Hello @mhanson

    I found 2 possible solution might solve this issue:

    1. This may due to resolution conflict between monitor and RDP client, so just change resolution in RDP settings.
    2. Disable the option "Use all my monitors for the remote session" on the Display tab of the client settings.

    Hope this could help!

    Thanks
    Karlie

    1. mhanson 31 Reputation points

      Thanks for your help

      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)

      Disable the option "Use all my monitors for the remote session" on the Display tab of the client settings.

      This works, but is not ideal as I often need both screens.

      Why does logging into the computer locally solve this? Is there any way to solve this longer term and maintain access to both screens?

    2. Anonymous

      please check if this thread helps:Remote machine closes automatically

    3. Anonymous

      Hi,
      We have not heard from you for several days, any update?

    4. Anonymous

      Have you tried above settings ? Is it work for you ?
      Hope to hear some progress.

    5. Wolf Scott 6 Reputation points

      Having this same issue AFTER I disconnect the first time AND been putzin with this for several years off and on depending on my level of anoyance.

      If the target machine is rebooted, I CAN connect with "use all my monitors" AND at the highest color rating; it connects and continues to function as expected as long as I do not disconnect. Once I drop the connection and attempt to reconnect, I get the 0x112f error.

      For me, unchecking "use all my monitors" works BUT I have several monitors AND I use the session extensively so that HAS been how I reestablish the connection to reboot the target (major pain), and then once again, Bob's your uncle.

      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 - Since I'm not gaming or using any graphic intense, or even moderate for that matter, this is a reasonable workaround for me until such time as I restart the target machine (which is likely days, if not weeks) -

      But, as all answers, your mileage may vary -- this seems to work for me, however.

      cheers,
      \//\//olf

    Sign in to comment
Sign in to answer

Your answer