as of 10.0.22621 Build 22621, this solution no longer has any effect: Good news! This fix made it into the next build which will be flighted on the dev channel of the Windows Insiders program. Here...