Exactly - it would be interesting to know what borked the driver - a bad kernel change, or a change that triggered some bad code issue in HP code which went unnoticed before?
Anyway, why MS thinkers with kernel code so often is a bit worryingly - it got issue with the Intel audio driver, now with the HP keyboard one.
Biting the hand that feeds IT
