Hello Egol,
Yes, that's correct. I was on holidays and wished to give time test it before claiming it's fixed but general public feedback I have seen is extremely positive.
The fix is available from build 15049.
To get the update, simply search for updates in the settings of your Windows 10 machine.
Builds 15049+ are only available through users and computers registered to the Windows Insiders' Programme today. If you are using a corporate machine, you may not be able to get it.
Should you be using a consumer Windows 10, what is available today will make the official Windows 10 Creators Update release.
As an appeal to all readers, if you have multiple machines affected, please flag this to us.
We're working to get the fix serviced in the current version of Windows 10 (called Anniversary Update) because we know most corporate users will NOT get Windows 10 Creators Update until at least September (
when it reaches the Current Branch for Business, 6 months after the release-to-market date).
Also,
there were multiple origins for the issues seen (one symptom, multiple root causes). Microsoft has done what they could to fix them, however
please do report if you are still seeing problems once running 15049 or above.
Kind regards,
Alban