Listener state: Not listening not supported

[moqiguzhu]

I follow the installation instruction:

• download the latest released RDP WRAPPER, version 1.5
• run the install.bat
• run the RDPCheck.exe -- failed
• run the RDPConf

I see that Windows 10 home edition has already been supported, where am I wrong?
Should I download the source codes and compile myself?

[bubbleguuum]

Confirming the same issue on Windows 10 Home.

[binarymaster]

Why you don't read closed issues?

[bubbleguuum]

Got it but why don't you make a download that just works to avoid the same issue being reported again and again and again ?

[binarymaster]

Indeed... v1.6 released! :)

[EliezerBee]

So does v1.6 now support running a session on one PC (under my username)
then continuing that same session (applications still running) from another
PC (again under my username)?

On Wed, Aug 12, 2015 at 11:58 AM, binarymaster notifications@github.com
wrote:

Indeed... v1.6 released! :)

—
Reply to this email directly or view it on GitHub
#51 (comment)
.

[binarymaster]

So does v1.6 now support running a session on one PC (under my username)
then continuing that same session (applications still running) from another
PC (again under my username)?

No, see this issue: #37

[EliezerBee]

I see in issue #37 #37 that
this has been around since Win8. I've been using it for exactly that on
Win8.1 for quite a while - never had an issue.

So please explain: if this does not work, what exactly does RDPWrapper
accomplish on Windows 10? Isn't that the whole point of it?... (Confused.)

On Wed, Aug 12, 2015 at 12:15 PM, binarymaster notifications@github.com
wrote:

So does v1.6 now support running a session on one PC (under my username)
then continuing that same session (applications still running) from another
PC (again under my username)?
No, see this issue: #37
#37

—
Reply to this email directly or view it on GitHub
#51 (comment)
.

[binarymaster]

I actually have none of these issues on my Windows 10 Virtual Machine, so I can't confirm nor refuse it... You have to test it yourself.

[aiugrivef]

Tested on Win 10 Home edition, both 32 and 64 bits, and indeed rdpwrap does nothing...
TermServ service is not even listening on 3389 port.

[binarymaster]

@aiugrivef
Did you test latest v1.6 release?

[EliezerBee]

Aiugrivef, does it at least accomplish the following? If User A is
physically sitting at and using the "server" - can User B concurrently
access his own login on the server from another computer?

On Wed, Aug 12, 2015 at 12:49 PM, aiugrivef notifications@github.com
wrote:

Tested on Win 10 Home edition, both 32 and 64 bits, and indeed rdpwrap
does nothing...
TermServ service is not even listening on 3389 port.

—
Reply to this email directly or view it on GitHub
#51 (comment)
.

[binarymaster]

does it at least accomplish the following? If User A is
physically sitting at and using the "server" - can User B concurrently
access his own login on the server from another computer?

Yes. See the latest screenshot in the README.md

[moqiguzhu]

Sorry to bother you.
It is the first time that I use issues. Before I post the issue, I have not noticed that there is a column called closed issues.
Never happen next time.

[binarymaster]

Thanks :)