Can't install game with Xbox Beta

[bit]

Got XGP (just the regular PC one, not the ultimate one) to play Gears 5 with a friend, will be a couple of weeks before I can play it so I decided to finally play DR4 since it's included with XGP cus i guess i'll finally play the shit show. Gears 5 installed fine on my secondary drive, I go to install DR4 on my third drive since secondary got a bit full with Gears 5 and it keeps giving me an error at install saying it can't be done. 

 

 

Throws up an 0x80242020 error which according to microsoft doesn't exist in their code book, did their troubleshooting including powershell to reinstall game services, tried some other things from reddit that all didn't work. I can't really try to install it on my primary or secondary drive cus there's literally no room for it (45gb on primary and 62 on secondary), there's about 400gb left on my third drive. Have rebooted PC multiple times, tried as admin, etc etc nothing. 

[SlayerOfHellWyrm]

• Either select the link under the message to go to Settings, or press the Windows key and selecting Settings > System > Storage. Select Change where new content is saved.

• Using the menu under Where apps will be saved to, choose the drive you want.
  
  Above is something I found in about 2 minutes of Googling with the exact error you've been seeing.

[bit]

and that's from reddit, which i've already done, thanks 

[SlayerOfHellWyrm]

Just now, bit said:

and that's from reddit, which i've already done, thanks 

It was not, MS forums actually. Saying the error code doesn't exist is kinda dis-ingenuous though. It does, but like most errors they aren't all documented. That being said, have you tried removing Gears 5 and then installing DR4, or trying to reinstall Gears 5 to see if the error is specific to DR4?

[bit]

have tried with forza horizon whatever number we're on and same error when installing to same drive

[SlayerOfHellWyrm]

1 minute ago, bit said:

have tried with forza horizon whatever number we're on and same error when installing to same drive

So what happens if you remove Gears 5, and try?

[bit]

A smaller game to secondary drive works just fine

[SensibleCuddles]

Yes, I know this is an old thread, but I actually think this is important so I'm going to share my thoughts on this in the event someone finds this someday:

 

The reason the XBOX app, and the Windows settings for "App installation" are linked is the creation of a folder called "WindowsApps". Most people find out about this folder when they, like I did, have to change ownership of the folder from "TrustedInstaller" my own user after finding that it took up SO MUCH SPACE on my drive. I went in, found all my old, unused games, and deleted them. Yay! More disk space!

 

The problem, however, is that the "WindowsApps" folder now is not what the xbox app expects... and no matter what you do with it in the future... it never will be again. Once you've changed these permissions... you can't go back, and installs will fail with 0x80242020.

 

So... what's the solution? How do you get WindowsApps back?

 

Well, first go remove it... at least if you don't have any games installed. If you do... THEY MIGHT BE IN THIS FOLDER! Be careful! But if you don't... then delete the folder. If you don't... WIndows won't recreate it properly. Go ensure that the drive you *want* to use doesn't have a WindowsApps directory (be sure to show Hidden files, as this is a hidden folder sometimes by default (like on C:).

 

Now, once you've cleared that out... go to the Windows > Settings pane (no not the Control Panel, the useless new one), and then go to "System", then "Storage", then select the drive you ensured was clean and save it as the new "App" location.

 

This recreates the user-locked folder "WindowsApps" on that drive, and you should be able to install your games now. If you tried this and it didn't work, AND the error-message didn't change, go check again for a pre-existing WindowsApps folder. If you can access the folder by double-clicking on it... it's broken. You should not have permissions. Delete the folder, and try again to re-point the App installs in Settings. Once you're no longer able to access the folder because it's owned by "TrustedInstaller", it's 'fixed' again and should work.

 

Yes, this is dumb and yes, Microsoft shouldn't create user-protected folders for no reason other than protecting app folders. It's dumb. But... I hope this helps somebody in the future, it took me like 90 minutes to figure out why this helped/hurt others and why it wasn't helping me (my WindowsApps folders were still out there).