This is a bug which is there back to mostly the beginning of the Insider Program (build 9xxx). I have reported it several times over the past 1,2 years over the insider tool, but also in the MSDN forums. Like you can see, it was ignored and got into final (RTM) version (nice work Microsoft)...