Rdpwrap: How to add support to a new Windows build? How to get the offset for the ini file?

[lordscales91]

I'm tired of hunting down a working rdpwrap.ini every time Windows 10 updates. I want to learn how to examine the termsrv.dll or whatever and find out the code to paste into into ini file myself.

What do I need to do?

[robbak]

There is a video link on the front page of this github that demonstrates the process - but this is the only documentation that I know of.

http://www.youtube.com/watch?v=FiD86tmRBtk

[affinityv]

Is this something that can actually be automated? I wouldn't think so, but can it?

[sebaxakerhtc]

Is this something that can actually be automated? I wouldn't think so, but can it?

I make it with autoclicker. In this video you can see how it works https://youtu.be/7ZjgehDztBQ

Now it's just for saving my time and not a ideal. But i want to remake it with any open source tool and give it to you all :) To make it by yourself..

[tgrushka]

Abandonware? This hasn't been updated (including the INI) in 2 years...

[lordscales91]

@tgrushka Yeah, sadly this seems an abandonware, and looking through the forks I didn't found any active one either.

@sebaxakerhtc Thank you very much. I'm looking forward to it.

[robbak]

While the owner of this repo doesn't post as often as the rest of us,, the
users are very active, and regularly provide updated ini files on their
repos. Indeed, several of us provide these files on this very thread.

On Fri, 19 Jun 2020 07:02 Lordscales91, [e-mail] wrote:

@tgrushka https://github.com/tgrushka Yeah, sadly this seems an
abandonware, and looking through the forks I didn't found any active one
either.

@sebaxakerhtc https://github.com/sebaxakerhtc Thank you very much. I'm
looking forward to it.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stascorp/rdpwrap/issues/1098#issuecomment-646303987,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMCGIUTSLUYIBWY2ULLKBTRXJ6G7ANCNFSM4OBISOBA
.

[sebaxakerhtc]

While the owner of this repo doesn't post as often as the rest of us,, the users are very active, and regularly provide updated ini files on their repos. Indeed, several of us provide these files on this very thread.
…
On Fri, 19 Jun 2020 07:02 Lordscales91, @.*> wrote: @tgrushka https://github.com/tgrushka Yeah, sadly this seems an abandonware, and looking through the forks I didn't found any active one either. @sebaxakerhtc https://github.com/sebaxakerhtc Thank you very much. I'm looking forward to it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1098 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAMCGIUTSLUYIBWY2ULLKBTRXJ6G7ANCNFSM4OBISOBA .

I started to make ini when rdpwrapper by stascorp was banned from ms side... I use it and i need to have working ini, not more

[affinityv]

@tgrushka Abandonware, please; the project works perfectly well "as is", it just needs the 3rd party support of updates with INI file sections and that happens really well. There is no code that needs to be fixed for this project, that doesn't make it abadonware at all. There is even an a video showing how to get the INI file settings for new termsrv.dll files as required -- that is awesome. Sure it would be good if the project's own INI file got updated, but I believe my version of the INI file has every known INI section to date; it may not be perfect, but many people are able to use it successfully. In fact I know that at least one INI setion is missing a value, so that won't help (but it is an older version, so less of a concern). There have been instances of conflicting INI file sections from two or more INI file providers, one of them must be wrong, but which one? If my INI file doesn't do it for you with the original, stable and excellent project that this is, then I want to know about it so that I can hopefully fix it as needed.

[affinityv]

btw When github caused this project grief recently, I found an alternate site to help with communicating about new INI sections. I do hope this project remains as is, at the very least, but I don't trust Microsoft as the github owners to keep it here. They, Microsoft, and the AV vendors are not helpful, but this project is truly extraordinary and can live on with the absence of github if necessary.

[tgrushka]

Microsoft is terrible. I'm a software engineer for my entire life, and use a Mac for accessibility. And personal preference. And I have friends who own Windows PCs. All I want to do is help them remotely. I cannot worth a damn get RDP to connect to the shadow/console session of Windows 10 Pro, because Microsoft crippled it. Used to work great on older Windows, but no longer. So I've got to install Server 2019 on friends' machines just to get access to the console session so I can help them remotely. I don't want to kick them out when connecting. And thanks for pointing out MS acquired GitHub ... how did that slip under me? Thank you Satya ... what a jerk he is.

[affinityv]

I've done shadowing on Windows 10 Pro / upgraded from Windows 7 Pro (no license cost upgrade). Don't need MS Server product.

I use Linux for my desktop and connect from a trusted IP address to a site with xfreerdp client; if I can't connect direct, then I tunnel through OpenSSH via a Tor .onion service with an authorized key in place (no password login for OpenSSH, especially on a Winblows machine). Once I connect as admin on a Win10 machine, I can do the shadowing from that connection to help the end user.

[tgrushka]

Sorry, not correct. No matter what group policy settings, patched termsrv.dll, Windows Server 2019... xfreerdp cannot connect to /admin (shadow) session. Windows Remote Desktop host session manager still kicks out the user, no matter what I do. Contrary to Microsoft's claim, connect to console:i:1 setting in .RDP file does not/no longer works on Mac client. Neither does adding the /console or /admin switch to the computer name in the RDP client on Mac ... those are gone too. :( What gives? What kind of tricks are they playing on people here?

[affinityv]

I don't go direct shadow with xfreerdp -- once I am connected as admin, then I shadow with 127.0.0.2 localhost. It does work.

[lordscales91]

@affinityv but I believe my version of the INI file has every known INI section to date

Not all of them. I'm using Windows 10 version 1903 build 18362.900

[sebaxakerhtc]

@affinityv but I believe my version of the INI file has every known INI section to date

Not all of them. I'm using Windows 10 version 1903 build 18362.900

Can you share your termsrv.dll?

[lordscales91]

Actually, Windows 10 is starting to bug me about the 2004 update. Probably it's better for me to wait until it forces me to update. Because fixing it now may not last for long.

On another topic. What do you think about creating a Discord server for this? @robbak @affinityv @sebaxakerhtc @tgrushka

Just to have an alternative source for asking / getting updated INI files. Because I'm concerned MS may shut down this repo eventually. Specially if people are sharing their termsrv.dll files (that's another reason why I prefer to wait).

[affinityv]

@lordscales91 We need the version of the termsrv.dll as reported by RDPConf.exe, not the Windows build version....
Discord, maybe... but this project was recently offline for undisclosed reasons, but it's back now. It makes sense to lessen risk of Microsoft taking this out again though.

[binarymaster]

this project was recently offline for undisclosed reasons, but it's back now

If you don't see anything disclosed, it doesn't mean it wasn't disclosed at all. In fact, it was discussed in the RDP Wrapper Telegram chat.

[affinityv]

Is there "anything" you can tell us?
Telegram vs Signal.... isn't Signal more trustworthy and secure?