![\"Windows](\"https:\/\/www.europesays.com\/uk\/wp-content\/uploads\/2025\/11\/1762346539_434_960x0.jpg\")
<\/p>\n<\/p>\n
This update mistake has finally been fixed.<\/p>\n
NurPhoto via Getty Images<\/p>\n
Updated on Nov. 5 with details of the fix for Microsoft\u2019s latest update mistake.<\/p>\n
Microsoft has finally confirmed a serious update mistake affecting Windows 10 and Windows 11 users. It has now issued a fix. This comes after multiple emergency updates<\/a> and issues were confirmed<\/a> through October. A month that also saw Microsoft bring Windows 10 to an end, stopping security updates for millions of users.<\/p>\n ForbesIf Your Work Password Is On This Website, Change It NowBy Zak Doffman<\/a><\/p>\n This latest fix resolves a long-standing issue where selecting \u201cupdate and shut down\u201d on a Windows 10 or Windows 11 PC would \u201cupdate and restart\u201d instead. Per Windows Latest<\/a>, \u201cstarting with Windows 11 25H2 Build 26200.7019, and newer, your PC will finally shut down when you explicitly choose \u2018update and shut down\u2019.\u201d<\/p>\n The Windows specialists describe this as a \u201cdecades-old bug,\u201d albeit it\u2019s unclear when it first began to affect users. What is clear is that \u201cit affects Windows 11 and 10, and is one of the most reported issues. Microsoft shipped a broken \u2018update and shut down\u2019 toggle with Windows 10, and it never acknowledged it until now.\u201d<\/p>\n While this might be little more than an inconvenience for desktop users, it\u2019s a very different matter if it happens to your laptop. \u201cWhen it\u2019s 11 PM and there\u2019s a pending Windows Update. I\u2019d select update and shut down, and go to bed, but the next morning, Windows would be on the login screen if its battery didn\u2019t drain out.\u201d<\/p>\n Update and Shut Down \u2014 Windows update mistake resolved.<\/p>\n Windows Latest<\/p>\n The two different options appear side-by-side, so it\u2019s easy for users to assume they have selected the restart option instead of the shut down option by mistake. Now Microsoft has confirmed \u201cthe October 2025 optional update (KB5067036) finally fixes it.\u201d<\/p>\n This isn\u2019t the only update change that Microsoft has just confirmed for Windows users. As spotted by Neowin<\/a>, \u201cMicrosoft is making Windows updates simpler and ‘more intuitive\u2019.\u201d This means updates will have more “user-friendly” names rather than then jumble of numbers and codes that users have waded through until now.<\/p>\n Microsoft explains<\/a> \u201cto further enrich the user experience, we\u2019re introducing a simplified and standardized titling system for a range of updates. This new format is designed primarily with the user in mind. Titles are more intuitive, consistent, and informative to help users quickly understand what updates they\u2019re receiving.\u201d<\/p>\n New update names confirmed.<\/p>\n Microsodt<\/p>\n Microsoft provides examples of the new, updates titles here<\/a>. \u201cWe\u2019ve removed unnecessary technical elements such as platform architecture or date prefixes, while keeping identifiers like the KB number and build or version.\u201d<\/p>\n Unfortunately, not all Windows update mistakes have been fixed. Windows Latest<\/a> also warns that \u201cMicrosoft admits a long-standing Windows 11 driver 0x80070103 error, and says it can\u2019t fully fix the issue.\u201d An October 2025 patch does make this less acute.<\/p>\n The issue occurs when installing a driver that\u2019s already on the PC. Windows Update shows 0x800f0983. \u201cMicrosoft officials previously told users to ignore error 0x800f0983 because there\u2019s nothing you can do. One of the workarounds is to reset Windows, but what if you come across the same error again?\u201d<\/p>\n Hopefully, it won\u2019t now affect you.<\/p>\n Meanwhile, Microsoft has now corrected another mistake, after over-simplifying its update process. Per Windows Latest<\/a>, \u201con Nov 1, Microsoft removed the month-year (YYYY-MM), the word \u2018cumulative,\u2019 and OS version from Windows Update titles. After outrage from IT admins, Microsoft says it will bring the dates back.\u201d<\/p>\n Microsoft confirms \u201cwe are going to ensure that the date (month and year) remain present on update titles.\u201d It remains to be seen whether any more of the now removed information will also be restored to the update titles. You can see why this could be causing havoc for those responsible for managing hundreds or thousands of PCs.<\/p>\n The dateless update.<\/p>\n Windows Latest<\/p>\n Perhaps if there\u2019s more of a backlash from the IT admin community, Microsoft will backtrack further.Apparently, \u201chundreds of IT administrators have called out Microsoft for unnecessarily changing the titles of Windows Updates.\u201d<\/p>\n \u201cUp until now, there was nothing confusing about these update titles,\u201d Windows Latest says. \u201cBut on October 28, when Microsoft released a new optional update (KB5067036), we noticed that it looked very odd when it showed up for download.\u201d<\/p>\n These update mistakes are not confined to Windows 11 users. Separately, Microsoft has also confirmed that some Windows 10 users are seeing the \u201cyour version of Windows has reached the end of support,\u201d even when they shouldn\u2019t. <\/p>\n As Neowin<\/a> explains, \u201cthe tech giant has clarified that this is a false notification that is incorrectly being displayed on the following Windows 10 versions: Windows 10, version 22H2 Pro, Education or Enterprise editions that are correctly enrolled in the Extended Security Updates (ESU) program and configured with an ESU product key, Windows 10 Enterprise LTSC 2021, Windows 10 IoT Enterprise LTSC 2021.\u201d<\/p>\n ForbesApple Starts Silently Updating Your iPhone\u2014Do Not Stop ThisBy Zak Doffman<\/a><\/p>\n This incorrect out-of-support notification is generating more coverage that might be thought. But that\u2019s hardly surprising. given that Windows 10 is stubbornly refusing to go away, with its market share<\/a> still sticking above the 40% level.<\/p>\n Per Windows Central<\/a>, the Windows bug \u201ccauses Windows 10 users to see an error when they check for updates, even when enrolled into Microsoft\u2019s extended support program.\u201d And given the intense push for users to enroll before or not long after the Oct. 14 deadline, at which point regular Windows 10 security updates stopped.<\/p>\n \u201cWhen this error appears,\u201d the website says, \u201cit\u2019s not possible to click the check for updates button. Luckily, Microsoft says that there\u2019s nothing to be worried about, and that Windows Update will still successfully download and install the latest security updates as issued via the ESU program.\u201d<\/p>\n Microsoft says it has already fixed the issue, which is server-side, so it should disappear from worried users\u2019 screens any time now, if not already.<\/p>\n