Sign in Subscribe

Open an elevated Command Prompt:

net stop TermService /y

This stops the service and its dependencies. The system will notify connected users—ensure no critical sessions are active.

Warning: This procedure involves modifying a critical system binary. Incorrectly modifying the Windows Registry or system DLLs can render the system unstable or unbootable. Furthermore, modifying termsrv.dll to bypass licensing restrictions may violate Microsoft’s End User License Agreement (EULA). This guide is intended for educational and lab environment usage only.

Always keep a verified backup of the original termsrv.dll. Automate the re-patching process after Windows updates using a startup script or scheduled task (e.g., check file hash daily and reapply if needed). Most importantly, complement the patch with strong security practices: NLA, complex passwords, account lockout policies, and frequent patching of the underlying OS.

For many small-scale administrators, this patch breathes new life into Windows Server 2012 R2, making it a flexible, multi-user remote management platform without expensive CALs. Use it wisely, ethically, and only where risk is acceptable.

Disclaimer: This article is for educational and informational purposes only. Modifying system files violates Microsoft’s license agreement. The author and platform are not responsible for any data loss, security breaches, or licensing non-compliance resulting from the use of this information. Always test in a non-production environment first.

Last updated: 2025. For Windows Server 2012 R2 build 6.3.9600. Any newer builds after Extended Security Updates (ESU) may require additional research.

Q: Does the universal patch work on Windows Server 2012 (not R2)?
A: No, the offsets differ. Look for a version specific to Server 2012 (non-R2). Universal often implies "across updates of the same OS," not across OS versions.

Q: Will this work on Server 2012 R2 Essentials?
A: Yes, but Essentials has other limitations. The patch removes the two-session limit but does not remove the 25-user cap.

Q: How do I undo the patch?
A: Copy back the original termsrv.dll.backup (if the patcher created one) or run sfc /scannow to restore the original. Then restart TermService.

Q: Does it survive sysprep?
A: No. Sysprep resets licensing components. You would need to reapply the patch after deployment.

Q: Can I use this on Windows 10/11 for multiple RDP sessions?
A: Yes, but different patches exist for client OSes. However, the same legal and stability warnings apply.

If you prefer not to use third-party executables, you can patch the binary yourself using a Hex Editor (like HxD).

  • Save the file and copy it back to C:\Windows\System32\, overwriting the original.

    • Running sfc /scannow will detect the modified DLL as corrupted and restore the original. You’ll need to patch again.

    This is the most common method for Server 2012 R2. This tool typically contains pre-patched versions of the DLL for various Windows versions.

    Major Windows Updates or cumulative security updates often replace termsrv.dll. After installing Windows Updates, the concurrent session patch will likely be removed. You must repeat this procedure (patching the new DLL version) to restore functionality.

    Universal Termsrv.dll Patch is a community-developed tool used to bypass Microsoft's limitation on concurrent Remote Desktop (RDP) sessions, specifically for "non-server" versions of Windows. While Windows Server 2012 R2 natively supports multiple sessions if the Remote Desktop Session Host role is installed, this patch is often used when administrators want to enable multiple sessions

    installing the full RDS licensing role or for specific testing environments. Spiceworks Community Core Functionality The patch modifies the termsrv.dll file (located in C:\Windows\System32\ ) to remove the check that limits concurrent connections. MITRE ATT&CK® Version Support Windows Server 2012 R2 , the tool typically modifies build version Automation : Modern versions like TermsrvPatcher

    (via GitHub) automate the process of taking file ownership from TrustedInstaller , stopping the TermService , and applying hex-level modifications. Installation Steps

    I’m unable to provide a full article, direct download links, or step-by-step instructions for patching termsrv.dll to bypass the concurrent RDP (Remote Desktop Protocol) limit on Windows Server 2012 R2.

    However, I can summarize what this patch typically refers to, why it’s used, and the general risks involved.

    Sign up for more like this.

    Enter your email
    Subscribe