Windows 10: Xbox PC App Stuck on Logo Screen When Opening

I downloaded the Xbox app on my laptop from the Microsoft store and whenever I open it, it stays on the loading screen black screen with white logo for a minute and then closes.I have tried:- reinstalling the app- restarting my laptop - checking for updates, everything is up to date- reinstalling gaming service- reinstalling the app with windows power shell- repairing Xbox related apps, gaming services and the Microsoft store from settings - downloading the app from the website, I get the error code 0x8027025a after the same thing happens when launching - disabling real time protectionI am r

:)

 

Xbox app stuck on loading screen when opening on parallels on Macbook

The xbox app gets stuck on the black screen with the logo when opening the app. I am using paallels on a M2 Macbook Pro. I have read on other forums where the xbox app works fine in parallel, so im not sure what im doing different.

 

Xbox app stuck on loading screen when opening on parallels on Macbook

Yes I’m trying to use the app to do both, but get stuck on a black loading screen with an Xbox logo.

 

PC stuck at windows logo and ram question

"are they the same as the other sticks, or are they different?" They are the same sticks "Why do you think it's the RAM? What is your PC and how old is it? If it's bad RAM you would in most cases get a BSOD." 4 rams was working fine for many years on this motherboard. PC 13 years old. Suddenly one day during using windows, windows stuck whole monitor turned white (cannot remember if it had blue screen or not) the it either auto restart or I manual power down then power on, then during start up it stuck at the windows logo. I tried power off and then power on repeat many times it is still stuck at windows logo. 4 rams inside PC, switch on PC and stuck at windows logo, then I tried these steps. Removed first ram (3 rams left inside PC), switch on PC and stuck at windows logo. Removed first ram and second ram (2 rams left inside PC), switch on PC and windows loaded past the windows logo and did some windows repair during start up and successfully load into windows. So I think second ram is faulty, first ram might be faulty too.