topic Re: Windows 2025 setup error in HPE Morpheus VM Essentials Software

Windows 2025 setup error

Jim-P — Wed, 30 Sep 2026 18:15:29 GMT

Attempting to create a new Windows 2025 instance but the install hangs right away with error code 0x80070001 - 0x4002C. Is there a trick to installing this version of Windows? How can I add the drivers in if it won't go past this point?

Re: Windows 2025 setup error

paguti20 — Mon, 05 Oct 2026 21:02:47 GMT

Enable UEFI

CREATE INSTANCE: Configure - Advanced Options - UEFI

Enable ATACH VIRTIO DRIVERS

Re: Windows 2025 setup error

Jim-P — Thu, 08 Oct 2026 15:12:44 GMT

I've tried selecting UEFI but that makes it boot into the UEFI install shell.

I have tried just about all the various config options with no luck.

That includes attaching virtio drivers.

Any other thoughts?

Re: Windows 2025 setup error

CalvinZito — Fri, 09 Oct 2026 17:25:41 GMT

From my documentation based Copilot:
The documentation does recommend enabling UEFI and Attach VirtIO Drivers when provisioning Windows to an HVM cluster. During installation, if Windows cannot see the virtual disk, use Load Driver and select the appropriate VirtIO storage driver from the mounted VirtIO ISO.

However, I couldn't find any documentation that specifically references Windows Server 2025 or error 0x80070001 - 0x4002C. The documented guidance is focused on ensuring the VirtIO drivers are available during setup.

A few questions that may help narrow this down:

Are you installing directly from a Windows Server 2025 ISO?
Does the error occur before the disk selection screen or during Windows setup?
If you open the console, does Windows Setup see the virtual disk at all?

If the disk is not visible, that would point toward a storage driver issue and manually loading the VirtIO storage driver from the attached VirtIO ISO would be the next step according to the documented installation procedure.

Re: Windows 2025 setup error

dya — Sun, 11 Oct 2026 04:05:13 GMT

While it wasn't the exact same situation, I had an experience in the past where a Windows VM booted from an ISO file during creation, but under unusual circumstances. In that case, deleting the Windows installation ISO file that had been copied to the datastore and trying again sometimes resolved the issue. What I found out back then was that the size of the Windows installation ISO file was incorrect. I recommend checking thoroughly once to see if the ISO file is correct. *Whether the ISO is copied to the datastore or to the host's /var/morpheus/kvm/images/ depends on your settings.

Below are the areas to check in a v9.0.2 environment. This is for an environment where the ISO file is uploaded to an NFS server and copied to the datastore.

ISO file on the NFS server

[root@vme-iscsi-nfs ~]# ls -l /mnt/nfs-iscsi/morpheus-virtual-images/196/
total 6009364
----------. 1 root root 6153586688 Sep 26 11:49 ISO-Win2025.iso
[root@vme-iscsi-nfs ~]#

ISO file on the datastore

root@vme-iscsi2:~# file /mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/dd82bcac-0eb9-4d66-ae1e-20775a3f979e
/mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/dd82bcac-0eb9-4d66-ae1e-20775a3f979e: ISO 9660 CD-ROM filesystem data 'SSS_X64FREE_JA-JP_DV9' (bootable)
root@vme-iscsi2:~# 
root@vme-iscsi2:~# ls -ltr /mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/dd82bcac-0eb9-4d66-ae1e-20775a3f979e 
-rw-r--r-- 1 root root 6153586688 Oct 10 07:56 /mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/dd82bcac-0eb9-4d66-ae1e-20775a3f979e
root@vme-iscsi2:~#

ISO file attached to the provisioned Windows VM

root@vme-iscsi2:~# virsh list
 Id   Name       State
--------------------------
 12   win-vm01   running

root@vme-iscsi2:~# virsh domblklist win-vm01
 Target   Source
------------------------------------------------------------------------------------
 vda      /mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/win-vm01/hvm_22-disk-0-a27121b
 sda      /mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/win-vm01/hvm_22-disk-1-df97984
 sdb      /mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/win-vm01/hvm_22-virtio-win

root@vme-iscsi2:~# file /mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/win-vm01/hvm_22-disk-1-df97984
/mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/win-vm01/hvm_22-disk-1-df97984: ISO 9660 CD-ROM filesystem data 'SSS_X64FREE_JA-JP_DV9' (bootable)
root@vme-iscsi2:~# ls -ltr /mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/win-vm01/hvm_22-disk-1-df97984
-rw-r--r-- 1 libvirt-qemu kvm 6153586688 Oct 10 08:33 /mnt/9768f179-5719-4e41-8be0-3bc5c44b4dd9/win-vm01/hvm_22-disk-1-df97984
root@vme-iscsi2:~#

If all three of the above points have no issues, I don't think it is a problem with the ISO file.
*Assuming that "the ISO file on the NFS server" is normal.