@LDS
Exactly. This is, perhaps, an oversight in the way things were originally developed and this crash shows on of the reasons why it's so difficult to fix after the fact.
Developers use the code and libraries and so on as they are provided. Sometimes they use deliberately undocumented calls to enable functionality or improve speed or simply make their coding easier. Problem like this can occur - in part - when MS 'fix' something and it then breaks the way a third-party uses that feature/library/API.
It does seem as though - based on the widespread report of this issue - that MS really did mess this up. Using the excuse that you can't test for everything only really works if it's just a small number of people affected.
Biting the hand that feeds IT
