By 17 February 2021, some Windows 10 users were watching an update marked optional install itself after a routine check for updates. The package was KB4577586, Microsoft’s “Update for Removal of Adobe Flash Player,” and tests reported that it could install without a separate permission prompt.

Microsoft’s own documentation continued to describe KB4577586 as an optional Windows Update at that stage. What followed was more definitive: starting in June 2021, Microsoft began including the removal in Windows 10 preview and cumulative updates, and in July extended that servicing path across older supported Windows releases.

What KB4577586 actually does

The update targets the copy of Flash Player installed by Windows itself. That was the Microsoft-managed component used with Internet Explorer 11 and legacy Microsoft Edge, rather than every Flash runtime that might happen to exist on the machine.

Microsoft’s KB4577586 support page says the package removes the Windows-installed Flash Player and cannot itself be uninstalled once applied. It also says a Flash Player installed manually from another source is not removed, although Microsoft warns that registry settings associated with a third-party version may be affected.

That permanence made the patch unusual compared with ordinary Windows updates that can often be rolled back. Microsoft said restoring Flash after KB4577586 would require going back to an earlier system restore point or reinstalling Windows without applying the update.

Why the removal was staged so carefully

Adobe gave the industry years of warning. On 25 July 2017, the company announced that it would stop updating and distributing Flash Player at the end of 2020, working with Apple, Google, Microsoft, Mozilla and other technology partners on the transition.

The formal end-of-life date was 31 December 2020. Adobe then blocked Flash content from running in the official player beginning 12 January 2021 and stopped issuing security patches.

Microsoft had a separate problem to solve because Flash was embedded in Windows itself. Its September 2020 plan said the removal patch would first be optional through Windows Update and WSUS, then become recommended later, giving organizations with Flash-dependent line-of-business applications time to move away from the Microsoft-provided runtime.

The timeline therefore came in layers. Reports of automatic installation appeared in February while the package was still officially classified as optional; Microsoft then announced that KB4577586 would be folded into cumulative servicing from June, with more Windows versions joining that path in July.

Why Flash had to go at all

Once Adobe stopped maintaining Flash Player, leaving an old copy installed became progressively harder to justify. Adobe explicitly recommended uninstalling it because no further updates or security patches would be issued after the end-of-life date.

The web had already been moving away from plug-ins. In its 2017 retirement announcement, Adobe pointed to HTML5, WebGL and WebAssembly as technologies that had matured enough to provide capabilities that once required browser plug-ins.

Adobe’s own authoring software followed that shift. Flash Professional was renamed Adobe Animate CC with its February 2016 release after Adobe had added native support for HTML5 Canvas and WebGL; the company described the change as a move toward web-standard output while retaining support for formats such as SWF.

By the time KB4577586 reached ordinary Windows servicing, the question was no longer whether Flash would remain a mainstream web platform. Adobe had stopped supporting it, mainstream browsers were disabling it, and Microsoft was removing the copy built into Windows.

What the update does not do

KB4577586 is narrower than the phrase “remove Flash” can suggest. Microsoft’s documentation says it removes Flash Player installed by Windows; a copy installed manually from another source requires separate removal.

The package is also aimed at the player, not the old content itself. An SWF file saved to a hard drive does not disappear simply because the Microsoft-provided runtime capable of opening it has been removed.

That distinction matters for preservation. The open-source Ruffle emulator reimplements Flash playback using Rust and WebAssembly, allowing compatible SWF material to run in modern browsers without Adobe’s abandoned player.

The Internet Archive adopted the same approach in November 2020. Its archivists integrated Ruffle into the Archive’s Emularity system so preserved animations, games and other Flash works could continue running in a browser, and its Flash software collection remains accessible. Make Tech Easier has also looked at the wider effort to preserve Flash-era software and culture.

Why an operating system removes its own features

KB4577586 shows how differently modern operating systems age from software sold on a disc. A Windows installation is continually changed by servicing, and cumulative Windows updates can add fixes, replace components and retire code that Microsoft no longer intends the system to run.

Flash made that process unusually visible because the component had once been a familiar part of the web. Microsoft first let administrators deploy the removal separately, then made it available through Windows Update, and finally folded it into the normal cumulative-update stream.

After that point, removing Flash no longer required somebody to seek out a dedicated cleanup package. Keeping Windows current increasingly accomplished the removal as part of maintaining Windows itself.

What is left of Flash

On Windows systems that received KB4577586 through the removal package, a later cumulative update or an upgrade to Windows 10 version 21H1 or newer, Microsoft’s built-in Flash component was removed. Adobe had also taken down its official Flash Player download pages, and the standard player had been programmed to block Flash content beginning 12 January 2021.

The content survived in a different form. Old SWF files remain in personal collections and digital archives, while preservation projects use emulation to reproduce enough of the vanished runtime for many of those files to work again.

A Flash animation can therefore still open in a browser today, but the machinery underneath it is different. The Microsoft component that once sat quietly inside Windows is gone from serviced systems; what remains is the file, an emulator rebuilding the old behavior, and a piece of the web continuing to move long after its original player disappeared.