{
	"id": "1468fe9d-7f7f-43b8-b7d6-232424ae640d",
	"created_at": "2026-04-06T01:30:42.815136Z",
	"updated_at": "2026-04-10T03:20:16.511289Z",
	"deleted_at": null,
	"sha1_hash": "f404070ad07b9d53c7658f55f7e9e2436987a1ba",
	"title": "How to Allow Multiple RDP Sessions on Windows 10 and 11 | Windows OS Hub",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 2414812,
	"plain_text": "How to Allow Multiple RDP Sessions on Windows 10 and 11 |\r\nWindows OS Hub\r\nBy Eric\r\nPublished: 2023-06-30 · Archived: 2026-04-06 00:28:52 UTC\r\nRemote users can connect to their Windows 10 and 11 computers through the Remote Desktop Services (RDP).\r\nAll you need to do is enable Remote Desktop, grant the user RDP access permissions, and connect to the computer\r\nusing any remote desktop client. However, the number of concurrent RDP sessions is limited in desktop versions\r\nof Windows. Only one active Remote Desktop user session is allowed.\r\nA warning will appear asking you to disconnect the first user’s session if you try to establish a second RDP\r\nconnection.\r\nAnother user is signed in. If you continue, they’ll be disconnected. Do you want to sign in anyway?\r\nContents:\r\nNumber of Concurrent RDP Connections on Windows\r\nRDP Wrapper: Enable Multiple RDP Sessions on Windows\r\nRDP Wrapper Not Working on Windows\r\nPatch the Termsrv.dll to Enable Multiple Remote Desktop Sessions\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 1 of 16\n\nMultiple Concurrent RDP Connections in Windows 10 Enterprise Multi-session\r\nNumber of Concurrent RDP Connections on Windows\r\nThere are several restrictions on the use of Remote Desktop Services in all desktop versions of Windows 10 and\r\n11:\r\n1. Only Windows Professional and Enterprise editions can accept remote desktop connections. RDP access is\r\nnot allowed to Home/Single Language Windows editions;\r\n2. Only one simultaneous RDP connection is available. Attempting to start a second RDP session will prompt\r\nthe user to end the active session;\r\n3. If the user is working at the computer console (locally), their local session is disconnected (locked) when\r\nthey make a remote RDP connection. The remote RDP session will also be terminated if the user logs into\r\nWindows from the computer’s console.\r\nThe number of concurrent RDP connections on Windows is a license limitation. Microsoft prohibits the creation\r\nof a workstation-based Terminal RDP server for multiple users to work simultaneously.\r\nIf your tasks require the deployment of a terminal server, Microsoft suggests purchasing a Windows Server\r\n(allows two simultaneous RDP connections by default). If you need more concurrent user sessions, you will need\r\nto purchase RDS CALs, install, and configure the Remote Desktop Session Host (RDSH) role, or deploy an RDS\r\nfarm.\r\nTechnically, any version of Windows with sufficient RAM and CPU resources can support dozens of remote user\r\nsessions simultaneously. On average, an RDP user session requires 150-200MB of memory (excluding running\r\napps). This means that the maximum number of concurrent RDP sessions is limited only by the available\r\nresources of the computer.\r\nIn this article, we are going to show you three ways to remove the limit on the number of concurrent RDP\r\nconnections in Windows 10 and 11:\r\nRDP Wrapper\r\nModifying the termsrv.dll file\r\nUpgrading Windows 10/11 edition to Enterprise for virtual desktops (multi-session)\r\nNote. Any modifications to the operating system that are described in this article are considered a violation of the\r\nWindows License Agreement and may be used at your own risk.\r\nBefore you proceed, make sure that the Remote Desktop protocol is enabled in Windows.\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 2 of 16\n\nGo to Settings -\u003e System —\u003e Remote Desktop -\u003e Enable Remote Desktop;\r\nOr use the classic Control Panel: run the command SystemPropertiesRemote and check the option Allow\r\nremote connection to this computer.\r\nRDP Wrapper: Enable Multiple RDP Sessions on Windows\r\nThe RDP Wrapper Library OpenSource project allows you to enable multiple RDP sessions on Windows 10/11\r\nwithout replacing the termsrv.dll file. This tool acts as a layer between SCM (Service Control Manager) and the\r\nRemote Desktop Services. The RDP wrapper doesn’t make any changes to the termsrv.dll file, it simply loads the\r\ntermsrv with the modified settings.\r\nThus, the RDPWrap will work even in the case of termsrv.dll file update. It allows you not to be afraid of\r\nWindows updates.\r\nImportant. Before installing the RDP Wrapper, it is important to make sure that you are using the original\r\n(unpatched) version of the termsrv.dll file. Otherwise, the RDP Wrapper may become unstable or not start at all.\r\nYou can download the RDP Wrapper from the GitHub repository\r\nhttps://github.com/binarymaster/rdpwrap/releases (the latest available version of the RDP Wrapper Library is\r\nv1.6.2). The project hasn’t been updated since 2017, but it can be used in all new builds of Windows 10 and 11. To\r\nuse the wrapper on modern versions of Windows, simply update the rdpwrap.ini configuration file.\r\nRDP Wrapper is detected as a potentially dangerous program by most antivirus scanners.  For example, it is\r\nclassified as PUA:Win32/RDPWrap (Potentially Unwanted Software) with a low threat level by the built-in\r\nMicrosoft Defender antivirus. If your antivirus settings are blocking the RDP Wrapper from starting, you will need\r\nto add it to the exceptions.\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 3 of 16\n\nThe RDPWrap-v1.6.2.zip archive contains some files:\r\nRDPWinst.exe — used to install/uninstall an RDP wrapper library;\r\nRDPConf.exe — RDP Wrapper configuration tool;\r\nRDPCheck.exe —an RDP check tool (Local RDP Checker);\r\ninstall.bat, uninstall.bat, update.bat — batch files to install, uninstall, and update RDP Wrapper.\r\nTo install RDPWrap, run the install.bat file as an administrator. The program is installed in the C:\\Program\r\nFiles\\RDP Wrapper directory.\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 4 of 16\n\nRun RDPConfig.exe when the installation is complete.\r\nMost likely, immediately after installation, the tool will show that the RDP wrapper is running (Installed, Running,\r\nListening), but not working. Note the red [not supported] warning. It reports that this version of Windows 10\r\n22H2 (ver. 10.0.19041.1949) is not supported by the RDPWrapper.\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 5 of 16\n\nThis is because the rdpwrap.ini configuration file does not contain settings for your Windows version (build). +\r\n✅ Download the latest version of rdpwrap.ini here\r\nhttps://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/master/rdpwrap.ini\r\nManually copy the contents of this page into the C:\\Program Files\\RDP Wrapper\\rdpwrap.ini file. Or download\r\nthe INI file using the PowerShell cmdlet Invoke-WebRequest (you must first stop the Remote Desktop service):\r\nStop-Service termservice -Force\r\nInvoke-WebRequest https://raw.githubusercontent.com/sebaxakerhtc/rdpwrap.ini/master/rdpwrap.ini -\r\noutfile \"C:\\Program Files\\RDP Wrapper\\rdpwrap.ini\"\r\nYou can create a scheduled task to check for changes to rdpwrap.ini and update it automatically.\r\nThis screenshot shows that the latest version of the rdpwrap.ini file ( Updated=2023-06-26 ) is used on the\r\ncomputer.\r\nRestart your computer and run the RDPConfig.exe tool. Check that all items in the Diagnostics section are green\r\nand that the [Fully supported] message is displayed. The RDP wrapper started successfully on Windows 11 22H2\r\nin my case.\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 6 of 16\n\nNow try to establish several concurrent RDP sessions with this computer under different user accounts (use your\r\nfavorite RDP client: mstsc.exe, RDCMan, mRemoteNG, etc).\r\nYou can check that two (or more) RDP sessions are active on the computer at the same time by using the\r\ncommand:\r\nqwinsta\r\nrdp-tcp#0 user1 1 Active\r\nrdp-tcp#1 user2 2 Active\r\nThe RDPWrap tool is supported in all Windows editions, so you can build your own terminal (RDS) server on any\r\nWindows device. So you can turn any version of Windows client into a full-featured terminal server.\r\nThe following options are available in the RDP Wrapper:\r\nEnable Remote Desktop\r\nRDP Port —change the default remote desktop port number (TCP 3389)\r\nHide users on logon screen – allow hiding the list of users from the Windows Logon Screen;\r\nSingle session per user — allow several concurrent RDP sessions under the same user account. This\r\noption sets the fSingleSessionPerUser registry value to 0 ( HKLM\\SYSTEM\\\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 7 of 16\n\nCurrentControlSet\\Control\\Terminal Server\\fSingleSessionPerUser ). This parameter is also configured\r\nthrough the GPO option Restrict Remote Desktop Services to a single Remote Desktop Services session\r\nunder Computer Configuration \u003e Administrative Templates \u003e Windows Components \u003e Remote Desktop\r\nServices \u003e Remote Desktop Session Host \u003e Connections;\r\nThe Session Shadowing Mode allows you to configure the remote control (shadow) connection mode to\r\nthe RDP users’ desktops\r\nRDP Wrapper Not Working on Windows\r\nIn some cases, the RDP Wrapper may not work as you expect it to and you may not be able to use more than one\r\nRDP connection on Windows.\r\nThe termsrv.dll file version can be updated during Windows Updates installation. If the description for your\r\nversion of Windows is missing from the rdpwrap.ini file, then the RDP Wrapper will not be able to apply the\r\nnecessary settings. In this case, the status [not supported]. will be displayed in the RDP Wrapper Configuration\r\nwindow.\r\n✅ In this case, you must update the rdpwrap.ini file as described above.\r\nIf RDP Wrapper does not work after updating the rdpwrap.ini file, try to open the rdpwrap.ini file and look for the\r\nsection for your version of Windows.\r\nHow to understand if your Windows version is supported in rdpwrapper config?\r\nThe screenshot below shows that for my version of Windows 11 (10.0.22621.317) there are two sections of\r\nsettings:\r\n[10.0.22621.317]\r\n...\r\n[10.0.22621.317-SLInit]\r\n...\r\nIf there is no section in the rdpwrap configuration file for your version of Windows, try searching the web for the\r\nrdpwrap.ini file. Add the configuration settings you found to the end of the file.\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 8 of 16\n\nIf the RDP Wrapper does not work after you install security updates or upgrade the Windows build, check that\r\nthere is no Listener state: Not listening warning in the RDPWrap Diagnostics section.\r\nTry updating the rdpwrap.ini file, and then reinstalling the rdpwrapper service:\r\nrdpwinst.exe -u\r\nrdpwinst.exe -i\r\nIt can happen that when you try to make a second RDP connection as a different user, you will get an error\r\nmessage:\r\nThe number of connections to this computer is limited and all connections are in use right now. Try c\r\nIn this case, you can use the local Group Policy Editor (gpedit.msc) to enable the “Limit number of connections”\r\noption under Computer Configuration -\u003e Administrative Templates -\u003e Windows Components -\u003e Remote Desktop\r\nServices -\u003e Remote Desktop Session Host -\u003e Connections section. Increase the ‘RD maximum connection\r\nallowed’ value to 999999.\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 9 of 16\n\nRestart your computer to update the local Group Policy and apply the settings.\r\nPatch the Termsrv.dll to Enable Multiple Remote Desktop Sessions\r\nTo remove the limit on the number of concurrent RDP user connections in Windows without using rdpwrapper,\r\nyou can replace the original termsrv.dll file. This is the main library file used by the Remote Desktop Service.\r\nThe file is located in the C:\\Windows\\System32 directory.\r\nIt is advisable to make a backup copy of the termsrv.dll file before editing or replacing it. This will help you to\r\nrevert to the original version of the file if necessary. Open an elevated command prompt and run the command:\r\ncopy c:\\Windows\\System32\\termsrv.dll termsrv.dll_backup\r\nThen you need to take ownership of the termsrv.dll file. To change a file’s owner from TrustedInstaller to the local\r\nAdministrators group, use the command:\r\ntakeown /F c:\\Windows\\System32\\termsrv.dll /A\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 10 of 16\n\nSUCCESS: The file (or folder): c:\\Windows\\System32\\termsrv.dll now owned by the administrators group\r\nNow use the icacls.exe tool to grant Full Control permissions to the termsrv.dll file for the local Administrators\r\ngroup:\r\nicacls c:\\Windows\\System32\\termsrv.dll /grant Administrators:F\r\nprocessed file: c:\\Windows\\System32\\termsrv.dll Successfully processed 1 files; Failed processing 0 f\r\nNow you need to stop the Remote Desktop service (TermService) using the services.msc console or with the\r\ncommand:\r\nnet stop TermService\r\nIt also stops the Remote Desktop Services UserMode Port Redirector service.\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 11 of 16\n\nRun the winver command or the following PowerShell command to find your Windows build number:\r\nGet-ComputerInfo | select WindowsProductName, WindowsVersion\r\nIn my case, Windows 10 build 22H2 is installed.\r\nThen open the termsrv.dll file using any HEX editor (for example, Tiny Hexer). Depending on the build of\r\nWindows you are using, you will need to find and replace the string according to the table below:\r\nWindows build Find the string Replace with\r\nWindows 11 22H2 39 81 3C 06 00 00 0F 84 75 7A 01 00\r\n \r\nB8 00 01 00 00 89 81 38 06 00 00 90\r\nWindows 10 22H2 39 81 3C 06 00 00 0F 84 85 45 01 00\r\nWindows 11 21H2 (RTM) 39 81 3C 06 00 00 0F 84 4F 68 01 00\r\nWindows 10 x64 21H2 39 81 3C 06 00 00 0F 84 DB 61 01 00\r\nWindows 10 x64 21H1 39 81 3C 06 00 00 0F 84 2B 5F 01 00\r\nWindows 10 x64 20H2 39 81 3C 06 00 00 0F 84 21 68 01 00\r\nWindows 10 x64 2004 39 81 3C 06 00 00 0F 84 D9 51 01 00\r\nWindows 10 x64 1909 39 81 3C 06 00 00 0F 84 5D 61 01 00\r\nWindows 10 x64 1903 39 81 3C 06 00 00 0F 84 5D 61 01 00\r\nWindows 10 x64 1809 39 81 3C 06 00 00 0F 84 3B 2B 01 00\r\nWindows 10 x64 1803 8B 99 3C 06 00 00 8B B9 38 06 00 00\r\nWindows 10 x64 1709 39 81 3C 06 00 00 0F 84 B1 7D 02 00\r\nTiny Hexer cannot edit termsvr.dll file directly from the system32 folder. Copy it to your desktop and replace the\r\noriginal file after modifying it.\r\nFor example, my build of Windows 10 x64 is 22H2 19045.2006 (termsrv.dll file version is 10.0.19041.1949).\r\nOpen the termsrv.dll file in Tiny Hexer, then find the text:\r\n39 81 3C 06 00 00 0F 84 75 7A 01 00\r\nand replace it with:\r\nB8 00 01 00 00 89 81 38 06 00 00 90\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 12 of 16\n\nSave the file and start the TermService.\r\nIf something goes wrong and you experience some problems with the Remote Desktop service, stop the service\r\nand replace the modified termsrv.dll file with the original version:\r\ncopy termsrv.dll_backup c:\\Windows\\System32\\termsrv.dll\r\nTo avoid manually editing the termsrv.dll file with a HEX editor, you can use the following PowerShell script to\r\nautomatically patch the termsrv.dll file. The PowerShell script code is available in my GitHub repository at the\r\nfollowing link:\r\nhttps://github.com/maxbakhub/winposh/blob/main/termsrv_rdp_patch.ps1\r\nThis script was written for the Windows PowerShell version and does not work in modern PowerShell Core.\r\n👍 The advantage of the method of enabling multiple RDP sessions in Windows 10 or 11 by replacing the\r\ntermsrv.dll file is that antivirus software will not react to it (unlike RDPWrap, which is detected by many antivirus\r\nproducts as a malware/hack tool/trojan).\r\n👎The disadvantage of this is that you will have to manually edit the file each time you update the Windows build\r\n(or if the monthly cumulative patches update the version of termsrv.dll).\r\nMultiple Concurrent RDP Connections in Windows 10 Enterprise Multi-session\r\nMicrosoft has recently released a special edition of the operating system called Windows Enterprise Multi-Session (Previously known as Windows 10 Enterprise for Remote Sessions and Windows 10 Enterprise for Virtual\r\nDesktops)\r\nThe key feature of this edition is that it supports multiple concurrent RDP user sessions out of the box. Although\r\nthe Windows multi-session edition is only allowed to be run in Azure VMs, you can install this edition on an on-premises network and use that computer as a terminal server (even though this would be against Microsoft’s\r\nlicensing policies).\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 13 of 16\n\nThe Enterprise Multi-Session edition is available for both Windows 10 and Windows 11.\r\nNext up, we’re going to show you how to upgrade a Windows 10 Pro edition to Windows 10 Enterprise for Virtual\r\nDesktop and use it for multiple RDP users simultaneously.\r\nOpen a command prompt and check your current edition of Windows ( Professional in this example):\r\nDISM /online /Get-CurrentEdition\r\nUpgrade your edition of Windows 10 from Pro to Enterprise with the command:\r\nchangepk.exe /ProductKey NPPR9-FWDCX-D2C8J-H872K-2YT43\r\nNow install the GVLK key for Windows 10 Enterprise for Remote Sessions:\r\nslmgr.vbs /ipk CPWHC-NT2C7-VYW78-DHDB2-PG3GK\r\nCheck that your edition of Windows 10 has now changed to ServerRdsh (Windows 10 Enterprise for Virtual\r\nDesktops).\r\nActivate your copy of Windows 10 Enterprise Multi-Session edition on your KMS server:\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 14 of 16\n\nslmgr /skms kms-srv.woshub.local:1688\r\nslmgr /ato\r\nOpen the Local GPO Editor ( gpedit.msc ) and enable Per-User licensing mode in the Set the Remote Desktop\r\nlicensing mode  (Computer Configuration -\u003e Policies -\u003e Administrative Templates -\u003e Windows Components -\u003e\r\nRemote Desktop Services -\u003e Remote Desktop Session Host -\u003e Licensing).\r\nYou must restart Windows after activation. Now try connecting to the computer using RDP with different user\r\naccounts. As you can see, Windows 10 Enterprise multi-session supports simultaneous RDP connections right out\r\nof the box.\r\nGet-ComputerInfo | select WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer\r\nWindows 10 Enterprise for Virtual Desktops 2009 10.0.19041.2728\r\nqwinsta\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 15 of 16\n\nIn this article, we have looked at a number of ways to get rid of the limit on the number of concurrent RDP user\r\nconnections and run a free terminal server on desktop versions of Windows 10/11. Each method has its own\r\nadvantages and disadvantages. Which one you choose is up to you.\r\nSource: http://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nhttp://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/\r\nPage 16 of 16",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"http://woshub.com/how-to-allow-multiple-rdp-sessions-in-windows-10/"
	],
	"report_names": [
		"how-to-allow-multiple-rdp-sessions-in-windows-10"
	],
	"threat_actors": [],
	"ts_created_at": 1775439042,
	"ts_updated_at": 1775791216,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/f404070ad07b9d53c7658f55f7e9e2436987a1ba.pdf",
		"text": "https://archive.orkl.eu/f404070ad07b9d53c7658f55f7e9e2436987a1ba.txt",
		"img": "https://archive.orkl.eu/f404070ad07b9d53c7658f55f7e9e2436987a1ba.jpg"
	}
}