New
#221
This DEFINITLY WORKS GUYS N GALS. Just make sure to right click over the powershell name after you search for it in the 'Search Windows' tab to RUN AS ADMINISTRATOR. It's about the only thing right click works on. THEN, your windows button will work (LASTLY). because during the process you will notice right click is working FIRST after about 23 processes complete. Takes about 5 min max. - Ten Boy (Just like Windows 10, I'm a lil haywire but I'm better than the old me after all is said and done) BUT windows 95 ...U always miss your first! Well Windows 3.1 was my crush, but 95 moved next door and it was OVER.
After 5 months of struggling - the problem is gone after installing (KB3152599).
Hallelujah!
Most likely,
Here as well. The broken apps are working again and start menu (for the moment) It worked before after updates but only for a week or so. Fingers crossed :)
Well, the very first step in the reference you posted IS what caused the loss of the Start menu in the first place!. The latest build update this week (10586.218 to .318) is what BROKE my system!
What I wish is that MS would once and for all get to the point of addressing WHAT causes this issue and FIX IT! It is all very well to have to resort to a re-install every 6 months, but that causes all sorts of other issues which can take one months to recover from.
This also worked for me. I WAS trying to fix some TOTALLY unrelated network problems (by changing some network setting) and the the start menu functionality (and Cortina) stopped working because ...reasons?
It worked (and I didn't need to reboot). I rebooted anyway and of COURSE MS had more updates for me. So I held my breath to see if it still worked. After I passed out (never hold your breath during updates) I saw it DID still work.
I have 3 theories about Windows 10.
1) Parent's of some of the 4th string programmers (who were always sitting on the bench and never got to write code) complained to management, so they let them write an OS to make their mom's happy.
2) They got it to work for a few minutes on ONE machine ONCE and said "Great. Works. Ship it."
3) They care more about cross-marketing stuff to give a damn if it WORKS, and care more about covering their asses when it doesn't work then helping.
Unfortunately, the powershell method:
Code:Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"*}
Didn't work for me at all. It does 4 complete "tasks" then gets stuck about 20% of the way through the fifth one indefinitely. No idea what to do about that. It's getting very frustrating.
PowerShell worked for me. But because there are many different causes of the same problem, it doesn't work for everybody.