In response to this, a Microsoft support representative confirmed to Windows Latest that the message is indeed a bug. "This is just a reporting bug on our side," the representative explained. Microsoft stated it is actively investigating the issue and plans to resolve it through a server-side update, likely to be deployed within a week.
You are viewing a single comment's thread from: