search

stascorp / rdpwrap

RDP Wrapper Library
Apache License 2.0
14.66k stars 3.83k forks source link

Windows 10 1803 10.0.17134.706 (KB4493464) support #721

Open DarkDaemon1 opened 5 years ago

DarkDaemon1 commented 5 years ago

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 commented 5 years ago

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

grix25 commented 5 years ago

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

SuperSpe commented 5 years ago

yes this solved the problem for me too. thanks

luisBSBDATA commented 5 years ago

Where do I need to place this termsrv.dll?

DarkDaemon1 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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

It works.

calvinbay commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

@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 commented 5 years ago

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 commented 5 years ago

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

luky92 commented 5 years ago

@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 commented 5 years ago

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

Thank you so much!!

fre4kyC0de commented 5 years ago

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 commented 5 years ago

老铁真6666

easy1481437320 commented 5 years ago

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

007amitgarg commented 5 years ago

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

ali-95 commented 5 years ago

help my system is win 10 64bit 1903 OS Build

simonchen commented 4 years ago

@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 commented 3 years ago

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.

havkacik commented 2 years ago

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.

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:

  1. 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!
  2. changed the owner from TrustedInstaller to Administrator and then back
  3. Restarted services in between.

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

image

DennisJacobs1992 commented 2 years ago

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

RDPConf seems to be ok: image

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

Someone any idea what could be wrong here?

Scorpio-22 commented 2 years ago

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

DennisJacobs1992 commented 2 years ago

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

image

Unfortunately this doesn't work for me

Scorpio-22 commented 2 years ago

Something is missing, you contact me, WhatsApp +573505554727

sultanmansoor40 commented 1 year ago

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.

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

auto-update-user commented 1 year ago

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 https://github.com/stascorp/rdpwrap/issues/721#issuecomment-1763821528, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALKNFAP3RUAWCNHMAFMDJ3TX7TI5BAVCNFSM4HEY5VJKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZWGM4DEMJVGI4A . You are receiving this because you commented.Message ID: @.***>

sultanmansoor40 commented 1 year ago

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 commented 1 year ago

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 https://github.com/stascorp/rdpwrap/issues/721#issuecomment-1764234175, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALKNFAKBDC66UPWRFNOMEMTX7UIJDAVCNFSM4HEY5VJKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZWGQZDGNBRG42Q . You are receiving this because you commented.Message ID: @.***>

sultanmansoor40 commented 1 year ago

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:

  1. sc config TermService type= own
  2. If you have antivirus software, try to add rdpwrap.dll to exclusions
  3. Create file rdpwrap.txt in the root of system disk (for example C:\rdpwrap.txt)
  4. Restart PC
  5. 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