19-10-2017, 05:27 PM
(27-06-2017, 09:29 AM)DevOma Wrote: Update from MS - the issue is caused by a new (system) API that is currently undocumented! Seems that mstsc.exe is the only product that knows how to handle this new API - the documentation of this new API and official support will start with the next major upgrade of Windows 10 (Redstone 3) - this is planned for September 2017 - we do not get any more information about that API before the Release will be published!
Is there any update on this or update on fixing this issue? I am currently running Windows 10 1709 and still experiencing the issue.