Windows Server and infrastructureNew in this releasePublished 20 July 2026

After Windows 10 support ended, what should enterprises test before moving to Windows 11?

Windows 10 support ended on 14 October 2025. Validate hardware, business applications, drivers, Group Policy, VPN clients and peripherals before broad Windows 11 deployment.

Control risk before changing productionValidate first in a test environment or on one representative system, and preserve configuration, logs and recoverable backups. Production cutovers, bulk policy changes, database repair and storage rebuild require a maintenance window and explicit rollback criteria.

1. Conclusion and scope

An enterprise endpoint upgrade is not simply pushing an installer to every device. Finance software, ERP clients, browser extensions, USB security devices, printers, scanners, VPN clients, endpoint protection and Group Policy can all affect the outcome, so devices and applications must first be grouped by risk.

This issue involves Windows Server lifecycle, role dependencies, endpoint compatibility or infrastructure migration. Inventory business dependencies and rollback first.

2. Risk signals that deserve priority

Devices do not meet TPM 2.0, UEFI, Secure Boot or supported-processor requirements.
Critical workflows depend on legacy browser controls, old drivers, 32-bit plug-ins or unsupported peripherals.

3. Pre-change assessment checklist

Collect model, BIOS, TPM, processor, memory, storage, driver and current Windows-version information.
Inventory applications, browsers, Office, VPN, printers, scanners, dongles and security agents by department.
Export user and computer GPO results and review logon scripts, drive mappings, certificates, proxies and update policies.
Create a representative pilot covering finance, design, production, remote workers and management.

Read-only checks and validation examples

Get-ComputerInfo | Select-Object WindowsProductName,WindowsVersion,CsModel,CsProcessors
Get-Tpm
Confirm-SecureBootUEFI
gpresult /h C:\Temp\gp.html

corp.example, 192.0.2.0/24 and 203.0.113.0/24 are documentation-only examples. Replace them only after the actual environment values have been verified.

4. Recommended implementation sequence

Upgrade the pilot first and observe it for two to four weeks before phased deployment.
Run incompatible legacy applications on isolated endpoints, VDI or replacement platforms rather than weakening security on every device.
Back up user data, confirm BitLocker recovery keys and define the rollback window before upgrade.
Use a central deployment process that records success, failure, rollback and manual-intervention status.

Remote assessment or on-site work?Logs, configuration and a small number of systems can usually be assessed remotely. Physical servers, storage, data-centre power, bulk cutover and recovery exercises should use a controlled on-site window. On-site service is available for Zhejiang, Shanghai and Jiangsu; other locations can be supported remotely.

5. Validation, rollback and common mistakes

Verify domain sign-in, GPO, shares, printing, VPN, Office, ERP and endpoint security.
Test sleep and resume, camera, audio, wireless, docks and multiple displays.
Confirm patching, inventory, antivirus, logging and remote-support platforms recognise the new OS.

Common mistakes

Using processor speed alone as the compatibility test.
Upgrading every department at once without a business pilot or rollback.
Disabling Windows 11 security controls globally to support one old NAS or application.

Official references

Microsoft Lifecycle: Windows 10 end of support

Frequently asked questions

Can unsupported devices be forced to install Windows 11?

Workarounds may exist, but they increase support and update risk in an enterprise. Replace or isolate such devices instead.

Must every application be reinstalled?

Not always, but installation method, drivers, licensing, browser components and user-data migration must all be tested.

Need an assessment based on the actual environment?

Provide versions, topology, complete errors, event-log timestamps, scope of impact, recent changes and actions already taken. We will first determine risk, service boundary and rollback, then confirm the implementation scope.