search

stascorp / rdpwrap

RDP Wrapper Library
Apache License 2.0
14.56k stars 3.81k forks source link

Looking for 10.0.17763.168 support #606

Open ZooShu opened 5 years ago

ZooShu commented 5 years ago

Just trying the tool for the first time and I'm not sure what I'm doing. Already broke the server once and had to connect via KVM Console to get back on

Any help/steps would be great

https://i.imgur.com/hHgEY6u.png

Thanks in advance

Here's the dll file

https://transfer.sh/LaY0f/termsrv.zip

Davey126 commented 5 years ago

@ditchmagnet - confirming a working solution; thank you. 10.0.17763.195 (10.0.17763.168) x64 PRO

Whon-T commented 5 years ago

Now have RDPWrap working again. However, cannot restrict to single user session despite the box checked. Any suggestions to restrict to one session per user? image

SunshineAndSnow commented 5 years ago

I'm curious why this rdpwrap.ini doesn't get updated with the Update.bat ?

binarymaster commented 5 years ago

Because it is not updated in repository yet.

jaxjexjox commented 5 years ago

Because it is not updated in repository yet.

Howcome though? There's now, definitely a good ini file out there, I got one from someone nearly a week ago and even then, a week ago, i thought it was late.

Davey126 commented 5 years ago

Err...perhaps the developer/maintainer is busy with life or is waiting to insure the proposed changes don't cause other issues.

fragtion commented 5 years ago

Not my project but I would suggest that Priority #1 should be to include any new termsrv offsets for new builds as soon as they are discovered to allow concurrent sessions at the very least, even if other side issues are anticipated. Surely the Issues area would be better suited for users to report bugs with the newer offsets rather than being an experimental/discussion zone where we're explaining to n00bs over and over how to patch their own rdpwrap.ini. There's already an update.bat script, but it's essentially useless if the ini file is years out of date. Microsoft are patching the dll more regularly lately lately so RDPWrap becomes basically useless when the offsets aren't available almost immediately

Having the rdpwrap.ini file in two places also causes confusion - at first I did not even know that RDPWrap installs itself to Program Files and that there is where the file should be updated. Requiring UAC to replace the file in this directory, and needing to tamper with Services manually, seems to defeat the whole objective of this project

I propose that if we push the updated offsets to all users sooner, then we will have a bigger pool of users and developers to report on and resolve any "real" bugs that arise, and the issues area could be focused on dealing with these bugreports rather than duplicate "latest build not working" posts, manual patching tutorials, and pointless forks..

Note: I'm not suggesting that a whole new version/release of Rdpwrap be pushed out unnecessarily on a regular basis (1.6.2 still works great on newer builds) - instead only that a more robust update mechanism for update.bat be employed, so that the script actually functions as intended to provide incremental ini patches without requiring a whole new version number / release of the binaries on the one hand, or users complaining that the update script isn't working or that their build isn't supported, on the other hand. It's no co-incidence that this question "why this rdpwrap.ini doesn't get updated with the Update.bat?" is raised on a regular basis.

Arguably, the automatic update for rdpwrap.ini is the biggest "issue" plaguing this project at this stage, yet it could be the easiest to address with a small change in approach. As a huge fan of this project, I hope to see such changes implemented somehow in the near future

Davey126 commented 5 years ago

↑↑↑ This is the reason why I and many others do not publish hobby works. It ain't commercial project with a dedicated support team. Be thankful for whatever service is provided by (likely) one dude in his/her spare time.

cowwoc commented 5 years ago

Uh, no. As someone who actually publishes open-source software I can say that there is abuse on both sides. On the one hand you have people demanding something for nothing. On the other hand you have people hiding behind terrible projects with "it's free so be happy for what you get". The latter is just as bullshit as the former. Stop polluting the internet with broken-ass projects. This noise prevents others from stepping in with better solutions because they think someone else is already handling it.

In this particular case, it would take the author all of 10 seconds to post: "I am aware of this issue. Thank you for your contributions. I will be release an update in the near future."

For those of you wanting to see a quicker resolution to this issue, I suggest publishing a Pull Request such as https://github.com/stascorp/rdpwrap/pull/612. Then the author just needs one minute to review, click a button, and release an update.

Davey126 commented 5 years ago

Lol - presumed entitlement is a beautiful thing. Good suggestion on the pull request.

Mighty1983 commented 5 years ago

Hey, i am new to rdp. I hope someone can help me. My RDP Check looks good but i can`t open grafik

grafik I got an Error that says: The computer was unable to connect to another console session on the remote computer because a console session is already active.

alexfon commented 5 years ago

Tick the check box "single session per user"

Mighty1983 commented 5 years ago

The same . Restartet and no change grafik

With RDP Checker it works but not with mstsc.exe

Mighty1983 commented 5 years ago

Yes. with RDPcheck.exe i can open more. grafik

alexfon commented 5 years ago

The screenshot shows a RDP to local host. Initiate RDP by another PC.

Mighty1983 commented 5 years ago

From Tablet it works. can i open rdp from local too?

alexfon commented 5 years ago

OS prevents RDP to local host. I know there are some work arounds for XP (e.g. changing standard port for RDP). But I do not know if there are work arounds for Win 10 as well. I have no need for local RDP.

Mighty1983 commented 5 years ago

I just found a solution. Used 127.0.0.2 to rdp local

jaxjexjox commented 5 years ago

Not my project but I would suggest that Priority #1 should be to include any new termsrv offsets for new builds as soon as they are discovered to allow concurrent sessions at the very least, even if other side issues are anticipated. Surely the Issues area would be better suited for users to report bugs with the newer offsets rather than being an experimental/discussion zone where we're explaining to n00bs over and over how to patch their own rdpwrap.ini. There's already an update.bat script, but it's essentially useless if the ini file is years out of date. Microsoft are patching the dll more regularly lately lately so RDPWrap becomes basically useless when the offsets aren't available almost immediately

_Having the rdpwrap.ini file in two places also causes confusion - at first I did not even know that RDPWrap installs itself to Program Files and that there is where the file should be updated.

I can't echo the sentiments of this post any more!

I'm in exactly the same boat, I always thought RDPWrap was running standalone?! My "copy" is in c:!tools\RDPWrap. NO idea it wrote elsewhere, infact I posted on these forums "what INI file?" I didn't know it had one.

The highest priority should be updating the INI file. I know, without question that there's an INI file "out there" 100% compatible with 168, because I got it nearly 2 weeks ago and it fixed me up.

I've set my Windows Update Channel to be slightly slower (as they allow anyhow, only 2 options now?) and hopefully next time this happens, I won't be in the list of bleeding edge users who get done by this - it'll be fixed by the time I'm upgraded.

HOWEVER a big bonus SCREW YOU to Microsoft, who never used to "mess with" the termserv.dll file back in the old days? Under Windows 7 I don't recall this being ruined / wrecked at all. Why is it suddenly dying constanmtly under Windows 10?

Appreciate the good work but we need to work on a solution which makes this program up to date within I dunno, a week ? I don't know if we are STILL having users posting "HELP, it's not working - but we need to fix that.

niwhsa9 commented 5 years ago

@ Tom wrote ( Tom Forever) Just read #611 for the actual data needed ; you should Need Nothing else. … ----------------------------- 10.0.17763.194 - CU KB4471332 - keeps/lifts the termsrv.dll to its file version 10.0.17763.168. Therefore since .165, .167, .168 use the data-offset, which are the same, we have to add to the rdpwrap.ini dated 2018-10-10 ( last.ini in the repository - code: res\rdpwrap,ini). Ensure you have the correct ini file with two ini-sections [10.0.17763.1] , [10.0.17763.1-SLInit] and add then the two sections [10.0.17763.168], [17763.168-SLInit] Keep an eye on Acces Rigths and at least use "stop net termservice" before you exchange the rdpwrap.ini (2018-10-10) with your newly edited ini file. ---read more in #611 Or If is to keen just wait till the updated „official“ and validated Version of rdpwrap.ini will be given into the repository (Code: res\rdpwrap.ini) then you can just push the button after you have updated your OS to Version 10.0.17763.194 (-.1.5). My recommendation is just do your Job in a VM/VBox with the last ISO e.g. even the RTM 17763.1 will do it for any purpose , you want (x64,x86 – Home, Pro, etc). Then you can pick up what you ever need for your purpose. .Good Luck Von: Tom Gesendet: Mittwoch, 12. Dezember 2018 18:41 An: stascorp/rdpwrap Cc: hajubu; Mention Can someone upload the working dll and ini files here?

the solution in issue #611 worked perfectly for my system.

artemmen commented 5 years ago

Вчера пропустил обновление до 168 и все пропало, при том что все зеленое. Только одно соединение и ничего выше не помогло. Хорошо что возможность отката обновлений есть еще, что и спасло после нескольких часов попыток вернуть работоспособность.

Kommunist7304 commented 5 years ago

Когда будет официальное обновление без ручных ковыряний?

When will there be an official update without manual picking?

Davey126 commented 5 years ago

Developer/maintainer doesn't publish a schedule. Check back for updates.

cmhowarth commented 5 years ago

I have tried this and failed so many times now - I don't know what to do next. I had RDPWrap working for release 1803 with no problems. Updating it for 1809 I can't get it to work. I have tried everything in threads 601, 606 and 611. I have Win10 x64 Home v1809. I used the ini file from the other threads, which people say works: rdpwrap.zip I start with it uninstalled.

  1. From an elevated command prompt I run: RDPWInst -i -o.
  2. Then I ran RDPWInst -w image
  3. I did: net stop termservice (it wasn't running so did nothing)
  4. I replaced the C:\Program Files\RDP Wrapper\rdpwrap.ini with the one above.
  5. I then started the termservice again: net start termservice It stayed in a state of "starting". image
  6. I rebooted. The service was still permanently in a state of "starting": image image The only way I can stop it is going into the Task Manager, finding the process and killing it. Nothing obvious in the Event Viewer. I don't understand why I'm finding it so difficult when others aren't and previously I had it working. Can anyone help or have any suggestions?
andrePKI commented 5 years ago

@cmhowarth Chris, first find the version of your termsrv.dll (it is in C:\Windows\System32, rightclick it from Explorer) image Next, go to the directory where you installed RDPWrapper (By default it is in C:\Program Files\RDP Wrapper). Check if the INI files does contain the two sections for your version (.168 in my case):


[10.0.17763.168]

[10.0.17763.168-SLInit]

Make sure the file ends with a newline (i.e. in Notepad you must be able to move the cursor beyond the last line, like this) image (The file in your zip is OK for .168). Make sure the file is in the same folder as rdpwrap.dll, e.g. C:\Program Files\RDP Wrapper. If you made any changes, restart the service. Note that most of things you do require you to do it as Administrator (or click Yes in the User Account Countrol popup window, if any)

andrePKI commented 5 years ago

@jaxjexjox https://github.com/stascorp/rdpwrap/issues/606#issuecomment-451835245
Not sure why you blame Microsoft? They are free to modify their own software at will ;-) Multiple RDP sessions into a Windows10 workstation is not a supported Microsoft scenario. Hence to us it is a matter of keeping up with the changes. Basically it is nothing more than a workaround or hack, and I would not be surprised if it is against the Windows EULA. The fact that so many users find issues in W10 and not W7 is that W7 is more or less stable at this point, whereas W10 is (especially in the preview fast and slow rings) constant improvement. Also I have seen people picking on and even being very rude to the IMHO very clever guy who made this software @binarymaster. A BIG THANK YOU for Stanislav!

alyexe commented 5 years ago

Works for me. Try to add this to c:\Program Files\RDP Wrapper\rdpwrap.ini :

[10.0.17763.168]
LocalOnlyPatch.x64=1
LocalOnlyOffset.x64=77941
LocalOnlyCode.x64=jmpshort
SingleUserPatch.x64=1
SingleUserOffset.x64=132F9
SingleUserCode.x64=Zero
DefPolicyPatch.x64=1
DefPolicyOffset.x64=17F45
DefPolicyCode.x64=CDefPolicy_Query_eax_rcx
SLInitHook.x64=1
SLInitOffset.x64=1ABFC
SLInitFunc.x64=New_CSLQuery_Initialize

[10.0.17763.168-SLInit]
bInitialized.x64 =ECAB0
bServerSku.x64 =ECAB4
lMaxUserSessions.x64 =ECAB8
bAppServerAllowed.x64 =ECAC0
bRemoteConnAllowed.x64=ECAC4
bMultimonAllowed.x64 =ECAC8
ulMaxDebugSessions.x64=ECACC
bFUSEnabled.x64 =ECAD0

Last line MUST be empty Dont forget to "rdpwinst -r" ;)

Davey126 commented 5 years ago

_> > I have tried this and failed so many times now - I don't know what to do next. I had RDPWrap working for release 1803 with no problems. Updating it for 1809 I can't get it to work. I have tried everything in threads 601, 606 and 611.

I have Win10 x64 Home v1809. I used the ini file from the other threads, which people say works: rdpwrap.zip :_ Most others are using Win10 Pro vs Home. Quite possible additional tweaks will be needed to accomodate the latter.

cmhowarth commented 5 years ago

@andrePKI Thanks for the suggestions.

  1. Yes, my termsrv.dll matches yours (except the modified date, which you might expect) image

  2. Yes, my in file had those 2 sections, but the first had different offsets than @alyexe's post (despite others saying it worked for them). I replaced it with the sections from @alyexe 's post above making sure the last line is empty.

  3. Restarted with RDPWrap -r (elevated cmd prompt) Service is still permanently "starting" and not listening. Aargh!

@Davey126 - Yes I am doing it for Win10 Home but that's the point of it. I don't need it for my Win10 Pro machine because that already allows RDP for 1 session, which is all I need. I just need to be able to access my other 2 machines' desktops (1 Pro, 1 Home) from my main system without having to have a KVM switch.

Davey126 commented 5 years ago

@cmhowarth - no challenge on your use case; simply observing what works for most may not be applicable in your situation due to difference in platform. I the past I used rdpwrap on Win 10 Home boxes and appreciated the capability it brought to the table (in violation of the EULA). Good luck.

Hamza31231 commented 5 years ago

I managed to do. I took the file from this post #601 (comment) replaced it at home. And I added lines from the same post to my rdpwrap.ini file. 2

YES !!! THIS WORKS !!! PLEASE DO NOT FORGET TO WRITE-PROTECT YOUR rdpwrap.ini. Otherwise the tool will download new version that das not contain the needed additional marks like discribed here: https://github.com/stascorp/rdpwrap/issues/601

  1. Download newest version rdpwrap
  2. Install RDPwrap normaly
  3. Download newest rdpwrap.ini ( https://github.com/stascorp/rdpwrap/blob/master/res/rdpwrap.ini ) and place it into your rdpwrap install folder
  4. add this lines to your rdpwrap.ini

[10.0.17763.165] LocalOnlyPatch.x64=1 LocalOnlyOffset.x64=77941 LocalOnlyCode.x64=jmpshort SingleUserPatch.x64=1 SingleUserOffset.x64=132F9 SingleUserCode.x64=Zero DefPolicyPatch.x64=1 DefPolicyOffset.x64=17F45 DefPolicyCode.x64=CDefPolicy_Query_eax_rcx SLInitHook.x64=1 SLInitOffset.x64=1ABFC SLInitFunc.x64=New_CSLQuery_Initialize

[10.0.17763.165-SLInit] bInitialized.x64 =ECAB0 bServerSku.x64 =ECAB4 lMaxUserSessions.x64 =ECAB8 bAppServerAllowed.x64 =ECAC0 bRemoteConnAllowed.x64=ECAC4 bMultimonAllowed.x64 =ECAC8 ulMaxDebugSessions.x64=ECACC bFUSEnabled.x64 =ECAD0

  1. Download this termsrv ( https://github.com/stascorp/rdpwrap/files/2588141/termsrv_x64.zip )
  2. replace safely yout termsrv.dll with this new downloaded one
  3. write proctect yout rdpwrap.ini in your install folder (that you downlooaded in step 3 and modified in step 4)
  4. start update.bat

THAT WORKS 100% on 10.0.17763.165

@Developer Team: Sdelajte etot malenkij update poshalusta ! Agromnoje spasibo sa vashu rabotu !

incheyeg commented 5 years ago

hey newbie here :)

trying to make this work on windows 10 pro 1809 17763.253 I seen a thread was opened already for 17763.253 and was closed:

https://github.com/stascorp/rdpwrap/issues/636

the ticket advises this was a duplicate and links to this thread.... doe this mean I can use the fix here or that 1809 17763.253 isn't supported?

basically what I'm trying to achieve here is to rdp into my account through my Mac's Microsoft Remote Desktop app while another user is using a different account on the same pc, is this possible?

cmhowarth commented 5 years ago

Thanks @Hamza31231 , that has now got me to the next stage - it all now shows green and listening. However, I now have the same problem as @spamme2 in that I can't connect from the remote computer. It terminates immediately when trying to connect. I get the same behaviour from the RDPWrap computer itself when using RDPCheck.

Hamza31231 commented 5 years ago

I am busy at the moment, but will answer next week of course.

I had the same Problem but got it working.

I will answer

Thanks

Von meinem iPhone gesendet

Am 18.01.2019 um 09:53 schrieb ChrisH notifications@github.com<mailto:notifications@github.com>:

Thanks @Hamza31231https://github.com/Hamza31231 , that has now got me to the next stage - it all now shows green and listening. However, I now have the same problem as @spamme2https://github.com/spamme2 in that I can't connect from the remote computer. It terminates immediately when trying to connect. I get the same behaviour from the RDPWrap computer itself when using RDPCheck.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/stascorp/rdpwrap/issues/606#issuecomment-455471714, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Asd4bqRHbwGZZOSC_5jkAIm6zZfD4HQuks5vEYtxgaJpZM4ZGYR4.

Hamza31231 commented 5 years ago

Please retry all but WITHOUT the step 5 (so do not replace the termsrv.dll, keep the original one) I remember the problem was about the termsrv.dll !!!

Von meinem iPhone gesendet

Am 18.01.2019 um 09:53 schrieb ChrisH notifications@github.com<mailto:notifications@github.com>:

Thanks @Hamza31231https://github.com/Hamza31231 , that has now got me to the next stage - it all now shows green and listening. However, I now have the same problem as @spamme2https://github.com/spamme2 in that I can't connect from the remote computer. It terminates immediately when trying to connect. I get the same behaviour from the RDPWrap computer itself when using RDPCheck.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/stascorp/rdpwrap/issues/606#issuecomment-455471714, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Asd4bqRHbwGZZOSC_5jkAIm6zZfD4HQuks5vEYtxgaJpZM4ZGYR4.

cples408 commented 5 years ago

working with this file - ini_rdpwrap.zip

p1 p2

cmhowarth commented 5 years ago

Finally working! Thanks @cples408 - that ini file did the trick (I copied back my original termsrv.dll v168 Home) I don't know what's going on but I tried multiple .ini files which people said were working for .168 and none of them worked till now.

hrco1980 commented 5 years ago

i hav problem with rdp wrap winwer 10.0.17763.195 thx

tbishop9 commented 5 years ago

@binarymaster, it's now been 7 weeks since this build was reported. INI files to rectify the issue have been available for most of that time. You seem to be still active on general issue admin, just curious as to why you haven't published the updated INI file/s? Is your plan for the future that everyone will download the tool, find it doesn't work and then have to read through issue tickets to teach themselves how to manually patch the INI file?

jaxjexjox commented 5 years ago

I can't believe the INI file hasn't be updated at this URL yet?

https://github.com/stascorp/rdpwrap/tree/master/res

This is astounding, why has this not been updated? WTF is going on?

cowwoc commented 5 years ago

Looking at https://github.com/binarymaster/ Contribution history I submit to you that this project is dead, either temporarily or permanently, because binarymaster is very active on other projects that seem to interest him more.

Looking at https://github.com/stascorp/rdpwrap/network it seems that https://github.com/tmaguire/rdpwrap is the most active fork of this project and 10.0.17763.168 is supported.

I recommend you try out that fork and report back (post a comment here) whether it's worth moving on to greener pastures.

tbishop9 commented 5 years ago

Thanks @cowwoc, have checked out tmaguire's fork but I can't see where to download the compiled installer and batch files - at https://github.com/tmaguire/rdpwrap/releases I can only download the source code. Any ideas?

cowwoc commented 5 years ago

@tbishop9 Not sure. I suggest asking the author directly. His email is listed here: https://github.com/tmaguire

Mochalo commented 5 years ago

Спасибо всё работает Надо остановить службу изменить ini файл Запустить .

rdpwrap.zip