This is the exact opposite of Linus's well known and ranted about position on kernel compatibility with user space.
https://lkml.org/lkml/2012/12/23/75
https://unix.stackexchange.com/questions/235335/why-is-there...
https://blogs.technet.microsoft.com/askperf/2008/04/23/under...
https://blogs.technet.microsoft.com/joscon/2010/06/15/servic... https://blogs.technet.microsoft.com/joscon/2010/07/06/servic...
A handful of Windows calls can be used to detect the version, if necessary.
What new Microsoft software will install on ancient windows anyway?
E.g. Office 2016 system requirements: https://support.microsoft.com/en-ca/help/4026853/office-offi...: Windows 7 or newer, or Server 2008 or newer.
Do we need deep analysis to sort out whether we're on 7, 8, or 10?
Windows installers are designed to fail if they detect software piracy. For instance a machine with MS Office installed, install Delphi, uninstall Delphi and Office refuses to run. Presumably because it thinks it's been copied from another machine.
The Windows software system has different tradeoffs than Linux where distributions are compatible with specific versions of software -- i.e. if the distro doesn't have a package there may not be binary compatibility. With Linux changes to the kernel can require cascading upgrades to packages or make packages obsolete or break packages.
Windows' tradeoffs are also different than those made by BSD and similar systems that eschew binary distribution --- systems where everything gets compiled from source on the user's machine. In terms of speed, compiling a large application from source can take significant time though it will probably require few if any reboots.