Skip to main content

That's a wrap! See all the announcements and debuts in our

NerdioCon 2026 recap!
Get a demo Try it free

Blog

Windows 10 end of life (what comes next?)

Windows 10 end of life leaves 6 paths: upgrade, replace hardware, use ESU, convert thin clients, adopt cloud desktops.

Table of Contents

If you're planning for Windows 10 end of life, the decision usually comes down to six paths: upgrade compatible devices, replace hardware, buy temporary extended security updates (ESU) coverage, convert older PCs into thin clients, move workloads into cloud desktops, or switch platforms. 

Most end-of-life planning guides spend their time on the first two. We will be focusing on two paths that deserve more attention (thin client conversion and cloud desktop migration) because they apply to the devices that don't qualify for Windows 11 and the workloads that shouldn't stay local. 

Windows 10 reached end of support on October 14, 2025. If you're still running it on part of your fleet, every unpatched month adds to your attack surface, and ESU costs double each year. 

This guide is for IT directors and end-user computing leaders deciding how to handle devices that can't upgrade to Windows 11, whether that means converting existing PCs to thin clients, migrating workloads to cloud desktops, or both. For many organizations, that decision now sits within Windows Cloud (Microsoft's umbrella for Azure Virtual Desktop and Windows 365).

Why the hardware question comes first

The first step is understanding what hardware you already have. 

Windows 11 requires a TPM 2.0 module, UEFI with Secure Boot, and a CPU on Microsoft's supported processor lists for Intel and AMD. Those lists include older processors such as 7th Generation Intel chips and certain AMD EPYC and Athlon models, but for mainstream business fleets the practical cutoff lands at Intel 8th Generation Core and AMD Ryzen 2000 series. Because most fleet devices below that line do not qualify, a large share of older hardware needs a different path forward.

Lansweeper telemetry showed that 39.9% of business devices worldwide were still running Windows 10 less than a month before the October 2025 deadline. A Canalys estimate put approximately 240 million PCs globally at risk of becoming e-waste because of Windows 11 incompatibility. Those devices are the ones this article addresses: functional hardware that still has endpoint value and needs a new role.

Running an unsupported OS also creates security and audit risk, especially in regulated environments where supported software and current patching matter.

Before committing procurement dollars, many enterprise devices carry firmware TPM implementations that may ship disabled by default in BIOS. A firmware audit across your fleet may recover devices that simply need a configuration change. That can shrink the replacement population before you spend anything.

Six paths forward after Windows 10 end of life

Your fleet likely needs a combination. Here is the full matrix.

1. Upgrade compatible devices to Windows 11

Devices meeting hardware requirements get a free in-place upgrade under existing Windows 10 Enterprise/Pro licenses. Primary costs are IT labor for assessment, compatibility testing, and deployment orchestration via standard tooling: MDT, Configuration Manager, Microsoft Intune/Autopilot, and Windows Autopatch. Enterprise rollout timing depends on fleet size and application complexity.

2. Purchase new Windows 11 hardware

Highest upfront capital expenditure, best suited when a large share of your fleet predates the Windows 11 hardware cutoff and capital budget or Device-as-a-Service financing is available.

3. Enroll in Extended Security Updates

Microsoft's ESU rates deliver critical and important security patches at $61 per device for Year 1, doubling to $122 in Year 2 and $244 in Year 3. The cumulative rule means joining in Year 2 costs $183 per device retroactively. Based on Microsoft's published per-device rates, a 1,000-device fleet would spend $427,000 over three years for patch-only coverage with no new features, no bug fixes, and no technical support. ESU is a temporary bridge and does not restore full Windows 10 support.

4. Convert existing PCs to thin clients

Repurpose Windows 10 hardware by replacing the local OS with thin client conversion software. Zero hardware acquisition cost. The converted device connects to a cloud desktop or VDI backend instead of running applications locally. Covered in depth below.

5. Migrate workloads to cloud desktops

Move desktop workloads to Windows 365 or Azure Virtual Desktop. The physical endpoint only needs a supported client to access a Windows 11 cloud desktop. Devices that can't run Windows 11 locally access it from the cloud. Also covered in depth below.

6. Switch to Linux or do nothing

Linux is viable for browser-only workflows but can introduce application compatibility gaps, including limited support for some desktop applications such as Microsoft 365 desktop apps, and may require different or additional endpoint management tooling. Running Windows 10 without ESU leaves systems without security updates after support ends and increases exposure to newly discovered threats.

Many fleets need a blend: upgrade compatible devices, convert incompatible ones, and migrate workloads to cloud desktops where the use case fits.

How to convert a PC to a thin client

Thin client conversion replaces a full Windows installation with a lightweight OS built to connect to remote desktops. The device stops running local applications and becomes a secure access point to a cloud-hosted or server-hosted desktop session. The hardware requirements are dramatically lower than Windows 11: IGEL OS does not require TPM 2.0, and  IGEL's published minimums range from 2–4 GB of RAM and 8 GB of storage depending on the OS version. That decade-old Dell sitting in your storage closet becomes a viable endpoint.

Thin client conversion software options

Seven tools dominate the market, and each takes a different approach.

  • IGEL OS replaces the host OS with a lean Linux-based system. It runs on x86-64 hardware (including low-specification laptops and PCs) making it viable for devices that can't meet Windows 11's hardware requirements. IGEL documents compatibility with both Azure Virtual Desktop and Windows 365.
  • nComputing LEAF OS is a small Linux-based OS that repurposes x86-64 PCs, laptops, and thin clients into cloud-ready endpoints for AVD, Windows 365, and other VDI and DaaS platforms. Minimum requirements are 4 GB of RAM and 8 GB of storage which is lower than Windows 11. PMC, nComputing's web-based endpoint manager, is included with LEAF OS licenses at no additional charge.
  • ThinScale ThinKiosk locks down the existing Windows installation into thin client mode without replacing the OS. ThinScale describes it as "Software-defined” with no device purchase or OS wipe. ThinKiosk installs directly on any Windows device and creates a locked-down environment that uses the Windows OS while preventing user access to the underlying system.
  • 10ZiG RepurpOS is a Linux-based OS designed for VDI, DaaS, and cloud access, deployable via USB onto existing PCs, laptops, or third-party thin clients. The minimum storage requirement is 4 GB. 10ZiG Manager, the included centralized management tool, ships with no per-device or per-user license fees.
  • HP ThinPro PC Converter converts existing PCs into Linux-based HP Thin Clients and supports any x86 hardware with a purchased license. The base license is perpetual and per device; software maintenance is available on 1- or 3-year terms. HP also offers a separate product (HP PC Converter for Windows) which maintains the existing Windows OS instead of replacing it.
  • Dell ThinOS 10 is available for both Dell and non-Dell devices. The August 2025 release expanded device compatibility beyond Dell's own hardware so ThinOS 10 can be installed on a wider range of existing PCs and thin clients. Dell publishes a Hardware Compatibility List (HCL) that outlines which Dell and third-party devices have been tested and validated for ThinOS conversion; organizations should verify against the HCL before fleet-wide deployment.

Picking the right tool is only half the work. The bigger risk lies in how the conversion itself is executed.

The failure mode nobody talks about

A common thin client conversion failure is installing a VDI client on an otherwise unmodified PC and placing a shortcut on the desktop. Nothing prevents employees from continuing to use the local Windows installation. IT ends up supporting both environments, eliminating every management benefit the conversion was supposed to deliver. 

A proper conversion either replaces the OS entirely or locks it down with a tool like ThinKiosk so users cannot access local Windows outside the managed session.

A clean conversion paired with the right OS gives aging hardware a defined, manageable role. The next question is whether that hardware sits on a desk or travels with the user.

Turn a laptop into a thin client for distributed teams

Laptops introduce constraints that fixed desktops don't. Battery life, Wi-Fi driver compatibility, offline access, and built-in peripherals (webcams, fingerprint readers, trackpads) all require validation that goes beyond a desktop conversion checklist.

  • Power and battery impact should be validated during pilots. The effect depends on the laptop hardware, thin client OS, and workload profile.
  • Wi-Fi driver compatibility is a key gating risk. The thin client OS must include drivers for the specific wireless chipsets across your target laptop fleet. Teams should validate this before fleet-wide deployment, not after.
  • Offline access is the most significant constraint. Thin clients typically require a network connection because applications and data are usually accessed from remote servers. Offline functionality is typically limited (e.g., using cached data) until connectivity is restored.

For BYOD scenarios, ThinScale's Secure Remote Worker product lets users launch a secure corporate session on a personal laptop with no trace of corporate data remaining after the session ends.

Whichever path an organization chooses, the converted laptop still needs a backend to connect to. That backend is where cloud desktops enter the picture.

Cloud desktops as the enterprise backend

Thin client conversion solves the endpoint problem. Cloud desktop migration solves the workload problem. They work together: the thin client OS converts the physical device; Windows 365 or Azure Virtual Desktop hosts the Windows 11 desktop the device connects to.

Microsoft's Windows 10 end-of-support guidance emphasizes Windows 11 upgrades and ESU as a temporary bridge, while also pointing organizations to Windows 365 as another path. Microsoft's support guidance highlighted Windows 365 as an option for organizations planning their next steps.

The financial case starts with one fact. Windows 10 Cloud PCs in Windows 365 and virtual machines in Azure Virtual Desktop receive ESU patches at no additional charge. Based on Microsoft's published ESU rates, moving 1,000 eligible Windows 10 workloads to cloud desktops avoids up to $427,000 in three-year ESU fees for those hosted workloads.

Windows 365 vs. Azure Virtual Desktop for this use case

Choosing between the two usually comes down to how predictable your usage is. 

Windows 365 automatically provisions a Cloud PC when a licensed user is assigned the required provisioning policy in Microsoft Entra ID. No manual VM creation or session host setup is required. Pricing is fixed per user per month as of April 2026: $28 for a 2 vCPU/4 GB RAM/64 GB Storage configuration, with pricing scaling up from there. Management runs through Microsoft Intune.

Azure Virtual Desktop is consumption-based. Your team manages session host VMs, scaling rules, and FSLogix profile containers in Azure. Multi-session pooled desktops let multiple users share a single VM. That lowers per-user costs for variable or shift-based workloads. The management surface is different: Azure Portal, PowerShell, and Microsoft Intune are all part of the operating model.

Windows 365 fits predictable-usage knowledge workers. Azure Virtual Desktop fits variable-usage populations, seasonal workloads, and scenarios where granular cost control matters. Some enterprises run both. 

Both platforms add management work at scale: 

  • Windows 365 around Cloud PC and Intune operations
  • Azure Virtual Desktop around session hosts, scaling, and cost control

The management tooling that connects thin client endpoints to cloud desktops at scale sits above that platform choice.

How Nerdio Manager fits the thin client and cloud desktop architecture

The architecture described above includes three layers: the thin client endpoint, the cloud desktop platform, and the management tooling that ties them together. Nerdio Manager for Enterprise is that management layer for Windows 365, Microsoft Intune, and Azure Virtual Desktop.

Nerdio Manager provides a unified console for managing Windows 365 Cloud PCs, Intune policies, and Azure Virtual Desktop resources. That can include policies for enrolled physical endpoints that access cloud desktops, but thin client vendors still manage the thin client hardware and OS through platforms such as IGEL UMS, nComputing PMC, ThinScale Management Console, or 10ZiG Manager. Nerdio Manager manages the cloud desktop layer and the Intune policy layer around supported endpoints; it does not replace the thin client vendor's device-management platform.

On the Azure Virtual Desktop side

Nerdio Manager's patented auto-scaling dynamically scales compute up or down based on real-time demand. It stops and deallocates idle VMs to eliminate waste, and switches OS disks from premium SSD to standard HDD when VMs are stopped and deallocated. TechTarget's Enterprise Strategy Group found that customers achieved up to 55% reduction in Azure Virtual Desktop costs with Nerdio Manager compared to running Azure Virtual Desktop alone. 

Desktop orchestration automates patching, versioning, and rollout to host pools with point-and-click workflows rather than manual PowerShell scripting.

Unified Application Management deploys applications to session hosts and Intune-managed endpoints from a single catalog.

On the Windows 365 side

This is where the day-to-day work shifts to Cloud PC and Intune operations rather than session host scaling, Nerdio Manager deploys applications to Windows 365 Cloud PCs in approximately 30 seconds via Unified Application Management. Its monitoring polling interval is configurable down to one minute, with a default of every five minutes. 

Nerdio Advisor analyzes Cloud PC utilization to surface right-sizing opportunities so oversized Cloud PCs can be reduced and underpowered ones can be corrected. It also identifies underused licenses that can be reclaimed and recommends Flex (formerly Frontline) license conversions where users never overlap in time. 

Nerdio Manager also backs up and restores Intune policies, a capability native Intune does not offer. Those are concrete operational outcomes on the Windows 365 path: faster application delivery, tighter Cloud PC sizing, fewer wasted licenses, lower-cost licensing where Flex fits, and recoverable policy management from the same console used for the rest of the cloud desktop estate. Readers focused on endpoint governance can also review Nerdio's Microsoft Intune overview.

Nerdio's thin client ecosystem partnerships

10ZiG and Nerdio are expanding their partnership to align 10ZiG's endpoint hardware, RepurpOS, and 10ZiG Manager software with Nerdio Manager for Enterprise. Nerdio also announced a new integration with IGEL live on stage at IGEL Now & Next 2026. nComputing (another Nerdio technology partner), connects its LEAF OS endpoints to the same AVD and Windows 365 management layer.

This architecture separates endpoint conversion from cloud desktop operations while keeping both in a defined operating model. That means managing them as connected decisions rather than disconnected projects.

Building your post-Windows 10 decision framework

The process starts with the fleet audit. Devices fall into four categories: 

  • upgradeable to Windows 11
  • convertible to thin client endpoints
  • candidates for cloud desktop migration
  • devices that should be retired

ESU buys time, and its doubling cost structure pushes Year 3 to $244 per device, a level that some organizations may find economically comparable to a hardware refresh amortized over four to five years. 

For fleets still carrying unsupported Windows 10 devices, rising security exposure and ESU's doubling cost structure turn this into an endpoint and workload decision, not just an OS upgrade project. Organizations typically upgrade the devices that qualify, convert the hardware that still has endpoint value, move the workloads that need a supported Windows 11 desktop into the cloud, and retire the systems that no longer fit any of those paths before ESU costs and unsupported-device risk compound further.

For organizations evaluating Nerdio Manager's fit, Nerdio provides resources for AVD TCO analysis. Organizations can Get a demo to see how Nerdio Manager works across your Windows 365, Intune, and Azure Virtual Desktop environment, or Try it free in their own Azure tenant.

Frequently asked questions about Windows 10 end of life options

Resources

Learn more about Nerdio Manager

Ready to get started?

Get a demo Try it free