> wouldn't it be more productive if they'd put some pressure on Synaptics to fix it? They might take notice if Microsoft comes knocking. It's possible that is

> wouldn't it be more productive if they'd put some pressure on Synaptics to fix it? They might take notice if Microsoft comes knocking. It's possible that is happening, indeed, I suspect it's likely. The Microsoft developer "Orange" who the blog poster linked to is almost certainly Gov Maharaj (ORANGE),[1] a very prominent member of the Windows application compatibility team who has earned enough influence internally to be able to lean on hardware vendors like Synaptics through the hardware compatibility and partner ecosystem teams. I used to work at Microsoft and saw Gov in action on internal email lists for people running daily Windows builds. He probably answered about a quarter to half of all the "this program is broken in this build!" emails. You can see Gov (and perhaps be surprised by his technical chops) on the MSDN "Defrag Show" PC troubleshooting video series. [2] [1] Origin of the name "Orange": https://blogs.msdn.microsoft.com/oldnewthing/20081021-00/?p=20503 https://blogs.msdn.microsoft.com/oldnewthing/20081021-00/?p=... [2] https://channel9.msdn.com/Shows/The-Defrag-Show https://channel9.msdn.com/Shows/The-Defrag-Show