Windows Store error 0x80070005 when using a different location to C:

Yes someone like Brink will be well placed to advise. Your prob right on that feature, I just thought I'd read otherwise. Maybe someone else can confirm this.

i know how you feel on the posts - I've done a few where you just end up posting to yourself and getting nowhere! The guys on here are very helpful and I just think no responses generally means nobody is sure. I don't think a repair install is the way to go as I think maybe you'll hit this roadblock again as it seems a deep rooted bug/oversight on the part of Windows itself

one thing I have learned though is to try and stay away from those power shell fixes. They seem to create more carnage than good - at least in my experience. I'm very anti the store and the native apps and the way store updates them, they are the most buggy and troublesome aspect of Windows 10, again in my experience

What I suspect may have happened, and I might be completely wrong but it kind of makes sense to me as far as I understand it, is that when I upgraded Windows 10 Pro from v1511 to v1607 that Windows updated all the security permissions for the apps and games installed on C:, including reassigning a new Security ID (SID) to my account, but "forgot" to update them for the stuff I'd previously moved to my H: drive. It seems that Windows *can* read from this folder hence why I am still able to play games like Quantum Break which is installed there (all 67 GB of it, which is why it is not on my C: drive!) but it seems unable to write to it (although I have seen it create folders in there).

I'm not quite sure how Windows can move apps and games from H:\WindowsApps to my C: drive though since that requires it to read, copy, write to C: (which I know is OK) but also finally DELETE the original files from H:. Presumably deleting and writing have different permissions on my system because of this, i.e. Windows can delete from H: but it cannot write to it?

I've just opened up the H:\WindowsApps folder now and tried to create a folder in there... I get a Bad Data 0x80090005 error (that is typed correctly by the way, it is not the same error as 0x8007​0005).

I took a look at my nephew's laptop yesterday, which is running Windows 10 v1511 and I played around with downloading a small game from the Store to the default C: drive then moving it to D:. I then examined the permissions for the folders and found that the D:\WindowsApps folder was owned by SYSTEM and the D:\WpSystem folder (which is the equivalent of the C:\Users\<Name>\AppData\Local\Packages folder was owned by S-1-5-21-XXXXXXXXXXXXXX-1001 (which I think is the main user account). When Windows creates a WpSystem folder on my system it shows as being owned by Administrators\Darren, not as an SID string. Not sure if this is part of the problem though.

The lack of a string on your machine does sound like a key difference. You seem to of done a lot of hard work. I totally understand your rationale for wanting to use your H drive. There is no way the majority of users can support large game installs on the C drive if they are using SSD. Not unless you've got pots of cash to buy a 1 or 2 TB SSD drive. Mine is a 500 gb SSD and even this is half full, and I keep 99% of my games on my steam install which is on I drive.

i will see if can message Brink to alert him. Maybe he will have an idea. Between keeping an eye on the seven forums, eight forums and ten forums I imagine he has a lot on his plate!

Total long shot but have you tried updating your gpu drivers? It sounds crazy but I have seen on nvidia forums about how some of the sets have been interfering with Store app updates. I don't expect it to be the answer but it's worth a shot. I still use 355 driver set and refuse to update them until there is a compelling need to do so - purely because everything is ticking along fine on these. Bizarre that could be a connection. I'll try and find the forum discussion and link it here if I can find it.

Found it and then realised the person who had brought this up was you!! So I presume you've already tried this

Solved Unable to check for updates in Windows Store - Page 2 - Windows 10 Forums

Yes, that was a bug in the pre-v368.xx drivers that was fixed in v368.81. I am using the latest v368.95 Hot Fix and can confirm that the issues triggered by setting MFAA to On in the Global Profile has been completely fixed for me. That was a string of non-gaming related Windows issues caused by a buggy driver but somehow I do not think I am so lucky as to be able to fix this one with a driver update, no matter how much I'd like to pin the blame on NVIDIA for it.

Again, appreciate the feedback and assistance. I mean if I have this issue then who's to say that someone else won't several months down the line? Maybe the issue isn't being acknowledged yet because few people (a) have upgraded to Windows v1607; and (b) have moved apps and games to drives other than the default location of C:?

I suspect it's (b) where not too many have changed the location. I am not really clued up on the gaming scene from the store. I guess as it takes off and becomes more popular more people will try and download large GB game installs through the store and feel the need to store on secondary drives due to space constraints. Then the issue you have will become more prevalent. I am sorry it's giving you the frustrations you have - this seems to be a really complex issue that even some of the gurus resident in this forum will be hard pushed to explain. The anniversary update is almost upon us, just maybe that could bring salvation

It's the Anniversary build which I have installed though via the Insider Preview: v1607 Build 14393.5. This is strongly rumoured to be close to the final version as it is just being updated with cumulative update now rather than full install builds.

Good to hear you've sorted the issue and an important warning to people ahead of the dreaded anniversary update! Totally agree that taking a system image ahead of this update should be something people undertake. I hope post update your difficulties do not resurface, I would be very keen to hear how things are holding up once you've had a chance to run with it for a while