To have multiple RDP sessions working your need to make some modifications to the termsrv.dll file. There are tools that do these changes automatically, but they often come from dubious sources and it's difficult to be sure that they are completely safe. This article shows how to modify termsrv.dll file yourself.termsrv.dll file is normally located in C:WindowsSystem32 folder.
Before modifying this file for the first time, you need to take ownership and assign yourself read/write permissions. You also need to stop Remote Desktop service ( TermService).Once this is done, it's simply a question of opening termsrv.dll with a HEX editor and changing small part of the file. Always backup the original file before making changes.Certain Windows updates can replace your patched version of termsrv.dll.
Oh no sorry, wasn't intended to be like that at all, was just busy that night.Here is what I did to edit the x64 9.3.9600.17415 termsrv.dll file:Change this HEX:39 81 3C 06 00 00 0F 84 D3 1E 02 00To:B8 00 01 00 00 89 81 38 06 00 00 90I couldnt find the other two lines which I believe give the ability to have the same user logged in simultaneously but I dont use that as I use a seperate account for the Console session and another for each Remote Desktop Login.Oh and just incase it helps, here is a link to a pre modded one:http://www.datafilehost.com/d/367b5fcb. New version of termsrv.dll 6.1.7601.18637 WINDOWS7 pro x86HEX replacements what should I do?Just found a W7sp1 64-bit with termsrv.dll vers. 6.1.7601.18637For now I put in 6.1.7601.18540 patched with the 3 strings given above by strongbox on, and this restored concurrent RPD for now. I'm concerned this may upset WUpdate or TrustedWhatsit, and it would be nice to get strings for 18637. (Also, if I patch systems that are still on 18540, that too may soon get clobbered by auto-update to 18637, right?). Thank you all for supporting this patches!Until patch is also available for Win8UltimateX64 (termsrv.dll versions 6) i succeed by uninstalling 'bad' update kb2973501 and running the old patch again:Check for 'bad' update:wmic qfe where 'hotfixid like '%%2973501%%' get hotfixid,installedOnUninstall 'bad' update(Only local!
Does not work remotely via winexe/ssh):wusa /uninstall /kb:976002 /quiet /norestart /log:kb976002.logUninstall alternative (DOES work remotely via winexe/ssh):dism /Online /Get-Packages findstr 2973501DISM.exe /Online /Remove-Package /PackageName:Pa ckageforKB297 350131bf3856ad 364e35amd646.2.1.4.
Horizon Client Stops Responding or the Remote Desktop Freezes 29. Connecting to a Server in. Windows 6.1.7601 SP1. Connect to a remote desktop or published application from a client device. You might need to. I cannot connect to a windows server 2008r2 with any remote desktop.No firewall enabled -No antivirus firewall -Remote Desktop is enable thru system properties -Changing listening port via. SOLUTION Remote Desktop Not listening on Port 3389 Windows 2008R2.