Microsoft names this code but does not publish the wording it prints on screen, so we quote only the code itself: 0x80190190. Any site showing you an exact message for it has written one.
This one genuinely goes both ways, so the first job is telling which you are looking at.
Microsoft has no support article for this code. We verified that properly rather than assuming: their support sitemap lists 542 error-code pages and this is not among them, and their content system returns nothing for it in either spelling. Neighbouring codes in the same range do have articles, so the method works and the article genuinely does not exist.
What Microsoft does document is the number itself, in a different context. In their Windows networking headers, 0x80190190 maps to HTTP status 400, Bad Request. Decoding the value confirms it: an error severity, the HTTP facility, and 400 in the low bits. That is an inference from the structure of the value and from Microsoft's own HTTP status mapping — not a statement from Microsoft about Xbox.
In plain terms: something in the sign-in or store request was rejected as malformed by the server. Which is why it clusters around signing in to the Xbox app and the Store.
Check the live status above first, since a rejected request can be the service misbehaving. Then try signing in to account.microsoft.com in a browser: if that works, your credentials and account are fine and the problem is the app's request rather than you.
Microsoft documents 0x80190190 only as an HTTP status mapping in their Windows networking documentation, where it corresponds to HTTP 400 Bad Request. They publish no Xbox article for it. We would rather tell you that the operator is silent than invent an explanation, because the search results for this code are otherwise entirely guesswork presented as fact.
Microsoft has no support article for this code. We verified that properly rather than assuming: their support sitemap lists 542 error-code pages and this is not among them, and their content system returns nothing for it in either spelling. Neighbouring codes in the same range do have articles, so the method works and the article genuinely does not exist.
This one genuinely goes both ways, so the first job is telling which you are looking at.
Start with: These are community findings, not Microsoft's instructions, and we are labelling them as such. Microsoft publishes no steps for this code. Everything below comes from user reports and from what the HTTP 400 mapping implies. Any page presenting a Microsoft-authored fix for 0x80190190 is presenting something that does not exist.