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

rdpwrap.dll x64 unknown crash / exception #39

Closed
binarymaster opened this issue Jul 30, 2015 · 23 comments
Closed

rdpwrap.dll x64 unknown crash / exception #39

binarymaster opened this issue Jul 30, 2015 · 23 comments

Comments

@binarymaster
Copy link
Member

We are experiencing technical issues with x64 version on some machines. There is unknown exception somewhere in the code, here are related comments and logs:
#33 (comment)
#33 (comment)
#33 (comment)
#34 (comment)
#38 (comment)

For the advanced users who encountered the same problem, use Visual Studio 2013 or higher to debug the DLL file and to find actual reason of exception.

Test cases:

  • VirtualBox - Windows 10 Home x64 - no issue
@binarymaster
Copy link
Member Author

@Herjar @hooges8 @flauschi82 @XperianPro @alfred0
I joined your comments into one issue. If someone could help with realtime debugging of DLL file, you are welcome.

@FusixGit
Need your support.

Thanks in advance!

@Lunitur
Copy link

Lunitur commented Jul 30, 2015

Actually I am at the moment installing Visual Studio 2015. I will try to get some debug right now.

@binarymaster
Copy link
Member Author

Thanks! Please note that rdpwrap.dll works in the context of svchost.exe process, so to get actual PID, use tasklist /svc and find which process hosts TermService.

@flauschi82
Copy link

I get an access violation writing the location ("Access violation writing location 0x00007FFC8474F34")

@binarymaster
Copy link
Member Author

@flauschi82
If you are debugging, please provide more information... at least base address and number of line in the code.

@flauschi82
Copy link

The VS breaks inside of the termsrv.dll (Exception 0x00007FFC63F650FF). It seems like it tries to read a location at 0xFFFFFFFFFFFFFFFF - this causes an access violation.

@flauschi82
Copy link

Would it help, if i gave you access to that machine?

@Lunitur
Copy link

Lunitur commented Jul 30, 2015

This is where it fails.

rdpwrap+0x2953:
00007ffe'039d2953 8906 mov dword ptr [rsi],eax ds:00007ffd'fe4cf347=8b48000a

@asulwer
Copy link

asulwer commented Jul 30, 2015

any resolution with win10 pro? I just replaced my ini and it restarting now, so we will see if it works

@alfred0
Copy link

alfred0 commented Jul 30, 2015

asulwer please let us know if that works

@mrkengos
Copy link

just tried the latest ini with win10 pro and also experiencing the not listening status

@gompf01
Copy link

gompf01 commented Jul 31, 2015

I think i have found the solution to this, common ini file issue, happend many times before in different projects ;)

The last line in the ini is missing the CR LF thus the read is incomplete.

After adding the last CR LF, all is fine and the RDP is listening on RTM. at least here.

Chris

@gompf01
Copy link

gompf01 commented Jul 31, 2015

rdpwrapper

@flauschi82
Copy link

It's working like a charm now. Thanks a lot :-) 👍

@gompf01
Copy link

gompf01 commented Jul 31, 2015

You are welcome :)

For all: Of course after editing the file , you need to "Net Start TermService" from the command line to Start the RDP or reboot, both will do.

Chris

@hirolash
Copy link

hirolash commented Aug 1, 2015

gompf01, you sir are a saint, thank you. Something so trivial, yet so important to reminder, adding a blank line at the bottom of the ini file.

@binarymaster
Copy link
Member Author

WisdomWolf helped with adding a workaround, I hope this will help :)

f534a1c

@eXaminator
Copy link

I had a similar problem, but in my case 7and thanks to the screenshot above) I figured out that my ini fily hat unix format line endings, not windows. Changing those fixed the problem for me. :-)

@binarymaster
Copy link
Member Author

RDP Wrapper updated to v1.6, problem with line-breaks solved by adding update feature to the installer.

If someone have this problem with the new version too, let me know.

Notice:
Before updating to v1.6, uninstall previous version first.

@liuwenru
Copy link

can you write a.exe file to use in my computer how to use

@binarymaster
Copy link
Member Author

can you write a.exe file to use in my computer how to use

I didn't understood what you mean. If you're talking about something like help file, everything you need is README.md

@binarymaster
Copy link
Member Author

Seems like this issue was solved after introducing batch update method in the installer.

@danielwalo
Copy link

Same issue on 1.6, sorry. Win10 Home (Norwegian)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests