I don't think it's a bug, and I don't think this is a case of just wait until Microsoft fixes it. ...
Ah, well, if you think that, then maybe I could be accused of being a tad optimistic in supposing what I did there./Rant ON
Maybe, for whatever reason, MS won't
, in the end, take responsibility for fixing whatever they seem to have broken, and which apparently only they
could fix, so then it would be left to the app developer(s) to adapt the apps affected, so that they point to the new address (or whatever it is).
Then again, maybe MS will
fix it, given time. Fortunately, in terms of priority, at least the wheels don't seem likely to fall off anything critical because of it, meanwhile.
I suppose the question is: In this Richmond variant of "Waiting for Godot", how long does one actually wait?
And then, the possibility is that the app developer(s) will
adapt the app(s) to be in sync with the new address (or whatever it is) and then, having done so, MS belatedly actually fix it like they should have done in the first place
, which then could leave those apps already thus adapted to be out of sync again. Such fun. Stranger things have happened at sea.
Some people (not me, you understand) might say that it could thus seem more prudent to take a "Wait-and-see" approach in such cases. They might add that they admit the allure of getting on with and enjoying one's life, rather than spending one's cognitive surplus hovering over a partially crippled Windows OS with a spanner and screwdriver in hand, trying to fix up someone else's obscure mistakes. However, I couldn't possibly comment.
This is all kinda academic in my case anyway, as I am not generally predisposed towards being a "Creators Update" or "pre-release" or whatever-kind-of-ß-tester of new versions of the OS, because being the usual kind of enforced in-production-ß-tester is more than sufficient joy for me./Rant OFF