Concurrent RDP Patcher: How to Download & Enable
There are a lot of third party remote control pieces software around such as the popular freeware tools VNC, and TeamViewer, but there are times when the built-in Remote Desktop Connection feature in Windows 7 is the most useful since it’s already present in Windows and you don’t need to install any third party software. All you need to do is to enable it because the Remote Desktop function is disabled by default. You can enable Remote Desktop and allow connection from other computers by going to Control Panel -> System -> Advanced System Settings -> click on the Remote tab.
From there, you can either select “Allow connections from computers running any version of Remote Desktop” which is less secure or “Allow connections only from computers running Remote Desktop with Network Level Authentication”. If you are setting up a connection to a different Windows version such as XP or Vista from your Windows 7 machine , then you need to choose the less secure option.
Tip: Pressing the WIN Key+ Pause/Break keys simultaneously brings up the System window.
If you only see the Remote Assistance box in the Remote tab but not Remote Desktop, that is because there are some restrictions that Microsoft has implemented in your version of Windows. Only Windows 7 Professional, Ultimate and Enterprise can accept connections from Remote Desktop but NOT for Windows 7 Starter, Home Basic and Home Premium. You can however, use Remote Desktop to initiate a connection from any edition of Windows 7.
Many branded laptops and computers come with Windows 7 Home Premium or possibly Home Basic pre-installed, but not to worry because there is a hack patch that can enable the Remote Desktop Connection in Windows 7 Home Premium with a single click.
There is a tool called Concurrent RDP Patcher which is meant to enable concurrent remote desktop connections, which means multiple logons per user. When you log in using the Remote Desktop Connection, the computer that is being controlled will show a message saying “Logged on remotely from COMPUTERNAME”. If you click on the user icon to login, the remote connection will be terminated with the popup:Your Remote Desktop session has ended. Another user connected to the remote computer, so your connection was lost. Try connecting again, or contact your network administrator or technical support group.
This allows multiple users to control the remote computer using Remote Desktop.
Amazingly, this tool also enables the Remote Desktop Connection for Windows 7 Home Premium. The good thing about this patcher is you can revert the changes back to the way it was by clicking the Unpatch button. There are some scripts that can also do the same by patching termsvr.dll file but it doesn’t provide a way to undo the patch.
By default, a Remote Desktop Connection only allows you to login with a user account that has a password assigned to it. User accounts with a blank password cannot be used to login with a Remote Desktop Connection. You can handily bypass that restriction by checking the “Enable blank password logons” checkbox.
The Concurrent RDP Patcher tool was originally released by a member of The Green Button, which used to be the official Windows Media Center Community forum. Sadly that forum is no longer available. The patcher was updated by its original author a while ago to include compatibility for Windows 7 Service Pack 1. As it was effectively abandoned by the author after this we have since made further updates to the tool as and when needed. It is compatible with both 32bit and 64bit versions of Windows 7.
Download Concurrent RDP Patcher
SHA1: C7C79D848717E71209B21E3A43C623123FFFE0D3 (for Zip file)
Note that this version of Concurrent RDP Patcher patches the dll on Windows 7 RTM, Service Pack 1 and with update KB3003743 which was released in October 2014.
Important Updates For 2019 (and October 2018)
For four years the termsrv.dll file wasn’t changed and the Concurrent RDP Patcher worked fine from October 2014 onwards. Recently though, Microsoft made changes to the dll and it broke the patcher with Rollup update KB4462923 released in October 2018. If you are still running with that update or have not yet installed any Rollup updates beyond January 2019, we have a dedicated Concurrent RDP Patcher that works with it.
Download Concurrent RDP Patcher 2018 with KB4462923 Fix
SHA1: 2A257693D8492191FAF7E55B787398CB57EBAD09 (for Zip file)
Unfortunately, it’s only been a few short months and Microsoft has yet again changed the termsrv.dll to break the patcher once more. The offending update is Rollup update KB4486563 released in February 2019. The January 2019 Rollup Preview (KB4480955) also contains the same dll file. We have created a new patcher that should work for this latest update.
Download Concurrent RDP Patcher 2019 with KB4486563 Fix
SHA1: CCC6D13F966F833454DEBC05D77715A34142275F (for Zip file)
NOTICE: Please be aware that the Feb 2019 version of the patcher has not been extensively tested so it should be considered as alpha/beta software and could contain bugs. Please use it with care and at your own risk. Of course, we welcome any feedback on how this latest patcher version works for you.
Concurrent RDP Patcher fixed versions work on 32-bit and 64-bit Windows 7 Service Pack 1 and newer. Starter, Home Basic, Home Premium, Professional and Ultimate are supported, but not Enterprise. We will do our best to update the Concurrent RDP Patcher if there are any more updates to the termsrv.dll library in 2019. Support for Windows 7 ends in January 2020 so there aren’t likely to be any more updates after this time.
April 2019 Test Version
Microsoft has updated the dll for the second time in 2019 and enjoys making life more difficult! Rollup update KB4493472 will break things again. The below patcher is a test version and should be treated as such on 64-bit and 32-bit Windows 7 so please take care when using it.
Download Concurrent RDP Patcher April 2019
SHA1: 2451C977543871DC09EDEB383016A650261725D5 (for Zip file)
As always, feedback about this version is welcome.
The patcher does not work since the KB5008605 update on termsrv.dll which is 688640 bytes in size and has the SHA1 checksum C33E5592F2E29AED2FE9F1322AA70EFB48066E0C
Cannot start TermService on computer ‘.’.
This patcher is not working on Enterprise version of Windows 7.
That’s right, it never has supported Windows 7 Enterprise, the article makes that clear.
Seems not to be working anymore. Checked the patches, removed a couple of them. Repatched but not working.
I have a Windows 7 64 bit Home Premium version with SP1 installed.
I have checked which updates are installed on my machine (A side note: I have a genuine version so I would expect to have the latest updates installed):
KB3003743: Present
KB4462923: Not present
KB4486563: Not present
KB4480955: Not present
KB4493472: Not present
Which version shall I install?
I have checked Concurrent_RDP_Patcher_2-22-2011 and Concurrent_RDP_Patcher_APR2019 but I still only see the Remote Assistance box. Is it needed to restart the machine after the patch?
Thanks
I have to use Win7 Ultimate 32 Bit & RDP stopped working
Wonder if Microsoft have amended termsrv.dll again??
I haven’t been using Win 7 for a while, but there’s not been any updates for it since the start of the year, has there?
Update:
Re-ran the April 2019 patcher version & all is restored.
Happy again
Hi I have update Windows 7 Ultimate 32 Bti and later RDP path it not working.
hi. need windows 10 enterpise patch for mulitople rdp.
hex edited the termsvr.dll from google edit.. but that did not work.
joe
Many thanks for this!!!
Same here. Thanks for commenting too (helped me figure it out).
Sos un grande!!
Really thanks man
Thanks, I was stumped by this issue. Everything seems good using the April 2019 patch
Cheers!
I tried to apply the latest patch with Apr 2019 fix onto Windows 7 64 bit SP1 Home Premium, but I cannot click on the checkboxes. Am I the only one?
I have this problem. meaning this:
Microsoft Windows 7 Home Premium- temsrv.dll has an unknow checksum.
Perfect…or almost…. It allow only 4 remote connections….
:-/
Even if on GPO i put 99999
Latest patch seems to work just fine on Win 7 Pro.
Hi,
Worked like a charm on Win7 Home Premium! Did not see the Remote Desktop option, but connecting worked fine anyway! Thanks a lot!
Ake
It doesn’t work on Windows 7 Home Premium
Sorry. I realized that actually it provides the service but it it doesn’t provide the Remote Desktop settings on the Remot tab.
Hi, does this program run on windows 7 ultimate ? Because when I use it it tells me that termsrv.dll has an unknown checksum.. The windows was last updated in 2015
Yes, it’s supported. Which version of the patcher are you running?
Thanks, man!
All it did on my Windows 7 Pro was break RDP
Work Smarter, there are 100 other things that could break RDP, along with the patches,Digital Certificate Auth checks, Limitations of the HIGH SECURITY connection required of the Client,to Server. Dig a little deeper,you will find the solution. This is only a PATCH its not a PAID TOTAL Solution.
Hello – Also attempted patch of Windows 7 Pro (using the April 2019 Beta). RDP stopped working. Unpatching it did not fix it so RDP is down completely at this point. Uncertain what else to try other than restoring OS from backup. Oh well, it was worth a try. Thanks.
I wrote that message too soon. At first, I received an error message about TermServ.dll being in use and unable to patch. Then I was unable to RDP to that PC (as if it had patched and the patch failed). A couple of reboots and unpatch attempts failed to correct that.
For some reason I tried again one more time and it worked … now logged in with 3 different users. That’s the limit of my testing but this corrects my previous post about it breaking RDP. In fact, it seems to be working.
All those people complaining that it’s not working on Windows Home (any version) should remind themselves that Windows Home doesn’t support incoming RDP connections.
Quoting a response on Microsoft’s support site…
“Home Premium and below version: Cannot act as a remote desktop host, terminal services disabled entirely. Can access other desktops remotely using RDP client.”
answers.microsoft.com/en-us/windows/forum/all/which-version-of-windows-7-has-the-ability-to-use/50716e11-6911-41a8-8937-e08fd84390dc
Home can have RDP activated, it takes more work.
Most Complaints are from people that do not understand how RDP works or is configured,just shoping for a button click solution.
99% of The Business that started in REDMOND Washingtons Answers and Articles,are designed to have someone BUY the newest version of the BETA Software they SELL, which is actually only End USER Rented ALPHA Software anyway.
To get a Solution,to a Problem today or 20years ago,its best to Look around, and find people that actually SOLVE problems,they cant and wont.
Real simple reason RDP was no in HOME.,to be one of the 100 things that do not work,so people BUY and UPGRADE to PRO or Higher, at a Higher Rental of Alpha OS Software.
It supports windows 10?
No, it quite clearly says in several places it is for Windows 7.
Have Widows 7 Home Premium. Install of the patch went fine. I can’t RDP into the PC. I tried patching and unpatching each version for troubleshooting purposes. Here are my two observations.
1. I never see the selections under the System Properties > Remote tab. All I see is the Allow Remote Assistance checkbox.
2. When trying to RDP into the PC it looks like things are trying to connect.
A. I get a login screen asking for User/Password
B. I get the Security Verification (I answer YES to connect despite certificate errors)
C. My client PC screen then shows the remote connection bar at the top of the screen looking like it is about to connect. It even flashes a dark blue background with Waiting to Connect (something like that) on the screen. About a second later the connect screen then goes away. The connection is closed.
My termsrv.dll version is 6.1.7601.17514. Looking at the properties it shows a date of 4-13-19.
I also tried disabling the firewall and virus protection just to eliminate those.
Any thoughts? Thank you.
Look at the Event Logs,System,for the errors from the Auth.
Follow those error messages.
Solution is out there
Hi
I have downloaded the latest patcher to use with Win 7 Professional but i seem to be failing on attaining multi users.
where could i be going wrong?
you dont get Multi users, you get 1.
You want more then 1,call the Company and buy a Liscense for the RDP Server for the SERVER PLATFORM and TERMINAL SERVICES.
its to connect 1 terminal to a host, not to act as a Free Cheap Terminal Server, so you dont have to PAY for TERMINAL SERVICES LISCENSING, or CIT/r3x.
Thank you man. You did a very good job. This saved my job!
A beer is waiting for you.
Piero
it works!!! (after installing updates) as mentioned earlier in comments.
Thank you very very much.
Hi! many thanks for patches.
The only sad thing for me so far – it does not work for W7 Ultimate.
Win 7 Ultimate is obviously supported, so what is the issue causing it to “not work”?
99% chance his problems are listed in the Event Log,like most other people that cant figure it out.
Go to your event log,and look for the Errors about Auth,and Certs,and Digital Certs,and more about Upgraded MINIMUM REQUIRED Security level,connecting to and from stations.
After you have those Errors, search those and you will find people that also had those errors,
and how to fix them.
Example,Step down the Minimum Required SEC LEVEL for Connection.
Example II, Dont require Digital Signed…certs.
He Made the patches,for specific things, due to Redmonds Alpha Software UPDATES,it changes other things in the Workstation,that are part of RDP and your actually problems.
Learn how to USE an EVENT LOG.
Hi, sound subsystem doesn’t work with the last patch :(
you did something wrong.
somewhere else,this has nothing to do with AUDIO or HAL access to Hardware or Drivers specific with AUDIO. It might be able to WRAP sound thru RDP,but its not going to break your stations AUDIO Function.
So tell me please. Running the patch tool gives me a message termsrv.dll is patched. I can toggle from patched to unpatched. I don’t have remote access options opened up in the remote tab. Do I need to restart computer? What am I missing if anything? Win 7 Home Premium 64
Hi I had download the April 2019 RDP patch and try to unzip the file, it was password protected. Is there any fee for the release of the password? if so what will be the cost?
The password is displayed on the download page. We don’t charge for our tools/downloads.
Do the Jan.2020 updates addressing the RDP vulnerabilities CVE-2020-0609, CVE-2020-0610 and CVE-2020-0611, break the Apr.2019 version of this patcher ?
If termsrv.dll has been updated, then it will break the patcher.
Thank you! First ran all the latest windows 7 updates through 12/31, locked down any further updates without my okey dokey. Then installed your successful April patch. Am also running in a VM so I have an easy image of the whole shebang…
Can I buy you a beer, please?!
April 2019 still works perfectly, thank you soooo much for your work!
If I am setting up from scratch, do I download the original and all patches and run them one by one?
No, if you update Windows to current, you only need the latest patch.
Just installed the April 2019 RDP patch after installing all available Windows 7 updates including the Bypass ESU patch. Concurrent sessions work again, thanks!!!!
Thank you. It works for me.
many, many thanks! It worked!
thanks a lot, you save my life ;)
Hello,
Thanks for that patch. I downloaded and ran the April 2019 patch (termsrv.dll had a valid checksum), but after I ran the patch, and even after rebooting, I’m not seeing the RD settings on the advanced system settings page. I have W7HP. I’m not sure what to do next.
Thank you.
Can you provide sources?
downloaded April 2019 version and opened as administrator, however all controls, i.e. checkboxes and buttons are disabled on form.
Sadly, it doesn’t work with the update KB4499175 installed. Maybe there will be an update soon?
Can you be a bit more specific than just “it doesn’t work”?
I got an error that says termsrv.dll has an unknown checksum when using the April 2019 version. I don’t know that it’s related to the KB that OP mentioned (machine in question doesn’t appear to have that update installed) but the computer is otherwise up to date from what I can tell. I would understand if you let this project go with Win7 going EOL in January, though.
Does this patcher work with server 2019 ?
The article tells you more than once it’s for Windows 7, nothing else is supported.
I think nick, is kinda NEW…
To the Technical Field.
Hi,
The concurrent patcher is a great tool thanks.
It does not seem to work with the newest Bluekeep patch (KB4499175) does it?
I tried April 2019 update but can’t connect with RDP any more.
Does anyone else experience this?
(win 7 home 64 bit)
Uninstall that patch, MS has released another one KB4490628 that includes KB4499175. I have a PC with all updates and this works fine.
Thank you, thank you, thank you!!!! I’ve been trying to update my Win7 HP PC to where I could remote connect to it for at least a month, starting and stopping and starting again because of frustration that patches or even trying to upgrade to Win7 Pro all never worked. I even tried the Concurrent RDP Patcher but I used the initial version you made (and today it doesn’t work). So today I took my time and read down and down and down through this web site and finally tried the final April 2019 patch and it works just as you would expect. Maybe you should update your site and put the April 2019 patch at the top or even remove all the older patches. All I can say is thanks, thanks, thanks for keeping after Microsoft. They are good at upsetting things. Hopefully they don’t screw around and disable the April 2019 patch. Thanks, Nick
We’ve kept all versions up because people were rolling back to previous versions before the termsrv.dll was updated again. The latest version is listed at the bottom so it shouldn’t be a problem.
Worked great with my Win 7 SP 1 client. Thank you!
What is the password for the file?
Passwords are listed on the download page…
This patcher version breaks the remote desktop by not letting me see anything that is currently open,program wise. I can see no UI windows for ANYTHING that is open. no browsers, nothing. Just desktop with my icons on it. =(
you have another
END USER Problem
Try Rebooting the END USER.
Look in your Logs.
THANK YOU!
APR2019 looks good – thanks again
it keep return me a message say that termsrv.dll is being used by another process. may i know how should i get to know what process are using it?
Worked well for Win7Pro With the Latest April 2019 Patcher, others didn’t
Thanks!
After patched, can i change RDP port number?
yes
It works the same with me, help.
I use the April 2019 test version.
It seems only 3 user can log in at the same time.
But I have another problem. When users want to log off, they’re unable to log off (stuck at the logging off screen), and I need to force restart the computer.
Please help to fix the patch.
Thanks
I have only the admin user on my PC and when I login with the Microsoft RD android app, it starts a new session. This is very inconvenient when I’m trying to control the programs I have opened.
Help?
The Inconvenience is YOURS.
Its not the writer of this PATCH,for free problem
If you have a END USER INCONVENIENCE, take it up with the Software OS Provider that you are Using.
April 2019 Test Version
Fast check (not double checked),
Multiple Remote Desktop from 3 different user are working perfectly.
If using same user, the remote target will start new session for the same logon account (the account name will appear in folder “user” on C Drive and will be generated automatically).
So the first user already connected will not be disconnected if there are same account login again from another PC.
Tested on Windows 7 Build 7601 SP1
Just a little bit confused to change how many user can connect at the same time. Already changed from GPO (from server) and Local Group Policy, but maximum user still the same (Currently 3 users).
Additional Comment
If already 3 user doing remote session at the same time, the 4th user totally can not RDP to this host.
1 of 3 user must disconnect first.
anyone could try the patch on update KB4499164 (May 2019 security rollup) yet ?
need this too
I ran the April update and it appears to have run ok, but I don’t see the Remote Desktop info on the Remote Tab. Am I missing something?
Hi,
using Win 10 Pro N here, says unsupported – termssrv.dll has an unknown cheksum.
Any chance for support? :) AFAIK it’s the same dll (unless MS changed that too)
Thanks!
There will be no support for anything other than Windows 7.
Can confirm April patch works in Windows 7 after Microsoft patches critical wormable RDP exploit. (5/15/19)
For me, the RDP patches failed after installing the Microsoft Security update for the critical wormable.
Did you patch before or after installing the MS update?
Tried for a couple of minutes and it works good so far. Thanks!
How can I login remotely on current local session? It is not possible after patching.
password is incorrect for april 2019 and 2011
The passwords are all the same, are correct, and clearly shown on the download page.
April 2019 Test Version checksum you’ve listed:
SHA1: A8237B10BC30129A5EF1AD73BE1937A149F88F76
and the checksum of the downloaded zip file don’t seem to match?
Concurrent_RDP_Patcher_APR2019.zip:
SHA1: 2451c977543871dc09edeb383016a650261725d5
Yes, the SHA1 checksums were for the executable files but we’ve since Zipped everything to help stop them being flagged as malicious. The checksums have been updated for the Zips.
Thx!
April 2019 Test Version works fine on my Windows 7 Home Premium 64-bit.
Thank you always.
April patch does not work for Windows 7 Ultimate 64 bit. “unknown checksum” error
It works with the latest April 2019 Security rollup patch for Windows 7 x64 and x86. You don’t have the April patch KB4493472 installed or there is something wrong with termsrv.dll otherwise it wouldn’t say unknown checksum.
The correct unpatched termsrv.dll is version 6.1.7601.24402 and 688,128 bytes in size.
Thanks! Works perfect! Just got the april beta and it seems to work just as good as previously.
Btw, do the patcher contain all earlier patches, or do I need the older versions for older win7 machines?
Thanks for the report.
One patcher doesn’t contain all earlier patches but it supports more than one. Each one supports the default Service Pack 1 dll, the KB3003743 patch from 2014 and whatever latest patch is listed in the article. If you want support for Windows 7 RTM, download the original patcher.
Thanks for your work on this. I’m not able to unpack using the password provided. Any help would be greatly appreciated.
All the files work with the password provided, don’t forget it’s case sensitive so enter exactly as shown.
Thanks, HAL9000! I was thinking the SHA1: was the password but I see on the download page the password is listed. Sorry for the confusion.
Dear Sir,
thanks for your effort but link (to patcher April 2019) is srill the same: 64-bit only.
Doesn’t work for 32-bit :(
Sorry about that, our CDN hasn’t caught up with the file change yet. I’ve purged the old file manually so the new one should be available now.
Just tested! April 2019 Test Version works perfect (Windows 7 32-bit).
Thank you so much! Keep up with great work! :))
The April 2019 patcher has been updated with 32-bit support.
Thanks HAL9000. This morning I tried 64bit and worked pergectly. Now this new version is asking for a password.
Password is noted on the download page.
Sorry sir. You are correct.
Thanks again for all your efforts!
Please, there are still many of us who have Windows 7 32-bit ( there are reasons for that)!
Please make 32-bit version! Thank you :)
Hi!
32 bit will be not?? :-(
4/13/19 – latest update still says termserv.dll has unknown checksum
sorry Win10 Pro, all updates current. but i don’t see either KB listen in the comments as installed on my machine.
currently my machine has Termsrv.dll 10.0.17134.706 located in System32
file date 4/2/19 7:16am
Erm, I would have thought it was very obvious that this tool is for Windows 7, it doesn’t work on anything else.
crap dude sorry, i have another one that i use for windows 10 and it quit working too, went hunting around on google and this was one of the apps that kept coming up.
sorry about that. feel free to remove my comments if they let you
RDP Wrapper might work for you.
github.com/stascorp/rdpwrap
Windows 7 x64, April 2019 patch working like a charm once again, thank you so much!
It works with KB4493472 x64 April 2019 Security Updates. Thanks HAL9000 for the quick fix!
April patch works. Thank you again for keeping this alive.
Latest April patcher worked for me with KB4493472 updates.
Hello all
Yes M$ did it again:
KB4493448
Termsrv.dll 6.1.7601.24402
KB4493472
Termsrv.dll 6.1.7601.24402
On W7Pro it is showing unknown checksum.
Have you tried the April 2019 patcher? That should work with Termsrv.dll 6.1.7601.24402.
Hey HAL9000 !
I came to report it after uninstalling both KBs and getting it back to work. I’ll try it, just downloaded it. I really appreciate your work sir!
Have an excellent weekend!
Thanks again!
My W7 Pro is also showing unknown checksum
The test Version for KB4493472 worked like a charm for me, thank you :)
I’ve added a test version for KB4493472 to the article. Only 64-bit has been updated, 32-bit may be added later but I’m guessing virtually nobody is running 32-bit Windows 7 these days.
Please add 32-bit ver
I’ll think about it…
Yes, it has problem with April 2019 update. It’s written termsrv.dll has unknown checksum
Unknown checksum with KB4493472 .10th April update
Patch still works with April 2019 update.
Thanks for your feedback.
Not for me: KB4493472 (Monthly rollup 2019-04) replaces termsrv.dll, and it has got a different hash. Please update the RDP Patcher. Thank you
OS: Windows 7 Professional Italian
Nope it does not – I get error message that termsrv.dll has different checksum.
April 2019 Update has changed termsrv.dll again :-( at least on Win 7 Professional
Yeah, April 2019 Security update KB4493472 does break the patcher.
Ran this today, 5th of April. termsrv.dll has a different hash, so I’m guessing it was updated :(
Nope, my Win 7 is fully up to date and my status is simply “unpatched”, therefore the dll has not been changed.
IF you are running a preview update it might change, but they are not official patches so we don’t count them.
works!
I think there were some updates from April that are blocking this. I am also having issues with this.
not working for me using the 2019 patcher. Windows 7 Home Premium.
I ran the patcher today April 1, 2019. termsrv.dll file is dated March 19, 2019
Local OS (Windows 7 Professional 64bit) resources (disks and clipboard) aren’t accessible from the remote OS (Windows 7 Home Premium 64bit) during remote desktop session with the latest RDP Patcher 2019. Is it alright, or it is some problem on my remote OS?
Hi, I’m running Windows 7 Home Premium and I’ve just downloaded and applied the February 2019 patch – but I still don’t see any options for RDC in the Advanced System Settings (only remote assistance). I’ve tried restarting after the patch (no change). Is there any other step I have to do?
Also, thanks for your work on this project! Doesn’t seem right some of us should miss out on such a great tool.
HAL9000, excellent job! Is working!
We have 5 RDP clients working concurrently after patching Termsrv.dll – 6.1.7601.24326 – 2-Dec-18 – IA-64 on Win 7 Pro. Got upgraded again with KB4489892 (FYI).
Thanks again for your effort!
I’m curious why this works with Windows 7 Starter, Home Basic, Home Premium, Professional and Ultimate, but not Enterprise.
Not sure why the original author excluded Enterprise, must have been a valid reason for it though.
Thank a lot! Im patch successfully! Test 19.03.2019 on Windows 7 SP1
If you are having trouble with the patcher where it says it cannot access file termsrv.dll because it is being used by another process it may be because you have previously installed the RDP Wrapper. Once you Un-install this you will be able to use this patcher. I was finally able to update all the security patches and use this patcher. It works with the March 2019 security updates.
Thanks for confirming it works with the March updates. Yes, obviously if you have something like RDP Wrapper installed it will interfere with the operation of this tool.
Is there a solution for Windows 7 Enterprise?
I was using it just fine up until 1809 on windows 10, on both machines. :-\
Not this tool. It will open on Windows 10 but all the options will be unavailable.
Thank you so much for your ongoing maintenance of this patch. Concurrent_RDP_Patcher_2018.exe fixed rdp for me – it stopped working after I updated on 2018-12-29. System is Windows 7 Home.
In case it is helpful to anyone else, the updates installed were KB4483187, KB4471987, KB890830 and KB4471318.
Is there any way commands to set the options automatically on this installer? I cant push it automatically because of the two check mark options during install
No commands are available.
hi, your system works.thank you. I use thin clients with it but connects only two..how can i increase that number to accomodate more thin client machins.Im using windows7 profesional
You should probably warn people that if you use this to allow more than one user to connect to the system, at the same time, you are in violation of the Windows 7 EULA.
Useful to remind people of that fact, but I really don’t think anyone is interested in the EULA aspect. If everyone took the Windows EULA literally they’d barely be able to use their computer.
And besides, this tool originated from an official Microsoft based Forum, so they didn’t seem to mind at the time.
Just tried the patch with two Windows 10 Pro x64 1809 machines, doesn’t work :-(
I have two computers I remote into, can’t run more than one user on both.
It is a Windows 7 only tool and never has worked on Windows 10, 8 or 8.1.
I’m concerned the file may have been replaced by a virus. When I download it I get a warning:
Category: Trojan
Description: This program is dangerous and executes commands from an attacker.
Recommended action: Remove this software immediately.
Items:
file:C:\Users\tv\Downloads\Concurrent_RDP_Patcher_2019.exe
webfile:C:\Users\tv\Downloads\Concurrent_RDP_Patcher_2019.exe|https://raymond.cc/wp-content/sun/Concurrent_RDP_Patcher_2019.exe|chrome.exe
The trojan is identified as Win32/Spursint.F!cl.
That would also explain why its not working for some people in the last couple days.
Nope, just checked and the files are all clean and identical to the files I have here.
If you get this from Windows Defender then it’s just being overzealous with a false positive. Some security applications dislike tools like this because they patch system files and edit registry entries, which is similar to what malware might do.
For a bit more peace of mind, I’ve added the SHA1 checksums of the original files.
I tried the Feb 2019 patch on W7 Prof French version.
Not working.
When trying to remotly connect, the session start but then stop.
If a running session on console, this session is not impacted at all.
Any ideas ?
I still have problems with a KB4034664 version of Windows 7 Professional, I tried all 3 version but got always the same error of inknow checksum
Find out what the version number of the dll is. As far as I recall, there were no new dlls between October 2014 and October 2018, so you might have the 2014 dll.
This is a fantastic tool. I’m very glad to see it being kept up to date as I would have been in a pickle today without it. Works flawlessly here following KB4486565.
Thanks, the dll is the same as in KB4486563 so should naturally work, but it’s helpful to have it confirmed.
2019 Patcher confirmed working on Win7 x64 Ultimate KB4486563
Thanks for the report.
What am I doing wrong? I stopped Remote Desktop Services and still saying cannot access file termsrv.dll because it is being used by another process? Are there other processes that need to be stopped?
Thank you very much for updating the tool again! Worked flawlessly for me (KBKB4486563).
Thanks for the report, first feedback for the latest patcher and it’s positive. :)
I have not had to use the latest patch but the previous versions have worked fine.
Thanks so much for keeping this alive!!!
Yes! Thank you for keeping this up to date! It’s been a life saver.
Can I take from this both of you have used the new Feb ’19 patcher and it works OK?
FYI. Now they just changed it again with KB4486565
I’ve just checked the dll in KB4486565 and it’s identical to the previous dll in KB4486563, so won’t affect anything unless they change it between preview and release. The worst that will happen is you’ll need to re-run the tool to patch the dll again.
Hi HAL9000!
As discussed above, the Security Update KB4486563 for W7 Pro includes a new termsrv.dll Version 6.1.7601.24236, RDP is affected. Deinstallation of KB4486563 solved the to the state before.
Greetings!
Do you have patch for KB4480970 ??
because if we installed this KB, our concurent rdp will not working. as soon as i uninstalled that KB, its worked again. Please we need patch. or this is something not possible anymore? thanks.
No, we don’t have an update because everyone else says it’s patch KB4480955 (Jan Preview) that’s causing the problem.
If the information to update the patcher becomes available, we will update it.
oke i found out that if patch kb4480970 is installed, you can’t login with the windows 10 Microsoft store remote desktop app.
Only can login with the android Microsoft remote desktop app.
I deleted patch kb4480970 and now i can login again with the win 10 remote desktop app!
i don’t have the KB4480955 patch installed, i used the 2018 patcher, i have something strange.
I can login on my android phone with the microsoft RD app,
On my win 10 laptop i can’t login with the microsoft RD app, it says: perhaps is your password expired or the remote pc doesn’t accept blanco passwords.
It worked very good untill i guess a few weeks,
Hallo, Windows 7 x64 Home Premium (6.1.7601.24326) not working with ‘2018 test version’ anymore – “termsrv.dll has an inknown checksum”.
You’ve installed the January Preview patch, just uninstall it for now if you need the RDP functions.
When the patch is out of preview and goes live next month I’ll look at the possibility of an update.
We really appreciate your help HAL9000!
Have a great weekend! (I’m already thinking weekend, yes.) :-)
Have a good one everyone! And you are all welcome!
PS: Hal9000, any link with the info about what has to be changed and where? I understand is something that has to be done with en hex editor to the file, correct?
There is no specific page but several pages around the internet with plenty of old information about the bytes to change. It’s a case of waiting to see if a page gets updated with the new bytes to edit, thankfully a kind user listed the last edits here. :)
The tool is, in fact, a mixture of functions. There are hex edits to the dll, registry edits, permissions adjustments, and some other related small edits/fixes.
Ok, thanks you for the clarification. I assumed it was just a few bytes on the dll and though of not bothering you again.
Thanks for the info anyway.
Have a great weekend sir!
Thank you Zerox! I uninstalled KB4480955 and that solved the issue
Zerox you are correct so thank you for that. I just restored from my last system backup and applied all of the latest updates except for KB4480955 and the Concurrent_RDP_Patcher_2018.exe now works correctly. I notice that KB4480955 is optional anyway so I will leave it uninstalled for now.
I just found the update that did it (apparently):
KB4480955
File name File version File size Date Time Platform SP requirement Service branch
Termsrv.dll 6.1.7601.24326 1,283,072 2-Dec-18 15:43 IA-64 None Not applicable
support.microsoft.com/en-us/help/4480955/windows-7-update-kb4480955
For a list of the files that are provided in this update, download the file information for update 4480955.
download.microsoft.com/download/E/1/C/E1CCE995-79C5-49C5-A74F-D6B2EB690B93/4480955.csv
Did you figure out how to make the RDP Patcher work?
Confirming. I just uninstalled KB4480955 and declined future installation for now on this machine.
Now my W7Pro termsrv.dll is back to version 6.1.7601.24234 (from 10/18/2018) and 2018 Patcher shows file has been patched.
News:
Microsoft just do it again
KB4486563 updates termsrv.dll to version 6.1.7601.24326 and doing so disables this
Hello again!
Microsoft released a new termsrv.dll now 6.1.7601.24326 on 12/2/2018 for Windows 7 Pro.
Is there someone that know what is that has to changed in the file so we can do it manually and be done with it? Or if HAL9000 has the time to commit a new version that recognizes this new checksum.
Any ideas? Thanks in advance if someone can help!
Latest windows updates applied but Concurrent_RDP_Patcher_2018.exe says “termsrv.dll has an unknown checksum” HELP !!! PLEEEEASE
HAL9000! Thank you! Your new 2018 patcher works great on my 60+ Windows 7 Pro machines! What an enormous time saver since I can now connect remotely as the admin user and fix things without disturbing the local user! Do you have a tip jar? Thanks again!
Sorry but it doesn’t work on my Win 7 Home Pre, I tried everything but all I got was “temsvr.dll has an unknown checksum”
Are you trying the 2018 test version listed here in the comments?
Seems to work with Enterprise after I changed registry:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductName to Windows 7 Ultimate.
Thank you!!!
I have been trying to get RDP to work for weeks. I have Win 7 Home. I set a password on the target machine (my home laptop). I forwarded the correct router port and used the laptop’s ipv4 address. I downloaded Concurrent RDP Patcher 2018 and selected “Enable multiple logons per user,” then “Patch,” and it successfully patched, showing the message “termsrv.dll is patched.” I found my home computer’s public IP address at whatismyip.com and entered that IP address in Remote Desktop Connection in the “Computer” field on another computer. Every time I’ve tried, no matter what I’ve tried, I get the standard error message on RDC, which says, “Remote Desktop cannot connect to the remote computer for one of these reasons: // 1) Remote access to the server is not enabled // 2) The remote computer is turned off // 3) The remote computer is not available on the network. . . ” etc. What more do I have to do? Thank you.
Thank you. It works and really helped me in this critical testing time.
It needs updating again. I’m not sure what update did it but had to be a critical update in Sep, Oct, or Nov 2018 because those are the only updates I do.
Have you tried the link I posted below??
OK last patch I installed today after windows update it’s working! thankyou
I did a full update with the latest rollups and the 2018 patcher works. It seems even smart enough to restart RDP service because no reboot required!
I only need one extra session so don’t know if it is now capped at 4 as others have reported. However for me it is back to normal. I’m running Windows 7 x64.
Just did a bunch of win 7 updates and it killed my RDP. I re-ran the patch, and it *almost* works. I next tried teh new 2018 patch, but no difference.
I am able to connect to the machine. On the remote machine I see a blue desktop-type of screen with the win 7 logo at the bottom, and it says “please wait” with a spinning cursor. Then the window size gets smaller for a second, then disappears. Maybe this is a different problem from this patch.
Windows 7 Pro, 64bit. Patched in late October/2018. The ‘concurrent rdp patcher 2018’ recognizes the dll. I run it as admin and reboot. But when I go to run it again, it thinks the dll is unpatched. And now I am limited to 4 concurrent users. Previous versions of this patch on the same system allowed more than 4 users, now there is some limit which is imposed.
Any ideas of what to try?
Thanks
Sounds like something might be replacing the patched dll on reboot. When I do the same in Pro x64 and reboot, the tool still says the file is patched. The tool checks the MD5 checksum of the patched and unpatched dll. If it is telling you the dll is not patched after restarting, then the MD5 is the unpatched checksum and the file has reverted to the original. That could be caused by security settings or software.
Since recent Windows 7 Update, this version (Concurrent_RDP_Patcher_KB3003743_Fix) reports that termsrv.dll has an unknown checksum and will not patch.
Is there a newer version of the RDP Patcher? iIf so, where?
Thanks!
Yes, there is an update here:
https://raymond.cc/wp-content/sun/Concurrent_RDP_Patcher_2018.exe
I haven’t added it to the article yet because it’s just a test version which I’m looking for feedback on. Feedback so far mostly says the update is working successfully, so maybe it’s soon time to include it…
Thank you so much, It worked!
Thank you. That worked perfectly with the latest (as of 2018-11-10) update of termsrv.dll on MS Win 7 Pro SP-1 64-bit
the same happened to me ! i’m going to test this updated patch soon
Thanks. Keep it up. It is still useful
Thank you. It worked!!!
07/11/2018 update. Applied all updates and run as admin your Concurrent_RDP_Patcher_KB3003743_Fix.zip – rebooted my pc, and works fine. Win7 pro x64 bit..
Thanks!
I want to patch this file–Concurrent_RDP_Patcher_2018.exe
So when i run this program and press the patch button, a pop-up window saying
“This termsrv.dll is in use by another processor and can not be accessed by the process”.
What should I do?
Lifesaver, thanks again!
Concurrent Rdp Patcher Kb3003743 Fix refuses to patch my Windows 7 Home Premium in Portuguese (Pt) because it says that the checksum of termsrv.dll is unknown. This file was updated by Microsoft on 2018-08-13. File version: 1.6.7601.24234 (win7sp1_ldr.180813-0600)
I’m sorry, we are unable to test non-English versions.
Thank You! Thank You! Thank You!
I have been using “Concurrent RDP” patches with all Windows operating systems since it was first released for Windows XP. Ever since there has been Windows updates that fixes the patch, so the concurrent RDP stops working.
Once again I’m experiencing this issue. I’m running Win 7 Pro 64 and with some of the latest Windows update the RDP stopped working.
I tried everything, but this time I can not figure out, what is the matter.
RDP Service is working and it accepts connections. However, every time when I try to remotely connect this computer, the RDP client is able to establish the connection. However, it will disconnect immediately without any warning, or message etc. I can see quick flash of my desktop. When I logon this computer localy, I can see from taskmanager, that there is no other users logged on. So the logon fails. What can be the issue?
Are you using the recent update to the RDP tool?
I tried t0 use them all. This _2018 version claims the checksum of the termrv.dll is invalid. I tried to restore the original .dll from the installation media. However, the result is the same, Is there any place to download prepatched termsrv.dll?
The latest update to the tool will work with the Windows update mentioned, as you can see from others commenting it works on the latest dll as intended. If the checksum fails you have the wrong or an incompatible dll. The tool will now not recognize the original RTM dll because I replaced that patch with this one (by now nobody should be using it).
Which version and architecture of Windows are you using? Is it an original install media or some custom install?
Thank you for answer. I found this. Full path to Limit number of connection: Computer Configuration\Policies\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections.
If in default setting, GPO allows me to connect max 5 users, why i have this problem with 2 connected users ?
Thanks, the Concurrent_RDP_Patcher_2018.exe fixed it for me after the recent Windows update
Again: THANK YOU SO MUCH
IT worked like a charm for me
Thank you sooo much for the update!
Hi HAL9000. Any news on an update. I tried rolling back kb4462923 but this didn’t work for me. TIA
Ok, I have updated the tool for the latest termsrv.dll for both 32-bit and 64-bit versions. Please try this version of the patcher and report back as I have been unable to test it properly. Use this tool at your own risk…
https://raymond.cc/wp-content/sun/Concurrent_RDP_Patcher_2018.exe
HAL9000 thank you. Yes all worked like a charm. Love your work.
Worked on windows 7 x64 7601 with all patches installed on 16/10/2018
Thank you!
It works again :)
thanks a lot!
Hello HAL9000, i used a Concurrent_RDP_Patcher_2018.exe and i have a little problem. I have a 5 session to one PC with Windwos 7 Pro. Used an earlier rdp patcer ( 2017) and everything works fin. After this year updates in widows 7 i musz use a new rdp patcher. Multiple session is back, but on PC, whith i have connectet, at least, 5 session via rdp, i see tle last logget user desktop. For examle:
3 users : Admin, X1, X2.
Admin is localy logged on PC , and i see an Admin desktop. When X1 log via RDP to PC, on PC (i still logged on locally Admin) suddenly OS is swiching Account Admin to account of X1 user, and i see what he is opening, what he clicking etc. When X2 is logging (Admin still localy loged and X1 still logged) OS on PC switching X1 profile to X2 profile and again, i see what X2 is opening, what he clicking etc
On the site of clients, X1 is using X1 profile, X2 is using X2 profile. On the client site everything is ok, but on the “serwer” site is a problem…
Good morning, I’m Portuguese and although I do not understand your words well, I think your problem is solved by: menu starts, executes, writes gpedit.msc and presses ENTER, locates / searches for maxconcurrenteusers, by default this is not configured (only allows 5 users), then change the dot [.] to enabled and in the box below write the number you need. You may have to re-start your pc.
Excellent work sir! It is working on W7 Pro Build 7601.
Thank you so much!
Dude you freaking rock – thanks bunches!
Ditto, kb4462923 broke RDP, uninstalled it and now RDP works again. Win 7 home premium.
Dear Hal9000!
Please fix the patch we did not have unfortuna telly restore points and can not revert the changes. Now we are sitting duck and can not work. Please let us know it you are fixed it. Thank you sir.
Mine stopped working too. :(
Ran into the same problem and backing out kb4462923 worked for me. Hoping someone will come up with a revised patch for this so further updates can be allowed.
I have same issue today , I shocked after this update , because I cannot open more than 1 session at the same time and I rely on multi session for remote desktop , I’ll roll back windows update :(
I rolled back kb4462923 (2018-10 Security Monthly Rollup for Windows 7 x64) and it worked again.
Because there is an updated termsrv.dll in the monthly roll ups all further rollups need to stop until the patcher is updated.
I second, package kb4462923 was causing the issue on my Windows 7 x64, once rolled back the dll revert to the patched version
We just got the latest windows update that happened yesterday and the Concurrent RDP patcher is now working now.
Is this affecting anyone else or just me?
An update around Sept 2018 broke this again sadly, been an avid user. hope it gets patched again!
If that’s the case and I could find what needs to be patched, I would update the tool.
Yes, confirm. Today we lost it after windows update KB4458611, KB4457139, KB915597 if is of any help. I haven’t check each one but only one should be the infringer.
Thanks in advance for your help!
I just got it back to work after uninstalling kb4457139.
Thanks for your work on this sir!
support.microsoft.com/en-us/help/4457139/windows-7-update-kb4457139
Hey @zerox which version windows do you have?
My bad, sorry. This problem was on the only machine we use with this and is a W7Pro
Hello.
For me it was KB4462923 that causes the RDP problem. (on a Windows 7 Family Premium).
support.microsoft.com/fr-fr/help/4462923/windows-7-update-kb4462923
Any update on the patcher? I cant even find where to patch the dll in a hex editor.
No news, like you, I have no information about what needs to be patched in the latest dll.
I have 60 computers running Win7 in my facility and rely on concurrent sessions heavily. I have had to disable these three updates on all. I hope this helps:
kb2984972
kb3003743
kb4462923 – rolled this one back yesterday
Thanks, it’s not the files I need to know about, I need to know what bytes have to be patched in the termsrv.dll file.
Last time this happened in 2014 I was lucky enough to find out online what bytes needed to be patched, so could update the program. If similar information can’t be found for the latest dll, the tool can’t be updated.
Windows 7 x64
termsrv.dll v6.1.7601.24234
Find and Replace the Three Lines of Hex Below
————————————————————
Find the line:
8B 87 38 06 00 00 39 87 3C 06 00 00 0F 84 60 C4 00 00
Replace it with:
B8 00 01 00 00 90 89 87 38 06 00 00 90 90 90 90 90 90
Find the line:
48 8D 4C 24 60 BB 01 00 00 00 C7 44 24 60 1C 01
Replace it with:
48 8D 4C 24 60 BB 00 00 00 00 C7 44 24 60 1C 01
Find the line:
E8 B3 49 00 00 85 C0 78 1F 83 7C 24 50 00 74 18
Replace it with:
E8 B3 49 00 00 85 C0 78 1F 83 7C 24 50 00 EB 18
Thanks, may I ask where you got that information from? There appears to be only about 2 bytes difference from the old dll and I need to check this out before trying to update the patcher…
I tried the hex numbers SM Patcher posted (somehow couldn’t reply to his post) on termserv.dll with this version number and it seems to work fine.
Could log in with two users remotely and one user locally (being member of the Remote Desktop Users group). This didn’t work with before.
Thanks to SM Patcher for making my life easier!
Kaspersky endpoint security seems to block this. Any idea how to allow in the rules of the firewall for concurrent connections? It works fine without Kaspersky enabled. thanks!
It worked for me for years, using xfreerdp (package freerdp) from Linux to Windows Home.
But since yesterday when I ran Windows Update for the first time in 3 months, I get these errors:
[11:24:11:093] [2930:2931] [ERROR][com.freerdp.core.transport] – BIO_read returned an error: error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error
[11:24:11:093] [2930:2931] [ERROR][com.freerdp.core] – freerdp_set_last_error ERRCONNECT_CONNECT_TRANSPORT_FAILED [0x2000D]
[11:24:11:093] [2930:2931] [ERROR][com.freerdp.client.x11] – Freerdp connect error exit status 1
Anyone else seen anything like this?
It’s… so… beautiful…
Works like a DREAM on windows 7 ultimate x64
i have downloaded and used the patch, but how do i get the remote desktop to come up so i can connect to my remote pc?
you run the patch on the remote pc not on the one that you’re using.
it is working !!! great!
windows 7 pro x64
Thank you!!
i want windows 8.1 rdp patch
please help me
Doesn’t work with Windows 7 Ultimate SP1 x64 build 7601 PL.
Patcher says “Unknown cheksum.”
Of course, just because Windows Ultimate already has remote desktop support already enabled!!!!
Hi yesterday I have done fresh installation Windows 7 home premium SP1 and fully updated and the patch not is working for me. I tried patch-unpatch a lot of times but remote desktop open and looks is goingo to work but close ver fast without errors.
Anybody know ony workarround?
Regards
Latest version works great on updated Windows 7 Professional! Make sure you are using the version on the very bottom of the post!
Not working on latest updated version of Home Premium x64 – termsrv.dll has an unknown checksum
ok. in windows 7 ultimate 32 spanish
kb:3006625
v 6.1.7601 compi 7601
Thnks
It works for Window 7 Pro SP1. Thank you!
MAN! GOD BLESS. IT WORKED! ****** YOU GOT NO IDea how much stress I had. In the freaking middle of the night. Still 2hours to make this freaking server with 25 employees work. Stressed out. 2 hours left as they will start to work, since I’m on a different time zone. The entire company would be on production hold. I’m talking about manufacture in a huge scale. What could I do??! Found this site…….and it worked. POEF!!!!!!!!! Man If I ever knew who had this solution patch? I would personally send them a beer!!
Confirm that it works with W7 Home Premium 64bit
It’s a little weird to actually LOGIN to the computer, and not just ‘drive’ the computer remotely.
Worked fine on my Win 7 Home Premium 64bit SP1 which is running as a virtual PC on Win 10 Hyper-V. I used the later “fixed” version of the Patcher as my install already had KB3003743 update applied. Worked perfectly first time.
it is working in my pc windows 7 32bit
Thank you
Thank you.
Really works
I am running Windows 7 Home Premium. Using information posted with the original patch (Concurrent RDP Patcher_2-22-2011) I uninstalled Patch KB2984972 and then tried patching, but the patch said “unknown checksum”. I Then found this post and I see that I do have KB3003743 installed (termsrv.dll is version 18637). I ran this patch Concurrent_RDP_Patcher_KB3003743_Fix.zip. The Patcher says “termsrv.dll is patched”.
However System_Properties–Remote still only shows Allow Remote Assistance (and I can’t connect from another system).. I’ve rebooted multiple times and tried uppatch/repatch but no luck.
Any suggestions? Thanx
Home Premium is not capable of RDP out of the box – that is why it is not working. Look for another application called ‘RDPWrap’. That will finish it up for you.
It is working on Windows 7 Pro X86
Thank you
Windows 7 Home Premium.
Using; Concurrent_RDP_Patcher_KB3003743_Fix.zip
Says that termsrv.dll is patched but I still only see Allow Remote Assistance.
Am I missing something?
Try to unpach then pach again
this version is not working on my W7 home basic THANKS to the last update of microsoft -_-
There is new versions of the RPD-Patcher??
Pls it would be so helpfull
Doesn’t support Windows 7 Enterprise x64
Yes, as the article states, this is not for Enterprise.
Downloaded this today and can confirm that it is still working on windows 7 professional. Double click to run and enabled multiple logins per user, clicked patch and it kicked me off while it replaced the file. Waited 2 minutes then hopped back in and tested multiple concurrent sessions.
it just keeps re-asking me for the password as if I had typed in the wrong passwords. i am using parallels client standard rdp. any help with this? i get fail with my firewall on . so i turned it off and got 1 step closer. then it asks for the password and keeps saying its incorrect
As BrankoH said, any chance the desktops can mirror one another? I find it disconcerting that I’m remoted onto the W7HP machine and what I do from my Windows 10 RDP screen doesn’t reflect on the W7 screen itself. Shouldn’t everything reflect, just as if I were on with Teamviewer, etc.?
I can connect and fully remote in from my android tablet but only to the main user. I have a total of three users and when i try to remote into to ano other users it just keeps re-asking me for the password as if I had typed in the wrong passwords.
I’m starting to think that it only works with one users. I tried to make two users to be administrators with passwords and it still only allows remoting to the first user that was originally the administrator.
I have 64 bit windows 7 Premium and the android table uses the app called “Microsoft Remote Desktop”. It works super good but only for one user in the desktop.
thank you for any help !
hi can you tell me how the patching process work ?
Awesome solution…..after toiling the internet the whole day…….FINALLY !!!!
Thanks a lot for the patch _fix….it works perfectly
Thanks man, used this today!
Try RDPWrap
github.com/stascorp/rdpwrap
I got it working! Thanks! But can I make the screens mirror each other?
Thank you alote it worked on Windows 7 Ultimate
Says that Windows 7 Enterprise is not supported. The patcher program is showing everything grayed out. I ran it on a different Windows 7 Professional machine and it worked fine.
That’s right Pro is supported, Enterprise is not supported.
Will this work on Windows 7 Pro and Windows 10 Pro versions? What would happen if Microsoft decides to patch the file again. Will it cause system instability? Should we backup the original termsrv file first before installing? Where is the file located?
Windows 7 Pro: Yes
Windows 10 Pro: No
If Microsoft patches termsrv.dll again it will simply overwrite the patched dll and will work like it did before patching. If that happens we would need to update the tool again to patch the newer dll.
Thanks HAL9000. If it does happen, is there place where we can download the newer patcher or do we just go back to this site?
Here is the only place you will get an updated patcher if one is required…
Hi all,
I’m still looking for a resolution for this. I’ve been looking for the past 2 days and still having no joy.
I’m trying to connect to a Windows 7 Home Premium from a Mac.
Is there still not way to accomplish this without using a third party application?
Would I need to upgrade to a newer version of windows? I like Windows 7 though.
Forgot to mention, I’m trying to connect over the internet, outside the network. I’ve setup port forwarding on the router. I cannot see remote desktop options in system preferences.
Thanks, J
I downloaded and it ran it and all I got was an IMMEDIATE show-stopping error. “termsrv.dll has an unknown checksum”.
Can you see what you think? i have windows 7 home premium.
That’s simply because you don’t have the correct termsrv.dll that the program is looking for.
Download the updated version and make sure you have update patch KB3003743 installed.
hi its wrks thanks for the information
Works! Thank you!
Hello there, thanks for the article, but i have a question, does this patch enables multimonitor on host? I ask that because my host has win7 pro, and by default that OS version does not support multimonitor.
installing this patch does not work, even the patched version. I still do not see Remote Desktop options, only Remote Assistance. I’ve Googled this to see if anyone else has the same issue and can’t find anything. What gives?
Maybe your system’s version doesnt support RDP; ie Win7 home edition…
I installed the patch on both my computer and the one I want to remote into. Both are running Win 7 Home Premium. When I attempt to connect, it pops up the user and password input. For some reason, it keeps telling me that it’s the wrong password. I know it is the correct username and password. Any thoughts?
You need to make sure the local user account (for the machine you want to connect to) is a member of the remote users group. Go to Start, type “mmc.” This is the microsoft management console. Click on file > Add snap-in, and double click on Local Users and Groups. Click on Users, then find your account. The login name should be the first thing listed on the left. Then, go back, go to groups, and go to Remote Users group. Add your login account there if it is not already present.
Unfortunately, that snap-in is not allowed on a computer running home premium. Any other thoughts?
After trying literally everything, I found a solution. There was a discrepancy between the login name and the account name on the profile in Win7HP. Normally, the login name is used for everything. Under the hood, the default account name was “Dell” and not the login name. Once corrected, I logged in without any issue. Hope this helps!
Im thinking KB 2952664 or KB 3021917
A recent Windows update seems to have broken rdp. (April 12,2016). Anyone else have this problem and knows which one?
What happens when you run the RDP patcher?
I’ve just checked after installing the latest updates and my Termsrv.dll is still from 2014, version 18637.
Get the message ‘Termsrv.dll has an unknown checksum and all the options are greyed out.
..
Found the problem. KB 3003743 got installed again somehow.
..
Well, uninstalling the KB 3003743 didn’t solve the problem. When I run RDP it still says unknown checksum with all the options greyed out. ????
Have a look at the Termsrv.dll itself in System32 and see what version number it has
Created Apr.13/16 v. 18540
The RDP Patcher patches Termsrv.dll version 18637 so you will need to reinstall KB3003743.
Thanks very much. Reinstalled 3003743 and ran the patch – worked just fine. Thanks again for your help!
Everything is cool, thank you!
One more thing you need to do if you use Windows Firewall on your windows 7 home edition machine. You need to create a new inbound rule to allow port 3389. Otherwise you’ll have to turn off the firewall every time you want to connect.
100 % Working Thx
I want to remote desktop over the internet but it wont work. I checked to see if the port was open at canyouseeme.org and it was. do you know why I cant access my computer over the internet. it works fine on the local network tho.
thanks
Thank you for this. Works like a charm on my windows 7 home premium.
I have a quick question. How can I login to a same RDP session if I left it with unfinished work. For example if I login with user X and worked on a word document. Can u close the RDP session without logging out and then log back into the same session so I can continue my work?
Also on the desktop where I installed the patch, if I have my main user logged in with multiple programs running with my current work opened. If I want to remote into that users desktop and preserve the work so I can continue remotely, what’s the best way to do that?
Right now when I log in with the same user, it creates a new session and hence does not take me to the current working window.
Thank you again for this tool.
I have the same problem as listed a little below: connection dialog comes up, but after entering the login/pw it just dies. No messages.Nothing in event logs either. It does validate the login, because when I enter an invalid login, it does come back with ‘invalid credentials’
Win7 Home Premium, patched to the latest updates.
Any ideas? Or any logs I can check?
I can’t able to access on my PC its Windows 7 Home Basic. Its said it is unsupported
Windows 7 Home Basic is supported, are you using any special version other than standard?
Fantastic work! Thanks.
Worked a treat! Thanks guys.
(In detail: I can get into my Win7 Home system containing KB3003743, using xfreerdp from a Linux system)
Tried the patched version with Windows 7 Starter that has KB3003743 installed. OS Info window says “Microsoft Windows 7 Starter – Unsupported termsrv.dll is unpatched” Thought I might be able to get remote desktop working with Win 7 Starter. Any ideas?
The patcher does not work with the Starter Edition because it has some networking and RDP restrictions.
Hi, it is possible to run this patcher with parameters? I want to install this patch “quiet” on more computers…
No, command line parameters are not possible.
I just found a great RDP patch that works with any version of windows.
github.com/binarymaster/rdpwrap/
Tom,
the RDP wrapper is only to increase the number of valid remote sessions;
i tried this tool (everything is green), but it doesnt work – i still cant have a remot desktop with Windows 10 Home Premium…
Which version of windows do you have?
Please let me know when a Windows 10 Home patch is available.
Keep up the good work.
works on win 7 home premium 64 bit. Remote desktop does not show on controlled computer [win 7 home prem ] but allows login using mstsc
Upgraded to windows 10 home and the patch stopped working.. Any fix for this please ?
The patcher is for Windows 7 only, has never worked on Windows 8/8.1 and won’t work for 10.
Wrong
It does works in windows 8 and 8.1
Therfore I also think that windows 10 will be the same thing.
The reason that tblog has a problem is because he upgraded to “home” version, which actually doesn’t have RDP anymore… you need at least “pro” version
Are we talking about the same thing? Concurrent RDP Patcher does not work on Windows 8/8.1 or 10 because it checks to see what version of Windows 7 you have before starting and won’t work without a compatible version, the termsrv.dll is also different in those operating systems and won’t be patched.
Really, Sebastien?
Perhaps you are unaware, but the entire reason that the Concurrent patch exists is to enable RDP hosting in a Home edition of Windows. If tblog had Pro, he wouldn’t need the patch because it would already work “out of the box”
I hope they update this for Windows 10 Home.
My computer is telling me that I will get the free upgrade to Windows 10. However, this will be Windows 10 Home, which is not likely to include Remote Desktop. Does anyone know a way of making this work?
please help me., i was able to install and make the RDP run ( after the so called checksum error) – termsvr.dll now patched. but when i tried to access remotely, it quickly terminates after the logon. (after entering the user credential). I turned off the firewall already, and uninstall antivirus too..
Worked perfectly first go. Thank you.
Thanks for this you are a star – it worked like a charm on Windows 7 Professional!
Worked like a charm. Easy fix. Thanks for taking the time to fix this patch. Awesome!
Thanks for taking your time to update this tool.
After installing your updated version on my RDP host, I can get to the screen where I enter the user name and password from my RDP client but nothing happens after that.
I’m wondering if this might have to do with using Windows 7 Home Premium ‘K’ version (K for Korean).
It would help tremendously to get this to work so I can do part of my work at home.
If the patching process just involves changing some of the codes in Termsvc can you please show which codes I need to replace?
Unfortunately we are unable to test the patcher or make edits for any language version other than English.
Thanks, works like a charm on Windows 7 Professional
First of all, I’d appreciate your patch.
But, unfortunately, after windows updates(Windows 7 Home Premium), I’ve failed to connect…
(Of course, before windows updated, I can login using RDP without any problem. After windows update,
And also, I repatched it with KB3003743.)
As colin said, I also have same symptom,
it accept username and password, but then it never show any messages, no response… just as like blocked by something. Could you please let me know what is problem? Thank you in advance.
Here the same issue. With the latest Windows update the patch doesn’ t work anymore. You can add the username and password, but nothings happening. Beside, the RDP option isn’t available anymore, only the remote support option. Keep up the good work!!
Thank you for keeping this up to date. Some of the other versions of this have since stopped working, but after pulling the troublesome updates, your updated version does the job.
I am having a problem with changing the ports, though. I’ve changed the port in the Registry, changed the forwarded port, and entered the connection in the [IP Address]:[Port] method, as well as restarting the services (and even the PCs themselves). For whatever reason, I can’t connect even with all the proper port changes. This used to be possible with the now defunct MissingRemote version, but it doesn’t seem to take on this version.
If you have any thoughts on the matter, it’d be much appreciated. Thanks again for keeping this up!
Well, I hate to reply to myself so foolishly, but the problem was so simple I’m ashamed of myself… Firewall ports had to be updated.
Sorry for pestering you.
That’s what makes computers so much fun… :)
Quick Heal tests this positive for CryptoLocker… YIKES. I’m too careful to think about installing this if it might have something like that in it.
Quick Heal is obviously talking rubbish, i.e. a false positive. I compiled the Concurrent RDP patcher myself and it’s not malicious in any way. It’s flagged as malicious by some antivirus because it patches a system file (termsrv.dll)
The result at Virustotal for the last released test version:
virustotal.com/en/file/629af3522e7c32f63c304ad743f3f617d24b6a11c4786d102183703d41ad199f/analysis/
You’ll note both detections there have “gen” or “generic” in the result, that means they are making a guess at detecting it’s malicious, and getting it wrong.
You are of course free to not use the program if you are in any way unsure about its safety.
Hi. Tested with windows 7 family premium and both version of the patch. I don’t have access to RD options in system properties/remote even after patching.
I may be doing something wrong, but it seems that it does not work.
Hi, No go with Win 7 Home Premium SP1 32 bit with the KB3003743 version. The original version worked perfectly…
Now it accepts the username, asks for password, but the remote desktop never loads. It just terminates with no message.
Thanks a lot. Works great! Save my day!
Worked like a charm.
BTW:
I did it remotely. Via RDP, of course. :-) I was disconnected for obvious reasons, so I reconnected. No problems. I’ve noticed however, that termsrv.dll modification date was changed to 2015-04-04 03:35.
CRP was waiting on the screen, so encouraged, I tried to unpatch. This time I couldn’t reconnect. After an inspection on place I’ve found, that remote access via RDP was disabled while unpatching and modification date was not restored. But that’s another story. :-)
It actually is ‘Windows 7 Professional N’. So the same way:
“Ultimate” -> “Ultimate N”
“Enterprise” -> “Enterprise N”
“HomePremium” -> “HomePremium N”
Thanks for the confirmation, I’ve updated the tool, try it out using this link:
files.raymond.cc/Concurrent RDP Patcher_test.zip
Your files are not accessable anymore. Can you please redistribute them?
All the files are currently available, perhaps try again…
Thanks. Actually the patcher could accept blindly all N variants:
windows.microsoft.com/en-us/windows7/products/what-is-windows-7-n-edition
Let me know if you need a tester or some data from Windows 7 Professional N registry.
That’s right, the patcher simply doesn’t try to detect N variants, but it should be easy to do, all I need is the text from this registry location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductName
I’m guessing it will be ‘Windows 7 Professional N’ but need to make sure…
Would you please recompile the patcher to accept Windows 7 Professional N that is stripped down (no Media Player, Windows Meaaadia Center and Windows DVD Maker) version on Windows 7 Professional? Thanks.
i don’t have any N versions to hand at the moment, but I’ll look into it…
Thanks for writing this up, it’s working for me in Windows 7 Home Premium SP1.
I have a question though about the resolution of the remote desktop, when I connect remotely the resolution of the Remote Desktop window is only 1024×768.How can I increase that? In the remote desktop session, in Control Panel > Display > Screen Resolution, the Display is shown as: 1. (Default Monitor) on RDPDD Chained DD. Resolution: 1024 x 768. Both are greyed out and not changeable. At the top of that window is a yellow box with the message: The display setting can’t be changed from a remote session.
The system I’m accessing actually has a 1280×1024 LCD attached, so it appears that 1024 x 768 is hard coded somewhere as the resolution to use for remote sessions? Does anyone know how I can increase that resolution? BTW, I’m using CoRD on OSX as the RD client.
I was excluded by the patch using a windows 7 enterprise and found a more universal solution
github.com/binarymaster/rdpwrap/releases
hi there,
AVG says the files have trojan and removes to vault, is it intentional?
It’s a false positive, most likely because the program patches a system file (termsrv.dll).
Great new version.
Concurrent RDP Patcher is working again (Win7 Home Premium SP1 64bit)!!
Thank you!
Thank you very much, Your patch worked.
I Have a laptop with fully patched Genuine Win7 Home premium 64bit SP1 with the KB3003743 installed. Your modified patch worked.
thanks a lot it help in widows 7 ultimate service pack1 (updaed)
Have run patch on my genuine Win7 Home Premium x64 SP1 without problems. It now says patched. However, any RDP connection (local or remote) starts, asks for username+password, then brings up the remote desktop for ~2 seconds and then TERMINATES immediately (closes remote desktop window). Only help seems to be to uninstall KB3003743 update. Is it possible the patch only works on cracked Win7 and fails on genuine ones? I have tried also the “RDP Wrapper”, same results – works only with KB… update uninstalled.
Thanks for any ideas.
It took me 2 hours, before I realize, that my issue is WIN7 Home Pro edition.
Thanks heaps for your help!
Chears
Michal.
WINDOWS 7 Home Premium 64 – bit. Tried installing 3003743 and was able to click patch. Went back to system to enable remote desktop and the option to enable still didn’t come up. I just opened the extracted files from my downloads folder. I’m trying to connect using the ipad app Microsoft Remote Desktop. I didn’t see any directions to do anything differently but just double checking. Thanks!
I downloaded your test file. When i Run it as administrator. It says termsrv.dll has an unknown checksum. and it don’t give me the option to check any boxes. what does this mean?
It means either you don’t have patch 3003743 installed, the termsrv.dll has been modified from it’s default in some way, or you are trying to run it on an unsupported OS, like Win 7 Enterprise.
Is there any command line options so that patcher may be used from command line in “silent” mode, so tp patch system in case it may do it?
Not that I know of.
Is there any source code available? It should be easy to add command line options.
The original source code is available online, you can get it here:
mediafire.com/download/qis33sfqq1l33p8/Concurrent_RDP_patcher_source_07-18-2010.zip
Update: Despite the error message about the process being in use by another user, the patch seems to have worked. I’ve been able to connect concurrent sessions. I used “run as administrator” by the way, when running the patch.
Great work!
Thanks for your work on this. I’m having a pretty basic problem. When I run the patcher, it verifies the termsrv.dll is unpatched. When I tell it to Patch, it gives me an error that the file is being used by another process. What’s the proper way around it?
I’m running Win 7.1 Pro x64, if that matters. Thank you!
Hi there,
thanks for your efforts.
The think is I ran all your patches I found on your page. But none of them seems to work:
Windows 7 Home Premium SP1
OS info: termsrv.dll has an unknown checksum
all checkboxes and buttons are inactive
…
Any ideas what I could do?
Thank you very much!
If you have tried the test file (files.raymond.cc/Concurrent RDP Patcher_test.zip) and you are having the problem, either you don’t have patch 3003743 installed or something else has altered the termsrv.dll file. The patcher needs a completely unmodified dll to work.
Ok, and if it’s the case?
Uninstall patch 3003743 from Windows update. The RDP tool will definitely recognise a non modified termsrv.dll and patch it.
What is the maximum number of concurrent connections? Has anyone tried 8 or more concurrent connections? Thank you.
Hi,
First of all thank you for your effort!
I’m having some troubles whit the patch. version KB3003743 of the fix does not allow me to patch the dll file but the KB2984972 version does it. The problem is ,in spite of patching correctly the library, remote desktop option does not appears on the menu. I’ve tried rebooting but still missing.
Now I’m using W7 home premium. Let’s hope you can help me to make the patch work!
Thank you in advance.
The latest version we released for test was this one:
files.raymond.cc/Concurrent RDP Patcher_test.zip
It includes a few fixes for 32-bit.
You are a life savior.. updating the patcher is very much appreciated. Thank you.
AWESOME JOB AND KEEP UP THE GOOD WORK.
IT TOOK ME A WHILE TO FIND THIS SITE BACK AND IM GLAD I DID.
CHEERS MATE.
:p
Works great in Windows 7 Professional 64 bits updated in 28/01/2015.
Thanks a LOT for your work on the RDP Patcher, it works fine with all windows updates atm 19.01.2015 Windows 7 Home Premium :)
win7 home premium 64bit with all updates this patcher works fine and enable rdp to this device.
thanks a lot
Im new to this still learning. I did the patch it works but I cant log in can u help give me step by step on how to be able to access my computer
thank you ..it work fine
Works great in Windows 7 Home Premium 64 bits updated in 14/01/2015.
kiss my ass guys!
Hi,
I had downloaded the pacth in november and Remote Desktop connections were working fine.
This year they are not working, and I tried the above link. which is:
https://www.raymond.cc/blog/download/did/3119/
It still did not work!
What is the solution? is there a newer patch?
Thank you!
There are two versions of our modified patcher, the version in the post for the latest patch and the version you link to is for the previous patch. You need to check which patches you have installed to work out which program you need to run.
Try RDP Wrapper instead of Patcher. It does not get borken by the Windows updates.
github.com/binarymaster/rdpwrap/
First of all, Thanks for your help.
I download this patcher and run this file.
but OS info show termsrv.dll has an unknown checksum.
How i fix it?
It depends which recent patch you have installed from Microsoft. If you have hotfix KB3003743 installed use the one in the post, for KB2984972 use this one: https://www.raymond.cc/blog/download/did/3119/
Remember it only works on Win 7 non Enterprise and the termsrv.dll has to be untouched.
Hi, same problem. The latest KB3003743_Fix.zip shows termsrv.ddl is pathed, but I cannot connect. It has been working until November 2015.
Which version of Windows are you using? I’ve found some more code that might help fix problems on 32-bit but 64-bit is the latest patch code I can find.
I have got Windows home premium 32 bit, and the patch KB3003743_Fix.zip shows termsrv.ddl is pathed, but I cannot connect. Any idea what can help?
Many thanks in advance.
Ok, as I said earlier I’ve found some updated code for 32 bit so I will add that in the next few hours for you and others to try out.
Try this one and report back:
files.raymond.cc/Concurrent RDP Patcher_test.zip
Thank you for this. BIG help.
Running well on W7 Home Premium x64 with all of Winblows latest updates for about a week now. Only issue we found is that the clipboard doesn’t share across machines (as it does with native RDP sessions) despite how the RDP options panel is configured for the RDP_Patcher session.
Any ideas appreciated.
Thanks again.
Good catch … definitely could use a solution for that.
Hi Dude,
you saved my life, thank you! I have a partner who has a Home Premium in her pc and some days the remote desktop did not work … the last update could help, remote desktop is working fine again, thank you very much!
Great work, thanks a bunch!
Last Patch Tuesday’s update killed it though. Not sure which update it was, but I got it working again with the patches below. Maybe you can include them in the next version?
Original termsrv.dll MD5: 008CD4EBFABCF78D0F19B3778492648C
Patched termsrv.dll MD5: D3BABE04C2789C4C8D058B316C05E5A3
File offset 000173C0:
Change 8B 87 38 06 00 00 39 87 3C 06 00 00 0F 84 EB C2 00 00
to B8 00 01 00 00 90 89 87 38 06 00 00 90 90 90 90 90 90
Offset 000176FA:
Change 01 to 00
Offset 0005AD7E:
Change 74 to EB
(Same patches as in previous version, just different offsets.)
It was done a week ago, I’ve added it to the article so everyone can see it better.
Unpatched termsrv from before, installed KB3003743, used the new fixed patcher, patched and it doesn’t work. (i.e. it’s that same issue with connecting->configuring->etc and it looks like it connects, but then you get no window with the actual RDP session).
W7 SP1 x86 all patches installed.
Yes, it works perfectly on 2 different W7 Home installations. MANY Thanks for this great job!
Thank you again — Working Win7 Pro 64 VM.
Updated the link as a few people were having trouble downloading.
There does not seem to be a download available at that link-
Yes there is, try again…
got it now.
Yes, the same for me. W7 Home could be patched on 2 PC’s.
But since last MS-update not working again.
I removed the installation of update KB3003743 on one machine, and on the other I excluded it form the update process (see the update details and uncheck the box) and in both cases, worked perfectly afterwards.
A new patch came out today 11/12 for Windows 7 that broke the new Concurrent TDP patch again. termsrv.dll has an unknown checksum again.
Worked great for years. Today’s (11-11-14) windows 7 update killed it. Anyone know what to do to fix it?
They’ve updated it yet again?? Unbelievable!
Seems to be KB3003743 “Vulnerability in Remote Desktop Protocol Could Allow Security Feature Bypass” causing the trouble, the 2nd time in about 3 months they’ve updated this…
Yes in deed. Your update worked for a few weeks perfectly on 2 W7 Home systems.
But now again destroyed.
Hopefully you can again fix the problem, good luck and MANY thanks!!!
Stefan
After the 11-14 update uninstall update KB2984972. Personally I am not to concerned about security implications as my machines are on a secure internal network. One will need to hide the update in the Windows Update app otherwise it will be reinstalled.
Obviously a proper solution would be an update to the wonderful Concurrent RDP Patcher tool … Thank you too Raymondcc for providing the tool.
The “update” dind’t work for me correctly… i can’t see the Chrome Browser Window – an if i used rdp and Close the Connection, the pc still said, that someone uses the Computer… it seems to me, that it didn’t log out correct. :(
Hey, same error here!!!
Because the original Concurrent RDP Patcher was made open source by its author, we’ve updated the source code to patch the latest KB2984972 version of the termsrv.dll, you can try it out here:
https://www.raymond.cc/blog/download/did/3119/
Do note that this update should work but must be treated as a test version until it’s confirmed working by more users. Try it at your own risk…
thank you for the updated version! working on my updated Win7 pro VM.
Thanks for the report, hopefully we’ll get some more positive responses so it can be included in the article as a proper updated version to the original patcher.
This new patcher does not work for me on Windows 7 Enterprise SP1 x64. It appears Enterprise in unsupported.
The original patcher doesn’t support Enterprise either, it never has.
It works for me on a Win7 Pro 64 .
Thanks a lot !
Works for me, too. on Win7 Pro 64! THX
Works perfectly on both the Win & Home Premium machines that i needed this facility on…. MS REALLY needed to make the lack of this facility a little more obvious. It was assumed on the original purchase of the O/S that it would be there!!
This works for me!
Thanks very much for fixed version :):):)
anyupdate for this planned? not working after recent updates (Win7 pro 64bit)
It appears that M$ has been at it again and KB2973501 updates termsrv.dll to version 6.2.9200.17048.
Uninstalling that update got Multi-User UDP working again for me.
Is there an update to the RDP Patcher to resolve this?
The RDP Patcher was never designed to work with Windows 8/8.1/2012, which is what update KB2973501 is made for.
Hi.. great tool but with todays update NOT WORKING ANYMORE. WIN 7 HOME PREMIUM Your Application says “checksum error”
So….has the patcher software been updated to cope with update KB2984972 ? I found a different solution on another forum, but it does not preserve the CONCURRENT capability. Any chance that someone can modify the 2/22/2011 version of this software to cope with current issues? Thanks!
This has been reliable for several years but just stopped working on a windows home premium machine. Anyone else having the same issue (perhaps the last windows update)? The connection neither connects nor errors out, appears to connect then nothing..
Oh forgot to add when Concurrent RDP Patcher is run, it is grayed out and a check-sum error is present at top OS Info box.
Yes, the latest Windows Update ruined the RDP Patch. There is a patched dll floating around for it, but I don’t know if it is safe or not. I have not had a chance to install it and test it. Here is a thread about it: forums.mydigitallife.info/threads/57448-KB2984972-breaks-concurrent-RDP-patch
You’ll have to copy and paste that link because I’m not sure what the rules are for pasting links here.
The latest updates for Windows 7 seem to have replaced termsrv.dll. Can someone update the patcher as well?
Looks like it might be this one: KB2984972 released on 2014-10-14…
support2.microsoft.com/kb/2984972
Uninstalling KB2984972 is a temporary solution.
I’m hoping there is a solution soon, so I don’t have to keep KB2984972 patch from installing. It certainly is the cause of the failure of the terminal server patch, but I would like a longer term solution.
Thanks alot
It works.
I have this problem that the remote will not start a program when connected. I must be doing something wrong can you help please.
Frank
Did you ever know that you’re my hero? and everything I would like to be?
I can fly higher than an eagle,
’cause you are the wind beneath my wings.
It might have appeared to go unnoticed,
but I’ve got it all here in my heart.
I want you to know I know the truth, of course I know it.
I would be nothing without you.
THANK YOU FOR THIS
Remote Desktop could be enabled on Home Premium using Concurrent RDP Patcher, but with two limitations:
1. You can not pass the clipboard contents between computers;
2. You can not work remotely as an ordinary user. You have to be an administrator. There is no interface to assign Remote Desktop access rights to users, and administrators have this access by default.
THANK YOU SO MUCH!
Never been a big fan of using VPN software, and Don’t want to muck around with upgrading the OS on an OEM laptop. There always seems to be some problem with some software when you go this route. I can not thank you enough for the folks that made this tool. THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU!
RDP may not be the end all of how to remote in, but it is the best way to do it sometimes. And for me, I just don’t want to get up and mess with the laptop that is right next to me.
Thanks to this software, I can put on movies for my kid, or Music for him to go to bed to all from the comfort of my chair.
This just made windows 7 just that much better. As a user of 8, I have to say, there are just some things that Windows 8 just can’t do. Well, at least not without tons of help.
Again, You really just made my day. And my sons too!
Thank you. no where did a message say my version wasnt capable. that makes me mad. but this works awesome.
Excelente, me funciono perfecto, desde mi cel pude conectarme a la compu y ver mi escritorio perfectamente a buena velocidad y todo, el programa me abrio la posibilidad del Remote Desktop, lo recomiendo 100%
Hi Raymond,
I met a problem of “asking of credential” input windows.
client: windows 7 prof
host: windows 7 home premium
Connection: LAN
I have ran the patcher in the host computer, then, it installed successfully. Then, I ran the Remote Desktop Connection in client computer, input the ip addresses, click connect, but a “windows security” dialogue prompted out asking for password.
So, there is no password set on the host computer.
May I know how to disable the feature of asking credential from the client computer in order to connect the host computer?
Thank you.
Tiang,
RDP wont work without passwords on the login account!
Downloaded and ran patch.
Checked box for multiple logons and blank passwords.
Ran patch. Window says “- x64 termsrv.dll is patched”.
W7 remote settings page does not show “Remote Desktop” in bottom of page.
I am currently running W7 SP1.
Hi I am using this patch on my win7 premium machine which is running my mailserver. For two / three weeks worked perfectly but has now taken to bombing out. The symptom is that the client cannot pick up mail “Outlook cannot connect to….” and at the same time RDP stops working. I am running MDaemon. If I go to the machine it all looks normal no sign of a crash. The mailserver is still running etc. The temporary solution is to start a configuration session for MDaemon – that unlocks everything. But it isn’t elegant. Maybe I ought to buy VNC but before I do has anyone had this experience? Thanks
Hi, I’ve come across this post & tried the above & it partially works! Hoping someone could please shed some light into why it won’t work completely. Much appreciated in advance.
Firstly, I’m using the RD Client on my iPad 2. The computer I’m remotely controlling runs 7 Home Prem & has wireless internet connection. When I access thru my iPad 2 on the same wireless connection (at home in another room) it works perfectly – I’m able to remotely access the computer, however, when I’m on another wireless connection (away from home) than I can’t login at all.
Hope that makes sense as I can’t see why it doesn’t work!
Wifi networks that are behind a router that is connected to the internet have their own network. This is what is know as a lan. Addresses which start with 192.168.x.x or 10.0.x.x are lan IP addresses and can not be accessed by the wan or internet without the router being told to do so. Do a search for “remote desktop behind a router how to” this will help you make a global address to connect to that will work in remote locations
Hi
Malware Bytes just picked this up as a trojan.agent.. Is this a false positive or have I exposed my machine..
Cheers
Don’t worry it’s a false positive, this is because the program patches a system file and some security software flags it as malicious.
If you go to the Green Button community above which is an official Microsoft site, you’ll get the same result….
This worked GREAT for me! I was NOT looking forward to putting any more money into M$ pockets to upgrade Windows 7 to Pro, just to enable this one feature. Learning Linux so one day can get away from M$ completely.. in the meantime though this really helped.
THANKS!
This does work.
I got this to work well with multi user . How can I enable this and shre the same screen..for example lets say we want to work on the same application while on a conference call
Thansk a lot. This worked perfectly
This is good only in static ip address not in dhcp like in my country almost ISP here provides dhcp services and it was very difficult to open their ports to access other computers over internet… so I used teamviewer for remote desktop support… this is awesome software i like it very much…. it works even the port of your router is closed…..
Anonymous. If you utilise a Dynamic DNS agent, like noip.com, then you can connect to remote desktop, even if your internet connection has a dynamic IP. Don’t forget to set up obscurity on your router by utilising an alternative port to the default 3389 for RDP.
I have been using the concurrent patch for some time now in my HTPC. That way people can be watching a movie while I can do my own stuff remotely. Really Windows 7 should allow multiple sessions by default.
Also Raymond, if you can investigate what is the GREAT TECH BARRIER that doesn’t allow Windows to output same sound via HDMI and sound card at the same time… Thanks
now i can try remote desktop my home system from same network with current user logged in.
Thank You
Wow cool as usual from you ;). Thank you :D. O before use think ethically :P.
Many thank you,
it works for me.
You save me and my time.
Thanx for the info