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

Stefan Cuypers 45

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.

TPIT 1 Reputation point

2025-07-21T03:47:13.84+00:00

Same issue here. Sadly I could not pin down the exact faulty update!

but thanks for your direction!

Thought, I killed my VM. Even the back up…. :D

12 answers

Oliver Kehling 0 Reputation points

2025-07-22T16:41:13.6+00:00

Hi, I have a similar problem. I'm currently replacing a Hyper-V Server 2019 with a Hyper-V 2025. There are still two Windows Server 2012 R2 VMs on the Hyper-V 2019 server. After exporting and then importing to the Hyper-V 2025, the VM won't boot. Error: Inaccessible Boot Device. I tried the workaround with the SCSI controller, but unfortunately it didn't help. Regards, Oliver
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
BryceSor 3,965 Reputation points Volunteer Moderator

2025-07-23T07:35:30.35+00:00
Hi Stefan,

I been watching this post and ask CP if a script would help in your case to check the drivers etc in your 2012r2 VM.

Its up to you to try it but I hope it helps .

Absolutely, Bryce. Here's a PowerShell script tailored to check whether key storage and synthetic drivers (like storvsc, vmbus, winhv) inside a Windows Server 2012 R2 VM are:

Present and properly registered in the system registry

Configured to load during boot

Part of the correct driver group (e.g., System for boot-critical)

Compatible with newer Hyper-V patch levels

You can run this inside the affected VM (or remotely with PowerShell Direct):

powershell

# PowerShell Script: VM Boot Driver Audit Tool for Windows Server 2012 R2 $driversToCheck = @("storvsc", "vmbus", "winhv") foreach ($driver in $driversToCheck) { $path = "HKLM:\SYSTEM\CurrentControlSet\Services\$driver" Write-Host "`n--- Auditing Driver: $driver ---" if (Test-Path $path) { $props = Get-ItemProperty $path Write-Host "Start value:`t" $props.Start Write-Host "Group:`t`t" $props.Group Write-Host "Type:`t`t" $props.Type Write-Host "ImagePath:`t" $props.ImagePath } else { Write-Host "❌ Driver '$driver' registry key not found!" } } Write-Host "`n--- OS and Integration Services Info ---" Get-HotFix | Sort-Object InstalledOn | Select-Object Description, HotFixID, InstalledOn (Get-WmiObject Win32_OperatingSystem).Caption

🧠 What to Look For in Output

For storvsc, ideally:

Start = 0 → Loaded during boot

Group = System

Type = 1 (Kernel Driver)

If Start is 3 (Manual), the driver won’t load early enough, which is a major cause of the 0x7B BSOD.

Also, compare HotFixIDs against the new working 2012 R2 image to see if patch level might be helping it survive the new cluster environment.
Please sign in to rate this answer.
Stefan Cuypers 45 Reputation points

2025-07-23T15:11:14.4266667+00:00

Thank you for the script.

Except for the hotfixes the output is identical on both the working and non working VM. Note that the 'winhv' was not found (on neither).
When comparing hotfixes I found 38 hotfixes on the working VM that are not present on the non working one. And 87 on the non working that are not on the working one.

I tried to install the 38 on the non working VM. 5 are applied, 20 where not applicable and 13 are not on Microsoft Update Catalog. But machine still does not boot.

BryceSor 3,965 Reputation points Volunteer Moderator

2025-07-23T19:35:03.01+00:00

Can you post the output please. Make sure there are no PII showing

Stefan Cuypers 45 Reputation points

2025-07-24T03:54:33.1+00:00

Here's the output on the VM that is not working:
--- Auditing Driver: storvsc ---

Start value: 0

Group: Base

Type: 1

ImagePath: System32\drivers\storvsc.sys

--- Auditing Driver: vmbus ---

Start value: 0

Group: System Bus Extender

Type: 1

ImagePath: System32\drivers\vmbus.sys

--- Auditing Driver: winhv ---

? Driver 'winhv' registry key not found!

--- OS and Integration Services Info ---

Description HotFixID InstalledOn

Security Update KB4012213 09/01/2017 00:00:00

Security Update KB3205400 09/01/2017 00:00:00

Security Update KB3197873 09/01/2017 00:00:00

Update KB4020322 09/01/2017 00:00:00

Security Update KB4019213 09/01/2017 00:00:00

Security Update KB4015547 09/01/2017 00:00:00

Update KB3179574 09/01/2017 00:00:00

Security Update KB3178539 09/01/2017 00:00:00

Security Update KB3175024 09/01/2017 00:00:00

Security Update KB3192392 09/01/2017 00:00:00

Update KB3186539 09/01/2017 00:00:00

Security Update KB3185319

Security Update KB4041687

Update KB4040981

Security Update KB4040967

Security Update KB4103715

Security Update KB4093115

Security Update KB4054522

Security Update KB4025333 09/01/2017 00:00:00

Security Update KB4025252 09/01/2017 00:00:00

Security Update KB4022717 09/01/2017 00:00:00

Security Update KB4038793

Security Update KB4034672

Update KB4033428 09/01/2017 00:00:00

Update KB3173424 09/01/2017 00:00:00

Update KB3137728 09/01/2017 00:00:00

Security Update KB3135994

Update KB3134179 09/01/2017 00:00:00

Security Update KB3139914

Update KB3138615

Update KB3138602 09/01/2017 00:00:00

Security Update KB3127222

Security Update KB3126587

Security Update KB3126434

Update KB3133690 09/01/2017 00:00:00

Security Update KB3133043

Security Update KB3127226

Security Update KB3156059 09/01/2017 00:00:00

Update KB3147071 09/01/2017 00:00:00

Update KB3146751 09/01/2017 00:00:00

Update KB3172614 09/01/2017 00:00:00

Security Update KB3161949 09/01/2017 00:00:00

Security Update KB3159398 09/01/2017 00:00:00

Update KB3145384 09/01/2017 00:00:00

Update KB3140219 09/01/2017 00:00:00

Security Update KB3139929

Security Update KB3146723 09/01/2017 00:00:00

Update KB3146604 09/01/2017 00:00:00

Update KB3145432 09/01/2017 00:00:00

Security Update KB4537803

Security Update KB4535680

Security Update KB4534309

Security Update KB4541505

Security Update KB4540725

Security Update KB4540671

Update KB4532940

Security Update KB4530730

Security Update KB4525250

Update KB4534134

Security Update KB4532961

Update KB4532946

Update KB5029915

Update KB5022525

Update KB5022508

Security Update KB5031419

Update KB5031003

Security Update KB5030329

Security Update KB5012170

Update KB5001845

Update KB4578953

Update KB5016268

Update KB5014633

Update KB5013631 06/02/2022 00:00:00

Security Update KB4519990

Update KB4468323

Security Update KB4467703

Security Update KB4462941

Security Update KB4487028

Update KB4486459

Update KB4486105

Update KB4339284

Security Update KB4338824

Security Update KB4284878

Update KB4462901

Security Update KB4457143

Security Update KB4344178

Security Update KB4507457

Security Update KB4503290

Update KB4501226

Security Update KB4516064

Security Update KB4514331

Security Update KB4512489

Security Update KB4493467

Update KB4490128

Security Update KB4489883

Security Update KB4499165

Security Update KB4495625

Security Update KB4495615

Update KB3123245 09/01/2017 00:00:00

Update KB3013791

Update KB3013769

Update KB3013172

Security Update KB3019978

Update KB3014442

Update KB3013816 09/01/2017 00:00:00

Update KB3000850

Security Update KB3000483

Update KB2989930

Update KB3012702

Hotfix KB3004545 09/01/2017 00:00:00

Security Update KB3003057

Update KB3033446

Update KB3031044

Update KB3030947

Security Update KB3037579

Security Update KB3037576

Update KB3036612

Security Update KB3023222

Security Update KB3023219

Update KB3021910

Update KB3024755

Update KB3024751

Security Update KB3023266

Security Update KB2978126

Update KB2919355

Update KB2896496

Security Update KB2894856

Update KB2938066

Update KB2934520

Update KB2919442 04/10/2014 00:00:00

Update KB2883200

Update KB2959936

Update KB5001088

Security Update KB2894852

Update KB2894179

Update KB2894029

Security Update KB2972103

Update KB2971203

Security Update KB2968296

Security Update KB2978041

Security Update KB2977765

Update KB2975061

Update KB2962806

Update KB2957390

Update KB2954879

Update KB2967917

Security Update KB2966828

Security Update KB2966826

Update KB3094486

Update KB3091297

Update KB3087137

Security Update KB3098779

Security Update KB3097997

Security Update KB3097992

Update KB3080149

Update KB3078405

Update KB3077715

Security Update KB3086255

Update KB3084905 09/01/2017 00:00:00

Security Update KB3084135

Update KB3112148

Security Update KB3110329

Update KB3109976 09/01/2017 00:00:00

Security Update KB3122654

Update KB3121261

Update KB3118401

Update KB3103616 09/01/2017 00:00:00

Update KB3102429 09/01/2017 00:00:00

Update KB3100473 09/01/2017 00:00:00

Security Update KB3109103

Update KB3103709 09/01/2017 00:00:00

Update KB3103696

Security Update KB3074548

Security Update KB3045999

Update KB3045719

Update KB3045717

Update KB3054203

Hotfix KB3046737

Security Update KB3046017

Update KB3044374

Update KB3042085

Update KB3038002

Security Update KB3045685

Update KB3045634

Update KB3044673

Security Update KB3071756

Update KB3063843

Security Update KB3061512

Security Update KB3074545

Security Update KB3074228

Security Update KB3072307

Update KB3055323

Update KB3054464

Update KB3054256

Update KB3060793

Update KB3060681

Security Update KB3059317

Microsoft Windows Server 2012 R2 Standard

Stefan Cuypers 45 Reputation points

2025-07-24T04:04:13.52+00:00

And here is the output for the working VM:
--- Auditing Driver: storvsc ---

Start value: 0

Group: Base

Type: 1

ImagePath: System32\drivers\storvsc.sys

--- Auditing Driver: vmbus ---

Start value: 0

Group: System Bus Extender

Type: 1

ImagePath: System32\drivers\vmbus.sys

--- Auditing Driver: winhv ---

? Driver 'winhv' registry key not found!

--- OS and Integration Services Info ---

Description HotFixID InstalledOn

Update KB5001088

Update KB2959936

Security Update KB2894852

Security Update KB2894856

Update KB2896496

Update KB2919355

Security Update KB2920189

Security Update KB2928120

Security Update KB2931358

Security Update KB2931366

Security Update KB2933826

Update KB2938066

Update KB2938772

Hotfix KB2949621

Update KB2954879

Update KB2958262

Update KB2958263

Security Update KB2961072

Update KB2965500

Update KB2966407

Security Update KB2966826

Security Update KB2966828

Update KB2967917

Security Update KB2968296

Update KB2971203

Security Update KB2971850

Security Update KB2972103

Security Update KB2972213

Security Update KB2973114

Security Update KB2973351

Update KB2973448

Update KB2975061

Security Update KB2976627

Security Update KB2977629

Security Update KB2978041

Security Update KB2978122

Update KB2981580

Security Update KB2987107

Update KB2989647

Update KB2989930

Update KB2998527

Update KB3000850

Security Update KB3003057

Hotfix KB3004545

Update KB3008242

Update KB3012702

Update KB3013172

Update KB3013538

Update KB3013769

Update KB3013791

Update KB3013816

Update KB3014442

Security Update KB3019978

Security Update KB3023219

Security Update KB3023266

Update KB3024751

Update KB3024755

Update KB3027209

Update KB3030947

Update KB3031044

Security Update KB3032663

Update KB3033446

Update KB3036612

Security Update KB3037576

Update KB3038002

Security Update KB3042058

Update KB3042085

Update KB3043812

Update KB3044374

Update KB3044673

Update KB3045634

Security Update KB3045685

Update KB3045717

Update KB3045719

Security Update KB3045999

Security Update KB3046017

Hotfix KB3046737

Update KB3054203

Update KB3054256

Update KB3054464

Update KB3055323

Security Update KB3059317

Update KB3060681

Update KB3060793

Security Update KB3061512

Update KB3063843

Security Update KB3071756

Security Update KB3072307

Security Update KB3074228

Security Update KB3074545

Update KB3077715

Update KB3078405

Update KB3080149

Security Update KB3082089

Security Update KB3084135

Update KB3084905

Security Update KB3086255

Update KB3087137

Update KB3091297

Update KB3094486

Security Update KB3097992

Update KB3100473

Update KB3102429

Update KB3103616

Update KB3103696

Update KB3103709

Security Update KB3109103

Update KB3109976

Security Update KB3110329

Update KB3121261

Security Update KB3122651

Update KB3123245

Security Update KB3126434

Security Update KB3126587

Security Update KB3127222

Security Update KB3133043

Update KB3133690

Update KB3134179

Update KB3137728

Update KB3138602

Security Update KB3139914

Update KB3140219

Update KB3145432

Update KB3146604

Update KB3146751

Update KB3147071

Update KB3149157

Security Update KB3156059

Security Update KB3159398

Security Update KB3161949

Update KB3172614

Security Update KB3178539

Update KB3179574

Security Update KB3185319

Update KB4033428

Update KB4040981

Update KB4486105

Security Update KB5012170

Update KB5022525

Update KB5029915

Security Update KB5030329

Update KB5031003

Security Update KB5031419

Microsoft Windows Server 2012 R2 Standard

Stefan Cuypers 45 Reputation points

2025-07-24T04:07:56.0033333+00:00

The non working VM was installed in 2016.

The working VM was installed last week from DVD SW_DVD9_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_-4_MLF_X19-82891 recently downloaded from Volume Licensing.
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
BryceSor 3,965 Reputation points Volunteer Moderator

2025-07-23T22:16:41.1166667+00:00
Did you try this using Henry Mai method,

You can refer the procedure below as it can force the 2012 R2 guest OS to automatically install and register the storvsc.sys driver as a boot-critical device

Move the problematic VM back to the working cluster and boot it up.

Shut down the VM. In Hyper-V Manager, go to its Settings.

Add a SCSI Controller to the VM. You don't need to attach a disk to it; just adding the controller hardware is enough.

Start the VM again (on the working cluster). Log in and allow Windows to detect the "new" SCSI controller and automatically install the driver (storvsc.sys). You can verify it appears in Device Manager.

Once the driver is installed, shut down the VM.

You can now remove the temporary SCSI controller you added in step 3.

Move the VM to the new cluster and try to boot it.

Why This Works

When you add a new SCSI device, Windows:

Detects the virtual SCSI controller (storvsc)

Loads storvsc.sys during device discovery

Automatically updates the registry under HKLM\SYSTEM\CurrentControlSet\Services\storvsc to mark it as boot-critical (Start=0, Group=System)

Even though storvsc.sys is already present, older VMs sometimes lack proper boot-time flags, especially if they've never been re-initialized on newer Hyper-V hardware. This update convinces Windows to commit to using storvsc.sys during boot.
Please sign in to rate this answer.
Stefan Cuypers 45 Reputation points

2025-07-24T03:47:58.96+00:00

Yes I tried Henry Mai's method, but it did not help.

Peter Stam 46 Reputation points

2025-07-26T17:21:00.66+00:00

In my case it is a Gen2 VM so SCSI is already present. I found that method in another post and tried it, but in my case it is not solving the problem.

Complete remove SCSI with disks, re-add with disks.

On the original host, remove SCSI controller from device manager, also hidden, shutdown, move the VM, no luck.

Add an additional SCSI controller, no luck
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Andy Bryant 15 Reputation points

2025-07-24T10:57:09.7266667+00:00

I have exactly the same problem as Stefan. It's all the more frustrating as I can export/import the VM's to 2016 & 2022 Hyper-V hosts and they work flawlessly. Also, if I create a vanilla 2012R2 VM, leave unpatched, go through the export/import cycle that also works. So, it looks like it's something that was introduced in a Windows Update somewhere along the line. Looking on the EFI partition there are some differences there. Ultimately, the 2012R2 VM's will be replaced but I need to get them on to the new cluster first.

I tried adding an additional SCSI controller, but I also didn't have success.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
BryceSor 3,965 Reputation points Volunteer Moderator

2025-07-24T21:16:34.9266667+00:00
Both showing so its down to a patch or KB how it changed the way its interacts with the host.

all start valves should be set at 1

--- Auditing Driver: storvsc ---

Start value: 0

Group: Base

Type: 1

ImagePath: System32\drivers\storvsc.sys

--- Auditing Driver: vmbus ---

Start value: 0

Can you make a copy of the VM just for testing and try the following,

Boot the problematic VM on the older cluster and:

powershell

Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\storvsc" -Name Start -Value 1 Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\vmbus" -Name Start -Value 1 New-Item -Path "HKLM:\SYSTEM\CurrentControlSet\Services\winhv" -Force | Out-Null Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\winhv" -Name Start -Value 1

Then shut down, export, and move to the patched cluster. This forces early driver load on the one running Windows Server 2025, specifically the host that includes the newer update set: KB5063666, KB5062553, KB5056579, KB5059502, and possibly KB5064489
Please sign in to rate this answer.
Stefan Cuypers 45 Reputation points

2025-07-25T06:54:45.46+00:00

I just tried that and first tried to reboot on the older (working) cluster. The VM now blue-screens there with a 0x7B. So this seems to make things worse.

BryceSor 3,965 Reputation points Volunteer Moderator

2025-07-25T09:31:09.0933333+00:00

Very sorry about that Stefan, I have mis-read your original question, have I got this right, you have two clusters on Server 2025 one runs the 2012R2 and the other doesn't,

only difference is how they are updated as far as KBs.

Stefan Cuypers 45 Reputation points

2025-07-25T10:18:11.8666667+00:00

On the newer cluster the problem remains with those registry adjustments.

We indeed have 2 Server 2025 clusters. We had a lot of problems upgrading from Azure HCI to Azure Local on a 4-node stretched cluster.
So we decided to move to 2 clusters and to Windows Server 2025 (to have long term support and not being forced into upgrades too often).
We installed the first 2-node 2025 cluster beginning of June and successfully moved all VM's to it. It was based on the May 2025 release of Windows Server 2025 and then upgraded via Windows Update.
Since that has been succesfull we then reinstalled the other 2 nodes to a Windows 2025 cluster, this time using the June 2025 release of Windows 2025 and fully patched (with obviously more recent patches).
We noticed the problem when redistributing VM's to the newly installed cluster. It worked for Win2022/25 VM's, but not for 2012R2 VM's. Still to test a few Server 2008 servers that are not so easy to get rid of. Maybe they will have the same problem.

Andy Bryant 15 Reputation points

2025-07-25T12:53:43.2966667+00:00

As I have a very similar situation to to Stefan, I thought I'd try an experiment.

I created a new nested 2025 hypervisor on our 2025 cluster. Our Cluster is a 4 node 2025DC set up fully patched as of July 2025. Based on HPE ROK media.

I fired up the nested hypervisor, did not apply any patches and imported the 2012R2 VM. It fired straight up without issues and functions normally! So it does indeed appear to be 2025 update that is causing the issue.

Peter Stam 46 Reputation points

2025-07-25T18:28:38.6+00:00

@BryceSor Doing this will make the 'source' VM not boot anymore, same BSOD inaccessible boot device, no matter is secure boot is on or off.

BryceSor 3,965 Reputation points Volunteer Moderator

2025-07-25T21:46:20.6433333+00:00

iF 2025 May server works with 2012 R2 but the later 2025 server updates puts a spanner in the works, have you tried using DISM to remove the later KB on the server?

Do one at a time and you might find which update is causing your issue.

Starting with these KB5063666, KB5062553, and KB5059502.

Stefan Cuypers 45 Reputation points

2025-07-26T07:02:36.53+00:00

I tried to test this with nested virtualization (thanks @Andy Bryant for the tip).

And here is what I found:

If I install from the Windows 2025 June 2025 DVD the 2012R2 VM does not work.

If I install from the original 2024 Nov 2025 DVD the 2012R2 VM boots just fine.

That confirms without any doubt I think that there is a problem with an update somewhere. I'll try applying patches now on the working 2025 to figure out which patch causes the problem. The May DVD still worked (but I can't download it any more to start from it), so I can start with the May update...

Stefan Cuypers 45 Reputation points

2025-07-26T08:21:48.73+00:00

After applying KB5058411 (May 13) the 2012R2 VM boots succesfully.

After applying KB5060842 (Jun 10) the 2012R2 VM does not boot any more.

So the cause is in KB5060842.

TPIT 1 Reputation point

2025-07-26T08:49:07.6533333+00:00

Thanks for figure this out.

that was the Route I was gooing, but since a bit lack of time I was deinstalling a past updates :)

Stefan Cuypers 45 Reputation points

2025-07-26T09:00:38.49+00:00

I've logged a ticket with Microsoft support on this on Thursday. Still waiting for first reponse though.

Peter Stam 46 Reputation points

2025-07-26T09:57:11.9166667+00:00

VM ISO: SW_DVD9_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_-4_MLF_X19-82891.ISO

Both hosts clean installation no Windows updates

Winver 24H2 (26100.2894)

HOST ISO: SW_DVD9_Win_Server_STD_CORE_2025_24H2.3_64Bit_English_DC_STD_MLF_X23-94773.ISO

VM2012R2 installation with secure boot enabled, template Microsoft Windows -> no boot, the image's hash was denied

VM2012R2 installation with secure boot enabled, template Microsoft UEFI Certificate Authority -> no boot, the image's hash was denied

VM2012R2 installation with secure boot disabled -> boots

Winver 24H2 (26100.1742)

HOST ISO: SW_DVD9_Win_Server_STD_CORE_2025_24H2_64Bit_English_DC_STD_MLF_X23-81891.ISO

VM2012R2 installation with secure boot enabled, template Microsoft Windows -> no boot, the image's hash was denied

VM2012R2 installation with secure boot enabled, template Microsoft UEFI Certificate Authority -> no boot, the image's hash was denied

VM2012R2 installation with secure boot disabled -> boots

@Stefan Cuypers what is the .iso name u used for the working version?

We logged a ticket last week but the response was we had no ESU, so no support anymore...

We ran into this problem when live migrating 2012R2 server from a 2022 host cluster to a new installed 2025 host cluster. The live migration works and the VM keeps running but cannot reboot. Than we get the inaccessible boot device BSOD.

Stefan Cuypers 45 Reputation points

2025-07-26T10:03:33.5333333+00:00

Hi Peter, I've noticed too that you need to install the 2012R2 without Secure Boot. Seems the certificates used on the 2012R2 DVD are not present any more in Windows Server 2025 host.

However if you fully update the 2012R2 via Microsoft Update you can enable secure boot and it will work.

Peter Stam 46 Reputation points

2025-07-26T10:05:29.84+00:00

I tried that fully update the 2012R2 but it's not working, can u maybe post the storsvc.sys driver version of the working 2012R2 VM running on a hyper-v 2025 host?

Peter Stam 46 Reputation points

2025-07-26T10:06:17.8766667+00:00

I tried that fully update the 2012R2 but it's not working, can u maybe post the storsvc.sys driver version of the working 2012R2 VM running on a hyper-v 2025 host?

Stefan Cuypers 45 Reputation points

2025-07-26T10:14:22.51+00:00

I have installed a working 2012R2 VM as follows:

Create a new VM, Gen2, disable secure boot

Mount the ISO SW_DVD9_Windows_Svr_Std_and_DataCtr_2012_R2_64Bit_English_-4_MLF_X19-82891 (downloaded it from volume licensing in O365)

Installed the VM from the ISO

Once installed apply all Windows updates (did this in several steps since there are a lot)

After the last updates are applied, enable secure boot again

That gave me a new working 2012R2.

The storsvc.sys after all the updates is version 6.3.9600.19984 dating 3/4/2021 0:02

Stefan Cuypers 45 Reputation points

2025-07-26T10:19:03.6466667+00:00

Here are some notes I took while Windows Updating the image:

KB5052108 (Servicing Stack Update)

(109) KB4054519 - OK

(103) KB5031419 - 2023-10 Security Monthly Rollup - OK - Secure boot works now

(95) KB4486105 - .Net 4.8 - OK

(83) KB3185319 IE 11 - OK

(82) All Security Updates (also .net) - OK (.net one failed though)

(61) .Net Security Update

(60) -> first 10 Update for Windows Server 2012 R2 - ok

(50) -> next 10 Update for Windows Server 2012 R2 - ok - check for updates

Then continued per 10 updates until all are installed.

Peter Stam 46 Reputation points

2025-07-26T10:20:13.1033333+00:00

thank you Stefan, same version here but not booting at all...have to dig deeper I guess :)

Dimitri Iacomi 0 Reputation points

2025-07-26T13:57:08.3233333+00:00

I have exactly the same problem. A working 2012 R2 vm imported on a new 2025 host cannot boot anymore. BSOD regardless of secure boot on or off, I'm out of ideas...

Peter Stam 46 Reputation points

2025-07-26T20:21:37.9133333+00:00

Host clean installation 2022 so we can boot a server to be migrated from the old Hyper-V cluster, no Windows Updates

SW_DVD9_Win_Server_STD_CORE_2022_2108.16_64Bit_English_DC_STD_MLF_X23-32717.ISO

Moved the original 2012R2VM (not changed, no Windows Updates to latest with SSU) to 2022 host, secure boot on, -> boot

Moved the VM from 2022 host to 2025 host, secure boot on, -> boot (???)

Updated the 2025 host (24H2.3) with all the Windows Updates

Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.433.88.0) - Current Channel (Broad)

2025-07 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Microsoft server operating system version 24H2 for x64 (KB5056579)

2025-07 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5062553)

Windows Malicious Software Removal Tool x64 - v5.134 (KB890830)

Update for Windows Security platform - KB5007651 (Version 10.0.27840.1000)

Secure boot off, -> no boot (!)

Secure boot on, -> no boot (!)

Removed

2025-07 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5062553)

Secure boot off, -> boot (!)

Secure boot on, -> boot (!)

Installed again

2025-07 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5062553)

Secure boot off, -> no boot (!)

Secure boot on, -> no boot (!)

So for me the problem is clearly with KB5062553

Andy Bryant 15 Reputation points

2025-07-27T08:24:50.3733333+00:00

Having done my own testing. I agree with Stefan, the problem was first introduced with KB5060842 in June. The subsequent KB5062553 would also contain the problem, but it started with KB5060842.

Thank for raising a ticket with Microsoft @Stefan Kuypers

Peter Stam 46 Reputation points

2025-07-27T09:04:17.13+00:00

@Andy Bryant u are right, problem is with KB5060842 also, just tested.

Ben Gillam 10 Reputation points

2025-07-30T09:38:28.18+00:00

This method killed the server on original 2012 host for me.

had to boot with last known good config to boot again

It also didnt work on the new server either
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

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

12 answers

Your answer