Microsoft has pulled the 1809 update for now and at the time of writing it still hasn’t been re-released. Two very recent examples of this can be found in the 1809 build of Windows 10 that rolled out to the public in September, only to be pulled shortly afterwards after reports of users having all their personal documents and files mysteriously missing after the update was applied the other is a zip archive file extraction bug that doesn’t overwrite files when the user asked them to be, potentially risking data loss if the user isn’t careful. Anything from unexpected annoying behaviour right up to failing to boot into Windows or BSODs (Blue Screen Of Death). Where this goes wrong is when there’s a bad patch. It also makes sure the whole user base for the most part is running with the latest patches installed, meaning everyone is reliably patched and up to date and are thus safer, and the ecosystem can react quicker to threats or issues, without much – if any – intervention needed from the user. In most respects it’s a good thing as this now forces Windows to update no matter what – which is great for handling users who don’t care for running updates or aren’t computer literate enough to know how – or are simply just too busy to remember. Since Windows 10, that control has been taken away from the user. Sure, you could allow Windows to auto apply updates when they became available, but you could also choose if or when to install each individual patch manually as you decided, or you could simply turn off automatic updates and not run the update check.

However, up until Windows 10, online update installation was always somewhat controllable by the end user.

When patching Windows via the internet became more popular it certainly sped up the frequency in which Microsoft could react to vulnerabilities and fix or add features.

Patchmypc home