3 ms·
Looks like this is an issue with a a third party update client being confused by a potential misclassification in Microsoft's side about the update (security up
by jeroenhd 2y ago
Looks like this is an issue with a a third party update client being confused by a potential misclassification in Microsoft's side about the update (security update vs upgrade).
What I'm most surprised by myself is that there doesn't seem to be an option to revert this according to the comments. I'm pretty sure consumer Windows allows downgrades for upgrades installed in this manner, I can't imagine the pain it'd be to need to manually undo all the damage after an unintended upgrade using automated tooling!
- tallanvor 2y agoI agree that this looks like a 3rd party issue. They claimed that KB5044284 was the update, but others have noted that after installing that update, they had the option to upgrade to 2025 but it didn't happen automatically - seems the 3rd party RMM somehow pushed a command to start the upgrade. Honestly, I guess since it's an SMB it might make sense that they aren't able to test all patches before applying them in production, but you'd hope they'd delay the installation for a few days to let others catch major issues.
- graemep 2y agoWhat do third party update clients do? Why are they used? Why are they even able to upgrade the OS version? Not a Windows version and unfamiliar with how it works.
- worewood 2y agoProbably the third-party solution offers functionality not available from Microsoft, for example integrating with other management software they may have, enabling automated blue-green scheme for applying updates, so they can accurately measure the impact of updates for example.