Listener is not listening on Win 10 Home (build 14997+)

[aiugrivef]

Hello,

Thank you for rdpwrap!

Unfortunately, on Windows 10 Home edition, it is not working anymore since Insider build 15002.
Rdpwrap is fully updated and says "fully supported", but Listener state is "not listening" for some reason.

Thank you!

[binarymaster]

Support for 15007 has been added in 5814e3f, try again.

[aiugrivef]

Hello,

I have updated and tested again on 15007, without success.

It is not working on a Home edition, here is what RDPConf is displaying:

• wrapper: installed
• service: running
• listener: not listening

[johanatan]

I am experiencing the same thing on a fresh WIndows 10 Home install.

[johanatan]

i.e., Listener state: not listening

[binarymaster]

Try this way, maybe it will help: #45 (comment)

(i.e. fully uninstall and install again)

[aiugrivef]

Hello, I have tried again several times today, and it is not working.

I am nowhere near as good as you are, but it looks like M$ have changed their SLC method again starting with 15002...
15002 have public symbols, but I am not good enough to understand them sorry...

[wfmde]

I have the same problem with 15002. Reinstall does not solve the problem.

[CaptainThrowback]

I'm experiencing the same issue on 15007. Already tried a reinstall.

[binarymaster]

Issue confirmed in 10.0.15007.1000.

[binarymaster]

Interesting observation about file sizes between builds:

Build	x86 size	x64 size
10.0.14971.1000	840 KB	998 KB
10.0.14986.1000	840 KB	998 KB
10.0.14997.1001	? KB	1002 KB
10.0.15002.1001	847 KB	1002 KB
10.0.15007.1000	847 KB	1002 KB
10.0.15014.1000	847 KB	1002 KB

So there's something new added in 14997.

[aiugrivef]

Hello,
Same issue with 15014 and 15019 :-(

[aiugrivef]

Hello,
I have tried to debug the TermService, but I am not skilled enough :(
According to me, it looks like the patching of the global variables (bRemoteConnAllowed...) is done well, but this is not enough: the service does not start listening on RDP port.

Maybe there is a new variable?
Maybe the fact that CSQLQuery::Initialize() is not executed is blocking the service launch?

I fear this issue will be worse once Microsoft releases its next public version (probably in 1 month or so) - could you help me to fix this issue please?