god, irritating as hell. They couldn't hold off on the 16.4 release to incorporate this security update into it?![]()
It's possible that the security update was written by a separate team, and the issue was not known in time for integration into the .4 update. It's not easy, writing software as complex as an operating system. Plus there's the idea that 'programming is easy', and it *can* be, but all jokes aside, it's pretty complicated to 'just throw that update into the already shipping update'.
And, heck, I remember Microsoft 'patching NT4', and reintroducing their customers to previously squashed bugs. THAT was a lot of fun there... Yippee...