Rdpwrap: Windows 10 1803 10.0.17134.706 (KB4493464) support

[DarkDaemon1]

Listener state: Not listening Not supported
Please add support for
Windows 10 1803 10.0.17134.706 (KB4493464)
I've replaced termsrv.dll to version 10.0.17134.1 and it works fine yet.
termsrv.zip

[HarryUDM]

After termsrv replacement.dll does not let any user even locally.

[grix25]

@DarkDaemon1
Thanks for update. Problem solved for now or/until next win update.

[SuperSpe]

yes this solved the problem for me too.
thanks

[luisBSBDATA]

Where do I need to place this termsrv.dll?

[DarkDaemon1]

Where do I need to place this termsrv.dll?

you need it to place in System32 folder. Before you shoud stop Remote desktop service and get full rights to delete old termsrv.dll

[luisBSBDATA]

Where do I need to place this termsrv.dll?

you need it to place in System32 folder. Before you shoud stop Remote desktop service and get full rights to delete old termsrv.dll

I got the same result as @HarryUDM had, users can't even login locally (not using RDP).

[ITCMD]

Full steps to do this:
A. Stop the service

1. Open admin command prompt window (search CMD, right click, run as admin)
2. type net stop termservice and press enter
3. Leave window open to start service later (optional)

B. Move new dll

1. Open Explorer, type system32 to go to the system32 folder.
2. Search and find termsrv.dll
3. Open the file's properties.
4. Go to Security.
5. Click Advanced.
6. Click Change next to owner.
7. Type your username and press enter.
8. Press Ok.
9. Back in the security tab (step 4) Click Edit.
10. Under Group or user names Click on your username
11. Check the Allow Checkbox next to Full Control.
12. Press OK.
13. Drag and drop the new termsrv.dll File into the system32 folder. (found here, same link as above)
14. When prompted to replace, hit yes.
15. Now we want to change the settings back.
    16 Follow the same steps to get to the window in step 11.
16. Under your username, uncheck modify and write.
17. Press Ok.
18. Follow the same steps to get to the window in step 7.
19. Now type in NT SERVICE\TrustedInstaller to make TrustedInstaller the owner again.
20. Press Ok.
21. Done!

C. Star the service

1. If you didn't leave the admin window open, open a new one.
2. type net start termservice and press enter
3. Enjoy RDP

Note: if you get an error related to signing in (I.E. it quits right away or says there are too many connections) a restart of the host should fix it. It’s caused by previous attempts still being marked as connected in the windows software, even though it’s not.

[DarkDaemon1]

Yes, instructions is correct. Few years ago I made a bat file to update termsrv automatically. Just put termsrv.dll in the same folder and run as Admin
install.zip

[Scorpio-22]

damn so close.
so i went ahead and followed your instructions in the first post.
and it definitely did something, but a new error message comes up,
'The Local Session Manager serivce failed the sign-in.
The number of connections to this computer is limited and all connnections are in use right now. Try
connecting later or contact your system administrator.'
anyone have any ideas on what i did wrong, or what i should do to proceed?

Restart in safe mode, then restart normally, that should solve it

[jdphukd]

hey guys, this def works.
first try didnt work. but i rebooted the comp, and redid all the steps.
works perfectly now.
thanks darkdaemon and everyone else.

[jaggeri]

Yes this works for me too! :)

I got a "System error 5, access denied" when trying to net stop termservice in cmd prompt window.

So I just went in to the Computer Management and stopped all Remote Desktop services before replacing termsrv.dll. After replacing it, I just restarted all again. No reboot required.

Thanks for the instructions how to replace the termsrv.dll !!

[awhitworth06]

I've followed all the steps multiple times, but it keeps telling me that it can't start the service.

A system error has occurred.

System error 1067 has occurred.

The process terminated unexpectedly.

I tried rebooting, but same issue. The RDPConf is showing [fully supported] now, but it just won't start the service.

Any ideas?

[aa-delite]

It works now, thanks!
Manual by ITCMD is correct, but better stop service using services.msc or Computer Management -> Services. I think it's "Terminal Services" in English local. I couldn't stop it in cmd with Admin rights, got "System error 5, access denied".

[awhitworth06]

I've followed all the steps multiple times, but it keeps telling me that it can't start the service.

A system error has occurred.

System error 1067 has occurred.

The process terminated unexpectedly.

I tried rebooting, but same issue. The RDPConf is showing [fully supported] now, but it just won't start the service.

Any ideas?

Nevermind. Apparently I had an even newer Windows update (KB4493509) installed that this does not support. Uninstalling that fixed the issue.

[HarryUDM]

Да, инструкции верны. Несколько лет назад я сделал файл bat для автоматического обновления termsrv. Просто поставьте termsrv.dll в той же папке и запустить от имени администратора
установки.застежка-молния

It works.

[calvinbay]

Full steps to do this:
A. Stop the service

1. Open admin command prompt window (search CMD, right click, run as admin)
2. type net stop termservice and press enter
3. Leave window open to start service later (optional)

B. Move new dll

1. Open Explorer, type system32 to go to the system32 folder.
2. Search and find termsrv.dll
3. Open the file's properties.
4. Go to Security.
5. Click Advanced.
6. Click Change next to owner.
7. Type your username and press enter.
8. Press Ok.
9. Back in the security tab (step 4) Click Edit.
10. Under Group or user names Click on your username
11. Check the Allow Checkbox next to Full Control.
12. Press OK.
13. Drag and drop the new termsrv.dll File into the system32 folder. (found here, same link as above)
14. When prompted to replace, hit yes.
15. Now we want to change the settings back.
    16 Follow the same steps to get to the window in step 11.
16. Under your username, uncheck modify and write.
17. Press Ok.
18. Follow the same steps to get to the window in step 7.
19. Now type in NT SERVICE\TrustedInstaller to make TrustedInstaller the owner again.
20. Press Ok.
21. Done!

C. Star the service

1. If you didn't leave the admin window open, open a new one.
2. type net start termservice and press enter
3. Enjoy RDP

Thanks, mine working now.

But i can't uncheck the 'modify' and 'write' on my user name. It works anyway.

[1Pekol]

Solution for 32bit termsrv.dll is: (tested on W10 Pro 32bit)

[10.0.17134.706]
LocalOnlyPatch.x86=1
LocalOnlyOffset.x86=ADAB8
LocalOnlyCode.x86=jmpshort
SingleUserPatch.x86=1
SingleUserOffset.x86=36B1C
SingleUserCode.x86=nop
DefPolicyPatch.x86=1
DefPolicyOffset.x86=33579
DefPolicyCode.x86=CDefPolicy_Query_eax_ecx
SLInitHook.x86=1
SLInitOffset.x86=475DD
SLInitFunc.x86=New_CSLQuery_Initialize

[10.0.17134.706-SLInit]
bInitialized.x86 =CBF38
bServerSku.x86 =CBF3C
lMaxUserSessions.x86 =CBF40
bAppServerAllowed.x86 =CBF44
bRemoteConnAllowed.x86=CBF48
bMultimonAllowed.x86 =CBF4C
ulMaxDebugSessions.x86=CBF50
bFUSEnabled.x86 =CBF54

Have a nice day
p.s. Do not ask me for 64bit, I have any 64bit practice.

[sinsinpub]

@1Pekol could you search new offsets for 64bit guys? here is the 64bit termsrv.dll ver 10.0.17134.706:
termsrv.17134.706.zip

btw, @HarryUDM, @luisBSBDATA i have a different version 17134.1 64bit termsrv.dll file, its modtime is 2018-04-12 07:34, several bytes are different with the one of @DarkDaemon1 's. might resolve the issue which one session user cannot be reconnected even from local console.
termsrv.17134.1.zip

[1Pekol]

Sorry, I do not known any 64bit dll version I do not have any 64bit practice. So I hope somebody another from comunity will take some time to solve 64bit.

[sailendra00]

listener state listening but not supported after update to 10.0.17134.706 plese provide me rdpwrap.ini file which supports this version

[luky92]

@1Pekol could you search new offsets for 64bit guys? here is the 64bit termsrv.dll ver 10.0.17134.706:
termsrv.17134.706.zip

btw, @HarryUDM, @luisBSBDATA i have a different version 17134.1 64bit termsrv.dll file, its modtime is 2018-04-12 07:34, several bytes are different with the one of @DarkDaemon1 's. might resolve the issue which one session user cannot be reconnected even from local console.
termsrv.17134.1.zip

I useedd this one as a replacement and it works after restart

[janata]

Please help someone with offsets for 10.0.17134.706. Our 64bits system is down too.

Thank you so much!!

[fre4kyC0de]

All files patched, tests are running ATM.
Second half of 2019-04 updates will follow as sson as tests are finished.
https://github.com/fre4kyC0de/rdpwrap

[bigjqq]

老铁真6666

[easy1481437320]

my problem was solved !! thank you so much!!!!

[007amitgarg]

Please help my system is win 10 64bit 1903 OS Build 18362.53

[ali-95]

help my system is win 10 64bit 1903 OS Build

[simonchen]

@1Pekol could you search new offsets for 64bit guys? here is the 64bit termsrv.dll ver 10.0.17134.706:
termsrv.17134.706.zip
btw, @HarryUDM, @luisBSBDATA i have a different version 17134.1 64bit termsrv.dll file, its modtime is 2018-04-12 07:34, several bytes are different with the one of @DarkDaemon1 's. might resolve the issue which one session user cannot be reconnected even from local console.
termsrv.17134.1.zip

I useedd this one as a replacement and it works after restart

termsrv.17134.1.zip this one works for me on win10 home edition.

[strarsis]

Was able to fix it using some INI from another user - but RDPConf.exe incorrectly indicates an unsupported version, see https://github.com/stascorp/rdpwrap/issues/1054#issuecomment-742637185.