Windows 10 users will soon have to pay to keep getting security updates

Estimate Reading Time: 2 minutes

For the first time, Microsoft is planning to offer paid-for security updates to home users who continue to use Windows 10 beyond Oct 14, 2025. Previously reserved for businesses, this option will enable individuals to continue using a secure operating system for at least one year.

-Advertisement-

While Microsoft is obviously encouraging home users and business users alike to switch to Windows 11, some are likely to continue to run Windows 10 with no hope of a future upgrade due to incompatible hardware. In fact, Windows 11 requires a recent, high-performance computer. The PC must have a 64-bit processor of 1GHz or more, combined with at least 4GB of RAM.

It also requires at least 64GB of storage space, a DirectX 12-compatible graphics card and a trusted platform module (TPM 2.0). So, short of buying a new PC, millions of people will continue to use Windows 10 in the months and years to come.

-Advertisement-

In a recent blog post, Microsoft explains that from Oct 14, 2025, Windows 10 will no longer automatically receive security updates. However, an Extended Security Update (ESU) program will be set up for all those who want to continue receiving security updates. Usually offered to business customers, this program will, for the first time, be open to home users too, in the form of a one-year option priced at US$30 – the price to pay to continue enjoying a secure operating system.

Note that this program will only provide critical and important security updates for Windows 10. No new features, bug fixes or technical support will be offered. The publisher has announced that registration for the program will open closer to the end of support, in 2025. The firm also states that it will continue to provide security intelligence updates for Microsoft Defender Antivirus until at least October 2028.
-AFP Relaxnews
-TheStar


Notice: ob_end_flush(): failed to send buffer of zlib output compression (0) in /home/capitalp/public_html/wp-includes/functions.php on line 5427