Because the driver is the glue code between the device, and the operating system. What happens when the kernel changes, or needs to change? Then the driver on your devices don’t match up with the kernel anymore. A lot of Windows folks think Windows has some sort of stable interface and that’s why Windows is backwards compatible. But it’s untrue, Windows has inbox drivers, just like Linux has driver’s that build with the Kernel. Any driver that reaches inbox status get brought into the Windows source. As the Windows kernel changes, Microsoft engineers update all the inbox drivers to match the new kernel changes. When companies don’t get their driver inbox’d, they are responsible for keeping up with the kernel changes. Some devices eventually get left behind.
Because the driver is the glue code between the device, and the operating system. What happens when the kernel changes, or needs to change? Then the driver on your devices don’t match up with the kernel anymore. A lot of Windows folks think Windows has some sort of stable interface and that’s why Windows is backwards compatible. But it’s untrue, Windows has inbox drivers, just like Linux has driver’s that build with the Kernel. Any driver that reaches inbox status get brought into the Windows source. As the Windows kernel changes, Microsoft engineers update all the inbox drivers to match the new kernel changes. When companies don’t get their driver inbox’d, they are responsible for keeping up with the kernel changes. Some devices eventually get left behind.