I would think it would be a easy fix for Microsoft. Everything worked correctly in build 1703, repairing it in the latest builds shouldn’t be too difficult; the programing code was correct once, so moding the current version to what it “once was” should be easy for any programer. The biggest problem is getting Microsoft to acknowledge this problem or even fix it. We need more folks to complain about it. Lol
If Microsoft is unresponsive blame its new CEO.
To him, customer care must be foreign concept.
Miss you, Bill.