steven36 Posted October 15, 2019 Share Posted October 15, 2019 Microsoft acknowledges Start menu critical-error warnings and says the issue will be fixed later this month. Microsoft says it will fix a lingering broken Start menu problem that's been affecting Windows 10 users over the past few weeks. Early last week, some users began reporting that the KB4524147 security update was causing printer problems, while others said they were seeing a 'critical error' message stating that the Start menu isn't working. Some users resolved the broken Start menu by uninstalling the update. Then on last week's Patch Tuesday Microsoft released KB4517389, addressing the printer-spooler problem that surfaced after users installed an update on September 23, according to Microsoft's known-issues page for Windows 10 version 1903. But while Microsoft acknowledged and appears to have fixed the printer problems, last week it hadn't found the Start menu issues affecting a large number of users. Nonetheless, it said it was investigating, according to Windows Latest. It has since spotted a post from a Microsoft engineer on the Microsoft Answers site who says a fix will arrive in late October. "We are aware of this issue and estimate a resolution to be released in late October," the Microsoft employee said in a post on Saturday. The timing suggests that the fix could arrive in one of Microsoft's optional updates that usually happen towards the end of the month. While that's sort of good news – of course, affected users would appreciate a faster fix – the recent run of issues following Microsoft's Windows updates is causing confusion even among Windows technical experts. In the meantime, some users have reported fixing the Start menu error by uninstalling both October 8's KB4517389 update as well as the earlier KB4524147 update. But, of course, that would mean uninstalling Microsoft's latest security patches. Fortunately, the October 8 Patch Tuesday update was relatively light and there were no fixes for zero-day flaws under attack. Source Link to comment Share on other sites More sharing options...
funkyy Posted October 15, 2019 Share Posted October 15, 2019 Sometimes (like in my case) ignorance really is bliss Link to comment Share on other sites More sharing options...
Karlston Posted October 15, 2019 Share Posted October 15, 2019 That's Microsoft's WaaS in a nutshell... release bugs now, fix 'em later... Link to comment Share on other sites More sharing options...
zanderthunder Posted October 15, 2019 Share Posted October 15, 2019 8 hours ago, steven36 said: "We are aware of this issue and estimate a resolution to be released in late October," the Microsoft employee said in a post on Saturday. Well, until Microsoft investigates the issue, you might need to use 3rd-party Start Menu solution. Currently I use Start10 1.75 by Stardock (repacked version by @VandIT). Link to comment Share on other sites More sharing options...
Karlston Posted October 15, 2019 Share Posted October 15, 2019 5 hours ago, Edward Raja said: until Microsoft investigates the issue, you might need to use 3rd-party Start Menu solution. And afterwards too... Link to comment Share on other sites More sharing options...
flash48 Posted October 15, 2019 Share Posted October 15, 2019 The only possible logical reason for this bug is Microsoft's QA department does not use the start menu. Microsoft should bring back the "ProgMan" app from Windows 3.11!! Link to comment Share on other sites More sharing options...
Karlston Posted October 15, 2019 Share Posted October 15, 2019 21 minutes ago, flash48 said: Microsoft's QA department Microsoft's WHAT department? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.