Windows 10: Build 10586 broke RDP Wrapper

I was using RDP Wrapper:
RDP Wrapper Library by StasM Corp.
binarymaster/rdpwrap · GitHub

It allows a Remote Desktop Protocol session to log in as a separate user independent of the user logged in locally. Worked perfect until the 10586 update. Now it is "not supported" *cry

I guess I could look at Team Viewer, but I loved RDP Wrapper because it added the capability I needed completely transparently to Windows 10. I don't suppose anyone has any idea how to fix it?

:)

 

Windows 10 Remote Desktop Connection loses connection

Well,

I too was experiencing disconnection with RDP with the Windows 10 Build 10586. I have to connect to Server 2008R2 and remote desktop is the only way. I was losing connection after about 40 sec.

The FIX: After 5 days of attempting to find an answer on this forum and other threads on the Web, I got something to work.

Start RDP. Select More Options/Local Resources/More and unselect smart cards.

Now RDP maintains connection.

 

Remote desktop Windows 10

I realize this might be an old post. but here's my answer.

Use RDP Wrapper Library

It allows you to set up your windows sort of like a terminal server. Allowing multiple users to connect to you computer. This sorts the problem of windows kicking you out as well.

How to Allow Multiple RDP Sessions in Windows 10 | Windows OS Hub

 

I don't really understand what you're achieving with this that you can't achieve strictly with Windows 10 itself. You can log in with multiple users at the same time in Windows 10, and you can log in as any user remotely with RDP (although only one user can be the active user at any given time, which it seems might be the issue you're trying to overcome... however, the EULA specifically forbids that so discussion of circumventing it would be similar to discussion of piracy).

I don't read Russian, so your links are pointless.

 

Second Link is in english for me.
I am curious what part of the EULA forbids this?

 

I have a desktop computer with a local account on it that is connected to my living room TV and the primary use is as a media player. I would like to be able to log into it remotely in an completely independent session and be able to do maintenance and administrative tasks on it while the local account remains 100% unaffected and continues playing a movie or streaming. Windows 10 does not allow this natively. RDP Wrapper inserted this capability.

This does not violate the EULA. The EULA specifically allows it in paragraph 2.d.(v) because the computer I am using as the remote terminal has the same version of Windows as the desktop computer does.

Team Viewer won't do it for me either because the remote session interferes with the local "user" logged on playing the movie.

 

I suspect you'd be better off asking this at MDL or somewhere similar given that it's more of a hack than something that's designed to work that way.

 

I have the same problem. RDP Wrapper is no longer working.

 

I copied termsrv.dll from Windows 10 Pro build 10240 to Windows\System32 on build 10586 and re-installed RDP Wrapper. The developer of RDP Wrapper needs to update the .ini file for the new .dll version in build 10586. I'm sure he probably will, he updated it to work with Windows 10 before now.

 

I don't quite see how that section does what you claim it does. It ignores section 2.c, which states:

The manufacturer or installer and Microsoft reserve all rights (such as rights under intellectual property laws) not expressly granted in this agreement. For example, this license does not give you any right to, and you may not:
[...]
(iv) work around any technical restrictions or limitations in the software;
(v) use the software as server software, for commercial hosting, make the software available for simultaneous use by multiple users over a network, install the software on a server and allow users to access it remotely, or install the software on a device for use only by remote users;

"multiple users" does not mean humans. It means "user" in the sense that an interactive account is a user.

Regardless, 2.c.(iv) expressly prevents you from working around technical limitations.