Windows OS Hub
  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2022
    • Windows Server 2019
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Active Directory Domain Services (AD DS)
    • Group Policies
  • Windows Clients
    • Windows 11
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows XP
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
    • KVM
  • PowerShell
  • Exchange
  • Cloud
    • Azure
    • Microsoft 365
    • Office 365
  • Linux
    • CentOS
    • RHEL
    • Ubuntu

 Windows OS Hub / Windows 8 / Enable Multiple Concurrent RDP Sessions in Windows 8.1 /8

February 21, 2018 Windows 8

Enable Multiple Concurrent RDP Sessions in Windows 8.1 /8

In Windows 8 and 8.1, like in previous Microsoft client OS versions, only one simultaneous incoming RDP connection is supported. It means that only one user (one session) can simultaneously connect to a Windows computer using the Remote Desktop. In most cases it is enough, but sometimes it would be useful if multiple remote users could work simultaneously in their own sessions. A good example is when a computer is used as a Media Center, when video is played in the system console session and you need simultaneously to work remotely with the system without interrupting the video on TV.

Tip. A remote RDP access requires Pro or Enterprise version of Windows 8, and is not available in Home editions.

When you trying to start the second RDP session to a computer with Windows 8.1 / 8, a message appears that another user is already signed in locally and this session should be closed.

Another user is signed in. If you continue, they will be disconnected.

Windows 8 RDP warning: Another user is signed in. If you continue, they will be disconnected

Tip. Previously, you need to enable the RDP access in the properties of the computer on the Remote tab, and add the necessary user accounts to the local group Remote Desktop Users. For local administrators, remote RDP access is allowed by default. After enabling RDP access in the system properties, Windows Firewall automatically enables rules that allow incoming traffic to local TCP port 3389. Sometimes this rule should be checked manually.

For example, in the server versions of Windows two simultaneous concurrent administrative connections with the individual sessions are supported (in case of the terminal RDS server this number may be even higher).

Nevertheless, you can find a special patch in the web that allows to ignore this restriction. Due to this patch, multiple users can simultaneously connect to Windows 8 / Windows 8.1 computer over RDP.

Important. Using this patch breaks the licensing agreement and the terms of use for Microsoft products. So perform all the operations described below on your own risk.

So, the patch replaces the original system file %SystemRoot%\System32\termsrv.dll (a library used by Remote Desktop Services).

Here are the links to the modified library versions:

  • Windows 8 – windows8-termsrv.dll.zip
  • Windows 8.1 — windows8.1-termsrv.dll.zip

Before you replace the library, back up original termsrv.dll using the command:

copy c:\Windows\System32\termsrv.dll termsrv.dll_old

Backup original termsrv.dll

Now, if something goes wrong, you can always roll back to the original configuration by replacing the current file with the original termsrv.dll_old.

Download the archive with the patched termsrv library for your Windows version.

In Windows 8 at first you have to change the values of the following keys in HKLM\System\CurrentControlSet\Control\Terminal Server\:

  • fDenyTSConnections (DWORD) — 0 (the key allows to enable RDP on your computer)
  • fSingleSessionPerUser (DWORD) — 0

fDenyTSConnections - Enable RDP connections Windows 8

The same operation can be performed from the command prompt:

REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fDenyTSConnections /t REG_DWORD /d 0 /f
REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server" /v fSingleSessionPerUser /t REG_DWORD /d 0 /f

Then go to C:\Windows\System32, find the file termsrv.dll and open its properties.

termsrv.dll - file properties

By default, the owner of this file is TrustedInstaller and even the administrator doesn’t have any right to replace it.

termsrv.dll owner - TrustedInstaller

Go to the Security tab and click Edit button. In the access list, find the local administrators group and give it full control over this file and save the changes.

termsrv.dll security settings

The next step before replacing the library file is to open the service management console (services.msc) and stop Remote Desktop Services.

Stop Remote Desktop Services

Copy termsrv.dll from the downloaded archive for your Windows version to %SystemRoot%\System32\ (with replacement).

Note. The archive for Windows 8.1 contains two files: 32_termsrv.dll and 64_termsrv.dll for a 32-bit and a 64-bit version of Windows 8.1. Unpack the archive and rename the file for your version of the system to termsrv.dll.

After replacing the file, run Remote Desktop Services and try to create two RDP sessions with the patched computer from different accounts. If you did everything correctly, two separate Remote Desktop session should open.

Windows 8.1 enable multiple rdp connections

Tip. You may need to restart your computer.

Important note! Using the patched version of termsrv.dll has a number of drawbacks. The main one – when you install the next security update for Windows 8.1 / 8 this file can be replaced. In this case, you will have to patch a new file by yourself with the HEX editor, or you can search the Internet for the modified termsrv.dll file for your Windows build.

As a stable solution against replacing the termsrv.dll file with Windows updates, you should use the Open Source solution – RDP Wrapper Library (available on GitHub) which does not replace termsrv.dll, and is a layer between Terminal Services and SCM. More information about using the RDP Wrapper Library can be found here.

15 comments
0
Facebook Twitter Google + Pinterest
previous post
How to Install .NET Framework 3.5 on Windows Server 2012 R2
next post
Removable USB Flash Drive as Local HDD in Windows 10 / 7

Related Reading

PowerShell Install-Module Error: Unable to Download from URI

April 21, 2022

How to Disable “Open File – Security Warnings”...

June 15, 2021

Using Malicious Software Removal Tool (MRT.exe) on Windows

April 15, 2021

How to Restore Deleted EFI System Partition in...

July 29, 2020

Internal SSD/SATA Drive Shows as a Removable in...

December 16, 2019

15 comments

Heyvoon July 8, 2015 - 1:51 pm

Can I apply this to Windows 2012 server?

Reply
dh28 October 30, 2015 - 6:42 am

this article well works with 2012 server too. I successfully patched 2012 foundation server with 5 additional terminal licences! Author thank you very much. Many many thanks!

Reply
bkz81 December 21, 2015 - 12:41 pm

Is there a way to be notified when a second user logs in remotely? I like the feature but it does have a security risk if another account gets compromised.

Reply
Daniel February 28, 2016 - 11:39 pm

To my knowledge there is not a way of being notified of the second logon but you can see active sessions by going to TaskManager->Users tab. There you can see all active or disconnected sessions. 

Reply
Bruce September 21, 2016 - 6:16 pm

Followed these instructions and it did not work for me. When I tried to back out of it my machine was hosed and I could not remote to my machine any more.

Reply
Bruce September 21, 2016 - 8:44 pm

Update!!! It did work for me. I was trying from a network that did not have access to the box.

Reply
Jesus P. November 29, 2016 - 10:42 pm

I was able to do this remotely and it works. I was receiving Access Denied errors to the termserv.dll file. I had to login through Teamviewer to remove my reliance on Remote Desktop Services. Then I used the “takeown /F “C:\Windows\System32\termserv.dll” /A” command to take ownership of the file. Then I was able to continue with the steps. Thanks!

Reply
Y June 19, 2017 - 9:41 pm

fSingleSessionPerUser should be 1 if you want to reconnect to the same RDP session later.

Reply
M.Cihan Erdem October 4, 2017 - 12:33 pm

worked for me too, thank you very much.

Reply
jbOb April 14, 2018 - 12:28 am

The process seemed to work well for me but after restarting i attempt a login but get an internal error occurred notice. Anybody know whats wrong?

Reply
Max April 16, 2018 - 9:15 am

Specify the full error text and you Windows build number.
Does the error occurs when you logon locally or when try to access your computer over RDP?

Reply
Parichehr May 28, 2018 - 6:28 am

Is this working on windows 7?

Reply
catur May 11, 2020 - 5:09 pm

why i only can rdp administrator account, for local account i can’t acces, solution please

Reply
admin May 15, 2020 - 6:35 am

Add your user account to the local “Remote Desktop Users” group (this action must be performed with administrator rights).

Reply
CyberPod Mark 2 July 18, 2021 - 11:39 am

The Link is dead. Please give me a link or update this one. I still have an issue with the remote desktops not only for the virtual machines but the original computer such as Windows 8.1 32 bit.

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange Server
  • Microsoft 365
  • Azure
  • Windows 11
  • Windows 10
  • Windows 7
  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2
  • PowerShell
  • VMWare
  • Hyper-V
  • MS Office

Recent Posts

  • Create Organizational Units (OU) Structure in Active Directory with PowerShell

    May 17, 2022
  • Windows Security Won’t Open or Shows a Blank Screen on Windows 10/ 11

    May 17, 2022
  • How to Manually Install Windows Updates from CAB and MSU Files?

    May 16, 2022
  • RDS and RemoteApp Performance Issues on Windows Server 2019/2016

    May 16, 2022
  • Deploying Software (MSI Packages) Using Group Policy

    May 12, 2022
  • Updating VMware ESXi Host from the Command Line

    May 11, 2022
  • Enable or Disable MFA for Users in Azure/Microsoft 365

    April 27, 2022
  • Fix: You’ll Need a New App to Open This Windows Defender Link

    April 27, 2022
  • How to Reset an Active Directory User Password with PowerShell and ADUC?

    April 27, 2022
  • How to Completely Uninstall Previous Versions of Office with Removal Scripts?

    April 26, 2022

Follow us

woshub.com

ad

  • Facebook
  • Twitter
  • RSS
Popular Posts
  • Managing Printers from the Command Prompt in Windows 10 / 8.1
  • Using the BitLocker Repair Tool to Recover Data on Encrypted Drive
  • Auto-Mount a VHD/VHDX File at Startup in Windows 10, 8.1
  • Limited Wi-Fi Access in Windows 10 and 8.1 – Troubleshooting
  • Internal SSD/SATA Drive Shows as a Removable in Windows
  • How to Backup and Restore Boot Configuration (BCD) in Windows
  • Windows 7/8.1 Update Error “The Processor is Not Supported” On New CPUs
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top