I see these iterations as consumers filling the os makers need for recurring revenue, and it can be disruptive. Most businesses need a foundation of policy and procedure. The way they print, scan, and even read email attachments often changes when a new os comes out. Often their mission critical software doesnâ(TM)t support the os, and in order to upgrade work around and compromises have to be made to a system that was secure, reliable, and predictable. I know at least one government is still using Windows 7. Most of the bugs and security issues have been worked out. Expensive custom made software remains compatible. Companies need stability, and a new OS is invariably disruptive. This is why many kiosks mobile computing systems and telephone systems are still using NT, CE, and OS/2. The investment of integrating these systems into a highly secure and well documented infrastructure is just too expensive or impractical to do every year, or every 5 years. Microsoft moving to a subscription based scheme is probably a good compromise. Clients can keep using the systems they have in place, people can be trained, and documentation doesnâ(TM)t need to be recreated every year. Of course the OS makers keep trying to push these organisations to use the new systems by taking away support, and creating new applications incompatible with older OSâ(TM)s. This will probably always be a point of contention.