Upgrading from Windows 10 to Windows 11

To upgrade client machines from Windows 10 to Windows 11 (assuming the hardware meets requirements), follow these best-practice steps for a smooth upgrade:
✅ 1. Pre-upgrade Checklist
Hardware Requirements
Verify each machine has:

• TPM 2.0 enabled in BIOS
• UEFI with Secure Boot
• Compatible CPU (e.g., Intel 8th Gen+, AMD Ryzen 2000+)
• 4 GB RAM minimum (8 GB recommended)
• 64 GB+ storage
• DirectX 12 compatible GPU with WDDM 2.0 driver

Use the [PC Health Check tool](https://www.microsoft.com/en-us/windows/windows-11#pchealthcheck) or `WhyNotWin11` utility for a deeper analysis.
🛠️ 2. Back Up and Prepare

• Back up user data (use OneDrive, network shares, or imaging tools like Macrium Reflect).
• Uninstall incompatible software or drivers if flagged.
• Ensure Windows 10 is up-to-date.

Option 1: Windows Update (Recommended for 1–10 PCs)
If eligible, go to:

Settings → Update & Security → Windows Update → Check for updates

Look for the “Upgrade to Windows 11” prompt. Follow instructions.

Option 2: Installation Assistant (Manual In-place Upgrade)
For machines meeting hardware requirements:

1. Download from: Windows 11 Installation Assistant
2. Run the tool on each PC.
3. It performs an in-place upgrade while preserving data/apps.

Option 3: ISO File (Offline or Mass Upgrade)
For IT admins:

1. Download the ISO: Windows 11 ISO
2. Mount and run setup.exe.
3. Choose Keep personal files and apps.

Use command-line parameters for automation:

setup.exe /auto upgrade /quiet /noreboot

Option 4: Windows Deployment Tools (Large-scale Upgrade)
Use:

• Microsoft Endpoint Configuration Manager (SCCM)
• Windows Deployment Services (WDS)
• Intune (for remote upgrades)

You can create a Windows 11 task sequence with in-place upgrade paths for domain-joined machines.
🧪 4. Post-Upgrade Tasks

• Verify device drivers and Windows Activation
• Confirm domain/workgroup settings
• Restore data or custom configurations
• Test user apps and permissions

🧰 Tools & Scripts (optional)

• PowerShell: for scripting the deployment
• Group Policy / Intune: to enforce upgrade schedules
• MDT or SCCM Task Sequence: for zero-touch deployments

There are some differences between the version of NTFS used by Windows NT 4.0 operating systems (NTFS 4) and Windows 2000 operating systems (NTFS 5). This may prevent some of the programs you have used in Windows NT 4.0 from working properly in Windows 2000.
For example, anti-virus programs that work in Windows NT 4.0 may not be able to handle "reparse points" that they might encounter if you have created Volume Mount Points. This incompatibility may not be reported by the Upgrade Evaluation tool.