New version 10.0.18362.657

[AaronKelley]

This was released today through Windows Update. I used the same codes as for the previous version, 10.0.18362.267, and it seems to work (after service restart). I was able to log in via remote desktop as a different user while a console session was active. Anyone have issues?

[10.0.18362.657]
LocalOnlyPatch.x86=1
LocalOnlyOffset.x86=B7D06
LocalOnlyCode.x86=jmpshort
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=82FB5
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x86=1
SingleUserOffset.x86=50535
SingleUserCode.x86=nop
SingleUserPatch.x64=1
SingleUserOffset.x64=0DBFC
SingleUserCode.x64=Zero
DefPolicyPatch.x86=1
DefPolicyOffset.x86=50269
DefPolicyCode.x86=CDefPolicy_Query_eax_ecx
DefPolicyPatch.x64=1
DefPolicyOffset.x64=1FE15
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x86=1
SLInitOffset.x86=5A77A
SLInitFunc.x86=New_CSLQuery_Initialize
SLInitHook.x64=1
SLInitOffset.x64=22DDC
SLInitFunc.x64=New_CSLQuery_Initialize

[10.0.18362.657-SLInit]
bInitialized.x86 =D577C
bServerSku.x86 =D5780
lMaxUserSessions.x86 =D5784
bAppServerAllowed.x86 =D578C
bRemoteConnAllowed.x86=D5790
bMultimonAllowed.x86 =D5794
ulMaxDebugSessions.x86=D5798
bFUSEnabled.x86 =D579C
bInitialized.x64 =F6A8C
bServerSku.x64 =F6A90
lMaxUserSessions.x64 =F6A94
bAppServerAllowed.x64 =F6A9C
bRemoteConnAllowed.x64=F6AA0
bMultimonAllowed.x64 =F6AA4
ulMaxDebugSessions.x64=F6AA8
bFUSEnabled.x64 =F6AAC

[graphixillusion]

It seems that it's working good...

[dawidmosk]

Working good for me too... without problems (checked on 15 users) :)

[Jamy325]

Yes, working for me too .(10.0.18362.267 replace with 10.0.18362.657)

[Profres]

I'm a bit unclear on this. Do I add the lines provided by AaronKelley to the end of my existing ini file or is it the complete rdwrap.ini?

[asmtron]

use autoupdate fort the new 18363.657
#859

[UrlzWolf]

After use autoupdate, all work perfect!!! Thanks.

[MrGreenCol]

use autoupdate fort the new 18363.657
#859

Cool ! Again

[NMCowboy]

Works like a charm. Looks like MSFT is making a few changes with GitHub!

[ItsRaichura]

I'm a bit unclear on this. Do I add the lines provided by AaronKelley to the end of my existing ini file or is it the complete rdwrap.ini?

You can add these line below the existing lines. It'll work.

[milenpenev]

After adding the code termservice is not starting. Also autoupdate is not working for me. Could you please help me?

[TGeRi]

Same here. :(
I see v "10.0.18362.267".
Before the ini-update from the first comment in this thread: not supported.
After ini-update: fully supported, BUT: NOST LISTENING. :(

It was working until yesterday. :(

Thanks for your help in advance!

Br,
Greg

[NMCowboy]

Thee was a new release yesterday - 18362-657
You are using 267

[TGeRi]

Thank you!!! I figured it out, everything works like a charm! Note to all: there MUST BE an empty line on the end of the ini file! This took me a good 30 mins to figure out (thanks to another forum post). :)

[jvalencia167]

Muchas gracias perfecto

[guibrg123321]

Olá, pra mim não funciona, é full suportado, está ouvindo, mas não conecta multiplos usuários.
tentei net stop termservice mas ele nao conclui consegue finalizar o serviço

[saurav-biswas]

Not working for me....

[TGeRi]

What do you get with the config tool?

[Baiony]

@AaronKelley: Can you help us with the instructions for patching the *.dll file (.657) ? Thank you in advance !

[graphixillusion]

@saurav-biswas the installation it's easy. delete everything and start from scratch:

1. download the official release
2. install the usual way
3. go to Program Files\RDP Wrapper
4. double click on "rdpwrap.ini" file
5. delete everything and paste the content of this file: rdpwrap.txt
6. save the file and restart the computer
7. enjoy

[XOXE]

thank!!!, work!!
This is are the instruction to do this and work for me:

1. Open an admin CMD prompt and stop the service with "net stop termservice"
2. go to C:\Program Files\RDP Wrapper
3. open the file rdpwrap.ini and go to the last line and paste the code
4. save the file and start the service with "net start termservice" in CMD.

[jelenkovicn]

Thanks. It works.

[Baiony]

39813C0600000F845D610100 =>> B80001000089813806000090

047411488D1577 =>> 04EB11488D1577

58010000FF15F7 =>> 58000000FF15F7

[longsoft-dev]

@asmtron Thanks so much for your autoupdater. Works a treat for 18362.657!

[kbuffington]

This is not working for me today after updating to Windows 1909. Tried it manually and with the auto updater. Everything shows as good on the config check, but it won't let a concurrent session start.

Anyone have ideas?

Edit: Nevermind, the issue was the autoupdater couldn't find RDPWInst.exe because it wasn't in the same directory. Copy that over and re-running autoupdater and everything is good again.

[guibrg123321]

no windows 10 x86 NÃO FUNCIONA, SOCORRO!

[stepm65]

No more than 17 sessions are connected, what could be the reason? In Windows Settings, set the limit for simultaneous connections to 999.

[hb02]

use autoupdate fort the new 18363.657
#859

Cool ! Again

hadn't heard about the autoupdate.bat - always used the update.bat

Thanks

[affinityv]

@stepm65 There is another reason for the limitation of sesssions other than setting the allowable limit above 16 or stupidly high. That other reason may have to do with resource limits otherwise. Not sure how you fix that, but others may have more information.

[LGx0]

Hello,
Doesn't work. Build: 18363.657 (Windows 10 Pro x64), &
processed file: c:\Windows\System32\termsrv.dll Successfully processed 0 files; Failed processing 1 files.

Can u help me pls? Download latest rdpwarp.ini but.

[TGeRi]

Does your ini have "657" sections? Check it with notepad? If not, copy from here, paste to the end of your ini, put an empty line to the end, save (you have to run notepad as admin). Restart, check again!

[francwalter]

Does your ini have "657" sections? Check it with notepad? If not, copy from here, paste to the end of your ini, put an empty line to the end, save (you have to run notepad as admin). Restart, check again!

Thanks TGeRi, I checked this on a W10pro PC and the 657 section was still missing.
Works now :)

EDIT: I was wrong, the RDP Wrapper Config Tool shows all good:

But in fact, I can not connect 2 concurrent sessions, even with 2 different users (second user: "admin"). The actual logged in user (physically logged in) would be disconnected if I would continue to log in the second user:

and:

[francwalter]

But in the end, I found the working ini from feb 2020 from issue #859 and with that it works goodly 👍
On my Windows 10 Pro (64) PC (with W10 v1909 and termsrv.dll 10.0.18362.657) and with a W10 Enterprise VM (with W10 v1803 and termsrv.dll 10.0.17134.1304)
EDIT: and on Windows 8.1-64 Ent.

[gamma-577]

This was released today through Windows Update. I used the same codes as for the previous version, 10.0.18362.267, and it seems to work (after service restart). I was able to log in via remote desktop as a different user while a console session was active. Anyone have issues?

[10.0.18362.657]
LocalOnlyPatch.x86=1
LocalOnlyOffset.x86=B7D06
LocalOnlyCode.x86=jmpshort
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=82FB5
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x86=1
SingleUserOffset.x86=50535
SingleUserCode.x86=nop
SingleUserPatch.x64=1
SingleUserOffset.x64=0DBFC
SingleUserCode.x64=Zero
DefPolicyPatch.x86=1
DefPolicyOffset.x86=50269
DefPolicyCode.x86=CDefPolicy_Query_eax_ecx
DefPolicyPatch.x64=1
DefPolicyOffset.x64=1FE15
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x86=1
SLInitOffset.x86=5A77A
SLInitFunc.x86=New_CSLQuery_Initialize
SLInitHook.x64=1
SLInitOffset.x64=22DDC
SLInitFunc.x64=New_CSLQuery_Initialize

[10.0.18362.657-SLInit]
bInitialized.x86 =D577C
bServerSku.x86 =D5780
lMaxUserSessions.x86 =D5784
bAppServerAllowed.x86 =D578C
bRemoteConnAllowed.x86=D5790
bMultimonAllowed.x86 =D5794
ulMaxDebugSessions.x86=D5798
bFUSEnabled.x86 =D579C
bInitialized.x64 =F6A8C
bServerSku.x64 =F6A90
lMaxUserSessions.x64 =F6A94
bAppServerAllowed.x64 =F6A9C
bRemoteConnAllowed.x64=F6AA0
bMultimonAllowed.x64 =F6AA4
ulMaxDebugSessions.x64=F6AA8
bFUSEnabled.x64 =F6AAC

Thank you AaronKelley! your offsets worked like a charm! :-)

-Gamma

[affinityv]

A "guess" INI file section is very bad, how do we know it is correct?! Anything done this way should be very suspect; we need the good people whom can use the IDA to get accurate and correct values that we can properly trust.