What you need to know
- Microsoft is investigating an issue with Start and search that appears after updating to KB4515384.
- The issues can cause the Start menu to not work, not appear, or lead to a "Critical Error."
- The issues seem limited to a select number of devices.
Microsoft is investigating another search-related bug (opens in new tab) that appears in Windows 10 following a cumulative update. Several users reported issues with the Start menu after updating to cumulative update KB4515384. This is a separate issue from the high CPU usage issue that appeared last week.
This new issue can cause the Start menu to not appear, not work, or lead to a system stating it's run into a "Critical Error." The issue also breaks Windows Search in the taskbar. The critical error that appears states, "Your Start menu isn't working. We'll try to fix it the next time you sign in."
The issue seems to only affect a select number of devices. While there's a chance that it is related to the bug on build 18362.329, enabling the "BingSearchEnabled" Registry key won't resolve the issue. We have a guide on how to fix the issue by uninstalling the update that can help you use the Start menu and Windows Search while Microsoft figures out the issue.
Sean Endicott brings nearly a decade of experience covering Microsoft and Windows news to Windows Central. He joined our team in 2017 as an app reviewer and now heads up our day-to-day news coverage. If you have a news tip or an app to review, hit him up at firstname.lastname@example.org (opens in new tab).
Garbage software from Microsoft. Use Startisback, Start20 or Classic Shell to get back a normal start menu and search.
It's seems to be breaking Start Menu when you have uninstalled Provisioned Apps with DISM command.
EVERY WINDOWS UPDATE BREAKS SOMETHING
...this has been repeatedly proven over the past 30 years. The solution is here: https://ubuntu.com/download/desktop
Thank you for signing up to Windows Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.