![](/uploads/1/2/5/8/125805452/502247478.jpg)
Terminal Services Realtime Patch for Windows XP by Stas'M. Terminal Services Realtime Patch by Stas'M allows you to patch remote desktop concurrent sessions on Windows XP box and also able to unlock remote desktop on Windows XP Home Edition. And you don't need to change your OS edition or reboot the computer. 1) Download the Universal Termsrv.dll Patch by DeepXW and unzip it 2) Choose the corresponding patcher based on you Windows Version: For 32bit (x86) select UniversalTermsrvPatch-x86.exe. For 64bit (x64) select UniversalTermsrvPatch-x64.exe 3) Right-click the exe file, select Run as Administrator.
Terminal Services Realtime Patch by Stas'M allows you to patch remote desktop concurrent sessions on Windows XP box and also able to unlock remote desktop on Windows XP Home Edition. And you don't need to change your OS edition or reboot the computer. Patch works in realtime in 2 stages:
- Stage 1:
Apply patch to the Terminal Services process memory (that's why no reboot required). - Stage 2:
Patch the termsrv.dll in the system folder.
Also it can install RDP display redirector driver (rdpdr.sys) with devcon utility (built-in program).
And there are some useful features (tweaks):
- Keep alive VPN connections (such as PPTP or PPPoE)
- Single or multiple sessions per user
- Enable or disable blank passwords on remote logon
Attention:
This patcher support only Windows XP (Service Pack 2 and 3) and x86 system architecture.
Now we are trying to make patching support for SP 1 (termsrv.dll version 5.1.2600.1106).
This patcher support only Windows XP (Service Pack 2 and 3) and x86 system architecture.
Now we are trying to make patching support for SP 1 (termsrv.dll version 5.1.2600.1106).
Video instruction (how to enable RDP on Windows XP Home Edition):
http://www.youtube.com/watch?v=slG5paz8r8E
http://www.youtube.com/watch?v=slG5paz8r8E
References:
http://wasm.ru/forum/viewtopic.php?pid=404047
http://fouroom.ru/viewtopic.php?id=347 (post #8)
http://wasm.ru/forum/viewtopic.php?pid=404047
http://fouroom.ru/viewtopic.php?id=347 (post #8)
Other patchers:
![Termsrv Termsrv](http://i41.tinypic.com/20f421i.png)
- RDP Wrapper Library by Stas'M (Windows Vista, Windows 7, Windows 8) - no reboot
https://github.com/binarymaster/rdpwrap - Universal Termsrv.dll Patch (x86/x64) by deepxw - reboot required
http://deepxw.blogspot.ru/2009/04/universal-termsrvdll-patch.html - Concurrent RDP Patcher (Windows 7 RTM) by untermensch - no reboot
http://experts.windows.com/frms/windows_entertainment_and_connected_home/f/114/t/79427.aspx - Windows 8 Patcher by Peter Kleissner - reboot required
http://forums.mydigitallife.info/threads/31829-Windows-8-Patcher
Windows XP Professional and Windows XP Media Center Edition (MCE) has Remote Desktop (RDP) service that allows the computer to be remotely connected, accessed and controlled from another computer or host. However, Windows XP machine only allows one concurrent remote desktop connection from a single user been connected to it with no multiple remote desktop sessions or connections support.Whenever there is a remote user who user Remote Desktop Connection (RDC) client to connect to a Windows XP host, the local user is disconnected with the local console screen locked, with or without his or her permission. 00022A17: A69: 7F 9000022A6A: 16 90. Restart the computer and boot info Safe Mode by pressing F8 during initial boot up and select Safe Mode. If you cannot replace or overwrite termserv.dll with access denied or file in use error, turn off the “Termine Services” in “Services” control panel of “Administrator Tools”. Besides, each connecting physical connections must have their own user account in the target host, and must authenticate with corresponding own user name and password credential.To uninstall and revert back to original termsrv.dll, simply delete the patched version, and rename the backup copy back to “termsrv.dll”. You probably have to do it in Safe Mode if the Terminal Services is enabled and running.
If the Windows XP computer is connected to a domain on local networks, Windows will set the value of the regkey “AllowMultipleTSSessions” to “0” every time the computer is restarted. To ensure that multiple or unlimited Remote Desktop connection sessions is allowed in AD domain environment, the value data for “AllowMultipleTSSessions” has to be set to “1” on each system startup. To change the value, simply rerun the tsmultiplesessions.bat every time the computer is started.
Alternatively, put the tsmultiplesessions.bat at C:Documents and SettingsAll UsersStart MenuProgramsStartup folder so that it will be automatically run on first user with administrative privileges that logs on to the desktop. Another workaround is to install additional service or define a sub-key in HKEYLOCALMACHINESOFTWAREMicrosoftWindowsCurrentVersionRun registry branch that run the registry batch file automatically on boot up, and this is useful if the computer won’t be logged on by anybody, but still requires the hack to allow unlimited Remote Desktop users to work.Another issue is that if user closes the remote connection instead of logging off, when he or she tries to log back in, an error message related to TCP/IP event ID 4226 may occur. To resolve the issue, download and apply the Windows XP TCP/IP connection limit and Event ID 4226 patch, and set the connections to at least 50.
![](/uploads/1/2/5/8/125805452/502247478.jpg)