Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added 6.3.9600.18928 build Support #436

Merged
merged 1 commit into from
May 16, 2018
Merged

Conversation

1nd1g0
Copy link
Contributor

@1nd1g0 1nd1g0 commented Mar 26, 2018

No description provided.

@binarymaster
Copy link
Member

Hello, thanks for the patch!

Could you please also update the timestamp in INI file? This is required for update.bat to be functional.

Also corresponding changes should be added rdpwrap-ini-kb.txt.

@AMSD-AMSD
Copy link

But not working remote app this code(

@1nd1g0
Copy link
Contributor Author

1nd1g0 commented Mar 29, 2018

Correct me if I'm wrong, but RdpWrap tricks terminal server library only.
AFAIK, on some systems RemoteApp functionality needs rdp initialization executable to be tricked also and may require some registry changes as well. As for now there is no such functionality in the app, yet (?).

@AMSD-AMSD
Copy link

You are mistaken. Everything worked at all other assemblies of Windows perfectly. Except how to state in the register what program to start Remote APP, more nothing needs to be done

@1nd1g0
Copy link
Contributor Author

1nd1g0 commented Mar 30, 2018

More likely they took more measures to disable RemoteApp in this update. RdpWrap was indirectly helping you to exploit this functionality cause they did not bother to disable it completely relying on restricted RDP itself. Someone needs to investigate what was changed and where and write a new wrapper for it. As I said before, it could be that some more checks were added or there was partial code removal off the libraries/executables used in the system. Try to temporarily restore the old one rdpinit.exe for starters. If it solves the problem, it should be checked what have changed between releases. May be the author will add the second wrapper for this executable later. It's possible that there are even more changes and more wrapping is needed. In conjunction with registry patches.

@AMSD-AMSD
Copy link

At the roots cut out remote app last update!!! Why? I don't know(

@Dnominated
Copy link

I am a little confused, because I have two Windows 10 boxes signed up for the Insider previews, and both are at build 17133.1. So what is this ...18928? Build?

One is Pro, and one is Home. The Home used to work with the wrapper, and now it doesn't (see my other post). I copied rfxvmt.dll from \system32 and \syswow64, and termsrv.dll from \system32, from the pro system (but first just rfx to see if that fixed the issue). Also, I set the permissions as detailed in my other post, as someone else pointed out in another post.

Yet I still have the Listener State: Not Listening / Not Supported issue.

Tell me what to try because I have a working Pro version of Windows 10 that I can copy system files from.

@AMSD-AMSD
Copy link

Windows 8.1 6.3.9600.18928

@AMSD-AMSD
Copy link

Just copying won't approach, it is necessary to register libraries, also the regedit and so on.

@stascorp stascorp deleted a comment from AMSD-AMSD Apr 13, 2018
Copy link
Member

@binarymaster binarymaster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These files also should be updated: rdpwrap-ini-kb.txt, technical.txt, and README.md.

Take a look at any existing commit diff that adds versions to support.

Thanks!

6.3.9600.18928 (fix #418)
@binarymaster binarymaster merged commit 7dc8817 into stascorp:master May 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants