Windows 10 end of life is coming, what to do?

Updated: August 6, 2025

In a few short months, Windows 10 will reach the end of life (EOL) of mainstream consumer support. Without additional steps and remedies, by October 2025, roughly 50% of all Windows machines out there will no longer receives updates and patches. Yes, almost half of all boxen running Microsoft's operating system will become proverbial e-waste. If there's a better indicator to how much of a failure Windows 11 is, I can't name any. Never before has a "dying" version of Windows held such massive market share come its end of life. For that matter, the good ole Windows 7 was used by about 25% of all users when it was retired.

The reason I decided to write this tutorial is to help you with the conundrum. What do you do come October 2025? Should you upgrade to Windows 11? What if you cannot upgrade? Or don't want to upgrade? Are there any extended support options available? Should the end user be worried about the security implications of this change? Well, let's talk about all this, and then some.

Teaser

Official options

For the first time ever, Microsoft is offering Extended Security Updates (ESU) to its non-business users. You have three possible choices:

Alas, there are several caveats:

Should you do it?

My take is, no, unless you really have to, don't do this:

What if you do nothing, what happens?

Well, nothing. Your Windows 10 system will not suddenly explode or become super-vulnerable to hax0ring. Nope. Over time, perhaps months or even years, there may be some new vulnerabilities that may somewhat degrade the security posture of your operating system. Maybe. The thing is, the whole security drama on the desktop side is quite overblown, and it also depends much more heavily on your usage patterns than any specific software. In essence:

Believe it or not, that's the gist of it. But let me tell you some more. To wit, some security tips ...

How to stay protected

Okay, so, if you have a Windows machine, be it 10 or 11 or any, with or without patches, you have tons of tools and options to secure and harden your system. Practically, if you don't do stupid things with your computer, you won't experience any big problems. Here's how you may end up hax0red:

That's the general overview. Now, if you use Windows, here's what you can do:

Run a standard user account

Rather than being signed in as an Administrator all the time, use a standard account, with lesser privileges. You can always elevate privileges when needed. This reduces your attack surface. If you do encounter problems or exploits, they may fail or have lesser impact.

Windows hardening

One of the most overlooked tools available in Windows is the fantastic Exploit Protection framework. A successor to the equally amazing EMET, which still works for Windows 7 as it happens, is that it allows you to block entire classes of security risks by activating mitigations. These rules don't differentiate between good and bad programs per se. They simply block any bad or illegal instructions, whether they originate from benign or rogue software. If you apply mitigations for various programs, you can block or prevent most potential security risks.

System settings

I am always shocked and dismayed by the fact so few people talk about this superb toolbox. It's effective, light on the resources, and it does the job. Yes, your legitimate programs, due to sloppy coding, may also experience problems with mitigations in place. And yes, you do need some system understanding to utilize Exploit Protection effectively. But if you do, Bob's your uncle.

Use a good browser

Any of the modern crop will do, but Firefox is extra good. Why? It supports Manifest V2 extensions, including the amazing UBlock Origin (UBO), which lets you block ads, trackers, and then some. Not only will this make your Internet usage safer, it will also make it less stupid. You will use less data by not displaying crappy content, which includes pointless ads. And often, ads have been used as malware vectors, by either serving dangerous payload directly, or linking to suspicious or infected sites and software. Using UBO is a win win win on all fronts. Similarly, you can install the Noscript Security Suite (NSS) in Firefox, another amazing extension, which lets you block scripts, remote fonts, and more. With these as your default security tools, you're far less likely to see any Web exploits, let alone interact or activate them. Very neat.

If you use a mail client ...

Do you open your mail in a dedicated program like Thunderbird or Outlook? Well, then, you should:

Various other Internet-facing programs

The rules are quite similar to email clients, as the concepts are the same:

Attachments and media

By and large, try to use these as sparingly as possible. If you must, then:

Backups, snapshots

Always keep backups of your personal data. Multiple, verified backups. No matter what, no matter who, no matter when, at some point, you will encounter some form of data loss, through accident, negligence or whatever. Make sure you can recover from such problems, quickly and painlessly.

You can also create snapshots of your operating system. If something goes wrong, you can roll back to an earlier point in time. Cheaper and faster than reinstalling the entire operating system from scratch.

Social engineering

Most people won't ever be victims of brute-force attacks. Instead, they will fall prey to social engineering, to tricks of the mind designed to make them lower their guard. A combination of greed, haste, fear, and ignorance. The ways around the problem are:

And that's about it, really. If you do practice all these different routines, the chances of you getting hit by something bad is quite low. Perhaps even extremely low, updates notwithstanding.

So why even bother with updates?

Aha! Truly, for the common user at home, there's only one "real" reason why they should bother with updates. The word of the day is: compliance. You may be required to use a specific operating system, or a specific version thereof, to qualify for the use of certain online services.

For example, financial institutions or government portals may mandate that you use an up-to-date system when accessing their services. The requirements will usually be vague, on purpose, but they may read something like this:

The first bullet is what may "trip" you, if you're a Windows 10 user who intends to keep using the system after October 2025 (without ESU). You may use say a bank portal, and something goes wonky with your profile. The bank could make your life difficult if they insist you didn't follow their rules or guidelines. This scenario isn't very likely, but it COULD happen.

To that end, you may need to use an up-to-date operating system. That would mean, in October:

Enter virtualization

All right. So, we want to stay compliant. What's the quickest and easiest and cheapest way to achieve this, without any great changes on behalf of the user? The answer is: virtualization. This technology boils down to the following:

Why is this good?

Well, because you can run a COMPLIANT guest operating system on top of your Windows 10 machine, and inside the said guest, you can do all sorts of activities that require said compliance.

Choice of virtualization software

In the past 20 years, I've written a lot on tons of topics, including an entire section on Virtualization. Hop yonder for lots of useful, detailed tutorials. Now, specifically, if you need to narrow down your search for one particular piece of virtualization software (called hypervisor in technical parlance), then I would recommend you try VirtualBox. It's good for many reasons:

Furthermore, if you enable Guest Additions, VirtualBox also gives you 3D acceleration, to some extent, and you can use shared folders for host-to-guest sharing (although this lower security). There's also USB 3.0 bus, and as I mentioned earlier, you can "pass-through" your peripheral devices into guest systems. For example, you can let the guest use your USB drives (including hardware tokens and security devices). For additional functionality like RDP and encryption (by VirtualBox itself), you will need to install the Extension Pack. This component of the program is proprietary and optional, and it is only available for free for personal and educational use.

Passthrough

You can "forward" your peripherals into the guest operating system.

Virtualbox, snapshots 1

Taking an operating system snapshot.

Virtualbox snapshots 2

As a nice nostalgic example, here's Windows 7 guest with a couple of snapshots.

And so, you can keep using your Windows 10 machine, install VirtualBox in it, then, inside VirtualBox, configure one or more guest operating systems, all of which will be compliant - fully supported, with available patches, and up to date. Bob's your uncle!

What should you choose as your guest operating system?

There's no one answer. But there's a zero-cost answer. Linux.

Linux is an operating system, much like Windows. Long story short, as I will demonstrate shortly, you can have a full Linux desktop installed as your guest, and inside it, you can do various activities like banking, work with government portals, browsing, and more.

There isn't one Linux. There are many implementations of Linux. Each of these implementation is called a distribution, and they have names like Ubuntu, Kubuntu, Fedora, etc. My guide for newbies explains this some more.

Dedo, are you trying to make people use Linux?

Slow down. I am NOT trying to convert anyone into Linux, nor do I say it can replace Windows. Quite the opposite. The reason I'm suggesting virtualization and the use of Linux as a guest is exactly because I don't expect people to change their habits overnight, nor should they.

All that said, please note:

Which Linux distribution should you select then?

My take is, anything Ubuntu-based, preferably Ubuntu itself or Kubuntu. It really depends on what sort of visual layout and workflow you prefer for your desktop. The former has a more Mac-like setup. The latter has more of a classic Windows setup. I use Kubuntu, as I like it more.

The main reasons why I would recommend these two, among many dozens of Linux distributions are:

What can Ubuntu do?

Well, lots and lots. I've done tons of testing compliance wise and compatibility wise, and I've yet to encounter a serious obstacle. I tried various government and banking portals, including a service that requires the use of a hardware token (with certificates). I was able to use payment systems like PayPal and friends. Funnily enough, you're more likely to have problems with such tools based on your browser (e.g.: Firefox vs. say Chrome) than you are with an operating system choice (Windows vs. Linux).

Now, let me tell what Ubuntu cannot do (and neither of these affects our need for compliance):

Effectively, if you fire up an Ubuntu system, patch it up, and then use Firefox, Chrome, Edge or Brave inside it, you are going to be compliant with any modern security needs. Perhaps a service here or there may mandate Windows only, but I've yet to encounter such a scenario. Up to date system, up to date browser, and you're golden. For free.

Virtualization: Windows 10 host, Linux guest

This is your ideal setup. Minimal hassle, minimal change. You have everything you need in your Windows 10 box, check. You can still run programs and games as you did before. Now, you need to do something a bit more serious, with security and compliance? No problem. Fire up VirtualBox, launch your Ubuntu or Kubuntu, make sure they are up to date, and then do your banking or whatnot.

In fact, this usage scenario is way more secure than default Windows!

Linux guest

VirtualBox running in Windows 10. Here, I have a Kubuntu 24.04 installed as a guest. Fully up to date, usable, compliant, you name it. I have several browsers available, including two versions of Firefox (from a tarball and as a snap) plus Chrome and Edge. I can access and use any online service without any issues. I've created several snapshots of the guest operating system, and I frequently take new baselines, so if anything goes wrong, I can easily revert.

Security risks?

What I'm going to expand on below is almost sci-fi level of impossible, but I want to bring it up so you have a total and full understanding of the compliance implications of your setup:

And that's about it, for this particular use case. Let's move onto a more exotic scenario.

Virtualization: Linux host, Windows 10 guest

This is a more advanced scenario. It actually implies you can install and run Linux on physical hardware, but you still have some Windows-related needs. Indeed, I have exactly that. As an author, who writes books and often needs to send manuscripts and proposals to publishers, I must use Microsoft Office. Lots of these publishers require that the material be sent in DOCX format. That's life.

So, I am "blocked" from using Linux 100% of the time by my Office needs. No problem.

Virtualization

Windows 10 running inside VirtualBox on top of Kubuntu. The Windows 10 machine has Microsoft Office. And it can be set to fully offline use, with no network, providing excellent security without any loss of expected functionality.

Other, more advanced scenarios: dual boot, native Linux

Let me emphasize, I do not say that you ought to do or that you can do this. I am under no illusion that switching to Linux is easy, or that Linux can satisfy your actual usage needs. But if you can switch, and you're not limited by software or your ability to install and configure an operating system, then please consider this option as your Windows 10 legacy, if you will.

Dual boot

The idea is as follows: you install a Linux distribution alongside your Windows 10. You do some repartitioning of the hard disk, and set up the other operating system in the freed up space. Thus, you can boot into either one instance as you see fit. But this also requires more maintenance, some disruption to work, and you need to be extremely comfortable with this sort of configuration. There could also be hardware-related issues, like drivers and such. Not for the faint-hearted.

I have written several guides on how to accomplish this. They are for Windows 7 and Windows 8, but they are still 100% applicable. In particular, everything related to disk management hasn't changed. Even if you only wish to read these two tutorials as exercise, the lessons are practical and useful. The second guide also covers the UEFI boot scenario, which is what you would/will face today.

Native Linux

If you have a spare machine, you could try Linux fully natively. Burn/copy a Linux distribution ISO to a USB drive, then boot it on that system. Most Linux distributions come with a live environment, that is, you can test how the distribution looks and behaves before you decide to install it. Thus, if you try any one particular distribution, and you don't like it, you can try a different one, without making any changes.

This way, you can have a dedicated box running Linux, and use it for any compliance-related purposes, with a full up to date system and modern browsers and all that. And you can continue using your Windows 10 for other tasks, like say gaming.

The installation on physical hardware may be somewhat daunting, but you can practice with virtualization first! You can create any number of virtual machines, configure any number of Linux distributions, play with disk management and partitioning, even create dual-boot scenarios! Once you feel comfortable with the notation, the commands, and all the steps needed to safely handle a new operating system, you can then move on to real hardware in earnest. I've written about this dozens if not hundreds of times before. You can check my Linux distribution reviews, or any hardware-related article on the same topic. For instance, I also use one rather phenomenal Slimbook Executive, also running Kubuntu. Very neat.

Teaser

My Slimbook Executive, another Linux-native system that I use.

Conclusion

The end of life of Windows 10 is not the end of the world. Far from it. One, you're less likely to be pestered by pointless and nonsense upgrade nags. Two, various enterprise versions of Windows 10 will persist and remain supported until 2031/2, perhaps even longer. With 50% of all Windows boxes still running this version, you can bet your left kidney there will be awesome software and game support for the '10 for many years to come. Three, with good hardening and smart browsing, you're not in any great danger.

If compliance is what bothers you, then you can try Linux, for free, and with minimal changes. With virtualization in place, you can merely add to your setup, lose no functionality, and even gain security. For that matter, if you need to do "risky" browsing, do it in a special Linux virtual machine. If you make a mistake there, and there's no personal data inside, no big deal. Erase it, revert to an older snapshot, whatever. For that matter, even if you use Windows 11, if you spin up Linux guests, you will gain on security!

My testing over the past three years is positive. Linux never tripped the alarm sensors doing online things and services. Browsers did, on the other hand. Since many (crappy) sites are coded for Chromium only, similar to the situation we had with Internet Explorer 6 back in the day, some online services may fail in Firefox. But not because of Linux. Because of bad programming, and the browser requirements. And since all modern browsers work fine in Linux, this shouldn't be an issue. I even tested security hardware token passthrough in VirtualBox, and that worked like magic. Personal experience.

And those are your options for October 2025. Security hardening, smart use, virtualization, up-to-date browser, and you don't need to pay a tithe to Microsoft, or use its pointless Windows 11 system. You can be compliant and secure. In fact, by mixing Linux into the equation, you can be more secure than Windows alone can ever do. So, lament not, keep your Windows 10 boxen if you want or need to, and just do some extra work and experimentation with Linux. I think you'll be pleasantly surprised.

Cheers.