14 DAY TRIAL // The infamous cumulative update KB4515384 for Windows 10 version 1903 is not to blame for Start menu and search issues, Microsoft says.
The software giant rolled out this cumulative update on September 10 as part of its Patch Tuesday cycle. Shortly after the release kicked off, users started reporting various issues on their devices, including network connectivity problems and broken audio when playing games.
One more widespread problem concerned the Start menu and the search feature, which according to so many users, stopped working correctly after installing Windows 10 version 1903 cumulative update KB4515384.
Microsoft was quick to acknowledge these reports, promising to investigate the potential issues and come up with a fix.
“Microsoft has received reports that a small number of users are having issues related to the Start menu and Windows Desktop Search,” the company originally said.
Update not to blame
But in a new message posted on the Windows update dashboard, Microsoft says cumulative update KB4515384 is not to blame for these issues, so the company just asks users to send more feedback and then points them to a generic Windows Search troubleshooting guide.
“At this time, Microsoft has not found a Search or Start issue significantly impacting users originating from KB4515384,” Microsoft explains.
“We will continue monitoring to ensure users have a high-quality experience when interacting with these areas. If you are currently having issues, we recommend you to take a moment to report it in via the Feedback Hub (Windows + F) then try the Windows 10 Troubleshoot settings (found in Settings). If you are having an issue with search, see Fix problems in Windows Search.”
At this point, it just seems like users hitting these problems are on their own in an attempt to restore the Start menu or the search feature, and in most of the cases, many turn to the ultimate solution that involves removing the cumulative update altogether.
A new round of cumulative updates is expected later this month and it’ll be interesting to see if they fix this glitch or not.