If you have ever used a real remote computer system like Citrix, then you have probably been craving multiple Remote Desktop sessions since you first fired up Windows XP Professional and/or Media Center Edition. Here is a HACK (translated: USE AT YOUR OWN RISK), to enable multiple Remote Desktop sessions on your XP Pro or MCE 2005 box: NOTE: You will have to have knowledge of the Windows operating system and more specifically the Windows Registry. If you have no experience with the registry, then I would recommend you find someone who does or leave these alone. I do not make any kind of warranty that this will work for you or your friends. This is provided for entertainment purposes only.
Don’t call me if your computer stops working. Print these directions so that you have them to work from. Jason- I don’t know if you can help but here goes. Back in April I had a bug and in order to get my computer to respond I had to reformat my HD.
It is a Dell 5100 that came with Media Center Edition 2005. I never received a backup disc for this program.
Mar 12, 2008 - It is also the samllest patcher for Windows XP avilable now in comparision of WindowsX's. For disabling 'Windows File Protection(WFP)'. All software that you can find on our servers, including Windows File Protection Switcher, is either freeware, shareware or open-source, some of the software packages are demo, trial or patch versions and if possible (public domain licence), we also host official full versions of software.
I called Dell and they sent me a Reinstallation DVD /Winows XP Media Center Edition 2005 with update. Upon installing nowhere does it ask if I want to add or not add MCE. So it was never installed. I have tried PC Restore at the Del logo page (Cntrl-F12) but this file is history.
My question to you is: How do I get this program on my computer? Do I do it manually? Is there a separate DVD just for MCE 2005? So far Dell has been no help for the last 4 months.
Many Thanks. Every time I replace this file, it ends up not working, and the version of the file after the reboot is 5.1.2600.2180. Its almost like something on the computer is taking the file I copy to it from above, version 5.1.2600.2055 and updating it every time it reboots.
Its also deleting the copy I saved to the desktop of the machine. Could this be Norton Antivirus detecing that the file has changed and changing it, or system restore doing it or something? I am pretty much confused. I download 1 version, replace the file, and then it just goes right back. Whats interesting is the.2180 file isnt the same version as the original, it was even newer.
Jeremy - This is normal behaviour you are seeing with these windows system files being automatically replaced. The feature is known as Windows File Protection, designed to protect important system files.
C: windows system32 dllcache is this “backup” copy of the original system files. If the OS detects one of the protected system files has been modified or deleted, it replaces the file automatically with the original. My guess would be to replace the one in the dllcache with the new file, then delete the original and let WFP replace the deleted file with the new one you put in dllcache. So I have this hack working on my xp pro machine. I can have many Remote Desktop Connections at once. The machine I have this hack on is a “server” machine. There is no moniter hooked up to it.
What I’m trying to do is have a “console” user which is always logged in, to have a couple of applications which need to be always on run on that user. Once in a while I need to login and check on that user, just to see if there are any messages from the applications running on that user. I’m trying to use the “shaddow #” command, which requires you know the terminal ID of the user. I have a 2003 server machine which has this fantastic application called “terminal services manager” installed on it. Has anyone managed to get terminal services installed on an XP Prof. Or is it simply not possible?
Thanks for your help. I tried this method on Windows Vista Ultimate 6.0 Build 5600 and after replacing the DLL the service will not start and gives this error: “Error 1314: A required priveledge is not held by the client.” After reverting back to the Vista DLL, it works again, but is still limited to 1 user at a time. I am going to try and get my hands on the Windows 2003 Server DLL and I’ll post here again whether that worked or not. By the way, in Vista you need to change the permissions and owner on the DLL before you will be able to change it. The original owner is “TrustedInstaller” and you won’t be able to do anything to it.
Lee – You are absolutley right These retarded helpdesk idiots all have one thing in common. They are drooling over a file that enables RDP multiple sessions on XP Home, XP Pro. And for the one that wants to buy 15 dollar machines and set them up as winterminals to your intel celeron crap XP box.
![Windows File Protection Wfp Patcher Switcher Video Windows File Protection Wfp Patcher Switcher Video](https://hack4secure.files.wordpress.com/2016/09/d599d-img_20160617_131417.jpg)
You are an idiot too. I hope all of you download a virus. And it blows up your machines. You are the only reason that hackers get through to any machine. And you dumb asses who cant find the dll cache folder you too, are a bunch of drooling idiots this forum is like level.5 helpdesk wanna be. “Don’t feed the trolls” (Lee Childress and Joaquin Torres). “Trolls can be existing members of a community that rarely post and often contribute no useful information to the thread, but instead make argumentative posts in an attempt to discredit another person, more often than not based on what they thought was said rather than what was actually said by the other person, concentrating almost exclusively on facts irrelevant to the point of the conversation, with the intent of provoking a reaction from others.” Just don’t care about them By the way, i’m trying to make this patch works in a domain too!!!
I would like to congratulate all the guys for their hard work getting this to work. I shall try the patch shortly. I decided to install Win2k3 server on my P4 with Desktop board, but was really sad when I realized that Intel Desktop Boards does not support Server drivers.
The only reason I installed 2k3 Server was for multiple RDP’s. Now I can finally accomplish this thanx to you “STUPID” guys (as you were called by the two morons). I hate it when people act like children. Just because they are too stupid to follow instructions on a useful site like this, or have to much damn money. Regards, Giepie. I got the termsrv.dll hacked to allow unlimited users (really it is set to 99) to log into XP!!
I did some big tests with some thin clients. Here are my results: 5 thin clients on 512mb ram, no problem. If you close the connection instead of logging off, when you try and log back in you get booted with TCP/IP error 4226. Download the 4226 patch at and set the connections to at least 50. 10 thin clients got some resource errors on 512mb ram. On 1 gig, no problem. Opened lots of copies of word, excel, etc.
Had my 4226 patch set at 100 connections. 20 thin clients needed 2 gigs of ram to have each one open both word and excel. I had my 4226 patch set to 500. When the 21st user tried to login, I got an out of virtual memory and a BSOD (invalid page fault in module svchost.exe). I didnt have more then 2gigs of ram to try, so not sure if that woulda helped.
Anyway folks, enjoy! And video: Sweeeeet. I followed the directions exactly, double-checked my work, but when I log in using RD from another XP Pro desktop in my LAN the host machine logs off still. Fast User Switching was already enabled and I too had to manually copy the dll from the cache to System32. The host is running MCE2005, fully updated. Have there been changes to this OS that are blocking this patch since your article was written?
Incidentally, for a variation on this there’s a post at: by someone named “Brian”. I tried his additional GPEdit changes but that still didn’t change the host’s behavior. Any suggestions? I obey the steps. I restart the laptop and start the terminal services but then I cannot make remote desktop connetion to this laptop. It gives “protocol error”.
No one can connect to this laptop even only one user. I copied this new dll under the system32 too. The error is “Because of a protocol error detected at client, this session will be disconnected” Restarting was tried for several times.
Also Before making all the steps in this wep page I connected to this laptop from my pc for several times. There was no protocol error. Urgent help please.
Revised instructions 1. Print these directions so that you have them to work from.
Download the Terminal Services DLL – Save it to your Desktop or other suitable location 3. Restart your computer in Safe Mode – Follow this link to learn how to restart Windows XP in Safe Mode 4. Turn off/disable Remote Desktop Connection (RDC) and Terminal Services 5.
Right click My Computer 6. Select Properties 7. Click on the Remote tab at the top of the window 8. UNCHECK the box next to, “Allow users to connect remotely to this computer“ 9.
Go to Start - Control Panel - Administrative Tools - Services 11. Find Terminal Services in the list 12. Right click on Terminal Services and click Properties 13. In the Startup Type box, select Disabled 14. Click OK to close the window. Next you will replace the current version of the Terminal Services DLL (termsrv.dll) with an unrestricted version from a previous release of Terminal Services.
Using a file manager like Windows Explorer open C: Windows system32 dllcache 2. If there is an existing file termsrv.dll, rename the file to termsrvdll.bak or whatever you would like. Copy the downloaded termsrv.dll file (the one you just downloaded from the web) to C: Windows system32 dllcache 4. Open the C: Windows system32 folder 5. If there is an existing file termsrv.dll in this folder, rename this file to termsrvdll.bak or whatever you would like. Copy the downloaded termsrv.dll file to C: Windows system32.
Now we can edit the Windows Registry to enable more than one RDP connection. Go to Start - Run and type regedit – Hopefully you knew that already. Go to HKEYLOCALMACHINE SYSTEM CurrentControlSet Control Terminal Server Licensing Core.
Add a DWORD Key named EnableConcurrentSessions and give it a value of 1. Go to HKEYLOCALMACHINE SOFTWARE Microsoft Windows NT CurrentVersion Winlogon. Ensure the DWORD Key named AllowMultipleTSSessions is set to a value of 1. Though this is not required, you may also wish to modify the DWORD Key named LogonType. Set to a value of 0 to force users to enter a name and password to logon locally; set to a value of 1 to force users to logon using the Windows XP Welcome screen. Close the Registry Editor window. Go to Start - Run and type gpedit.msc to run the Group Policy Editor.
Browse to Computer Configuration - Administrative Templates - Windows Components - Terminal Services and double click Limit number of connections. Select the Enabled button and enter the number of connections you would like to enable.at least 2. Restart Windows. Right click My Computer and select Properties. Click on the Remote tab at the top of the window. CHECK the box next to, “Allow users to connect remotely to this computer“. Click OK.
Go to Start - Control Panel -Administrative Tools - Services. Select Terminal Services from the list and double click it or right-click - Properties. Set the Startup Type to Manual.
Restart Windows/Computer You should be good to go. Can only add that this method is simply replacement of termsrv.dll. This version is not a hack. It came from the beta of SP2 and didn’t have restrictions to 1 session. Only complication is that this service can’t be stopped by normal commands. That’s why there’s a suggestion about running safe mode. But you don’t have to.
And you can also do it remotely. I just did it. You need telnet session for that. First you upload termsrv.dll to C: on the target machine using terminal session or FTP. And then use the command sc config termservice start= disabled Then you restart the machine from the terminal service and reconnect telnet after it reboots. Then you replace termsrv.dll in system32 and system32/dllcache with whatever you uploaded using copy command.
Then use sc config termservice start= demand and then net start termservice That’s all. Thanks Netter for the reply. But I’m still confused, does it allow 2 users (1 on client computer and the other on the server) to logon simultaneously with the same username and can actually see same contents displayed on the screen, view same documents and control same applications at the same time? I followed the instructions carefully but still the server does not allow simultaneous logon using the same username. It only allows one user at a time except if the other user logs on using a different username. Hi, I followed the instruction carefully, but I am having troubles most of the time especially if local(other account) has already logged on to the system before I start remote desktop from other pc. I can see desktop background (using LAN connection) then remote desktop window will close automatically.
If I keep on trying it will ask to log off the current user (the one already logged on) so I can remote desktop into my pc the same way as if I were using regular/original termsrv.dll Any suggestions? I’ve just installed SP3 and my previous fix to the multisession was killed, and no way to get it up again. Yesterday I found these instructions from Jason and applied them. Did everything by the book, just one little difference: “C:/windows/system32/dllcache” does not exist. Si all I did was skip that instruction and go to “C:/Windows/System32” find the termsrv.dll delete it and paste the one downloaded from here.
All the rest was just the same as explained. Very straight forward and now: I’M BACK WITH MULTISESSIONES IN XP SP3!!!!!!
Thx so much Jason, I use an XP machine with 2 simultaneous users sharing one app installed in that computer that can not share the data base, so I have to have multisessions to run the business (very small business 3 people) to be able to open the this back office system app we use (one per user) without having to shut down the primary user session. Your the MAN!!! Well, hack seems to have worked for a lot of people, but not me the box I’m tryiing to enabled multiple concurrent RDP sessions on is running XP SP2.
Firstly, could not find dllcache folder, even after enabling ‘view hidden folders.’ So I just put “C: WINDOWS system32 dllcache” into Explorer and it went there, though there was no termsrv.dll file in that folder after following instructions, I first was not able to connect to the box via RDP at all. But after copying the termsrv.dll file provided to C: WINDOWS System32, I was able to connect via RDP, but with only one session. I then tried running the TS Reg Patch.reg file mentioned by “homenetwork” on 22/8/08, but still unable to connect more than one user to the box via RDP (just get the usual message that the other user will be kicked off when trying to connect another user via RDP). “Hey for what it’s worth, while this technique did work for me, my Anti Virus software (AVG) told me that the termsrv.dll I downloaded from was a trojan (Trojan horse Generic11.AGPO) So proceed with care if you do this method. (Myself, I’m rolling back to an earlier snapshot of my machine!)” Joshua this is VERY common for anti viruses to state modified system files as viruses.
If you use, or can use, multiple av scanners on that file you will get very different results. There is another “hack” out there that reverses an XP’s limit on TCP/IP connections from like 10 to 100.
Its perfectly normal, not a problem and helps with heavy network traffic (see P2P). Anyways, several Av scanners show this as a virus, and it clearly is not. Even the creator of the file discusses this openly on his site and explains why it shows as a trojan.
So not to worry, this is not a virus of any kind, this DLL file. (PS – Keygens show up as a trojan from Norton and Mcafee, not on Kaspersky or Bit Defender. Go figure). Everything works fine of course. There’s only one thing I can’t manage.
In windows 2003 (for example) I can have multiple logins from same account (i.e. From console and RDP by the same user at time) and both are two independent sessions.
In windows XP, after this hack I can’t login at the same user both to console and RDP or on two independed RDP sessions. When user “X” is logged in at console, every try to logon at this user via RDP causes to disconnect user “X” from console. Do you have any solution on that? HELP In principle it works for my.
Several users can RD-connect to this PC and work. BUT I can’t control it locally. When booting the usual starting screen (with the dots running from left to right) appears. After that I get either a black screen or a light blue screen with the mouse showing up (color depending on log on mode (showing users to click on vs. Old mode with user and pass to be entered manually)). But it is impossible to log onto that PC when sitting in front of it because I can’t do anything while these black/blue screen appears (also tried strg alt del to log on). I tried to remove it all (rereplace termsrv.dll and remove registry entry and gpedit.msc change) but still the same.
Please can anyone help me to get it either working correctly or completely remove it? Thank you in advance!!!
Works like a charm but: – copy the dll to system32 to. I renamed both old dll to bak. Taking over the session of the other users doesnt work here.
Like when someone is logged in you usualy can click the user and say take over. In case you need to assist. I declare what kind of key stroke i have to make to disconnect from them and nothing. So I installed vnc next. Multiple users under xp, well vnc doesnt see it as a second or third screen.
Normaly i would connect like: XPSP2PC:0 (main screen) XPSP2PC:1 (second screen/user logon) vnc will not load in the the other users. Ok one minus point if whe add the thing up. I am using xp2 on a intel celeron laptop. My query is,the above mentioned hack says, open C: Windows system32 dllcache Rename the file termsrv.dll to termsrvdll.bak or whatever you would like.
Copy the downloaded termsrv.dll file (the one you just downloaded from the web) to C: Windows system32 dllcache Open the C: Windows system32 folder Delete the file termsrv.dll in C: Windows system32, But i have read another article on. Kindly read the hack given on the above url, “.
Actually i am getting confused,which hack shall i use,currently i have tried the steps given on this url on my laptop.after doing these steps i couldnt connect the laptop machine from my desktop where the configuration are done. An error of 126 occur. File termsrv.dll has to be deleted from system32,as per given in this configuration on this url. Later i did copied the termser.dll file in system32,now i can connect RDC to the laptop machine from desktop machine. But,when i log on to the laptop machine,RDC gets disconnected.so i suppose the hack is not working properly on my laptop. Also do i have to install a different program of terminal services DLL,to run RDC for multiple users. My purpose of RDC is just to keep a track on office pc`s and internet cafe`s wher we have provided internet connections.
Actually i run an internet network in a radius of 7 Kms,with 300 above customer and 22 internet cafe`s. Kindly help me,also guide me if i am going wrong in doing the configurations. I have a question as I am pretty new to networking. Will this allow me to have 2 remote c omputers access the host computer at the same time without logging each other off? I am looking to have 2 computer cash registers run at the same time using a host computers drive that has all the inventory and program so both remotes need to be able to access and run the same program from the host at the same time without logging one or the other of. Or if this will not work what can i do to do so? A program of some sort?
This did not work for me as the termsrv.dll file is not available when I tried to download it so i used one I had from another website. I have tried 3 different version of this hack from different places and none of them work. All very similar, hack registry, hack gpedit, replace custom termsrv.dll with custom termsrv.dll. I am doing this on virtual XP SP2 and I can remote log in before I do the hack afterwards I can not even log into one session, this hack does not work like all the others have tried. To work in a machine which is part of a domain (AD or Samba/LDAP) you MUST enable it in the registry: “AllowMultipleTSSessions” must be “1”. (find it with regedit.exe) For default (all time the machine is started) Windows set this value to “0”. Then you must change it to “1” to made the solution explained here, work.
This must be execute with administrative rights, so, you will have to execute some command with another user/password (with administrative rigths), because for default i expect, not all users have this rigths. One solution is to use the command runasspc.exe, which you can execute inside a batch program in a non interactive way.
I did everything according to the instructions given in here. But I’m getting an error when I try to start Terminal Services. Error says: “Could not start the Terminal Services service on local computer Error 126: The specified module could not be found” Plus, I did start the dependant service before I start the “Terminal Services” I’m using XP box with sp 3 BTW, the new dll I got from the website is only 74kb. Kind a small file compare to the original. Do you guys have any ideas?
Thanks in advance. Trackbacks/Pingbacks. Enabling Multiple Remote Desktop Sessions in Windows XP Professional and Media Center Edition 2005 –Jason Golod Blogs (tags: windows. Enabling Multiple Remote Desktop Sessions in Windows XP Professional and Media Center Edition 2005.
Maybe this trick is old but it’s usefull for multiclient in windows XP. I was copy from here. November 2nd, 2007 If you have ever used a real remote computer system like Citrix, then.
Fonte:. Original Article Leave a reply. Enabling Multiple Remote Desktop Sessions in Windows XP Professional and Media Center Edition 2005. Enabling Multiple Remote Desktop Sessions in Windows XP Professional and Media Center Edition 2005.
I just found that. As for the google search, most (if not all) results will only apply to SP3 RC2. The article I found pertained to RC2, but I followed it and found that there was no difference in information. Just follow the steps, either way, good luck. If you really need assistance, I can offer help via AIM.
To previous posters about why you would want to disable Windows File Protection, for most moderate to experienced users - they don't require that Windows backs up critical operating files because they either format too often or they don't modify these files except for with hotfixes. When you apply a hotfix, you could always download a previous version if you run into conflicts. I myself disable it, it's a SHEER waste of space and it is SO annoying when I do modify a system file that it asks if this is 'OKAY' and tries to replace it with a previous 'WORKING' version. In response to: 'Hi, does anyone know how to disable Windows File Protection in Windows XP with SP3 RTM installed. And please, when suggesting a solution be sure that it works in the final version of SP3 and that it wont in any way fsck up my system.
Yes there is a simple way to do this in Windows XP SP3. Restart your computer, boot windows in safe mode. Depending on your BIOS you will usually have to press a button during the start up process to access safe mode. Could be 'delete', could be a 'function button'(i.e F8, F9, F10, F11, etc.). If you cannot figure out how to start your computer in safe mode. You are probably to stupid to be messing with vital windows components safely.
But if you insist on blindly.ing into the wind. Google: 'How To Restart my computer in safe mode' or some stupid thing.
Once you have started in safe mode you can delete, replace, cut, copy, rename, patch or ruin basically any file on the computer without being hassled by windows. NOTE: USING THIS METHOD CAN CAUSE WINDOWS TO STOP WORKING IF NOT DONE PROPERLY. IF YOU DO NOT KNOW WHAT YOU ARE DOING YOU PROBABLY SHOULDN'T TRY IT! UNLESS YOU DON'T CARE ABOUT THE DATA ON THE COMPUTER AND JUST WANT TO MESS AROUND! If you delete the wrong windows component you could be deleting one of the files that tells your computer how to start up.
IF YOU STAY OUT OF ANY 'C: WINDOWS' or 'C: DOCUMENTS AND SETTINGS' extensions and you should be fine. I guarantee nothing unless you understand what you are messing with.
General tip: First: If you can't figure out one way to do something on a computer there are usually 10+ other ways around it. If something isn't working try something else. Second: If you can't figure something out it's better to do mass amounts of research before tearing into it. Rather than ruining your windows installation because you dove in to fast. In response to: 'Hi, does anyone know how to disable Windows File Protection in Windows XP with SP3 RTM installed.
And please, when suggesting a solution be sure that it works in the final version of SP3 and that it wont in any way fsck up my system. Yes there is a simple way to do this in Windows XP SP3. Restart your computer, boot windows in safe mode. Depending on your BIOS you will usually have to press a button during the start up process to access safe mode. Could be 'delete', could be a 'function button'(i.e F8, F9, F10, F11, etc.). If you cannot figure out how to start your computer in safe mode. You are probably to stupid to be messing with vital windows components safely.
But if you insist on blindly.ing into the wind. Google: 'How To Restart my computer in safe mode' or some stupid thing. Once you have started in safe mode you can delete, replace, cut, copy, rename, patch or ruin basically any file on the computer without being hassled by windows. NOTE: USING THIS METHOD CAN CAUSE WINDOWS TO STOP WORKING IF NOT DONE PROPERLY. IF YOU DO NOT KNOW WHAT YOU ARE DOING YOU PROBABLY SHOULDN'T TRY IT! UNLESS YOU DON'T CARE ABOUT THE DATA ON THE COMPUTER AND JUST WANT TO MESS AROUND!
If you delete the wrong windows component you could be deleting one of the files that tells your computer how to start up. IF YOU STAY OUT OF ANY 'C: WINDOWS' or 'C: DOCUMENTS AND SETTINGS' extensions and you should be fine. I guarantee nothing unless you understand what you are messing with. General tip: First: If you can't figure out one way to do something on a computer there are usually 10+ other ways around it.
If something isn't working try something else. Second: If you can't figure something out it's better to do mass amounts of research before tearing into it. Rather than ruining your windows installation because you dove in to fast.