There may have been a number of other factors at play that led to the decision to have windows 8.1 as the default. I wouldn't immediately jump to "shitty code"

There may have been a number of other factors at play that led to the decision to have windows 8.1 as the default. I wouldn't immediately jump to "shitty code" as the culprit here, especially when the tool works exactly as it should for it's intended audience. It may have been something as simple as developing this tool before having confirmation as to which user-agent win 8.1 would use at time of launch (is it be 5.2? nope, bumped up to 5.3. Good thing we put in that fallback before pushing into production!) or evaluating the ROI on supporting an 'other/unknown' fallback with additional development. One may consider putting resources toward developing code for a user-base that provides no return on the development investment is 'shitty coding'.