Windows 10 issues with Start Menu and Cortana functionality.
Windows 10 issues with Start Menu and Cortana functionality.
Hello once more, I didn't mention enough. Windows menus, Cortana, and programs stopped working. The only thing I could use was Task Mgr, so I tried the original solution #1 and then restarted. This gave me access to menus and regedit and let me try solution #2. I changed the start value to 4 (from 2), thinking maybe it was a hex number instead of decimal. We'll test it and see if it helps, hoping for a lasting fix. Xysto
Oh don't worry about hex or decimal since hex and decimal for 4 is still 4 it only gets weird when 10 or above. Btw theres a new update that came out i don't know if it fixes anything for you. it did nothing for me... Its looking like Microsoft is neither actively trying to find a fix nor acknowledging the problem... Only if someone big points out the problem. **Cough** Linus **cough** But i can't blame him for not pointing it out though since not everyone is having this issue. I asked my friends only 3 out of 9 people I asked has the issue and out of the 3 only some of their computers have the issue. I guess i pulled the short straw... All 3 of my computers have the issue **sigh**
Windows applied the newest update after restarting yesterday. Also, the Radeon driver was updated. Just a guess. You're correct, MS doesn't seem to provide much help. I checked all the recommended fixes, scan tools, set up local accounts, switched antivirus, reinstalled everything—nothing worked. A Linux installation now seems like a viable alternative.
Start menu, Cortana, Action Center, and different taskbar options belong to an app named ShellExperienceHost. Windows Explorer handles launching it when needed, but this program stands alone as a separate executable. When a flyout appears, ShellExperienceHost becomes active and then stops when the flyout is closed. After closing, it remains paused in memory until another flyout is opened. You can monitor this in Task Manager, but you must enable the "Status" column and use the "Show suspended status" option. The problem lies in not properly suspending ShellExperienceHost. My usual solution is to close ShellExperienceHost.exe in Task Manager, which forces it to restart. This issue appears more severe in FCU compared to CU, and other fixes seem limited to simply restarting the app.
The regedit command you tried earlier has successfully resolved the issue.
Hey Rubin, it's been a month since I applied your most recent update, and I'm pleased to say Win 10 has performed very well. Thanks a lot! I'm also hoping the Spectre and Meltdown patches won't introduce any new issues. Always something to look forward to. Happy New Year!