[HELP] Windows Server 2025 sysprep not working in Proxmox VE 8.2.7

S

SubliminaL1989

New Member
Feb 18, 2024
5
0
1
Hello everyone,

I'm facing an issue when I try to run sysprep on a Windows Server 2025 VM in order to convert it to a template afterwards.
I've installed the virtio drivers, installed the windows updates, done a few tweaks and when I run sysprep with "OOBE experience" , "Generalize" and Shutdown option, the VM won't shutdown. I've manually shutdown the VM from PVE web interface, convert it to a template, but when I clone the template into a new VM, after setting up a new administrator password, the screen goes black and the VM becomes unresponsive.

I want to mention that I've encountered the same issue with sysprep on server core (no desktop), but after manually shutdown the VM and convert it to a template and then clone the template into a VM, everything is working as expected compared to the desktop experience version of the windows server.
I've also tried to replicate the issue in VMWare Workstation, but there is running the sysprep without any issue, the VM is shutting down properly after running sysprep, so I guess this is a Proxmox issue and not a Win Server issue...

Does anyone facing the same problem ?

Many thanks !
 
Last edited:
SubliminaL1989 said:
Hello everyone,

I'm facing an issue when I try to run sysprep on a Windows Server 2025 VM in order to convert it to a template afterwards.
I've installed the virtio drivers, installed the windows updates, done a few tweaks and when I run sysprep with "OOBE experience" , "Generalize" and Shutdown option, the VM won't shutdown. I've manually shutdown the VM from PVE web interface, convert it to a template, but when I clone the template into a new VM, after setting up a new administrator password, the screen goes black and the VM becomes unresponsive.

I want to mention that I've encountered the same issue with sysprep on server core (no desktop), but after manually shutdown the VM and convert it to a template and then clone the template into a VM, everything is working as expected compared to the desktop experience version of the windows server.
I've also tried to replicate the issue in VMWare Workstation, but there is running the sysprep without any issue, the VM is shutting down properly after running sysprep, so I guess this is a Proxmox issue and not a Win Server issue...

Does anyone facing the same problem ?

Many thanks !
Click to expand...
did you use the default language settings (US English) or changed to to your own locale?

when I set it to dutch (my county) is doesn't work after sysprep and even in windows itself its unstable (mouse not working, black screen, etc)

keeping it on US English and I have no issues!
 
  • Like
Reactions: MarvinFS and SubliminaL1989
bakker_erik said:
did you use the default language settings (US English) or changed to to your own locale?

when I set it to dutch (my county) is doesn't work after sysprep and even in windows itself its unstable (mouse not working, black screen, etc)

keeping it on US English and I have no issues!
Click to expand...
I’m using it with US English, only the region and timezone is set to my country.
 
I can confirm I have no issues with sysprep as well (except the internal Windows scrutiny with provisioned packages, which is not relevant to the subject) - all went fine answer file was also created fine, actually specifically for proxmox I also used specific settings for not to remove pnp info, which should speedup things and not to remove hardware specific and drivers information, since all that will be only running on proxmox.

XML: 
    <settings pass="generalize">
        <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
        </component>
    </settings>

The only issue I have now is that despite the latest qemu agent package being installed (virtio-win-0.1.262.iso) and ticked in VM's options, inside guest OS itself services are started and all PCI devices related to normal VIRTIO functionality are present, it still shows IP info like that: (I have one nic on VMs - several now - all are shown like that)

1731886149295.png
 
Last edited:
You must log in or register to reply here.
Top Bottom