Originally Posted by TFL Replica
Are we absolutely sure this is a bug and not a deliberate "feature"?
These days... one day you semi-take it as a joke, as it should be because as it stands you can't ever be too sure, but still, you're still having a giggle... then you read this:
If your problem is the latter, the good news is Microsoft is working on a fix. The bad news is it doesn’t seem to be in a huge hurry to solve the problem.
This bug is a known issue caused by KB4464330 (OS Build 17763.55). Microsoft is working on a resolution and estimates a solution will be available in late November 2018.
Late November. Wonderful.