Windows 10: Windows Store error 0x80070005 when installing/moving to non-C: drive

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.

 

Just a quick update...

I have managed to resolve this issue on my PC although, unfortunately, it now appears that the issue DID arise as a result of upgrading from v1511 Build 10586.494 to v1607 Build 143xx after all as I restored my backup of the previous build from 23rd July in the early hours of this morning, after noticing many Store games were opening and instantly closing (even after uninstalling and redownloading/reinstalling them). I tried taking taking ownership of the C: WindowsApps folder but I could not get them to load so I decided to just go back to the last stable build.

Now I am able to move games and apps (non-system ones) from C: to H: with no error. A few games did seem to have issues starting (they'd open then close) but I believe they were ones that were on H: then moved onto C: while v1607 was installed (since I could move them from H: to C: without the 0x80070005 error as stated above). What I think happened there was that I'd restored my v1511 build again last week, after moving certain games from H: to C: to update them on build v1607, but that backup did not contain the apps on C: (since it was done before they were moved). Therefore Windows still thought they were on H: but in reality they weren't H: or even C: anymore!!!

Anyway, I have been able to uninstall those few games and redownload them (to H: of course... FINALLY!!!). I am even downloading both Killer Instinct and Forza Motorsport 6: Apex (Beta) to my H: drive something that I have been 100% unable to do on any of the v1607 builds!

So this thread perhaps serves as a warning for anyone thinking of upgrading to the Anniversary update on 2nd August... I would seriously consider doing a full backup of your current Windows drive first before you do so. On my system, this update seemed to have messed up the security permissions for installing Store apps and games on any drive except the Windows C: drive and I was not able to fix it (believe me, I tried just about everything I could think of).

I will wait for the final build on the 2nd August, do another backup before I install it and then if I still have this issue then I will revert back to v1511 (for what would be the fourth time) and just defer the update until more people have been able to report feedback. It may be just specific to my setup and a one-off or it may be an issue others may have who upgrade a system that has existing apps and games that had previously been moved or installed to other non-C: drives before the upgrade.

 

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

 

@ Scottyboy99 - Yeah, resolved by basically just not installing the Insider Preview build of Windows!!!

My only concern is whether this issue will persist into the final release version of v1607 of Windows but as long as I have a backup then at least I know I can return to a working version of Windows free of the issue. Might just set the Defer Upgrades option though and wait for feedback from more people before upgrading again.

 

I've just installed v1607 Build 14393.5 from a mounted ISO of En-GB_Windows_10_Pro_14393_x64_DVD.iso and post-install I am *STILL* getting error 0x80070005 whenever the Store tries to update any of its apps and games on my H: drive (and any other drive except C: for that matter) or if I try to move anything from C: to H: or any other drive (yet I can move from H: to C.

This issue is absolutely infuriating me and does not happen on v1511 Build 10586.494. Looks like I'm going to have to restore the previous build AGAIN then set the Defer Upgrades option and pray that Windows does not install this build come 2nd August.

Can someone running this build please do me a huge favour and change your Storage location to another drive then try installing or moving a Windows Store app or game to that drive? Does it work OK for you or does it fail with error 0x80070005?

Note: that most of my Store games and apps on H: were installed some time ago, some when I had the release version of Windows 10 but until I installed v1607 of Windows they have never failed to install or update to my H: drive.

 

Update:

I restored my Windows v1511 backup, for what must be the fourth or fifth time, and confirmed that I had no issues installing/moving/updating apps from the Store to any drive (I didn't) then proceeded to update to the official Anniversary update (v1607 Build 14393.10) via the usual Windows Update.

Well the update when smoothly, as it has before in the Insider Preview, but the issue still remains. The upgrade from v1511 to v1607 actually corrupts or breaks some of the permissions such that anything located on any other drive than C: will only run and moved to C: but cannot be updated or anything new installed there. I have reported this issue to Microsoft via the Feedback tool but I noticed that I am not alone in experiencing this issue and that at least half a dozen other people had also reported the very same problem.

Looks like I am going to have to just put up with for now and hope that the larger games such as Quantum Break are not updated as it will fail and I have insufficient space to move games of that size back onto my C: drive to update (plus I will be unable to move it back once updated).

A very frustrating issue that is specific to the Store. I can install and update Steam, Origin and UPlay games which are installed across the same three hard drives just fine. At this point, I'm almost convinced that this is a v1607 bug.

 

I had this issue, what fixed it for me was to disable compression on my secondary drive. Everything worked after that, installing from store to drive and moving existing app from c:. Might not need to do the entire drive, maybe just the WindowsApps folder on the second drive.

 

Hopefully this helps the OP. It's yet another lame bug that MS seems to be ignoring. With SSDs being generally quite small due to costs and the OS residing in it, it's logical secondary larger drives would be levitated to for Windows apps. Will be interesting to hear from the OP on whether this helps. Personally it's only driven me further away from using MS store for anything other than basic apps. Will keep all my gaming to trusted platforms like steam

 

@ biggs - I was sceptical that this would even work but, yup, turning off compression for the WindowsApps folder on H: and hitting Apply does indeed fix this issue and I've been able to successfully move Age of Empires: Castle Siege from C: to H:!!! I can't believe it was something as dumb as that. Honestly I cannot thank you enough.

The irony is that I went and replaced my 256 GB Crucial m4 SSD over the weekend with a 1 TB Samsung 850 EVO specifically so that if I had to update any games on H: (which would fail with error 0x80070005) then at least I would have the option of moving them to C: and updating them there, something I could not do before due to a lack of space.

Oh well, I now have a much faster boot drive and can install some games to an SSD now; DDOM for example massively benefits from being on an SSD with my loading times cut down from 3-5 minutes (yeah, really!) to under a minute!

Thanks again. I will make sure to update my Guru3D.com thread with the solution as well for anyone else who has the same issue. And you're right it IS another dumb Microsoft bug, one that really should not happen since file compression has been around since Windows XP I believe. Clearly, Microsoft never bothered to test this with it enabled!

 

That's great, I'm glad that worked for you. You'd be surprised how often compression messes with applications. It's now my number 2 check after permissions for any weird I/O errors.

 

I have read this entire post with interest, I have learned several things. Compression which i do not use ( why would you ? ) and the nvidia drivers messing with things. I am about to update my drivers to see if this fixes the frustrating Store error 0x80070005. Its so odd for me as i have not moved any of the apps nor install them elsewhere. Worse is that i have 22 outstanding updates that sometimes install fine and report 'completed' then next reboot are again pending ? They then fail with the above error. I too installed Anniversary edition and had to roll it back for exactly the same reasons as the OP. Securities and permissions issues that broke everything. Missing quick links progs like Edge opening and closing immediately. Too much to list so i had to roll back. Ever since nothing is quite right. I did however have a failed raid drive (ddrive) that i installed many progs onto, these are all lost and awaiting reinstallation, however i may be able to repair the failed drive that took out the raid so i have to wait. Just to say thank you for such a detailed and intelligent breakdown of the same issues i have, you have helped me lots *Smile