Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
I didn't found any better solution - do the user uses Windows Insider Preview Builds? Because I read one article that this was an issue in a preview build
Regards/Gruss
Oliver
Posts: 8
Threads: 1
Joined: Apr 2016
Reputation:
0
I am getting the same issue after upgrading to Anniversary Update of Windows 10.
It works on normal RDP connections, but the connections that requires a RD gateway gives this error in ASG Remote Desktop 2016 Patch 3.
Have tried using Windows Remote Desktop with RD gateway and it works fine there, but not in ASG.
Have tried to reinstall ASG remote desktop also.
Note: I have also submitted a support ticket to ASG with this issue.
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
Which OS build number do you use?
Regards/Gruss
Oliver
Posts: 3
Threads: 0
Joined: Sep 2010
Reputation:
0
Windows 10 Enterprise
Version: 1607
OS Build 14393.10
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
Ok - I can reproduce on my "preview build machine" - on "standard win10" everything is working - some months ago we had a similar problem with "Server authentication" - and some weeks after the problem occurred a new Win10 build was published (by MS) and the problem was gone
In the link I added there is a solution how to remove the latest mstsc version - but as long as this is only a developer preview we can't change the program without to know if this is bug in this specific version or a change we have to implement too - if we change the mstsc interface (activeX) perhaps it will work for this version but not for the next one...
Regards/Gruss
Oliver
Posts: 8
Threads: 1
Joined: Apr 2016
Reputation:
0
Just a note
I am not using a developer preview.. It's a Standard Windows 10 Enterprise, upgraded with the latest SP (Anniversary Update, released on 2. August 2016)
Posts: 3
Threads: 0
Joined: Sep 2010
Reputation:
0
I´m also using the final release of Windows 10 Enterprise, upgraded with the latest SP (Anniversary Update, released on 2. August 2016).
No preview versions installed before.
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
Ok - it's the same build OS version I have on my "preview machine" - I will check to install on a standard win10...
Regards/Gruss
Oliver
Posts: 8
Threads: 1
Joined: Apr 2016
Reputation:
0
I got it working as a workaround by replacing the mstscax.dll (Version 10.0.14393.0) in %windir%\SysWOW64\ with the "backup file" in "Windows.old\WINDOWS\SysWOW64" version (10.0.10586.494)
I had to take ownership of the file and give Administrators Full control access to be able to replace the file.
Posts: 12
Threads: 4
Joined: May 2008
Reputation:
0
You are a star!! I had exactly the same issue. All my TSGateway sessions to anything older than 2012 R2 were failing with this error. Your fix worked for me too.
Cheers
Rob
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
We hope for a solution asap - but it takes some time to find the right persons at Microsoft :-)
Regards/Gruss
Oliver
Posts: 11,205
Threads: 101
Joined: Aug 2006
Reputation:
205
Problem is send to dev in Redmond - waiting for feedback and a fix :-)
Regards/Gruss
Oliver
Posts: 1
Threads: 0
Joined: Sep 2016
Reputation:
0
Same problem here.
Any word back from Microsoft on this?
