Legacy or not, this affects all .NET applications and also to some extent NodeJS (with its crazy node_moules mess) and you have to apply all kinds of crazy workarounds for this not to come back and bite you.
The amount of builds I've seen broken over stuff like this is ridiculous.
If they can get this fixed proper, I'd love to offer the MS engineer who made this happen a beer or twelve.