Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2024 Poal.co

1.2K

You know, this is why you typically have a non-prod environment that you can snapshot/backup/etc to test patches before your roll them out to the fleet. This is not just Microsoft fucking up but bad practices by the SA's in charge of the deployments of patches/systems (Well, they are MS admins after all).

Archive: https://archive.today/XVc0q

From the post:

>Administrators are reporting unexpected appearances of Windows Server 2025 after what was published as a security update turned out to be a complete operating system upgrade. The problem was flagged by a customer of web app security biz Heimdal. Arriving at the office on the morning of November 5, they found, to their horror, that every Windows Server 2022 system had either upgraded itself to Windows Server 2025 or was about to.

You know, this is why you typically have a non-prod environment that you can snapshot/backup/etc to test patches before your roll them out to the fleet. This is not just Microsoft fucking up but bad practices by the SA's in charge of the deployments of patches/systems (Well, they are MS admins after all). Archive: https://archive.today/XVc0q From the post: >>Administrators are reporting unexpected appearances of Windows Server 2025 after what was published as a security update turned out to be a complete operating system upgrade. The problem was flagged by a customer of web app security biz Heimdal. Arriving at the office on the morning of November 5, they found, to their horror, that every Windows Server 2022 system had either upgraded itself to Windows Server 2025 or was about to.
You are currently inside a comment thread.
Click here to see all the comments (4).
[–] • 1 pt

No arguement, it's one of my biggest gripes (And why I'd leave an Arch distro) about Pacman. No control to stop upgrading a single package during an update. But at least I dont worry about my distro updating without physical input from me.