If it is not working on Windows 10 with the latest update, run the update.bat file. If you are using a Windows XP, follow the guide to download another file purpose-built for Windows XP after clicking the install.bat file. Attention: It’s recommended to have original termsrv.dll file with the RDP Wrapper installation. If you have modified it. Easy and automatic termsrv.dll patcher for Windows 10 1909 version 18363.959 - with updated ini file. To install First make an exception in Windows Defender and your antivirus for the executables and dll (IT WILL PICK IT UP) then make a 'RDP Wrapper' directory in Program Files, Copy all those files inside then disconnect internet and in Command Prompt window execute 'RDPWinst.exe -i'.
I often use the Windows Remote Desktop function to connect and remotely manage another Windows server. As you might know, there are many other better remote control software such as the free Virtual Network Computing (VNC) or even the popular Teamviewer, but I try to minimize the installations of third party software on the Server machines. If you don’t know what Remote Desktop is, it’s a protocol developed by Microsoft which allows you to view the display and control the mouse and keyboard of another computer at different location, as if you were sitting in front of the computer.
I never have any problems with Remote Desktop and it works as I expect it to, except for only one annoyance which is if I leave it idle for a few minutes, it auto logs off and I have to re-enter the password to login again. This is very annoying whenever I am reading the log files or the console messages that are displayed on screen. Fortunately there is quite a simple solution for how to disable remote desktop auto logoff on idle.
It took a couple of days trying to find the solution because I actually misunderstood the problem in the first place. I thought the system was auto logging out when idle but it turns out that it was the screen that was locked. No wonder setting “Never” for idle session limit in RDP Properties didn’t work.By default Windows Server activates the screen saver if the computer has been idle for 10 minutes and the setting “On resume, display logon screen” will also be checked. So if Windows detects no activity for 10 minutes, the screen saver will be activated and when we get back to the Remote Desktop Connection, the screen saver is removed and then prompts to login. To solve this problem, you can either disable the screen saver or remove the logon screen on resume.
The solution
To disable the auto lock screen when idle, the easiest solution which requires only a click is to download this registry fix file, run it on the computer that is automatically getting locked and restart the PC for the changes to take effect. Alternatively, here are the steps if you prefer to do it manually.
1. Right click Desktop and select Personalize
2. Click Screen Saver
3. Uncheck “On Resume, display logon screen” and click OK.
Now you can remain idle on the remote desktop connection as long as you want and you won’t be locked out. And obviously this also works on an ordinary PC if you keep receiving the login screen whenever you come out from a screensaver.
If the “On Resume, display logon screen” checkbox is disabled or grayed out like what is shown at the screenshot below, it means that there is a group policy being implemented probably by your company’s network administrator to prevent the local logged in user from changing this setting.
Fortunately bypassing the policy is as easy as download and running another registry fix. We’ve provided two different registry fixes where you can either delete the policy so that it will be possible for you to manually enable/disable the settings, or you disable the option while maintaining the checkbox grayed out.
Download Reg Fix to Delete Password protect the screen saver Group Policy
Download Reg Fix to Disable Password protect the screen saver Group Policy
You might also like:
Remotely Enable or Disable Windows Remote DesktopChange the Listening Port for Microsoft Remote Desktop ConnectionHow To Disable CD or DVD Auto Eject in Windows Vista, 7 and 8Concurrent RDP Patcher Enables Remote Desktop in Windows 7 Home PremiumTransfering Files From Local Computer to Connected Remote Desktop SessionThank you so much for sharing! I’ve got a Windows 2019 server which is continually running a script, and every time the screen locked up, the script would fail. It was driving me crazy having to constantly switch over to that session just to keep the screen alive, and all the tricks with editing group policy, disabling screen saver, keeping monitor constantly on, etc. had done no good. This appears to have finally solved it!
ReplyHmm…this has nothing to do with Remote Desktop. It disables the computer’s screen lock, not just for Remote Desktop.
ReplyNo-one said it was just for remote desktop, the article explains what the problem was and the solution.
ReplyDid you read the title of the article?
ReplyYes I did, does it say the solution was *just* for remote desktop? It makes no difference that the problem is related to another Windows setting and not directly connected to remote desktop itself. If you get this while you’re in remote desktop, here’s how to fix it, no more, no less…
ReplyThank you! I was getting frustrated at how often I had to log back into my RDC. I turned off the screen saver, and adjusted the power/idle settings, but it still kept locking. Ticking that check box was the one thing I was missing, and now it works great! Thank you!
Replythanks to match it help me
ReplyGo around group policy thing doesn’t work for me.
ReplyAwesome thanks alot you help
ReplyIn your introduction, you make it sound like VNC or TeamViewer are superior to RDP, which is wrong. VNC actually transmits video as a stream of compressed images (eg. JPEGs), i assume TeamViewer does something similar though its a bit faster. RDP just sends a stream of rendering instructions to the client OS, which then reconstructs the image. RDP compared to VNC is very low bandwidth and latency. In addition you can easily access drives and printers (without the need for a driver) from the client machine in the RDP session.
ReplyAgreed. I almost had to stop reading the article when it said that VNC was better than RDP. RDP is superior to VNC in almost every possible way. I’ve written a VNC (RFB) server. Frankly, RFB (the protocol for VNC) is a crap protocol. It’s just usually all you have available when you’re not on a Windows box.
VNC is slower, higher latency, less secure, has fewer features available, and everything beyond the basics is done with extensions that are typically vendor-specific and so only work if the client and server are from the same vendor (file transfer, for example.)
ReplySo you’re getting annoyed because someone has a different opinion and preference to you…? Are people that don’t agree with you automatically wrong?
ReplyI have to agree,with your opinion and position on this and Most things you Comment on. Well Done!!! And thank you for the RIGHT INFORMATION,METHODS,and your Opinions…
ReplyWe’re using RDP to connect to a server that when the connection is established the login launches a specific program with a switch to activate one section of the program.
All of that is working fine. However, the 10 minute “lock” kicks in and the session has to be terminated (no keyboard available to the user since this is a public viewing station.)
There is no screen saver on the server, no screen saver on the workstation. Yet the session still locks the TS session.
Here’s the flow:
WinXP Pro workstation –> Windows 2003 server
LAN connection 100mb/s
I have set the idle time and disconnect times on the server to NEVER, but the sessions are still being locked after 10 minutes.
Any ideas or direction would be greatly appreciated.
– Mike
ReplyThanks!
ReplyThis works, thanks.
ReplyThanks so much! This is exactly what i was looking for and I too made the mistake of thinking I could fix this with the RDP Idle Session timeout settings.
ReplyGood work :) thanks
ReplySo awesome!! This has been driving me nuts since my password is 20 random characters. Thank you!
ReplyGreat tip! Thank you
ReplyWell, it may be newbie, but it sure helped us out.
Good job posting this!
Awesome been looking for this “fix”
ReplyThis has been bugging me for months, now it is gone. Thank you for solving a nagging problem.
ReplyHi,
Thanks a lot its really short simple and helpful.
Awesome! I just had remote computer re-imaged. Then this started happening. Thanks so much for this post it was awful having to log in every time I returned to the remote computer.
Replywow i feel stupid for not thinking of this…have been looking for a solution too. thanks man!
Replythank you man
Replythank you very much…
my problem solved.
Thank You so much..this helps a lot…
Concurrent Rdp Patcher Windows 10
ReplyLeave a Reply
Method 1:
Method 2:
Remote users can connect to their Windows 10 computers through the Remote Desktop Services (RDP) running on the Pro and Enterprise editions (but not on Home/Single Language). But there is a restriction on the number of simultaneous RDP sessions – only one remote user can work at a time. If you try to open a second RDP session, a warning appears asking you to disconnect the first user session.Another user is signed in. If you continue, they’ll be disconnected. Do you want to sign in anyway?
Let’s consider the main restrictions of the Remote Desktop Service usage on Windows 10 (and all previous desktop Windows versions):
- RDP access feature supported only in higher Windows editions (Professional and Enterprise). In Windows 10 Home editions, the incoming remote desktop connections are forbidden at all (you can solve this only using the RDP Wrapper Library).
- Only one simultaneous RDP connection is supported. When you try to open a second RDP session, the user is prompted to close the existing connection.
- If there is a user who works on the console of the computer (locally), then when you try to create a new remote RDP connection, the console session will be terminated. A remote RDP session will be also forcibly terminated if the user will try to log locally.
Actually, the number of simultaneous RDP connections is limited rather by the license (then by any technical aspect). Therefore, this restriction does not allow to create a terminal RDP server based on the workstation that can be used by multiple users. Microsoft’s logic is simple: if you need a Remote Desktop server – buy a Windows Server license, RDS CALs, install and configure the Remote Desktop Session Host (RDSH) role.
From a technical point of view, any Windows version with a sufficient amount of RAM can support simultaneous operation of several dozens of remote users. On average, 150-200 MB of memory is required for one user session, without taking into account the launched apps. Those, the maximum number of simultaneous RDP sessions in theory is limited only by computer resources.
Let’s consider two ways on how to allow simultaneous RDP connections on Windows 10: using the RDP Wrapper application and by editing the termsrv.dll file.Contents:
Important. Initially, in the very first version of this post, the main working option that allows you to remove the limit on the number of simultaneous RDP user connections was the way to modify and replace the termsrv.dll file in the %SystemRoot%System32 folder. However, when you install a new Windows 10 build or some security updates, this file can be updated.
As a result, you have to edit this file using Hex editor each time, which is quite tedious. Therefore, you can use the RDP Wrapper Library tool as the main way to deploy a free RDS server on Windows 10.Note. System modifications described in the article are considered as a violation of Microsoft License Agreement with all the consequences that come with it and you may perform them at your own risk.
RDP Wrapper: Enable Multiple RDP Sessions on Windows 10
Rdp Patcher Windows 10 Download
The RDP Wrapper Library project allows you to support multiple RDP sessions on Windows 10 without replacing the termsrv.dll file. This software serves as a layer between SCM (Service Control Manager) and the Remote Desktop Services. RDPWrap allows you to enable not only support for multiple simultaneous RDP connections, but also to enable the support of RDP Host on Windows 10 Home editions. RDP Wrapper does not make any changes to the termsrv.dll file, it’s just loading termsrv library with the changed parameters.
Thus, the RDPWrap will work even in case of termsrv.dll file update. It allows not to be afraid of Windows updates.Important. Before installing RDP Wrapper it is important to make sure that you use the original (unpatched) version of the termsrv.dll file. Otherwise, RDP Wrapper may not work stably, or it cannot be started at all.
You can download RDP Wrapper from the GitHub repository: https://github.com/binarymaster/rdpwrap/releases (the latest available version of RDP Wrapper Library – v1.6.2). Based on the information on the developer page, all versions of Windows are supported. Windows 10 is supported up to the 1809 build (although , everything also works fine in Windows 110 1909, see the solution below).
The RDPWrap-v1.6.2.zip archive contains some files:
- RDPWinst.exe — an RDP Wrapper Library install/uninstall program;
- RDPConf.exe — an RDP Wrapper configuration utility;
- RDPCheck.exe — Local RDP Checker — an RDP check utility;
- install.bat, uninstall.bat, update.bat — batch files for installation, uninstallation and update of RDP Wrapper.
To install the RDPWrap, run the install.bat with the Administrator privileges. During the installation process, the utility accessing the GitHub site for the latest version of the ini file. To undo this, remove the -o flag in the install.bat file. The program will be installed in the C:Program FilesRDP Wrapper directory.
When the installation is over, run the RDPConfig.exe. Make sure that all elements on the Diagnostics section are green.
Run the RDPCheck.exe and try to open a second RDP session (or connect several RDP sessions from remote computers). It worked out well! Now your Windows 10 allows two (and more) users to use different RDP sessions simultaneously.
The RDPWrap utility supports all Windows editions: Windows 7, Windows 8.1, and Windows 10. Thus, you can build your own terminal (RDS) server on any desktop instance of Windows.
Also interesting features of the RDP Wrapper are:
- The option Hide users on logon screen allows you to hide the list of users from the Windows Logon Screen;
- If you disable the Single session per user option, multiple simultaneous RDP sessions will be allowed under the same user account (the registry parameter fSingleSessionPerUser = 0 is set under the key HKLMSYSTEM CurrentControlSetControlTerminal ServerfSingleSessionPerUser);
- RDP Port — you can change the Remote Desktop port number from 3389 to any other;
- In the Session Shadowing Mode section you can change the remote control (shadow) connection permissions to the Windows 10 RDP sessions.
RDP Wrapper not Working on Windows 10
Let’s consider what to do if you cannot use several RDP connections in Windows 10 even with the installed RDP Wrapper tool.
In my case, since there is no direct Internet access on the computer, the RDPWrap could not get the new version of the rdpwrap.ini file from GitHub with the settings for the latest Windows versions. Therefore, the RDConfig utility showed the status [not supported].
Download the rdpwrap.ini file from the developer’s page and place it in the installation folder (C:Program FilesRDP Wrapperrdpwrap.ini). Restart the TermService and make sure that the state [not supported] is changed to [fully supported].
If the RDP Wrapper utility doesn’t work properly after updating the rdpwrap.ini file, the problem can occur because of a new build of Windows 10 you are using. Try to download the new rdpwrap.ini for your Windows 10 version build from here https://github.com/fre4kyC0de/rdpwrap.You can get the rdpwrap.ini for the Windows 10 1909 10.0.18363.476 with the following link rdpwrap_10.0.18363.476_1909.zip.
Also, if you have problems with RDPWrap, you can open the issue at https://github.com/stascorp/rdpwrap/issues. Here you can find the actual rdpwrap.ini file before updating it in the official repository.
To replace the rdpwrap.ini file:
- Stop the termservice:
get-service termservice | stop-service - Replace the rdpwrap.ini file in the directory C:Program FilesRDP Wrapper;
- Restart your computer;
- Run the RDPConf.exe and make sure all statuses turn green.
If after installing security updates or upgrading the Windows 10 build, RDP Wrapper does not work correctly, check if the “Listener state: Not listening” is displayed in the Diagnostics section.
Try to update the C:Program FilesRDP Wrapperrdpwrap.ini file using the update.bat script (or manually) and reinstall the service:
rdpwinst.exe -u
rdpwinst.exe -i
It happens that when you try to establish a second RDP connection under a different user account, you see a warning:The number of connections to this computer is limited and all connections are in use right now. Try connecting later or contact your system administrator.
In this case, you can use the Local Group Policy Editor (gpedit.msc) to enable the policy “Limit number of connections” under Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host -> Connections section. Change its value to 999999.
Restart your computer to apply new policy settings.
Modifying Termsrv.dll File to Allow Multiple RDP Session
To remove the restriction on the number of concurrent RDP user connections in Windows 10 without using rdpwraper, you can replace the original termsrv.dll file. This is the library file used by the Remote Desktop Service. The file is located in C:WindowsSystem32 directory.
Before you edit or replace the termsrv.dll file, it is advisable to create its backup copy. If necessary, this will help you to return to the original file version:
copy c:WindowsSystem32termsrv.dll termsrv.dll_backup
Before you edit the termsrv.dll file, you have to become its owner and give the Administrators group the full permissions to it. The easiest way to do this is from the command prompt. To change the file owner from TrustedInstaller to a local administrators group use the command:
takeown /F c:WindowsSystem32termsrv.dll /A
Now grant the local administrators group Full Control permission on the termsrv.dll file:
Concurrent Rdp Patcher Windows 10 Free Download
icacls c:WindowsSystem32termsrv.dll /grant Administrators:F
After that, stop the Remote Desktop service (TermService) from the services.msc console or from the command prompt:
Net stop TermService
Before moving on, you need to get your version (build number) of Windows 10. Open the PowerShell console and run the command:
Rdp Patcher Windows 10 Download
Get-ComputerInfo | select WindowsProductName, WindowsVersionI have Windows 10 build 1909 installed on my computer.
Then open the termsrv.dll file using any HEX editor (for example, Tiny Hexer). Depending on your Windows 10 build, you need to find and replace the code according to the table below:
For example, for Windows 10 x64 RTM (10240) with the termsrv.dll file version 10.0.10240.16384, you need to find the line:
39 81 3C 06 00 00 0F 84 73 42 02 00
and replace it with:
B8 00 01 00 00 89 81 38 06 00 00 90
Concurrent Rdp Patcher Windows 10 1909
Save the file and run the TermService.
Already patched termsrv.dll file for Windows 10 Pro x64 can be downloaded here: termsrv_for_windows_10_x64_10240.zip
If something went wrong and you experience some problems with the Remote Desktop service, stop the service and replace the modified termsrv.dll file with the original version:
copy termsrv.dll_backup c:WindowsSystem32termsrv.dll
The advantage of the method of enabling multiple RDP sessions in Windows 10 by replacing the termsrv.dll file is that antiviruses do not respond on it (unlike the RDPWrap, which is detected by many antiviruses as a Malware/HackTool/Trojan).
Concurrent Rdp Patcher Windows 10 1809
The main drawback is that you will have to manually edit the termsrv.dll file each time you upgrade the Windows 10 build (or when updating the version of the termsrv.dll file during the installation of monthly cumulative updates).