Microsoft, as a company, has issues with inter-team communication. So I'm guessing the bug of Windows drivers taking priority was discovered by the build team,

Microsoft, as a company, has issues with inter-team communication. So I'm guessing the bug of Windows drivers taking priority was discovered by the build team, and rather than talk to the relevant team about the problem, they decided to just fix it themselves with this hack. The adage "If it's stupid but it works, it isn't stupid" may apply here... or this may be the perfect counterexample. EDIT: It's also possible that this is the "simpler" solution. The behavior of the driver selector probably went through a litany of testing before this problem was discovered. Changing the driver ranking algorithm is a major modification that would warrant another litany of testing. Given budgets and deadlines, I can see someone implementing this hack as a clever way to avoid re-testing a major component. Technical debt is common for the same reasons monetary debt is common.