Windows 10 reached end of support on October 14, 2025. Microsoft no longer ships regular security updates for it, though eligible devices can receive critical and important security updates through the Extended Security Updates (ESU) program for a limited time [1][2]. That puts a lot of organizations in the middle of a refresh, moving users to new hardware or upgrading existing PCs to Windows 11.
I'm preparing for desktop support and help desk roles, so I wrote this checklist to organize what I've been studying. It isn't a substitute for an organization's own deployment standards. It's a way to think through a refresh one device at a time, from the desk side.
1. Confirm the hardware meets Windows 11 requirements
Microsoft's published minimums include a compatible 64-bit processor (1 GHz or faster, 2 or more cores), 4 GB of RAM, 64 GB of storage, UEFI firmware with Secure Boot capability, TPM 2.0, and DirectX 12-compatible graphics with a WDDM 2.0 driver [3]. The processor also has to be on Microsoft's supported CPU list.
Quick checks on an existing device:
- PC Health Check app: Microsoft's recommended compatibility check for Windows 10 devices [3].
- TPM: run
tpm.msc, orGet-Tpmin an elevated PowerShell window, and confirm "Specification Version: 2.0." - Secure Boot and BIOS mode: run
msinfo32and check that "BIOS Mode" says UEFI and "Secure Boot State" says On. - Storage: Microsoft calls non-rotational storage "highly recommended" rather than required [4]. For any device being kept in service, I'd check whether it still has a spinning hard drive, because that tends to be the biggest single drag on user experience.
2. Protect the user's data and encryption keys first
Before touching firmware settings or reimaging:
- Confirm where the user's files actually live (OneDrive Known Folder Move, a network share, or only the local disk).
- If BitLocker is on, confirm the recovery key is escrowed where the organization expects it (for example Microsoft Entra ID, Active Directory, or the MDM). Firmware or TPM changes can trigger a recovery prompt.
- Note the user's mapped drives, printers, browser profiles, and line-of-business apps so nothing gets lost in the move.
3. Understand 24H2 vs. 25H2
Windows 11 version 25H2, the "Windows 11 2025 Update," became generally available on September 30, 2025 [5]. Versions 24H2 and 25H2 share a common core and an identical set of system files, so a device on 24H2 moves to 25H2 through a small enablement package (KB5054156) with a single restart [6]. The prerequisite is the August 29, 2025 cumulative update (KB5064081) or later [6].
A few practical points for support staff:
- Check the version with
winver. Don't assume every device in a fleet is on the same release. - 25H2 removes some legacy components, including PowerShell 2.0 and the WMIC command-line tool [7]. Old scripts or vendor tools that call
wmicmay need updating, for example to PowerShell'sGet-CimInstance. - Feature updates can come with safeguard holds when Microsoft detects a known compatibility issue [5]. If a device isn't being offered the update, a hold is one possible reason.
4. Keep an eye on Secure Boot certificate updates
Microsoft has published guidance about Secure Boot certificates from 2011 that begin expiring in 2026 and are being replaced with 2023 versions [8]. Devices keep booting, but a device that doesn't get the new certificates won't receive future boot-level security protections. Most of this is handled centrally through updates and policy. At the desk, it helps to know that firmware (BIOS/UEFI) updates from the hardware maker can be part of the fix, and that Microsoft keeps a Secure Boot troubleshooting guide [8].
5. Wireless: Wi-Fi 6 and 6E
Newer business laptops often ship with Wi-Fi 6E or newer adapters. Things worth knowing:
- Wi-Fi 6E adds the 6 GHz band, and connecting on 6 GHz requires WPA3 security [9]. If the network or the driver doesn't support WPA3, the device falls back to 2.4/5 GHz.
netsh wlan show driversshows which radio types and authentication methods the adapter and driver support.netsh wlan show interfacesshows the current band, channel, and signal.- Out-of-date wireless drivers are a common suspect, so I'd check the device maker's driver package before anything else.
6. USB-C docks and peripherals
USB-C docks are convenient, but "USB-C" describes a connector, not a capability. When a dock misbehaves, I'd check:
- Port type: whether the laptop port supports DisplayPort Alt Mode, Thunderbolt, or USB4, and what the dock expects. Some docks use DisplayLink, which needs its own driver.
- Power delivery: whether the dock supplies enough wattage for the laptop. An underpowered dock can cause slow charging or warnings.
- Firmware: docks and laptops both get firmware updates, and the device maker's update tool usually handles both.
- Monitors: how many external displays the laptop and dock actually support, and at what resolution.
7. Hand-off checklist
Before closing the ticket:
- [ ] User signs in successfully; MFA works
- [ ] OneDrive syncing; files where the user expects them
- [ ] Outlook, Teams, and core apps open and sign in
- [ ] Printers, mapped drives, and VPN tested
- [ ] Dock, monitors, webcam, and headset tested
- [ ] BitLocker on; recovery key escrowed
- [ ] Windows Update shows the device current
- [ ] Old device tagged for wipe/disposal per policy; asset record updated
- [ ] Ticket notes describe what was done, in plain language
A refresh goes well when it's boring for the user: they sit down, sign in, and their work is there. A checklist is how I'd try to get that result every time.
Sources
- Microsoft Support, "Windows 10 support has ended on October 14, 2025": https://support.microsoft.com/en-us/windows/deployment/updates-lifecycle/windows-10-support-has-ended-on-october-14-2025
- Microsoft Learn, "Product Lifecycle FAQ – Extended Security Updates": https://learn.microsoft.com/en-us/lifecycle/faq/extended-security-updates
- Microsoft, "Windows 11 Specs and System Requirements": https://www.microsoft.com/en-us/windows/windows-11-specifications
- Microsoft, "Windows 11 Minimum Hardware Requirements" (Microsoft Download Center document)
- Windows Experience Blog, "How to get the Windows 11 2025 Update" (Sept. 30, 2025): https://blogs.windows.com/windowsexperience/2025/09/30/how-to-get-the-windows-11-2025-update/
- Microsoft Support, "KB5054156: Feature update to Windows 11, version 25H2 by using an enablement package": https://support.microsoft.com/en-us/servicing/os/windows/docs/2025/02/kb5054156-feature-update-to-windows-11-version-25h2-by-using-an-enablement-package
- Windows Insider Blog, "Releasing Windows 11, version 25H2 to the Release Preview Channel": https://blogs.windows.com/windows-insider/2025/08/29/releasing-windows-11-version-25h2-to-the-release-preview-channel/
- Microsoft Support, "Windows Secure Boot certificate expiration and CA updates": https://support.microsoft.com/en-us/servicing/os/secure-boot/2025/06/windows-secure-boot-certificate-expiration-and-ca-updates
- Intel Support, "How to Enable 6 GHz Band Using Intel Wi-Fi 6E or Wi-Fi 7 Products": https://www.intel.com/content/www/us/en/support/articles/000059385/wireless/intel-wi-fi-6e-products.html
I'm Rıza Korkusuz, an IT support professional in San Diego. I write these notes to organize what I'm learning about desktop and service desk work. More at rizakorkusuz.com/it-support and github.com/rizakorkusuz.