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

Troubleshooting steps for 10.0.17134.706, "Access denied", "Not Listening", "[not supported]" #765

Closed
Cobertos opened this issue Apr 29, 2019 · 4 comments

Comments

@Cobertos
Copy link

Cobertos commented Apr 29, 2019

I seemingly ran into every common issue while installing RDPWrap, so I just wanted to put together a troubleshooting guide to pull together all the information in the many other issues.
I'm running 10.0.17134.706 for reference.

Here's the status I ran into and how each one was fixed.
Wrapper Status: Installed
Service State: Running
Listener State: Not Listening

To fix this, you need the most up to date .ini file (located in C:\Program Files\RDPWrapper\rdpwrap.ini). The most comprehensive one I found was this one from Zeljko Manjkas. After downloading this and replacing the original .ini, you need to restart the service using RDPWInst.exe -r. After you have the right .ini with the right offsets for termsvr.dll and restart the service, this should go green. If not, open the .ini file and do a Ctrl+F for your windows version number. If it's not in there, you either need to make it yourself by disassembling the original .dll or wait for another developer to help you out.

[not supported] / "Access denied" when logging in with RDPCheck.exe

I found when using RDPCheck.exe, I would get an "Access denied" error after logging in. Some people suggest modifying the permissions on the rdpwrap.dll in C:\Program Files\RDPWrapper\rdpwrap.dll to allow for full control but this did not work for me. I found that my issue was related to the default Single session per user checkbox being checked, which is it's default. Unchecking it and restarting the service got me [fully supported]. Thanks to this comment for helping me figure this out. I was reading that this has something to do with newer versions of Windows not supporting the feature or something?

Hope this helps, they're all simple fixes, you just have to know where to look.

@theresnotime
Copy link

Thanks for this 👍

For anyone else, I'm running;

Major  Minor  Build  Revision
-----  -----  -----  --------
10     0      17134  0

and the above mentioned .ini from Zeljko fixed the issue

@silencexuzhaoxing
Copy link

Thank you very much,it solved my problem

@Pengyang233
Copy link

Pengyang233 commented Jun 19, 2019

Thank you very much, it helped me a lot and solved the problem!!!

@sebaxakerhtc
Copy link

Acceptable to #721

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

No branches or pull requests

5 participants