Windows 10 new install apps not launching

flowrider99 · 16 Mar 2016 at 17:26

I have just upgraded one of my PC's to Windows10 but most of the apps wont open. I have tried Mail, Calender, People, Maps, Groove Music, Film & TV, Photos, Store none of them will open. I see a window flash as if they are going to open but it disappears in a flash.

Anyone come across this before?

marc2003 · 16 Mar 2016 at 17:29

I'm pretty sure there was another post in the last day or 2 with this exact issue. Apparently it was caused by windows update running in the background. When it's all done, it should work.

edit: Found it- https://forums.overclockers.co.uk/showthread.php?t=18722933

flowrider99 · 16 Mar 2016 at 20:05

marc2003 said:
I'm pretty sure there was another post in the last day or 2 with this exact issue. Apparently it was caused by windows update running in the background. When it's all done, it should work.

edit: Found it- https://forums.overclockers.co.uk/showthread.php?t=18722933

Thanks for the link. Not the same as my issue as update is not running and Windows reports fully updated.

Looks like a lot of similar issues reported to Microsoft with no fix so i decided to do the install again and all is now ok.

flowrider99 · 17 Apr 2016 at 17:53

This is getting ridiculous............

I now have another Win10 PC where the inbuilt Mail app refuses to launch but only for one user, the other user is working fine. No way am I going to reinstall the OS just to fix one app so anyone have any ideas.

This is what I have done.......
1. Restored to a known working restore point.
2. Uninstalled Mail and then reinstalled.
3. Ran Windows update but no updates outstanding.
4. Ran Windows diagnotics, which found nothing.

This is majorly hacking me off.

flowrider99 · 17 Apr 2016 at 20:36

Fixed it again.....i created a new user, checked the W10 apps were working, copied the old user folder to the new user folder, renamed both users so the new user had the old user name and then deleted the old user account.

Microsoft have got to sort this issue out, there are loads of the same issue reported on the web and no definitive fixes. Microsoft dont even appear to recognise this as a common problem.