Here is a fun one. Imported Artoo into the registry as binary data, wrote it to memory as memorystream and run R2 without need for an.exe via right click shell extension. The memorystream seems to make it a bit more responsive. Instructions for 8.1 / R2 only - merge with registry, right click anywhere on desktop and choose "Artoo's Termsrv Patcher" to open. Here is an excerpt. FYI, this experimental method could be deleted by me at any time, so get it while the getting is good.
Stupidity on my part. Permissions issue, basically once you take ownership as admin, you need to change permissions to full control. I mistakingly had it changed to full control for users not admins. works perfectly now Thanks for the great tool Jinje
W81x64 gotcha, try this. Added a SnoopLoggy.Log for error collection, instructions are copy your unpatched termsrv.dll somewhere + edit the path where instructed. Report any errors.
Have anyone tried patching it in memory? Would it be possible? I tried on Windows 7 x86, but it seems to just hang at connecting...
I try R2_Beta3 Patch on Windows 8.1 Enterprise x64 now. Well, seems it works, I can connect to two users at the same time. I can't check whether the local user can enter, because I only could connect remotely now (until evening comes). Computer should automatically load user when comp started, but if i'm connecting remotely, it will ship it at this point, ie either it can not boot at startup now, or the connection is different from the connection of a local user. Teamviewer also going crazy, connects, but draws the devils and not responding ... Do I understand correctly, that it is possible to connect several times to the same user by using this patch? I don't need this feature, but need to connect to different users at the same time without troubles the local user. Thanks for your work)
I was testing all that right now. My wife is from local user, i'm - remotely. So that's ok with patch, i think. And TeamViewer connected correctly now. Magic? I'll watch what will happen next and tell about it here.
So I tried the same thing in ollydbg and attached it to the correct svchost, and did the same patch as I already tried with inline memory attempt. And it worked. So I guess the answer lies in how I have left the module, or its state. I tweaked the page protection and set it to PAGE_READWRITE, which may have produced undesired behaviour.. Btw, finding the correct svchost can be done by looping through all svchosts and using EnumProcessModulesEx (to search for termsrv.dll). Good to know that memory patching will work then!
Bingo! It was the page protection that had to be reset. Needed to be changed back to PAGE_EXECUTE_READ after temporarily being PAGE_READWRITE in order to write to the page. How x64 behaves with this is not yet tested.
Help- I've install the patch all ok. BUT I can't seem to get the RDC to auto login to the desktop. When I login remotely, I get the Windows 8 login screen, and therefore have to select the user name and type the password again. Tried all sorts to resolve. I appears to be a be an issue on the Windows 8 side not Client side. I'm testing between a windows 7 PC and windows 8 PC. RDC to windows 7 works fine (straight to desktop), RDC to windows 8 always get me to the login screen. How do I enable auto login on the RDC session?
@Mr Jinje The memory patch also works on x64 (at least Windows 7). After a couple of failed attempts I realized after trying your tool, that 2 other places had to be patched. Nice work though! Will you consider a memory patcher too?
like i said, if you can provide me a working example of the cmd line syntax, I'll take a look at it again, but for now I just don't have the free time to learn and do everything I want.
These steps worked great for me on a 8.1 pro box that I just upgraded from 8.0 pro using the beta3 r2d2. Only hiccup was remembering how to take ownership of the termsrv.dll file, which a post on winmatrix helped with. Thanks for everyone's hard work! e
i tried this on windows 8.1 64bit working good but it cant be undo even after restart service, restart windows, and full shutdown.