Concurrent RDP Patcher
To apply patch, simply download and unzip the file, then run the corresponding file as administrator (right-click the exe file and select Run as Administrator). For 32-bit systems use UniversalTermsrvPatch-x86.exe and for 64-bit versions of Windows use UniversalTermsrvPatch-x64.exe.
- Here you can download file ConcurrentRDPPatcher. 2shared gives you an excellent opportunity to store your files here and share them with others. Join our community just now to flow with the file ConcurrentRDPPatcher and make our shared file collection even more complete and exciting.
- The goal of this project is to enable Remote Desktop Host support and concurrent RDP sessions on reduced functionality systems for home usage. RDP Wrapper works as a layer between Service Control Manager and Terminal Services, so the original termsrv.dll file remains untouched. Also this method is very strong against Windows Update.
- RDP Patch Utility for Windows 10 1803 Print Modified on: Wed, 27 Jun, 2018 at 2:34 PM NOTE: As of 6/27/2018 Microsoft has released a patched 1803 Remote Desktop client to resolve several outstanding bugs, including the 'popup windows hidden' and 'right-click menus hidden' bugs.
Enables Multi Remote Desktops in Windows Vista Win7 and Win 8
Step 1:
Go to Control Panel ►System ► Advanced System Settings ► click on the Remote tab.
Concurrent Rdp Patcher Windows 7
or Pressing the WIN Key+ Pause/Break keys simultaneously brings up the System window.
Select Users (other than Administrators), you want to give access to Multi Remote Desktop Connection
Step 2:
This tool enables the Remote Desktop Connection for Windows 7. This patcher also allows you to revert the changes back to the way it was by clicking the Unpatch button.
The password to extract the archive is: raymondcc
Note that this version of Concurrent RDP Patcher patches the DLL on Windows 7 RTM, Service Pack 1 and update KB3003743 which was released in October 2014.
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.
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.
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 patched 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.
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.
Rdp Update Windows 10
The password to extract the archive is: raymondcc
For Windows 8
Windows 8 and 8.1 users please download the patched termsrv.dll file from here and edit the following registry keys at HKLMSystemCurrentControlSetControlTerminal Server.
Replace this file in C:WindowsSystem32
You are checking the helpdesk and a new problem rolls in. You know the solution but you (the administrator) will need to login. You immediately remote into the machine only to see that the user is showing a presentation or actively using it.
Do you:
A) Call the user and have them log off so that you can start fixing the problem. The problem will get fixed but the user is interrupted for 20 minutes.
B) Wait until later in the day and hope the user isn’t using their computer. The problem will get fixed at the end of the day but the user had to deal with it all day.
C) Use RDP and log into the computer. The user is able to continue the presentation. You are able to fix the problem in the background. Everybody is happy!
The answer is C!
“That’s wrong!”, you say! “Client OSs can’t have concurrent RDP sessions. When you try, you get an ugly message and the current logged in user is logged out!”
If Server can, the client can! All we have to do is trick it! How? Let’s find out!
Starting off, I am going to make two assumptions. One – you are an administrator of these remote machines. Two – you can already RDP into these machines when no user is logged on. If you aren’t sure or haven’t configured these settings, see this article on where to locate these settings.
Next: Download the CRDP zip file. The script and files came from Mike Garcen and can be found here. Once downloaded, extract the contents into a folder within your local profile.
Third Step: Download SysInternal PSTools. Copy PSEXEC.EXE from the download and paste it in the CRDP folder (under your local profile).
Last step! Create a batch file in the root of your profile named CRDP.bat. Paste these three lines into it:
xcopy “%USERPROFILE%CRDP*” %1C$WindowsTempCRDP /y
“%USERPROFILE%CRDPpsexec.exe” %1 C:WindowsTempCRDPinstall.cmd multi
mstsc /v:%1
That’s it! Now, you can press Windows Key + R. Then type CRDP COMPUTERNAME
XCOPY will copy over all of the files and PSXEC will execute the script. After it has finished, you will be asked to login with your administrative account. Just to show you how awesome this is, take a look at these screenshots.
A Standard User Logged On
An Administrator Logged on at the Same Time (Notice the Task Manager).
Zoomed in Task Manager Showing User Sessions:
Pretty awesome right! Now you can work on a computer at the same time as a standard user!! There are some caveats to this method. First, it currently only works on Windows 7. I’ve seen some Windows 8 methods but they are quite shady. Second, Microsoft released an update to patch Remote Desktop Connection. This update (2984972) broke this tool. You can remove this update by running wusa /uninstall /quiet /norestart /kb:2984972 . A big thanks to TenNine for researching that problem!
Concurrent Rdp Patcher Windows 10 64 Bit Download Windows 7
Concurrent Remote Desktop allows you (the administrator) to simultaneously use a client computer while a standard user is still interactively using it. For IT, this is huge! Imagine never having to kick a person off of their computer because you need to work on it. Concurrent Remote Desktop (CRDP) makes this possible. This guide will cover CRDP setup for Windows 10.
Back in the age of Windows 7, we published the first CRDP setup guide here. If you haven’t read it, do so now – it provides background information and some troubleshooting tips. For those of you that have already read it (or just don’t like prequels), let’s enable CRDP for Windows 10!
Step 1:Download and extract this ZIP file to a network location. Any IT employee who will be using CRDP will need Read/Execute to these files – computer accounts do not need permission to see these.
Step 2: Edit the CRDP.bat file. Change the ServerShareCRDP path to your network location. Leave all of the other settings at their default values.
Step 3: Copy the CRDP.bat file to the root of your user profile. To launch a CRDP session, run CRDPComputerName . This will launch the CRDP.bat file and target it to the remote machine name that you specified. It will then work its way through the install.cmd file to enable CRDP.
Concurrent Rdp Patcher Windows 10 64 Bit Download Windows 10
Running CRDP from the local user profile.
Caveats and Tips for Using Concurrent Remote Desktop
CRDP is dependent on the client OS that you are running. It works by modifying a few registry keys and replacing the termsrv.dll with one that doesn’t check for a logged on user. It will also enable the RDP firewall rule (if not enabled). You technically only need to run this once per machine but I find it easier to run it anytime that I am connecting to a remote computer.
There are a few things you need to know about CRDP though. First, this package only works on Windows 10 x64 installations. It will should work on any edition (that has RDP built in) and any update version. The important thing is that C:WindowsSystem32termsrv.dll is at version 10.0.10240.16384. Unless Microsoft patches this file in the future, your termsrv.dll should be this version.
Concurrent Rdp Patcher 2019
The currently supported Windows 10 termsrv.dll version.
Concurrent Remote Desktop Windows 10
Second, this script makes the assumption that you are an administrator on the local machine. If you aren’t, fix that now. Finally, don’t run this against your own machine. Because it allows multiple sessions for the same user, you would never be able to join your original session. If you do need to restore the termsrv.dll file, just delete the existing one and rename the termsrv.dll.old file to termsrv.dll.
In this guide, we configured CRDP for Windows 10 X64 installations. If you have any questions or thoughts, let me know in the comment section below.