Because there has been no word from Microsoft on this issue, and no patch to
the patch, I am quickly coming to the conclusion that what was earlier just
an assumption is, in fact, a fact: that this feature change poorly disguised
as a security patch was an intentional ploy by Microsoft to force driver
makers to update and sign their drivers.
Before this change, users could get around unsigned drivers so they probably
did not exert much pressure on the driver creators to update those drivers.
The behavior of this patch is such that users still have a way around the
unsigned drivers but now that work-around becomes a real nuisance. Could it
be that Microsoft is doing this to shanghai their customers into the fight
against unsigned drivers?