Rdpwrap: OS 10.0.17763.1369 not supported

Created on 22 Jul 2020  ·  15Comments  ·  Source: stascorp/rdpwrap

Hi,

I have OS build 17763.1369 but hen running the RDPConf.exe I get Listener state: Not listening and not supported

It seems that sections [10.0.17763.1369] and [10.0.17763.1369-SLInit] are missing in rdpwrap.ini, event after trying to update.

Does someone knows how to get the correct offsets for this build ?

Thanks in advance.

Cedric

Most helpful comment

It's obvious that 1369 has the same offsets as 771.
Sorry, only have x64 systems here to test.
Enjoy.

`
[10.0.17763.1369-SLInit]
bServerSku.x64 =ECAB8
lMaxUserSessions.x64 =ECABC
bAppServerAllowed.x64 =ECAC4
bInitialized.x64 =ECAB4
bRemoteConnAllowed.x64=ECAC8
bMultimonAllowed.x64 =ECACC
ulMaxDebugSessions.x64=ECAD0
bFUSEnabled.x64 =ECAD4

[10.0.17763.1369]
LocalOnlyPatch.x64 =1
LocalOnlyOffset.x64 =77AD1
LocalOnlyCode.x64 =jmpshort
SingleUserPatch.x64 =1

SingleUserOffset.x64=1339C
SingleUserCode.x64 =Zero
DefPolicyPatch.x64 =1
DefPolicyOffset.x64 =18025
DefPolicyCode.x64 =CDefPolicy_Query_eax_rcx
SLInitHook.x64 =1
SLInitOffset.x64 =1ACDC
SLInitFunc.x64 =New_CSLQuery_Initialize
`
1369

All 15 comments

What version does rdpconf.exe show for the DLL?

Hi,

Wrapper : 1.5.0.0
Service : 10.0.17763.1369

Okay, please upload the DLL so that some clever person can work out the details for the INI sections.

ditto!

remove latest updates for now, worked for me

It's obvious that 1369 has the same offsets as 771.
Sorry, only have x64 systems here to test.
Enjoy.

`
[10.0.17763.1369-SLInit]
bServerSku.x64 =ECAB8
lMaxUserSessions.x64 =ECABC
bAppServerAllowed.x64 =ECAC4
bInitialized.x64 =ECAB4
bRemoteConnAllowed.x64=ECAC8
bMultimonAllowed.x64 =ECACC
ulMaxDebugSessions.x64=ECAD0
bFUSEnabled.x64 =ECAD4

[10.0.17763.1369]
LocalOnlyPatch.x64 =1
LocalOnlyOffset.x64 =77AD1
LocalOnlyCode.x64 =jmpshort
SingleUserPatch.x64 =1

SingleUserOffset.x64=1339C
SingleUserCode.x64 =Zero
DefPolicyPatch.x64 =1
DefPolicyOffset.x64 =18025
DefPolicyCode.x64 =CDefPolicy_Query_eax_rcx
SLInitHook.x64 =1
SLInitOffset.x64 =1ACDC
SLInitFunc.x64 =New_CSLQuery_Initialize
`
1369

Says it is fully supported, but does not connect without logging off active user.

UPDATE: Working after complete uninstall and reinstall of rdpwrap.

@sbozdag Please, only provide properly determined INI sections; I understand it works for you, but it may not work fully and properly.

Says it is fully supported, but does not connect without logging off active user.

It is now working after a complete uninstall and reinstall - not sure why it didn't "take" at first like it usually does.

@s8m
copy this rdpwrap 10.0.17763.1369.zip *.ini file to C:\Program Files\RDP Wrapper and restart your pc
thx to @zzelalex

windows server 2019 datacenter 10.0.17763.1369

положить оба файла из архива в папку
"C:\Program Files\RDP Wrapper"
чтобы лежали так:
"C:\Program Files\RDP Wrapper\rdpwrap.dll"
"C:\Program Files\RDP Wrapper\rdpwrap.ini"
после чего ребутнуть винду и все должно работать "без пинка"

image

rdpwrap_windows_server_2019_datacenter_10.0.17763.1369.zip

windows server 2019 datacenter 10.0.17763.1369

положить оба файла из архива в папку
"C:\Program Files\RDP Wrapper"
чтобы лежали так:
"C:\Program Files\RDP Wrapper\rdpwrap.dll"
"C:\Program Files\RDP Wrapper\rdpwrap.ini"
после чего ребутнуть винду и все должно работать "без пинка"

image

rdpwrap_windows_server_2019_datacenter_10.0.17763.1369.zip

work with me

Hi, can somebody provide the original termsrv.dll with 17763.1369 for me, thanks a lot!

@wenan1130 If you do the following as an admin user in the C:\Windows directory, you may find the original termsrv.dll in one of the sub-directories, it should be around 1MB in size I expect.
dir/s termsrv*dll

When you find the right file, do something like the following with a cmd file in an admin cmd.exe window to replace a bad one in place:

@echo off

rem c:\windows\system32\termsrv.dll needs to be owned by administrators and modify rights enabled

net stop termservice /y
copy found_file_with_path c:\windows\system32\termsrv.dll /y
net start termservice

You want to run it as a cmd file because as part of the process, you will lose connectivity.... but the cmd file will continue to run in the cmd.exe window and restart the termservice facility so that, hopefully, you can reconnect!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

apolyakov2017 picture apolyakov2017  ·  4Comments

isidorosss picture isidorosss  ·  5Comments

eyeTechSolutions picture eyeTechSolutions  ·  5Comments

cakexxx picture cakexxx  ·  6Comments

sihow29 picture sihow29  ·  4Comments