Microsoft Will Eventually Start Charging You for Windows 10 Security Updates
1–10 of 92 posts
Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates
#2Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates
#3Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates
#4Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates
#5Nothing on this Earth could make me use Windows 11. I highly doubt Windows 12 will be any better.
Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates
#6https://learn.microsoft.com/en-us/troubleshoot/windows-clien...
Windows 8 didn't get an ESU program though, I have to assume because it didn't get the adoption of 7 and people mostly moved on to 10.
Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates
#7Cost to consumer, incentivizes companies to adopt new technology and avoid relying on specific OS versions. Seems like a good policy.
Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates
#8Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates
#9That's not what security updates are. They are fixes for errors in the original software. They are product recalls for dangerous product faults. You can't charge the customer because the product you shipped them was faulty.
Re: Microsoft Will Eventually Start Charging You for Windows 10 Security Updates
#10Cost to consumer, incentivizes companies to adopt new technology and avoid relying on specific OS versions. Seems like a good policy.
Or force you (the consumer) to upgrade to newer versions with hostile terms of service and/or applications. It works both ways.
Windows N+1 will share a majority of code with Windows N. Microsoft would now have to maintain two copies of the code N and N+1. This is added cost.
Alternatively Windows could do continuous releases, but this is less fun to market, and users might not like big changes happening many times a year instead of all at once, etc. There are also compatibility challenges for this since behaviors are tagged to such specific versions.