Windows 10 1803 10.0.17134.706 (KB4493464) support #721

DarkDaemon1 · 2019-04-10T06:41:46Z

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 · 2019-04-10T07:47:28Z

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

grix25 · 2019-04-10T08:24:17Z

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

SuperSpe · 2019-04-10T08:25:05Z

yes this solved the problem for me too.
thanks

luisBSBDATA · 2019-04-10T10:35:34Z

Where do I need to place this termsrv.dll?

DarkDaemon1 · 2019-04-10T11:22:46Z

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 · 2019-04-10T13:28:17Z

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 · 2019-04-10T15:04:15Z

Full steps to do this:
A. Stop the service

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

B. Move new dll

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

C. Star the service

If you didn't leave the admin window open, open a new one.
type net start termservice and press enter
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 · 2019-04-10T18:53:16Z

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 · 2019-04-11T01:09:28Z

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 · 2019-04-11T01:13:00Z

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 · 2019-04-11T02:25:35Z

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 · 2019-04-11T05:44:35Z

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 · 2019-04-11T06:17:58Z

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 · 2019-04-11T06:24:58Z

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 · 2019-04-11T06:53:30Z

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

It works.

calvinbay · 2019-04-11T07:02:16Z

Full steps to do this:
A. Stop the service

Open admin command prompt window (search CMD, right click, run as admin)

type net stop termservice and press enter

Leave window open to start service later (optional)

B. Move new dll

Open Explorer, type system32 to go to the system32 folder.

Search and find termsrv.dll

Open the file's properties.

Go to Security.

Click Advanced.

Click Change next to owner.

Type your username and press enter.

Press Ok.

Back in the security tab (step 4) Click Edit.

Under Group or user names Click on your username

Check the Allow Checkbox next to Full Control.

Press OK.

Drag and drop the new termsrv.dll File into the system32 folder. (found here, same link as above)

When prompted to replace, hit yes.

Now we want to change the settings back.
16 Follow the same steps to get to the window in step 11.

Under your username, uncheck modify and write.

Press Ok.

Follow the same steps to get to the window in step 7.

Now type in NT SERVICE\TrustedInstaller to make TrustedInstaller the owner again.

Press Ok.

Done!

C. Star the service

If you didn't leave the admin window open, open a new one.

type net start termservice and press enter

Enjoy RDP

Thanks, mine working now.

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

1Pekol · 2019-04-11T08:18:08Z

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 · 2019-04-11T09:26:20Z

@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 · 2019-04-11T09:34:52Z

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 · 2019-04-11T11:27:48Z

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

luky92 · 2019-04-11T12:27:03Z

@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 · 2019-04-11T20:24:58Z

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

Thank you so much!!

fre4kyC0de · 2019-04-11T22:30:18Z

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 · 2019-04-17T04:53:49Z

老铁真6666

easy1481437320 · 2019-04-30T09:26:31Z

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

007amitgarg · 2019-05-13T10:20:37Z

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

ali-95 · 2019-08-20T08:41:38Z

help my system is win 10 64bit 1903 OS Build

simonchen · 2020-08-11T04:02:06Z

@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.

havkacik · 2022-01-15T18:12:06Z

Full steps to do this: A. Stop the service

Open admin command prompt window (search CMD, right click, run as admin)

type net stop termservice and press enter

Leave window open to start service later (optional)

B. Move new dll

Open Explorer, type system32 to go to the system32 folder.

Search and find termsrv.dll

Open the file's properties.

Go to Security.

Click Advanced.

Click Change next to owner.

Type your username and press enter.

Press Ok.

Back in the security tab (step 4) Click Edit.

Under Group or user names Click on your username

Check the Allow Checkbox next to Full Control.

Press OK.

Drag and drop the new termsrv.dll File into the system32 folder. (found here, same link as above)

When prompted to replace, hit yes.

Now we want to change the settings back.
16 Follow the same steps to get to the window in step 11.

Under your username, uncheck modify and write.

Press Ok.

Follow the same steps to get to the window in step 7.

Now type in NT SERVICE\TrustedInstaller to make TrustedInstaller the owner again.

Press Ok.

Done!

C. Star the service

If you didn't leave the admin window open, open a new one.

type net start termservice and press enter

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.

Thanks for posting this. It seems that this solved the problem for me in for version 10.0.19041.1387 running on Windows 10 Home 21H2 with version 10.0.19044 Build 19044.

Basically what I did:

changed the permissions of file termsrv.dll file to full access to Administrator (and couldn’t go back) - so this is what caused the fix!
changed the owner from TrustedInstaller to Administrator and then back
Restarted services in between.

So I believe changing the permissions for Administrator resolved the issue.

DennisJacobs1992 · 2022-09-11T11:31:21Z

This doesn't seem to work for me, I followed the steps above:

RDPConf seems to be ok:

I am in Windows 11 Pro trying to solve the 0x708 error:

Someone any idea what could be wrong here?

Scorpio-22 · 2022-09-11T14:16:25Z

Hello, You must add every user to an Group: "RDP sessions users", in Computer Management. Try that

DennisJacobs1992 · 2022-09-11T16:51:40Z

Hello, You must add every user to an Group: "RDP sessions users", in Computer Management. Try that

Hey, Thank you for your message. I have put all users I want to be able to RDP in one group called: "Remote Desktop Users" and I also created a new group with the same members called "RDP sessions users" since you mentioned this specific naming

Unfortunately this doesn't work for me

Scorpio-22 · 2022-09-11T17:15:24Z

Something is missing, you contact me, WhatsApp +573505554727

sultanmansoor40 · 2023-10-16T06:37:54Z

Full steps to do this: A. Stop the service

Open admin command prompt window (search CMD, right click, run as admin)

type net stop termservice and press enter

Leave window open to start service later (optional)

B. Move new dll

Open Explorer, type system32 to go to the system32 folder.

Search and find termsrv.dll

Open the file's properties.

Go to Security.

Click Advanced.

Click Change next to owner.

Type your username and press enter.

Press Ok.

Back in the security tab (step 4) Click Edit.

Under Group or user names Click on your username

Check the Allow Checkbox next to Full Control.

Press OK.

Drag and drop the new termsrv.dll File into the system32 folder. (found here, same link as above)

When prompted to replace, hit yes.

Now we want to change the settings back.
16 Follow the same steps to get to the window in step 11.

Under your username, uncheck modify and write.

Press Ok.

Follow the same steps to get to the window in step 7.

Now type in NT SERVICE\TrustedInstaller to make TrustedInstaller the owner again.

Press Ok.

Done!

C. Star the service

If you didn't leave the admin window open, open a new one.

type net start termservice and press enter

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.

I have tried this and even tried restarting the PC multiple times . but the remote service got an unstable status it gets running then show started and again changed to started. Also i have received below error at the first time.

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.

Now I am not able to run both of these 2 services simultaneously.

auto-update-user · 2023-10-16T10:46:19Z

Did you edit your ini manually if so make sure there's no extra new line at the end of the file pon., 16 paź 2023, 08:38 użytkownik Sultan Mansour Raofi < ***@***.***> napisał:

…

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 <https://github.com/stascorp/rdpwrap/files/3062444/termsrv.zip>, 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. I have tried this and even tried restarting the PC multiple times . but the remote service got an unstable status it gets running then show started and again changed to started. Also i have received below error at the first time. 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. — Reply to this email directly, view it on GitHub <#721 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALKNFAP3RUAWCNHMAFMDJ3TX7TI5BAVCNFSM4HEY5VJKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZWGM4DEMJVGI4A> . You are receiving this because you commented.Message ID: ***@***.***>

sultanmansoor40 · 2023-10-16T11:05:41Z

No There is no extra new line and I get this error at the event log viewer
The server {F9A874B6-F8A8-4D73-B5A8-AB610816828B} did not register with DCOM within the required timeout.
and below
The Remote Desktop Services service terminated unexpectedly. It has done this 13 time(s).

auto-update-user · 2023-10-16T11:33:10Z

Try adding that extra line at the end please pon., 16 paź 2023, 13:05 użytkownik Sultan Mansour Raofi < ***@***.***> napisał:

…

No There is no extra new line and I get this error at the event log viewer The server {F9A874B6-F8A8-4D73-B5A8-AB610816828B} did not register with DCOM within the required timeout. and below The Remote Desktop Services service terminated unexpectedly. It has done this 13 time(s). — Reply to this email directly, view it on GitHub <#721 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALKNFAKBDC66UPWRFNOMEMTX7UIJDAVCNFSM4HEY5VJKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZWGQZDGNBRG42Q> . You are receiving this because you commented.Message ID: ***@***.***>

sultanmansoor40 · 2023-10-16T11:41:36Z

no after adding extra new line when I run net start termservice it says:

System error 5 has occurred. Access is denied

Before adding extra new line I did this but nothing happened:

sc config TermService type= own
If you have antivirus software, try to add rdpwrap.dll to exclusions
Create file rdpwrap.txt in the root of system disk (for example C:\rdpwrap.txt)
Restart PC
Check contents of rdpwrap.txt log file

And this Is the content of rdpwrap.txt log file:

SvchostPushServiceGlobals
Loading configuration...
Configuration file: c:\program files\rdp wrapper\rdpwrap.ini
Initializing RDP Wrapper...
Base addr: 0x00007FF9EA440000
SvcMain: termsrv.dll+0x0000000000038510
SvcGlobals: termsrv.dll+0x00000000000397A0
Version: 10.0.19041.3570
Freezing threads...
Patch CEnforcementCore::GetInstanceOfTSLicense
Patch CSessionArbitrationHelper::IsSingleSessionPerUserEnabled
Patch CDefPolicy::Query
Hook CSLQuery::Initialize
Resumimg threads...
<<< SvchostPushServiceGlobals
ServiceMain
<<< ServiceMain

mihalich1988 mentioned this issue Apr 10, 2019

Last Windows Security Update breaks RDPWrap #722

Closed

hajubu mentioned this issue Apr 16, 2019

INI: Add support for new builds (fix #611) #612

Open

sjoerdloeve mentioned this issue Apr 30, 2019

Add support for termsrv 6.3.9600.18928 #418

Closed

This comment was marked as spam.

Sign in to view

havkacik mentioned this issue Mar 6, 2022

10.0.19041.1503 not supported #1697

Open

Windows 10 1803 10.0.17134.706 (KB4493464) support #721

Windows 10 1803 10.0.17134.706 (KB4493464) support #721

Comments

DarkDaemon1 commented Apr 10, 2019 • edited Loading

HarryUDM commented Apr 10, 2019

grix25 commented Apr 10, 2019 • edited Loading

SuperSpe commented Apr 10, 2019

luisBSBDATA commented Apr 10, 2019

DarkDaemon1 commented Apr 10, 2019 • edited Loading

luisBSBDATA commented Apr 10, 2019

ITCMD commented Apr 10, 2019 • edited Loading

DarkDaemon1 commented Apr 10, 2019

Scorpio-22 commented Apr 11, 2019

jdphukd commented Apr 11, 2019

jaggeri commented Apr 11, 2019

awhitworth06 commented Apr 11, 2019

aa-delite commented Apr 11, 2019 • edited Loading

awhitworth06 commented Apr 11, 2019

HarryUDM commented Apr 11, 2019

calvinbay commented Apr 11, 2019 • edited Loading

1Pekol commented Apr 11, 2019 • edited Loading

sinsinpub commented Apr 11, 2019 • edited Loading

1Pekol commented Apr 11, 2019

sailendra00 commented Apr 11, 2019

luky92 commented Apr 11, 2019

janata commented Apr 11, 2019

fre4kyC0de commented Apr 11, 2019

bigjqq commented Apr 17, 2019

easy1481437320 commented Apr 30, 2019

007amitgarg commented May 13, 2019 • edited Loading

ali-95 commented Aug 20, 2019

simonchen commented Aug 11, 2020

This comment was marked as spam.

havkacik commented Jan 15, 2022

DennisJacobs1992 commented Sep 11, 2022

Scorpio-22 commented Sep 11, 2022

DennisJacobs1992 commented Sep 11, 2022

Scorpio-22 commented Sep 11, 2022

sultanmansoor40 commented Oct 16, 2023 • edited Loading

auto-update-user commented Oct 16, 2023 via email

sultanmansoor40 commented Oct 16, 2023

auto-update-user commented Oct 16, 2023 via email

sultanmansoor40 commented Oct 16, 2023

DarkDaemon1 commented Apr 10, 2019 •

edited

Loading

grix25 commented Apr 10, 2019 •

edited

Loading

DarkDaemon1 commented Apr 10, 2019 •

edited

Loading

ITCMD commented Apr 10, 2019 •

edited

Loading

aa-delite commented Apr 11, 2019 •

edited

Loading

calvinbay commented Apr 11, 2019 •

edited

Loading

1Pekol commented Apr 11, 2019 •

edited

Loading

sinsinpub commented Apr 11, 2019 •

edited

Loading

007amitgarg commented May 13, 2019 •

edited

Loading

sultanmansoor40 commented Oct 16, 2023 •

edited

Loading