New
#31
thanks for posting this, all.
I have been pulling my hair out trying all sorts of fixes and then found out I am not the only one.
Hopefully we have a fix coming soon.
Presumably if someone encounters this problem and
a. have no relevant /usable restore points
b. have not yet learnt to use disk imaging or have no relevant image
then an in-place upgrade repair install (See Tutorial) would fix this and be the only remaining option?
Am I correct in thinking that if you don't do manual updates with the store open, this problem won't arise?
Last edited by dalchina; 29 Jan 2016 at 05:45.
Unfortunately, I cannot confirm the avoidance of manual store update with it open will prevent the problem. However, this is what broke mine (and only on my user account), it could of been a co incidence but it's the conclusion I am reaching that keeping auto updates on is the safest thing. Don't fancy trying to recreate the issue. I just must stress to other users to avoid powershell fixes at all costs as that will make things worse. Restore points and images are very important.
Yep that's good advice. I think the auto route is the way to go. I only changed mine to manual because I didn't like the idea of a buggy update to an app going in. Wanted to research whether an app update caused an issue before committing. Unfortunately I have had my fingers burned before on iOS where sometimes app updates cripple the app because the developer has not bothered to QA test. Anyway auto is back on now and no problems since