Problem booting Windows 2012R2 VM on Windows 2025 Hyper-V

Stefan Cuypers 75 Reputation points
2025-07-20T05:33:22.69+00:00

We're having a problem with a Windows Server 2025 Hyper-V cluster.

We have 2 identical clusters (same hardware, same BIOS version) and when we move a Windows 2012R2 VM from one cluster to another it does not boot any more (tested with 2 different VM's).

The error is a blue screen 0x7B (INACCESSIBLE_BOOT_DEVICE).

If we move the machine back to the other cluster it boots just fine.

Only difference I see is the cluster path level. The working cluster is an older Windows Update (KB5058411, KB5058523 and KB5054979).

Whereas the newer cluster has KB5063666, KB5062553, KB5056579 and KB5059502. It tried installing KB5064489 also, but that does not help.

A VM with Windows server 2022 of 2025 does move fine, so it seems to be linked to 2012R2.

I also tried to install a brand new 2012R2 VM from the original iso and then completely upgrading it with Windows Update and that machine is working fine. It seems to have the same verson of storage drivers as the non working VM.

The faulting VM does boot succesfully into recovery mode. I tried bootrec /fixmbr and bootrec /fixboot, but that does not help.

Windows for business | Windows Server | Storage high availability | Virtualization and Hyper-V
{count} votes

17 answers

Sort by: Most helpful
  1. Peter Sommer 5 Reputation points
    2025-07-25T13:26:43.41+00:00

    I have a customer with the exact same issue. Windows Server 2025 S2D Cluster. After applying the last Updates, a Restart of the running Win 2012R2 VMs will boot into recovery. Things i already testet:

    • New VM Gen1 and Gen2 with the 2012R2 vhdx -> not working
    • disable secure boot -> not working
    • disable integration services -> not working
    • booting in safe mode -> not working

    VM ist configversion 12

    On another Server 2025 S2D cluster with older updates, the same VM is booting

    1 person found this answer helpful.

  2. Kalabis Tomáš 15 Reputation points
    2025-07-29T12:30:02.08+00:00

    hi guys, the customer had a same problem:

    Failover Cluster 2025 with 3 identical nodes, we uninstall the (KB5060842) from the one node and reboot it, after we migrate the affected VM (WS2012R2) back to the node and VM boot succesfully.

    post about this issue on my blog:
    https://tomaskalabis.com/wordpress/problem-booting-windows-2012r2-vm-on-windows-2025-hyper-v/

    1 person found this answer helpful.
    0 comments No comments

  3. Peter Stam 46 Reputation points
    2025-07-29T12:33:01.4966667+00:00

    Still waiting for MS to response to the opened case...hope they will respond soon...

    1 person found this answer helpful.

  4. Ben Gillam 10 Reputation points
    2025-07-30T09:46:33.1433333+00:00

    We have this same or similar issue although not a cluster.

    Windows 2025 server - Moved 3x Windows 2012 R2 VMs to it back in April time - They are archival manual boot access for old accounts system. Worked fine at time. Later tried to boot and they all fail. Restores from backup failed, new export and import fails etc which lead me here.

    The tweaks to Storsvc recommended along with a new export didnt work for me.

    I don't seem to have any of the updates listed however maybe they were bundled into a cumulative update.

    User's image

    At the point now of bringing a previous 2019 host online again to host these VMs if 2025 isnt going to play ball with them unless a fix comes along soon.

    1 person found this answer helpful.

  5. Stefan Cuypers 75 Reputation points
    2025-09-03T17:40:52.6966667+00:00

    I have a fix that seems to work for my 2012R2.
    After more testing with MS support, the support engineer suggested to do an inline repair :

    • First run the VM on an unpatched Windows Server 2025 so we can start it up. (may also work if done on a 2022, but not tested)
    • Attach the Windows Server 2012R2 DVD (I used the latest from volume licensing)
    • Run setup from the DVD and select the option to upgrade (keep settings)
    • Let it run the upgrade
    • Then move the VM back on a patched Windows Server 2025

    After that my 2012R2 VM booted fine on a patched Windows Server 2025.

    1 person found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.