Windows 10

Windows 10 Will Now Automatically Uninstall Corrupted Updates

With the release of Windows 10, Microsoft has moved to a significantly more aggressive schedule of releasing updates. Even though most of the times the updates install smoothly, when they don’t, things typically go downhill, fast.

Starting with the latest updates, if Windows detects a failed startup following an update, the OS will attempt to remove the update, and reboot the machine to see if this fixes the problem. If this does resolve the issue, Windows will not attempt to re-install the update for 30 days with the goal being that this is enough time for Microsoft or the OEM to fix the issue that is causing the machine to fail on startup.

This is an excellent update to Windows and should help to avoid downtime associated with a failed update. You will know if this process has happened on your machine if you see the prompt “We removed some recently installed updates to recover your device from a startup failure”.

Sponsored Content

Maximize Value from Microsoft Defender

In this ebook, you’ll learn why Red Canary’s platform and expertise bring you the highest possible value from your Microsoft Defender for Endpoint investment, deployment, or migration.

The more obvious question is why did it take this long for this functionality to arrive? A failed boot after updates has been an issue since the inception of Windows Update was introduced into Windows but late is better than never. You can read more about this new feature, here.

Hopefully, you won’t ever see this message on your device, but if you do, just know that you now have thirty days to figure out which update was causing the issue before the process starts all over again.

Related Topics:


Don't have a login but want to join the conversation? Sign up for a Petri Account

Comments (3)

3 responses to “Windows 10 Will Now Automatically Uninstall Corrupted Updates”

  1. <p>Most of the update failures don't result in a startup failure. They result in a loss of performance or connectivity issues between systems and/or applications that would not normally be detected by the update manager.</p><p>This appears to be a solution to a highly visible issue that occurs on rare occasions, at least in our 12,000 seat environment anyway</p>

Leave a Reply

Brad Sams has more than a decade of writing and publishing experience under his belt including helping to establish new and seasoned publications From breaking news about upcoming Microsoft products to telling the story of how a billion dollar brand was birthed in his book, Beneath a Surface, Brad is a well-rounded journalist who has established himself as a trusted name in the industry.
External Sharing and Guest User Access in Microsoft 365 and Teams

This eBook will dive into policy considerations you need to make when creating and managing guest user access to your Teams network, as well as the different layers of guest access and the common challenges that accompany a more complicated Microsoft 365 infrastructure.

You will learn:

  • Who should be allowed to be invited as a guest?
  • What type of guests should be able to access files in SharePoint and OneDrive?
  • How should guests be offboarded?
  • How should you determine who has access to sensitive information in your environment?

Sponsored by:

Live Webinar: Active Directory Security: What Needs Immediate Priority!Live on Tuesday, October 12th at 1 PM ET

Attacks on Active Directory are at an all-time high. Companies that are not taking heed are being punished, both monetarily and with loss of production.

In this webinar, you will learn:

  • How to prioritize vulnerability management
  • What attackers are leveraging to breach organizations
  • Where Active Directory security needs immediate attention
  • Overall strategy to secure your environment and keep it secured

Sponsored by: