Couldn't have phrased it better.
I work just across the hall from the IT worstation guys who have to roll out MS patches to the rest of the environment. I speak to them about their opinions about MS patch-Tuesday.
I havn't seen it myself, but evidently these patches are released for testing to support groups at workplaces early. This allows the people at work to test and make sure that the patches don't break something else. Just recently there was a patch released by MS that our support group said did not pass the test criteria. A few days after the patch was released - sure enough - MS put out a patch for the patch because they broke something.
So, you ask, why can they release a patch for DRM outside of their normal patch release? [honestly, can't you see already?]
Because being entertained while at work is not something that a workplace would test for! We, who listen to music or view You-Tube while at work are usually close to violating company policy anyway. Why would a support desk team even need to test a patch for software that the company discourages running?
To extend the idea, why would MS need to give workstation support groups time to test something they might have disabled on the workstations? The hordes of home-users of MS software an OS aren't going to get together and sue MS if a patch they released on WMP (or whatever) breaks and it hoses WMP (or whatever) for a few days. But I can imagine that companies the world over have it written into their contracts that if a patch from MS causes problems that the companies can seek $$$$ either in withheld payments or punitive amounts.
C'mon! Apply a little sense TMV, can't you see, now, why MS could release a patch for DRM, but wait to release other patches until 'patch Tuesday' ???