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
terminal service version : 10.0.18362.836 windows 10 home supported but not listening #1193
Comments
that version 10.0.18362.836 is supported by affinityv's .ini file.
https://github.com/affinityv/INI-RDPWRAP/blob/master/rdpwrap.ini
…On Sat, 31 Oct 2020 at 18:03, islamelarif ***@***.***> wrote:
termsrv.zip
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
That sounds a lot like the "Unix line endings" issue outlined in an issue
currently near the top in the list of problem reports. Check that issue out
and confirm that the file you downloaded doesn't have this problem.
…On Sat, 31 Oct 2020 20:53 islamelarif, ***@***.***> wrote:
i tried the redpwrap.ini that from affinityv's file but unfortunately now
it shows this message
[image: bug]
<https://user-images.githubusercontent.com/33578064/97777296-dbf11480-1b77-11eb-96dd-a7ea8d25a95c.jpg>
i replaced the old file with it and then restarted the computer but still
not listening
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1193 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAMCGIQTZVOFTEL7RSI2Y6TSNPUA7ANCNFSM4TFX6ANA>
.
|
Thats true the file is in theunix code |
Hey, all. I've got the 10.0.18362.836 driver and was having the same issue, with the listener state starting off at "Not listening / not supported," and switching to "not listening / fully supported" after trying affinityv's file and converting it to ANSI with Notepad ++. But then I screwed around with it and got it to work. I'm not quite savvy, so I'll just say what I did, to the best of my memory, and let the big-brains figure out what happened:
There might have been some runs of update.bat mixed in there, but I can't really remember where. Like I said, I have no clue what worked or why. For all I know, the newest ini file might have just gotten updated under my nose while I was tinkering with things. I just thought I'd give a new data point for y'all to chew over. Thank you for coming to my first GitHub post. |
Duplicate of #1083 |
i tried the difference solutions in other threads but unfortunetly none worked for me,
so i you can find my
termsrv.dll file if you can help i will be gratefull
The text was updated successfully, but these errors were encountered: