Latest patchday broke my termsrv.dll (I assume it was KB2959626), so here's the new one in case it's needed: Windows 8.1 + KB2959626 (x64): d-h.st/W3M
I confirm that KB2959626 is the culprit. A temporary work around is to just replace termsrv.dll with the old module until a patched version of the new one is available. Or, you can just not install KB 2959626 until a patched version of the dll is available.
I simply uninstalled the update from progs and features, and can confirm is working again (and set updates not to run automatically so it wont come back). The modified termsrv.dll re-appeared (from 3.0). I joined forum solely to be able to download the "members only" version, so I thought I'd contribute a little
Maybe someone who actually runs W8.1 can test this out make sure i didn't typo or something. Code: $KB = "KB2959626";$isinstalled = Get-HotFix -Id $KB -ErrorAction 0;If ($isinstalled -ne $null){write-host "$KB is installed!"}Else{Write-Host "$KB is not installed!"} #
Code: PS D:\> $KB = "KB2959626";$isinstalled = Get-HotFix -Id $KB -ErrorAction 0;If ($isinstalled -ne $null){write-host "$KB i s installed!"}Else{Write-Host "$KB is not installed!"} KB2959626 is installed!
Uninstall says error Hi. I have tried uninstalling the latest patch and get an error trying to do so. Anny suggestions
Replaced your patched dll and working again (win8.1/32). Thank you sir! I'm curious, if it is possible to prevent windows update form modifiyng termsrv.dll file? I mean like replacing permissions for all users to read only is enough...
I have had exactly the same issue - since that update the termserv.dll file can't be deleted or changed - I used unlocker to delete the file, then replaced it with the patched version Mr Jinje linked to - works fine again, but will be a bit frustrating if MS continue to change the file with random updates. Another question - is it possible to somehow manually adjust the registry entry so that the multi user is allowed, but not multiple sessions per user account if that makes sense? I'll try and explain that better.... If Fred is remoting on, and Tony is working locally on the PC, that's fine, but if Tony then leaves his account logged in, goes out of the office and then wants to remote onto his account, the default behavior after this patch will be that he is logged into another 'instance' of his account, I would like to set it up so that if someone remoted on, they will end up in the same account no matter what. Hope that makes a bit more sence.
If you have an additional one to replace the file with simply rename it and copy that one into the exact or same directory. That would do the trick.
I've done that and it's working fine, my point was that the windows update seems to have 'locked' the termserv.dll file, where before it could just be deleted or renamed without issue.
Just thought I would throw this out there, in case anyone else had the same issue. The termserv.dll file not only has to be taken ownership of, but you also have to check full access on the group you want to be able to modify it. At first glance it looks like Read/Write would be enough but it is not Cheers for the patch.
Hello all! I found really cool programm for muliti-rdp RDP Wrapper Library by Stas'M Link: stascorp.com/load/1-1-0-63 Very good thing is the original termsrv.dll file remains untouched. Also this method is very strong against Windows Update. Just tested on my Windows 8.1 with termsrv.dll 6.3.9600.17095 - it work! Many thanks to author!!!
Amazing, it´s working!. I use vmware 10 to install windows server 2012 r2 datacenter (I know this is obvious). For the moment 2 RDP conection and one local. Thank`s for your job!