There is an update for the Store app that won't install. It seems to complete the 'downloading' phase, and the 'installing' phase seems to run out to near the end and then all of a sudden I get
"Wait a few minutes and try that again
The update failed.
The error code is 0x80073cf3, in case you need it"
I tried to search it, but only got old and irrelevant Windows 8 responses. Is anyone seeing this issue? Any ideas on a fix/workaround?
TIA
Is this a new store update that came out today? Does store still launch for you despite the failed update - if it does it might be worth waiting it out a few hours as it could be an issue MS end. If it's an older store update then you could try a system restore point to before the failed attempt and then try it again
i did a quick google but it seems a common error code - sounds like the update relates to redstone / insiders though. Are you on that ring? I don't go in for the stress of beta testing for MS so just stay away from
insider stuff. I'm not home at the mo so cannot check if I have a store update waiting on the non insider normal Windows to report on whether it installs ok - or is even available as an update
just speculating that this store update is just not ready for mainstream based on this
Just got home, no store update waiting so this must be insider only
It is Insider only - I originally posted this to the Insiders subforum, but a moderator moved it here.
Ok cool. I did Google as mentioned and there were a few other reports of that error code so I'm assuming it's on MS end and no issue your side
I'm having the exact same issue..
Edit: Could it be that I've changed the default location to a drive other than the OS drive? Can any of you confirm that setting??
This is a Insiders-only update that just came out in the last day or two. The store not only launches, but is able to install other apps just fine, so maybe this problem is at the MS end and it will settle down soon enough.
Yes, I searched for that error code, but it is so common as to be not very helpful.
Thanks for your reply...
I just read in the News subforum that this is a known issue that everyone is having, so I'll mark it solved here - if any is interest they can follow it in the News section.