Enable Terminal Server/Multiple RDP Sessions on Windows 10

I got up a requirement to setup Windows 10 in a cloud from where we want to have concurrent users on it at the same time. It is an easy step for System Administrator on Windows Server, however, as being the normal operating system,  it wasn’t easy to fulfill this requirement on Windows 10.

I googled and tried to come up with a solution. I have seen few tools on the internet too but they are not working properly with the latest Windows update too.

In the end, I manage to get it done and thought to share my step on my blog. Hereby, I modify the termsrv.dll file from the System32 folder to get it done.

I tried RDP Wrapper but it didn’t help for the newer version of Windows 10. So the following solution would be convenient.

Solution:

  • First backup the DLL file to be on the safe side and take the ownership and provide full rights of termsrv.dll file for your profile.

Termsrv

  • After this, you have to stop Terminal Server before modifying it
      net stop termservice

Terminal.JPG

 

  • Install any HEX editor tool to modify the DLL file. I have used HxD Hex Editor which is freeware too.
  • You have to replace the string and be careful while doing it as you are modifying the system file. Strings are different as per Windows 10 build.
  • The current Windows 10 build I am working is 1703 and have modified the following things:

HEX_Editor

  • Once you saved the DLL file and reboot the machine, it will work to have concurrent user sessions.
  • However, if your Windows version is different as listed above, then kindly check the listed one

Windows 10 Version 1909

Find: 

39 81 3C 06 00 00 0F 84 5D 61 01 00 

Replace With: 

B8 00 01 00 00 89 81 38 06 00 00 90

Windows 10 Version 1903 (updated v2)

Find:

39 81 3C 06 00 00 0F 84 5D 61 01 00

Replace With:

B8 00 01 00 00 89 81 38 06 00 00 90

Windows 10 Version 1809 (updated)

Find:

39 81 3C 06 00 00 0F 84 7F 2C 01 00

Replace With:

B8 00 01 00 00 89 81 38 06 00 00 90

Windows 10 Version 1803

Find:

8B 99 3C 06 00 00 8B B9 38 06 00 00

Replace with:

B8 00 01 00 00 89 81 38 06 00 00 90

Windows 10 Version 1709

Find:

39 81 3C 06 00 00 0F 84 B1 7D 02 00

Replace with:

B8 00 01 00 00 89 81 38 06 00 00 90

Windows 10 Threshold Wave 2 Update

Find:
39 81 3C 06 00 00 0F 84 3F 42 02 00

Replace with:
B8 00 01 00 00 89 81 38 06 00 00 90

Windows 10 RTM 2015

Find:
39 81 3C 06 00 00 0F 84 73 42 02 00

Replace with:
B8 00 01 00 00 89 81 38 06 00 00 90

Hope this will help you guys too.

Feel free to write the comment if you need any support from my end.

Cheers,

Udhy.

92 thoughts on “Enable Terminal Server/Multiple RDP Sessions on Windows 10

      1. Windows 10 Release 1903 has 10.0.18362.53 termsrv.dll as file version. Udhy, could you update this article for this version. Really appreciated.

      2. Have you try this:

        for 1903:

        1. Backup original 1903 dll,
        2. Find and replace original 1903 dll with patched dll from 1809 Win version
        3. Done

      1. Now it is working for me.. after giving full security access to the dll file.

    1. Which Version of Windows 10 do you have?
      I have roll out on my side and shared this blog. So, I assume if you have appropriate version, it should work.

    1. I think one user can’t login with multiple connection in a same machine. It is a connection for different user on single machine at a same time.

  1. after importing the edited dll instead of rebooting drop to a dos box and type “regsvr32 c:\windows\system32\termsvr.dll” then “net start termservice” and then test it.

    1. Not yet man, I have to go through this as they have recently released this patch. I will update my blog if I manage to get it.
      Thank you
      Regards,
      Udhyan

    1. If you can’t find the hex in 1809, try this.

      Find:
      39 81 3C 06 00 00 0F 84 7F 2C 01 00

      Replace:
      B8 00 01 00 00 89 81 38 06 00 00 90

  2. hello folks
    File version: 10.0.17763.437
    search: 39 81 3C 06 00 00 0F 84 3B 2B 01 00
    replace with: B8 00 01 00 00 89 81 38 06 00 00 90

    1. for 1903 release the DLL version is 10.0.18362.53. Could you update for this version, please?

  3. for 1903:

    1. Backup original 1903 dll,
    2. Find and replace original 1903 dll with patched dll from 1809 Win version
    3. Done

    1. Windows 10 1903 18362.116
      Find:
      39 81 3C 06 00 00 0F 84 5D 61 01 00
      Replace:
      B8 00 01 00 00 89 81 38 06 00 00 90

  4. THANK YOU!!!!!

    Version 10.0.18362 Build 18362
    running

    Only advice, you probably need to start the rdp service in the system perferences

    😉

    1. Hi Sachin,
      Windows Server 2012 has its own builtin feature to have it as a terminal server, so they are termed as the server. I doubt you need this kind of tweak in Server. You simply enable Remote Desktop Session with concurrent users that you want and it will go in very simple steps.

  5. Not working buddy. Not found any of the mentioned string on Win version 1809 (OS Build 17763.775) termsrv.dll file version 10.0.17763.771

  6. Hi, I have problem with version 1809 and build 17763.805. I have HEX 39 81 3C 06 00 00 0F 84 CB 2B 01 00. Do you have any solve?
    THX

    1. I have a file patched for Windows 10 Version 1903 (updated v2) working on 18362.418. Try again carefully following all the instructions given by the author of the blog.

  7. Thank you for the great solution in win 1909. I tried it now with win 10, 20h1 (19041.113 insider) it did not work.

    What changes are? Maybe you have a tip

  8. Hello
    Thank’s for your tuto, i use it from 1709 and it’s awesome

    did you have a solution for Windows 10 2004 ? or how you get the value for old windows ? , can we find all HEX with a specific method ?

    thank’s in advance.

    1. Did you check HEX value with starts “39 81 xx xx xx xx xx xx xx xx xx 00” 12 characters and replace with the standard value that I shared. Let me know how it goes.

    2. For Windows 10 2004. Replace HEX value 39 81 3C 06 00 00 0F 84 D9 51 01 00 with B8 00 01 00 00 89 81 38 06 00 00 90. This worked for me.

    3. For Windows 10 2004. Replace HEX value 39 81 3C 06 00 00 0F 84 D9 51 01 00 with B8 00 01 00 00 89 81 38 06 00 00 90. This worked for me.

      1. Yes thanks Bro, this is working for me too. Windows update had upgrade my previous version to 2004. So the Hex number changed. I’m using Window 10 Pro Version 2004 ( OS Build 19041.508).

  9. 1903 10.0.18362.836 i found and replace after register termsrv.dll & start termservice but not work.. only one user logon….

  10. tq udhy.. it’s work for me… concurrent rdp work again
    btw… can you provide HEX value for win10 1607?

  11. Hello!
    For Windows Server 2016 and Server 2019?
    How did you arrived at the conclusion that those needed to be change?
    It really works on Win10 1909 but for Server 2019 1809 didn’t worked and i need at least 1 VM that can host at least 4 RDP Sessions and by default 2016 and 2019 let’s you only 2….

    Thank you!

  12. You can update this article with solution for 20H1
    Windows 10 x64 v2004 – May 2020 Update (20H1)

    After this update termsrv.dll is upgraded to version 10.0.19041.84 To get back concurrent remote desktop connections, make the following changes:

    Find:

    39 81 3C 06 00 00 0F 84 D9 51 01 00

    replace with:

    B8 00 01 00 00 89 81 38 06 00 00 90
    I tried it and worked perfectly

  13. Hi this works great been using it since 1903
    When will multi user termsrv.dll update for Windows 10 version 20H2 build 19042.572 be out?

  14. Hi this works great been using it since version 1903
    When will multi user termsrv.dll update for Windows 10 version 20H2 build 19042.572 be out?

  15. I have read about 10 different posts for this task – all of them appear to have the same HEX code to change. I am using HxD Hex Editor (Run as Admin) – and using the FIND option – after A) Taking Ownership of the file in C:\Windows\System32 folder. I have made a COPY of the file and named termsvc.dll_bkup (After Stopping the services with Net stop TermService.

    The string you present is not found. The OS version is Win-10 Pro 64-bit (1909) – shows version 10.0.18362.836 for the termsvc.dll file.

    I really would like to get this working, as GPEDIT.MSC does not seem to fix it. I have it set to 5.

      1. Thanks Udhy, really help me with this. After update windows , code had changed and very hard to find it.Now back to work again. :))

  16. Maybe instead of constantly helping people by telling them what to patch, you can instead share the methodology for locating the code and describing the change. If more people were to think about ‘how’ you found this and not just ‘what’ they should change, they would be able to patch their own versions without constantly pestering you to update for every new version.

  17. I have windows 20H2; Here I dont find 39 81 3C 06 00 string at all. Can you please let me know for 20H2 what string to be changed. Thanks a lot for your information

Leave a reply to jose silva Cancel reply