Steam In-Home Streaming: Fix the "screen is locked on the remote computer" error
Steam In-Home Streaming is an excellent way to stream Windows-based Steam games to other platforms (not just Mac and Linux, but even to other Windows machines with lower-performance hardware).
However, there is a compatibility issue between Microsoft Remote Desktop and Steam In-Home Streaming. Frequently, attempts to start a Steam streaming session after a Microsoft Remote Desktop session fail with the following error:
"The screen is locked on the remote computer."
Apparently, this is an issue with the way that Microsoft Remote Desktop (either the client or the server) terminates a terminal services session: something about the session is being left open on the server, thus locking the session and preventing a new session for the same user.
This conclusion is supported by the following observation. One of the only reliable solutions to this problem is to terminate the session *not* by closing the app, but by running the following command at an administrative command prompt:
for /f "skip=1 tokens=3 usebackq" %%s in (`query user %username%`) do (%windir32%\System32.tscon.exe %%s /dest:console)
Running that command (either live or as a script) causes the Terminal Services session to end on the client machine - and for some reason, Steam no longer displays the "locked" message and works perfectly.
This is a very widespread issue, and one that Valve has been unable to address for *several years* now. Just do a web search for "steam in-home streaming screen is locked" to see a high hit count, or look at the following links:
when I copy and paste that string it tells me "%%s was unexpected at this time."