Hello,
Thank you for all that. It sounds like a bug identified in Windows 10 v1903.
There is a tentative fix in the Windows Insiders beta programme.
We are working with Microsoft to justify getting the fix serviced in Windows 10 v1903 via the monthly patch system.
Kind regards,
Alban
Ref: 30343
|