that's so random and weird. Why would they push that?
I mean, isn't it better for them if people don't want their games updated? Less wasted bandwidth and all that?
What you describe sounds as DRMish as it can be. Can't play the game unless you "update" it.
I suspect it's a combination of
1) That thing people were talking about recently in the Consolesdämmerung thread about being able to plug and play without any additional hassle. Consoles have traditionally been perceived as superior to PCs in this regard, and part of why Valve has become such a powerhouse is that it made ease of use one of Steam's pillars with a largely standardized one-step installation process and automatic patching.
2) A bit of that same paternalistic attitude that leads Bioware to make statements like this:
Attaching things to toggles is great, but if someone flips [friendly fire] on and doesn't know that it will suddenly make their "Easy" game not quite so Easy anymore... well, that wouldn't be good.
Also, there are a significant number of people who would be greatly annoyed by reading the entire line and then having it repeated to them verbatim. Your response might be "well, they shouldn't select that option then." But many people will. They'll see it in the list of options and think "oh, that's an option that will give me more information? More information is better!" and they'll select it... and then be annoyed by the result. So we would be trading one group of people who believe this is what they want for another group who would take the option and make it a poorer experience for themselves.
It’s not about hand-holding or forcing the player to experience the game only a certain way, but about avoiding the player getting a radically different experience of which they may not be aware and for which we would be responsible anyhow, since we provided the option. You click that option in the settings, thinking it will do one thing, but end up getting something different. We have to consider that, and consider how well it meshes up with the experience we are otherwise crafting, and which we intend to support.
Essentially, the idea is that sometimes you shouldn't give your customers an option because they might end up dissatisfied with their choice and blame you for their dissatisfaction. Which has an element of truth to it, in that people both tend to be poor predictors of what will make them happy and practice a great deal of self-deception to protect their egos. But it's still a shitty and condescending reason not to make an option available because (a) it assumes that you know better than your customers what they want/need, (b) it forces everyone down to the level of the lowest common denominator regardless of their own ability or preferences, and (c) the ability to choose has its own intrinsic value independent of the happiness or lack thereof that results from it.
3) Publishers and developers probably like it the way it is because they don't have to deal with people complaining about issues that were already fixed or reviewing an unpatched version of a game.
There's also the cost of implementation, but that's such a minor consideration in this case - where the program is already capable of all the necessary functions but simply combines some of them needlessly - that I can't imagine that it's a factor in their decision-making process.