Hi,
This has been confirmed as a bug on Microsoft’s back-end system. It typically occurs after performing a clean installation or resetting the device. At the moment, only temporary workarounds are available, and there is no permanent fix yet since it needs to be addressed by Microsoft directly. It is important to report this through the Feedback Hub app or through the Get Help and support. Simply search for the problem then click the Contact support button at the end of the search result. The more reports they receive, the quicker Microsoft will resolve the issue with the page.