Rdpwrap: Add support for 10.0.15063.1155

[Yurii84]

Hello!
When windows update to 10.0.15063.1155. rdpwrap stopped working.
I found termsrv.dll only in C:\Windows\System32

termsrv.zip

[matheuscanela]

Hi,
I am having the same issue with the new version.
Any news?

[vvburkovsky]

For me, a temporary solution it's delete kb4284874 to downgrade windows 10 pro

[matheuscanela]

Yep, I have done that too

[zimmerma379]

Same issue here. Hoping for a "rdpwrap.ini" update soon.

[binarymaster]

Try duplicating an entry in the INI file from 10.0.15063.296 to 10.0.15063.1155 (run RDPWInst -r right after that), and check out whether it works for you.

[zimmerma379]

Try duplicating an entry in the INI file from 10.0.15063.296 to 10.0.15063.1155 (run RDPWInst -r right after that), and check out whether it works for you.

[Yurii84]

Try duplicating an entry in the INI file from 10.0.15063.296 to 10.0.15063.1155 (run RDPWInst -r right after that), and check out whether it works for you.

I try this to, it no working for me

[Kbotz]

Try duplicating an entry in the INI file from 10.0.15063.296 to 10.0.15063.1155 (run RDPWInst -r right after that), and check out whether it works for you.

Same here, no luck.

[Glandos]

Try duplicating an entry in the INI file from 10.0.15063.296 to 10.0.15063.1155 (run RDPWInst -r right after that), and check out whether it works for you.

Same here. I've duplicated the two sections (with and without -SLInit), the restart is fine, the RDPConf shows only green text, but only one connected user at a time is supported.

[guebert]

I'm not sure, if RDP Wrapper will work with Win10 1803 (64 Bit, Pro).

Could somebody clarify this, please?

Has to be anything changed on a now running RDP Wrapper configuration under 1703 before/after update to 1803?

[BashedCode]

It worked smooth(ish) on 1803. Once downloaded, install.bat worked as administrator. Then the next step was RDPCheck which didn't work as expected. Then RDPConf ran and showed installed/running/listening.
It was a fresh install and was tested to confirm concurrent users.
Service ver: 10.0.17134.1
OS Build: 17134.165

Thanks for your work!

[WoolenWang]

My way to solve this problem is uninstall the windows update (KB4338826),
after success uninstall KB4338826 the Service ver turn to be like this

and it successful support and listen ok

[MrRobot5000]

I'm still seeing this issue. Windows 10 1607 and 1709 appear to be fine. 1703 however is still showing as not a supported version of terminal services.

[CookiePLMonster]

Any news? Seems like plenty of people are affected, and uninstalling updates is a sub-optimal solution.

[binarymaster]

@CookiePLMonster the project is open source and anybody is welcome to contribute. I'm busy with other projects right now.

[CookiePLMonster]

Looking at the INI file, are x64-only submissions even accepted? If not, how one would get into obtaining this specific DLL file in x86 version from that specific build?

[binarymaster]

are x64-only submissions even accepted

Yes, but it would be more preferable to add both.

how one would get into obtaining this specific DLL file in x86 version from that specific build?

Either you have some x86 machines with Windows 10 installed, or search in the Internet (sometimes I use WZor's UUP archives).

[fre4kyC0de]

x64 offsets (no x86 version):

[10.0.15063.1155]
; no x86 version
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=8CB01
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=15EA4
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=FAE5
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=234DC
SLInitFunc.x64=New_CSLQuery_Initialize

[10.0.15063.1155-SLInit]
; no x86 version
bInitialized.x64 =E9468
bRemoteConnAllowed.x64=E946C
bMultimonAllowed.x64 =E9470
ulMaxDebugSessions.x64=E9474
bFUSEnabled.x64 =E9478
bServerSku.x64 =E9484
lMaxUserSessions.x64 =E9488
bAppServerAllowed.x64 =E948C

[phrsn]

Thanks! Works like a charm!

[MrRobot5000]

Thanks! It appears to be working!

[fre4kyC0de]

corrected one typo