Saturday, August 9, 2025

how to upgrade window server 2022 to 2025 in hyper v window ?








Upgrading a Windows Server 2022 VM to Windows Server 2025 in Hyper-V involves a few steps and considerations to ensure minimal downtime and no data loss. Here's your step-by-step guide:

✅ Prerequisites

1. Check Requirements

  • Ensure the Windows Server 2025 ISO is available.

  • Confirm the VM meets hardware requirements for 2025.

  • Backup your VM using Hyper-V Checkpoints or other backup solutions.

  • Make sure you have a valid license key for Windows Server 2025.

🔄 Step-by-Step Upgrade Process in Hyper-V

🧰 Step 1: Create a Checkpoint (Backup)

This protects you from any upgrade failure.

  1. Open Hyper-V Manager.

  2. Right-click your Windows Server 2022 VM > Checkpoint.

  3. Wait for it to finish (snapshot of current state).

💿 Step 2: Attach Windows Server 2025 ISO

  1. Right-click your VM in Hyper-V → Settings.

  2. Go to DVD Drive → Browse and select your Windows Server 2025 ISO.

  3. Click OK.

🔁 Step 3: Start VM and Boot from ISO

  1. Start the VM.

  2. Quickly press a key to boot into the DVD (ISO) when prompted.

  3. You’ll enter the Windows Setup screen.

🛠️ Step 4: In-Place Upgrade

  1. Choose Language and Keyboard, click Next.

  2. Click Install Now.

  3. When asked for a product key, enter your Windows Server 2025 key, or click I don’t have a product key if it will activate later.

  4. Choose the edition that matches your current installation (Standard or Datacenter).

  5. Select Keep personal files and apps (to do an in-place upgrade).

  6. Accept the license terms.

  7. Windows will now upgrade the system to 2025.

⏳ Step 5: Wait for Upgrade to Complete

  • The system will reboot multiple times.

  • Ensure Hyper-V does not time out or force shutdown during this.

✅ Step 6: Post-Upgrade Tasks

  1. Log in and check the version:

    open cmd

    winver

  2. Reinstall Hyper-V Integration Services (if necessary).

  3. Activate Windows (Settings > System > Activation).

  4. Install the latest updates:

    open powershell

    sconfig

  5. Test server roles & applications.

🧯 Rollback (If Needed)

  • If the upgrade fails, go back to Hyper-V Manager → Right-click VM → Revert to Checkpoint.

⚠️ Important Notes

  • Only in-place upgrades from Server 2022 to 2025 are supported. Older systems (2016/2019) must go to 2022 first.

  • Not all roles or apps are guaranteed to survive an in-place upgrade (e.g., Domain Controllers, SQL Server—test first!).

🎁 Need Help?

Would you like:

  • A PowerShell script to automate ISO mounting and upgrade?

  • A PDF version of this guide?

  • Help test the upgrade in a lab VM first?

If it's showing install a new window and repair my pc menu after the browse of 2025 file then you need to do flowing steps.

If your Windows Server 2025 ISO only shows:

  • ✅ "Install now"

  • ✅ "Repair your computer"

...and does not show an upgrade option, then it means either:

❌ REASONS Why the In-Place Upgrade Option is Missing:

🔸 1. You booted from the ISO directly (Clean Install Mode)

Booting the VM into the ISO (from Hyper-V BIOS) starts a clean installation — upgrade options won't appear here.

✅ FIX:

You need to run the setup.exe from inside the running Windows Server 2022, not by booting into the ISO.

✅ Correct Way to Perform In-Place Upgrade in Hyper-V:

🔁 Step-by-Step Fix:

1. Start your Server 2022 VM normally

(Don’t boot from ISO — just log in like normal)

2. Attach Windows Server 2025 ISO in Hyper-V

  • Go to Hyper-V Manager → Right-click your VM → Settings.

  • Under DVD Drive, choose Browse, then select the Windows Server 2025 ISO.

  • Click OK.

3. Inside the Server 2022 VM:

  • Open File Explorer → Go to the DVD drive (this is the ISO).

  • Double-click setup.exe from the ISO.

4. Now you'll see upgrade options

  • Select "Keep personal files and apps" to upgrade in-place.

🧾 Additional Tips

IssueFix
Booting into the ISO shows only "Install" and "Repair"Exit, boot into Windows normally, then run setup.exe from ISO
Setup says you can't upgradeCheck edition mismatch (e.g., Standard vs Datacenter)
Set up the blocks upgradeCheck language/locale must match (e.g., English to English)

🧯 Don't Forget:

  • Make a Hyper-V Checkpoint before proceeding.

  • Backup critical data just in case.

  • After the upgrade, use winver to confirm it's now Server 2025.