XBOX for PC on windows Misc Error Codes. workaround that works

I found during the last 3 Windows update cycles that something happens to the registry keys for gaming services, specifically they get deleted. you then see 1 of 3 different error in the app on launch.

1, having problems launching or installing apps click here to fix.......sends you to ms store to download and install gaming services. error code 0x00000001

2, same message sends you to xbox support site has a generic fix that dont work for most.

3, launching any game from your list including ea games sends you to either the store or to xbox support.

here is the workaround give by a microsoft tech from a third party websites known as BleepingComputers

the reason i say the registry keys are deleted or even corrupted is the powershell says they cannot be found when deleting them then removes the reference to them allowing proper install.



Replied on November 9, 2021

1. Right-click the Windows Start button in the lower-left corner of the main screen, and then select Windows PowerShell (Admin).
   
2. In the Administrator: Windows PowerShell screen, type the following command and press Enter:
   
   Get-AppxPackage *gamingservices* -allusers | remove-appxpackage -allusers
   
3. In the same window, type the following commands and press Enter:
   
   Remove-Item -Path "HKLM:\System\CurrentControlSet\Services\GamingServices" -recurse
   
   Remove-Item -Path "HKLM:\System\CurrentControlSet\Services\GamingServicesNet" -recurse
   
4. Restart your device.
   
5. Start the Xbox application. You should see a blue banner with the following message: "This app needs an extra component. Gaming Services is needed for playing some games. Administrator approval required. Install"
   
6. Select Install to reinstall Gaming Services.
   
7. After the installation is complete, you should be able to install and start games again.
   

I found the registry keys section I found elsewhere on the internet is not on the troubleshooting steps. It does seem to fix the problem. I was shown the actual website by a Microsoft tech during a support call 2 nights ago while he was remotely connected to my computer trying to find the actual source of the error. the error has something to do with windows updates. I have been plauged with this issue and notice it after each reboot from the last 3 windows update cycles. would be nice if a dev could figure out the cause and maybe fix it.

:)