Add support for termsrv 6.3.9600.18928

[burluckoff]

termsrv.zip
Dont working...

[KaterTomi]

Also for me and certainly for many other peoples very important.

[NMCowboy]

I didn't see this before I replied to Kipfun but I could use this one too. I read the Windows update descriptions but I didn't see anything about RDP. They are getting very sneaky.

[andydld]

Same problem here.
Two Windows Server 2012 R2 Standard.
Problem since the most current Windows Updates (installed 13.03.2018/14.03.2018)

RDPwrapper 1.6.1 and 1.6.2

Wrapper state: Installed ver. 1.5.0.0
Service state: Running ver. 6.3.9600.18928
Listener state: Listening [not supported]

RDP.ini: 2017.12.27

Reinstall of RDPWrapper doesnt help.

[lalogago]

Same here

Any ideas?

[burluckoff]

Only change termsrv.dll file on old version in system32 directory till...
termsrv18708.zip

[andydld]

I can confirm that the rollback to the older version auf termsrv.dll (like the one burluckoff posted) works with current version of rdpwrappers ini-file.

[NMCowboy]

Worked great for me also - Thanks. I had to reboot this time and I normally don't have to but then it worked so alls well that ends well.

[DATUC]

any update for this allready?

[amrgb]

For the x64 version add the following to the rdpwrap.ini file. This was tested on several of my win8.1 x64 systems.

[6.3.9600.18928]
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=8B25D
LocalOnlyCode.x64=nopjmp
SingleUserPatch.x64=1
SingleUserOffset.x64=36C09
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=45495
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=5D830
SLInitFunc.x64=New_CSLQuery_Initialize

[6.3.9600.18928-SLInit]
bFUSEnabled.x64 =FA054
lMaxUserSessions.x64 =FA058
bAppServerAllowed.x64 =FA05C
bInitialized.x64 =FA060
bMultimonAllowed.x64 =FA064
bServerSku.x64 =FA068
ulMaxDebugSessions.x64=FA06C
bRemoteConnAllowed.x64=FA070

[burluckoff]

On server2012 successfull, but for some time system fail...

[andydld]

Doesnt work an Windows Server 2012 R2. RDPConf says "fully supported", but the Remotedesktopservice (Termservice) crashes.

[amrgb]

This is my first rodeo, so I cannot confidently say what may be causing your problems.

Obviously this only works for x64. Depending on how the program reads the information from the ini, it may be possible that it says that it is supported for x86 because it finds the header, even though there is no variables for the x86 case.

Also, you have to be careful with the formatting of the ini file. From what I found, you must have an empty line at the end of the file. If you paste what I posted to the end of the file, it will likely not have that empty line at the end and will fail.

If it's neither of these, it could be something that's dependent on the configuration. Another user reported success on thread #432

I'll leave my modified ini file to rule out problems with the formatting of the file.

rdpwrap.zip

[andydld]

I confirm that it works under Windows Server 2012 R2.
Thanks @amrgb for the update and the explanation about the "empty line" at the end of the *.ini-file.

[unbrainwasher]

Windows 8.1x64 and Server 2012R2 seems to work fine. And how about the Win8.1x86-Edition?

[Rebelpyr7]

@amrgb

I don't know what you did with your ini file that I didn't do but your's worked on my Windows 8.1 box where my version did not. I can confirm that version of the ini file definitely works.

[EliezerBee]

@burluckoff, thank you very much for your post. I replaced my existing DLL with yours and RDP Wrap works again after only a reboot! Thank you much!

What is the plan going forward?

1. Will we need to keep manually swapping out the DLL with each Windows Update?
2. Assuming RDP Wrap will be updated to get around this issue, will I need to do anything to RDP Wrap to update it?
3. Will I need to get a new "official" version of the DLL at some point?
4. Should I disable any of the Windows Updates - either those that are already installed or any future ones?

@amrgb, regarding your post, do you mean that's all you changed - or did you also replace your DLL as @burluckoff recommended?

[amrgb]

@EliezerBee

For the termsrv version 6.3.9600.18928 x64 the only thing you need is my .ini file. No need to replace the dll.

I think many users don't understand how the rdpwrap works. In a nutshell, starting with version 1.5 all that is needed for the rdpwrap to work with newer versions of termsrv is to update the rdpwrap.ini file with the correct offsets for the new version of termsrv. In my first post here you see the kind of information that needs to be added to support a new version.

binarymaster has been updating the .ini file regularly, and when he does it, you can run the update.bat to automaticaly update the new .ini file. In the meantime, we can follow the excellent information he has posted on the mainpage (https://github.com/stascorp/rdpwrap), in particular this link to a video tutorial (How to find offsets for new termsrv.dll versions), and update the .ini file ourselves.

That's what I did. It's not overly complicated, but it's tedious. Specially for binarymaster who has to do dozens of versions (I just did for the version I needed). If we learn to this ourserlves, we can then post here to help others and, hopefully, after enough confirmations that it's working binarymaster may use that information to update the official .ini file and save him some time.

[Flexperte]

Thanks @amrgb your rdpwrap.ini worked perfect (Windows 8.1).

But I ran into unexpected difficulties replacing the original .ini with yours, as adjusting permissions was not enough because the file was permanently "in use". Worked neither: uninstalling RDP Wrapper, placing your .ini, then installing again - because the installer would overwrite it with the latest official version. Write-protecting the .ini resulted in the installer aborting mid-way. I finally resorted to blocking the github server in the hosts file - that worked.

Am I missing something? How do you edit or replace rdpwrap.ini?

[binarymaster]

Am I missing something? How do you edit or replace rdpwrap.ini?

180f411

[amrgb]

@Flexperte

In my case, I just copy and pasted. If I drag the file to the "C:\Programs\RDP Wrapper" folder it fails, which seems odd. But if I copy and paste it on this folder, it works. I made sure that my administrator account is the owner and has full control permission on the original .ini file.

By the way, this is with rdpwrap working, since I'm doing this through rdp. To load the new .ini you then have to restart the rdpwrap by running the command RDPWInst -r. You lose the rdp connection momentarily but it should come back. To be safe, do this step from teamviewer to have a backup access to the remote computer in case the terminal service doesn't come back up.

Edit to add: after you update the .ini, you don't need to do nothing for it to stay there. If you try to run the update.bat, it will say that it doesn't have a new version and will leave the updated .ini in place.

[Wajahat234]

i m using windows server 2012 r2 please help me out

[burluckoff]

See comments, them have answer on your question...

[Wajahat234]

i have try all the above solutions but i am still getting same error.

[ivanmara555]

confirm the same problem win8.1x64 termsvr.dll 6.3.9600.18928 from 26.01.2018 ... doesnot working !

[ivanmara555]

the working solution for me win8.1x64 6.3.9600.18928 from 26.01.2018 is add sections to ini file from this post: #432 ... please add to ini !

[DakotaBcn]

thanks @amrgb the ini updated work in Windows 2012R2

[sjoerdloeve]

Is there already a fix for this problem? Running into the same problems.

[binarymaster]

PR #436 is pending.

[TLBM]

Hi!

Tried the modified ini-file on a german Windows 8.1 Pro x64 with all updates, but it is not working anymore though it reads now "[fully supported]". Also tried the one from #432 and the 1nd1g0 commit.

The second user get's a message that a user is already logged-in and that he will be disconnected.

[tangsg]

I also have this problem and have not fixed it yet.

[easy1481437320]

i m using windows10 Pro please help me out i try run install.bat --> updat.bat --> RDPConf

[sjoerdloeve]

@easy1481437320 Windows 10 Pro has remote desktop standard available, you can use it without this program. Go to system properties -> remote and set allow remote connections to this computer

[easy1481437320]

@sjoerdloeve
Thanks for your quick response，but how can i Multiuser remote login without the tool?

[sjoerdloeve]

@easy1481437320 Not sure if it's possible to connect multiple users out of the box. But you're responding to an issue for version 6.3.9600.* while your version is 10.0.17134.*. Perhaps you should search for issues with this version number, like: #721

[easy1481437320]

@sjoerdloeve ok thank you for your help

[easy1481437320]

@sjoerdloeve Thank you so much !!! my problem was solved accroding to #721