Windows 10: How to fix "Critical Error" Your Start Menu Isn't Working?

Firstly, I'd like to say thanks for being such a helpful forum, especially to leeches (like me *Sick).

I'd really appreciate it if somebody could help me out. I installed Windows 10 on my desktop PC but after a while I kept getting the following error message so reverted back to windows 7. The error message was:

"Critical Error"

"Your start menu isn't working. We'll try to fix it the next time you sign in".

"Sign out now".

When I sign out then sign in it doesn't fix the error and the next time I click the Windows 10 start button the error re-appears.

The strangest part is that I bought a brand new Lenovo laptop and installed Windows 10 (which was a big pain to begin with) and it has hardly any programs on it (if that could be the cause of the interference) and now I've received the SAME ISSUE!

Anybody got any ideas? I can provide you with any information you'd need. I'd had to have to reinstall back to Windows 7 again, the aggravation Windows 10 has caused me hasn't been worth it so far but it seems like a nice OS.

:)

 

Inoperative start button

Every time I try to click the start button, I get a "critical error" message that says: "Your start menu isn't working. We'll try to fix it the next time you sign in." It never gets fixed and I have no access to any of the start menu or apps. This is
getting old. How do I fix it?

 

Stat menu error message on Windows 10

Keep getting a message "critical error. Your start menu isn't working. We'll try to fix it the next time you sign in". Repeats when I sign in again

 

Had the same problem with a brand new laptop (HP Envy) upgraded from W8.1 (not a pain in the ass)
Found a bunch of potential solutions, but none were feasible until you were logged in and I was hung up in the boot cycle.
Powered down and rebooted a couple of times and nothing.
So, I put it aside and decided I would take the laptop to my local computer store (as it turns out, they'd never seen this problem!)
After a time, I wondered if I had been impatient so I booted again, figuring I'd let it churn for a couple of hours.
Boom....no problem.
This wasn't very scientific, but my conclusion was to let it work for a while.
The fix might have also been from rebooting some number of times....
Or, a combination of the two...