3 ms·
"...this bug dates back nearly a decade now." A good trick, considering Windows 10 went RTM in 2015!
by throwanem 8y ago
"...this bug dates back nearly a decade now."
A good trick, considering Windows 10 went RTM in 2015!
- AnIdiotOnTheNet 8y agoYou're right, I don't know how my Googlefoo failed me so badly, but I could have sworn I had results from 2010 for Windows 8. PS: Seems it was because of this: https://answers.microsoft.com/en-us/windows/forum/all/start-menu-button-not-working/a4a94b13-1402-4f2d-aa7b-6c7547411826 https://answers.microsoft.com/en-us/windows/forum/all/start-... which appears to be a similar problem on Windows 7.
- throwanem 8y agoHmm. I haven't run into that one directly, but I have found that Start menu/taskbar issues tend to be very effectively solved by killing the explorer.exe process that's running the taskbar and starting a new one. It's a garbage way to have to solve a UI problem, I agree! But it's preferable to rebooting, or reinstalling, or what-have-you, I think. Might be worth a try with the Win10 issue, too.
- AnIdiotOnTheNet 8y agoOh believe me, it is one of the two dozen or so bullshit steps that is often recommended and it doesn't work. At least it has never worked whenever I've encountered the issue. Given that there are apparently so many different failure states for a fucking menu, I'm sure it's worked for some people.