Hello Peter,
We believe this has been fixed since Insiders builds of the Windows 10 Creators Update (1703).
The fix was not backported (=serviced) to Windows 10 Anniversary Update (1607). They were complex changes which included risk, without any guarantee of result on Anniversary.
Kind regards,
Alban
|