The most usual scenarios are with packages like Dropbox, Azure, VMware, etc. These regularly change and we sometimes have to react quickly to fix our integration for a specific type. In rare cases, it's the operating system version that causes issues. For example, the Windows 10 anniversary update forced a lot of our users to upgrade.Those reasons are outside of our control and most people understand the need to keep pace with the technology. There are other constraints when using other Devolutions products, namely our Devolutions Online Database service, or our Devolutions Server product. In all its history, we've kept it backward compatible with older versions of RDM, but with version 4.0 or our Server, we had to break with tradition because we brought significant architectural changes. Our current situation is that DVLS version 4.0 requires RDM version 12.0. We cannot commit to keeping the server forever backward compatible, but our track record indicates that we do not break compatibility lightly. If you use RDP, one can also see that the industry is moving towards HDPI displays. Those that follow Microsoft's insider preview program can see changes in that area in almost every release. They are keeping us on our toes and we cannot foresee when this will stabilize. This protocol is the most used within our community and it is likely that soon there will be another breaking change in that area.
Be assured that we do not wish to force people to upgrade, our licensing policy has always been customer friendly and we want to keep it that way.