Insights /Windows Server and infrastructure

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, remote-access clients and peripherals before broad Windows 11 deployment.

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

Establish a factual baseline with “hardware TPM/CPU/UEFI readiness” and “business-application compatibility”, then move to “drivers and peripherals”. Use OS state, applications, drivers and real business behavior as the evidence chain and avoid changing production before the fault boundary is clear.

Risk boundaries and prerequisites

Start by checking hardware TPM/CPU/UEFI readiness, business-application compatibility and drivers and peripherals independently. A healthy result for one of these checks does not establish the state of the entire service path.

Evidence and safe checks

CheckWhy it mattersRecommended action
01 · hardware TPM/CPU/UEFI readinessChecking hardware TPM/CPU/UEFI readiness helps establish whether support status, application dependencies and the target environment are compatible; compare it with a known-good baseline and the incident timeline.Record the actual state of hardware TPM/CPU/UEFI readiness. Inventory software, drivers, licenses, apps and backups and run compatibility checks before scheduling cutover.
02 · business-application compatibilityChecking business-application compatibility helps establish whether support status, application dependencies and the target environment are compatible; compare it with a known-good baseline and the incident timeline.Record the actual state of business-application compatibility. Inventory software, drivers, licenses, apps and backups and run compatibility checks before scheduling cutover.
03 · drivers and peripheralsChecking drivers and peripherals helps establish whether support status, application dependencies and the target environment are compatible; compare it with a known-good baseline and the incident timeline.Record the actual state of drivers and peripherals. Inventory software, drivers, licenses, apps and backups and run compatibility checks before scheduling cutover.
04 · domain policy and security baselineChecking domain policy and security baseline helps establish whether support status, application dependencies and the target environment are compatible; compare it with a known-good baseline and the incident timeline.Record the actual state of domain policy and security baseline. Inventory software, drivers, licenses, apps and backups and run compatibility checks before scheduling cutover.
05 · secure remote access, EDR and printingChecking secure remote access, EDR and printing helps establish whether support status, application dependencies and the target environment are compatible; compare it with a known-good baseline and the incident timeline.Record the actual state of secure remote access, EDR and printing. Inventory software, drivers, licenses, apps and backups and run compatibility checks before scheduling cutover.
06 · phased pilot and rollbackChecking phased pilot and rollback helps establish whether support status, application dependencies and the target environment are compatible; compare it with a known-good baseline and the incident timeline.Record the actual state of phased pilot and rollback. Inventory software, drivers, licenses, apps and backups and run compatibility checks before scheduling cutover.

Investigation and change sequence

  1. Capture a baseline for hardware TPM/CPU/UEFI readiness and business-application compatibility and compare it with a known-good system.
  2. Correlate evidence from drivers and peripherals and domain policy and security baseline to distinguish the direct fault from dependent symptoms.
  3. Only if evidence points to secure remote access, EDR and printing, plan a controlled change with backups, a change window and rollback triggers.
  4. Finally check phased pilot and rollback and the real business workflow. Test service functions, authentication and business applications with rollback triggers recorded.

Validation and rollback evidence

  • Test service functions, authentication and business applications with rollback triggers recorded.
  • Recheck secure remote access, EDR and printing and phased pilot and rollback against the expected business outcome.
  • Retain initial configuration, event evidence, validation results and rollback triggers for production changes.

Common actions that increase risk

  • Assuming hardware TPM/CPU/UEFI readiness is sufficient while overlooking business-application compatibility and dependent checks.
  • Changing several settings before preserving the original evidence for drivers and peripherals.
  • An end-of-support date is not permission to upgrade an untested production server.

Official references

Common questions and acceptance criteria

What should be checked first?

Begin with hardware TPM/CPU/UEFI readiness and business-application compatibility. Capture reproducible errors and protect recoverable data before changing production.

What proves the issue is resolved?

Test service functions, authentication and business applications with rollback triggers recorded.

What evidence should be retained?

Retain original logs, configuration snapshots, the approved change scope, business verification and rollback conditions.

PreviousWindows Server 2016 support ends in 2027: how should an enterprise plan migration now?NextWhy Windows 11 24H2 may fail to access an old NAS: the new SMB signing baseline

Need an assessment based on the actual environment?