I had this on Windows Creator and had to go back to previous version.
I tested on the then latest Microsoft Insider build and still had the problem there. The problem was repoprted against the Insider build. After installing the latest Insider build 16199 I'm unable to reproduce the problem so I anticipate the fix will be released to mainstream versions of Windows in time.