Because now you're moving the goalposts. This is about forced driver updates (read the title).
The issue is bigger than that, and this story is just one early example of how forced updates could go wrong (read the summary, and for that matter numerous other discussions on this and other forums since the forced update mechanism became widely known a few days ago).
I'm happy for you that apparently the systems you use are all running Windows Enterprise, and the people who set them up and maintain them have no problem with spending time figuring out which settings to adjust to turn this stuff off. Obviously from the fact that we're having this discussion a lot of people didn't know to turn this off and got stung by it, and as I've noted repeatedly, there are analogous cases that could be just as damaging but which will not have the option to turn them off even in Pro. A lot of people are going to wind up getting hurt by this policy, even if you personally aren't one of them.