Rdpwrap: Shadowing not working after Windows 10 Creators Update

[evdev]

Ever since I updated to Windows 10 Creators Update shadowing computers that have Windows 10 Creators Update installed no longer works. I get an small dialog box that says "Unspecified Error". I tried reinstalling and updating RDPWrap but it hasn't helped. Under version 1607 it worked great.

[evdev]

I have Windows 10 Pro on which RDPWrap is mostly functioning. The listener state is listening. My problem is only with shadowing.

[StAlKeRxXl]

I have the some problem too

[pagslol]

Yea, not an ideal way around it but I uninstalled creators update on the win10 home box, but if you are running Pro why do you need rdpwrap ? I'm assumeing is has something to do with session shadowing?

[kursatu]

I had the same problem, It stopped working on 2 PC's after creaters update
Then I ran the update.bat file that came with the .zip file and it started working again.
I did not need to uninstall it.

[hyun1022]

It seems to work normally after updating, but I can not connect to 127.0.0.2 in windows 10 Creator. How do I connect to 127.0.0.2?

[juneszh]

I have the same issure. my system info show the version is 1703/15063.296, but in RDP CHecker is show ver. 10.0.15063.0. My OS is Windows 10 home (amd64) with the 1703 update. I upload my termsrv.dll hope it can help.
termsrv.zip

[Fedomorro]

I have the same issure.

[simonbjornes]

@binarymaster where are you ;-) We need your perfection!

1703/15063.296 is not working

[MortenGuldager]

discussed in https://github.com/stascorp/rdpwrap/issues/194, but no fix yet

[evdev]

@MortenGuldager As I mentioned previously, this thread is for the issue of shadowing not working. The Windows 10 Pro systems I have have RDP Wrap installed and listening. It functions fine besides the shadowing part (at least for me with Windows 10 Pro).

[MortenGuldager]

@evdev oups my bad, didn't read it carefully enough, probably just saw the screenshots saying "not listening" and thought it was the same issue.

[binarymaster]

I'm pretty sure that the reason of why this is not working is the same as the reason of listener not listening.

[aclar]

Shadowing doesn't work as you can see from the screenshot of a computer with Windows 10 Pro, Version 1703 (OS Build 15063.296). No problems in running thirty-two concurrent RDP sessions, just shadowing. When trying to connect to a session from the command line (mstsc.exe /shadow:%uid% /control /noConsentPrompt), I get a dialog entitled, "Shadow Error", with the text, "Unspecified error". Shadowing always fails whether I'm logged in from a RDP session, the console or whether I'm using the built-in Windows administrator account, another admin-level account, or whether I'm controlling another admin-level account or a non-admin account. I've uninstalled/reinstalled RDP Wrapper v1.6.1 and made sure it had the latest rdpwrap.ini file (Updated=2017-06-10) all to no avail. I've also used multiple Remote Desktop clients, an old one on an XP box and the newest from a second Windows 10 box. If I can be of any assistance in resolving this problem let me know.

[felipog]

Hello!
I have the exact same scenario from @aclar . If there is news about this, let us know. I can provide some info if needed too.
CHeers

[grahamlower]

Please sign into Feedback Hub and up vote
https://aka.ms/Djo3gj (or search for: mstsc shadow broken)

[seanjeanc]

I am having the exact same issue as @aclar ...

Upgraded Win10 Pro to 1703 and lost shadowing capability, with error "Unspecified error". Tried re-installing / update.bat .... but no luck.

I hope someone can help.

[Evengard]

Same problem here. I hope it will get fixed.

[trafsta]

Same issue here :( Eagerly awaiting a fix/workaround

[aclar]

SHADOWING IS WORKING AGAIN!!!!!
I just now downloaded Windows 10 Fall Creators Update from Microsoft (Win10_1709_English_x64.iso, build# 10.0.16299.15) at https://www.microsoft.com/en-us/software-download/windows10ISO, installed it on a new hard drive (but didn't activate it since I don't own a license), created two user accounts with Administrator rights (actually, for one account I simply enabled the built-in administrator account), installed RDP Wrapper v1.6.1, under "Session shadowing mode" selected, "Full access without permission", logged into both user accounts via Remote Desktop (RDC), then successfully shadowed the 2nd user's session from the 1st user's session using a custom batch file that I created that I named, "shadowsession.bat":

@echo off
qwinsta.exe
echo.
set /p uid=Enter session ID to view:
start Mstsc.exe /shadow:%uid% /control /noConsentPrompt

[binarymaster]

SHADOWING IS WORKING AGAIN!!!!!

Looks like it was Windows bug, that was resolved in build 10.0.16299.15.

[Evengard]

In 10.0.16299.19 though the behaviour is same as before update. Though I haven't completely reinstalled the whole system but just upgraded it. It may be the cause.

[aclar]

Evengard: I just now manually updated an older Windows 10 computer with the Fall Creators Update then checked the version from the command prompt by typing "ver" and it reported 10.0.16299.19. I then tested shadowing and it is indeed broken as you experienced. This is bad news because the computer where shadowing worked (version 10.0.16299.15) will undoubtedly fail to shadow when Windows update is ran. So for the record:

Windows 10 Pro

10.0.16299.15 (shadowing works)
10.0.16299.19 (shadowing fails)

[Evengard]

What's interesting is that the service itself is 10.0.16299.15, but the system itself is 10.0.16299.19

I wonder if there is an additional "patch" required for some other files to unlock it.

[Evengard]

I'm actually starting to think that MS disables it intentionally. I wonder if it is working in Enterprise version of Win10.

[ferzal]

The problem is a basic Windows bug. rdpsaproxy.exe does not autostart/trigger when it's supposed to. You need to manually start that process each and every time you want to connect (or keep it alive via your method of choice).

It's a long standing issue that was fixed for a week or so (accidentally it seems). Microsoft is aware of the issue but obviously place it as very low priority (i.e. Don't fix). Maybe it'll get fixed in the new year. Until then - run it yourself. I did get some errors on the host from time to time that didn't make sense to me but the session still ran fine.

Not an RDPWrap issue.

Edit: Just for clarity: rdpsaproxy.exe needs to be running on the host for shadowing to work.

[aclar]

Shadowing Working on Windows 10 Education Version 1709 (OS Build 16299.64 & 125)
I just now installed Windows 10 Education from en_windows_10_education_x64_dvd_6848120.iso, then upgraded it with Fall Creators Update from here:

https://www.microsoft.com/en-us/software-download/windows10ISO

A side benefit of the Fall Creators update is it gets rid of the "Windows 10 Education" watermark embedded into the Desktop near the bottom right of the screen. The Education version that I installed was just "Windows 10 Education" and not the "Windows 10 Education N" variant. I actually prefer the "N" variant since it dispenses with a lot of stuff that I consider to be bloatware. I don't know if additional updates were installed after the Fall Creators Update but when all was said and done I manually checked for additional updates under Windows "Settings" and Windows reported that no additional updates were available. As of 12/18/2017, I confirmed that shadowing worked fine on
Windows 10 Education Version 1709 (OS Build 16299.64)

So for the record here is what I've tested:
Windows 10 Pro Version 1709 (Build 16299.15) - shadowing works
Windows 10 Pro Version 1709 (Build 16299.19) - shadowing fails
Windows 10 Education Version 1709 (Build 16299.64) - shadowing works, tested 12/18/2017

NEW!!
Windows updated itself again and I confirmed that shadowing still worked!
Windows 10 Education Version 1797 (Build 16299.125) - shadowing works, tested 12/18/2017

[ferzal]

Run rdpsaproxy.exe. Win-Run, cmd, shell, shortcut, keepalive. However you
like. It's a windows system file so just run it. That's the manual method.
If you want it to start remotely you'll need to set up a remote trigger or
keep it alive which is not something to go into here. Hopefully Microsoft
will fix the problem soon. Until then, run rdpsaproxy any way you can on
the host before attempting shadow.

On 20 December 2017 at 17:55, Evengard [e-mail] wrote:

Is there any tutorial/instruction on how to actually start correctly this
rdpsaproxy.exe so shadowing works?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stascorp/rdpwrap/issues/247#issuecomment-352981053,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhEmNT9pPYS-FEijUSQ-UdrhfzAexa_Rks5tCK9ygaJpZM4NbvoW
.

[tylerapp]

Since Microsoft refuses to fix the shadow issue, maybe this will help someone in the future.

1. Open notepad and paste –
   $list = get-process | where-object processname -eq rdpsaproxy
   if ($list -eq $null) { start-process rdpsaproxy }

Save as c:\RDP.ps1

1. Open notepad and paste –
   Dim objShell
   Set objShell=CreateObject("WScript.Shell")
   Do
   objShell.Run "powershell.exe -file c:\prep\rdp.ps1", 0
   WScript.Sleep(30000)
   Loop
   Save as C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp\RDP.vbs
2. At startup, the machine will run the vb script and call the ps script, which checks every 30 seconds to see if the rdpsaproxy service is running, and starts it if not. It will also launch the script silently, so you do not have the PowerShell window flashing at the user.

[aryasenna]

So after the Spectre/Meltdown update patch the above workaround mentioned by @ferzal and @tylerapp ceases to work.
Anyone know what can we do to get the shadowing working again?

[Rdnaskel]

It seems like Windows 10 Pro also have been updated and shadowing now works as expected. As @aclar mentioned shadowing working in Win 10 Education 16299.125, now Win 10 Pro is also 16299.125 and shadowing connection worked!

[Evengard]

Surprisingly, I'm on Win 10 Pro 16299.125 but shadowing seems to not working for me... Maybe it's time to do a clean system install anyway, but it doesn't work "out of the box" with an auto updating system.

[SGKarp]

I'm in the same position as Evengard. Win 10 Pro 16299.125. RDPConfig shows service state as 10.0.16299.15. rdpsaproxy is running. Wrapper 1.6.2, updated to 2017.12.27.

But trying to shadow gives me "Access is denied."

If it's relevant, I'm trying to shadow the console session. And yes, I'm trying to do it from a different account on the same machine.

[aclar]

Shadowing has started working again for me on Windows 10 Pro after I received the Spring 2018 update (1803, 10.0.17134.48, May 8, 2018). I first had to fix RDP Wrapper. The Spring update completely broke RDP Wrapper v1.6.2 so I had to manually copy the new rdpwrap.ini file into the "c:\program files\rdp wrapper" folder using the instructions here (https://github.com/stascorp/rdpwrap/issues/456) and downloading rdpwrap.in from here (https://github.com/stascorp/rdpwrap/files/1997399/rdpwrap.ini.TXT). This is the batch file I wrote to initiate shadowing:

@echo off
qwinsta.exe
echo.
set /p uid=Enter session ID to view:
start Mstsc.exe /shadow:%uid% /control /noConsentPrompt

I recently learned that attempts to shadow a session result in an error if one isn't logged in under the Windows built-in administrator's account or the above batch file isn't ran by right-clicking it and choosing, "run as administrator". I also discovered that making this change in Windows Group Policy is helpful for initiating shadowing as long as one is a member of the Windows administrator's group:

#

Allow members of Windows administrators group the
same access as the built-in administrator account

#

Run gpedit.msc to edit "Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options"
Disable "User Account Control: Run all administrators in Admin Approval Mode"