I’ve had this problem on most of my Win10 computers at home, and on almost every one of my client’s machines at one point or another. So I thought I would post my solution matrix that I’ve been using to remedy this problem for the last year. I have seen the odd mention of one of these solutions online, but I’ve never seen all four of them (not including the sub-solutions) in one matrix, so I decided to create my own. We’ll start with an elevated Command prompt and go from there:
1.) Admin Command Prompt
If you don’t have access to Elevated Command prompt, try this: use CTRL-ALT-DEL > Task Manager > File > New Task, enter CMD, and make sure to check the box “Create this task with Administrative Privileges”.
2.) Run System File Checker to scan the system to ensure no problems with file system.
SFC /ScanNow
Run the above command repeatedly until you get through 100% without experiencing any problems.
3.) Run Deployment Image Servicing and Management to check Cleanup Image. Run the first command, and if no errors were detected, then you can really skip the remaining commands and go to the next step (4). However, if you encounter problems, then proceed to the next DISM scan.
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /cleanup-Image /Restorehealth
4.) Only after all of the prior steps have been completed, you can start a PowerShell session
Type in PS (powershell) and hit enter.
Once again, if you don’t have access to Elevated Command prompt, CTRL-ALT-DEL > Task Manager > File > New Task, enter PowerShell, and check the box “Create this task with Administrative Privileges”.
Then run these commands in the following order; you’ll likely only ever need to run the first one:
Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “\appxmetadata\appxbundlemanifest.xml”)}
…then reboot. If still having problems, try this script:
Get-appxprovisionedpackage –online | where-object {$_.packagename –like “*windowscommunicationsapps*”} | remove-appxprovisionedpackage –online
…then reboot. If still having problems, try this script:
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}
5.) Even after all those Steps above, I’ve had a client who continued to experience problems. Admittedly, this is a rare situation, but if you find yourself still experiencing issues, then I would recommend the following steps:
- Go to the run interface (Windows + R)
- Type “RegEdit” and press Enter.
- Click OK to the User Access Control challenge dialog box.
- Go to HKEY_CURRENT_USER>Software>Microsoft>Windows>CurrentVersion>Explorer>Advanced
- Create a new Dword with name ‘EnableXamlStartMenu’ (click on Edit > New > DWord)
- Assign it a value of 0 (zero).
- Log off and login again, or restart your computer if you’d like.
I’ve only had one situation where the last step was necessary. Because the previous steps had always worked prior to that occasion, I’m mentioning this step last. Thankfully, I can honestly say that I have yet to experience a problem with the Win10 Start Menu not working that wasn’t resolved by one of these many solutions shown above.
(Clarifications and Fixed typos 1/28/16)