The XML did not paste through, but you get the point.

I found a workaround with the black screen Windows Store apps “bug” in OOBE.
Basically, do sysprep with a config XML that sets the password and autologins in. Then provided the XML to sysprep.

You can still use any customization to override the existing sysprep.

Example:
C:\Windows\System32\Sysprep\sysprep.exe /generalize /oobe /shutdown /mode:vm /unattend:C:\Windows\System32\Sysprep\unattend-server2025-appxfix.xml

true
true
true
true

ChangeThisPASSWORD!!!!!123
true

true
Administrator
2

ChangeThisPASSWORD!!!!!123
true

Yes. NGT 4.5

Totally agree with you about sysprep and server 2025! The Windows Store apps “bug” is a shambles for starters! I templated 2025 last year and have been having issues with windows updates applying to VM’s built from the template, basically the winxsx cbs store gets corrupted at some point (not right away) and windows updates won’t install. I think its probably something to do with appX probably language settings. VM’s installed via the ISO are fine but 2025 VM’s installed from our template are not! If the in place updates of 2025 don’t work to fix the issue we’re going to have to rebuild in the region of 50 VM’s 30 of which are in production! 🙁 Wish we had stuck with 2022!

I’m not using audit mode. I dont like that. Did you install ngt 4.5 in it?? (Minimum version 4,5)

I am banging my head with templating Windows Server 2025.
Install vm -> audit mode (windows updates, adjust language and other settings) -> sysprep with oobe, generalzie, mode:vm and shutdown -> VM comes up black screen with language switcher.
Doesn’t matter if I use Nutanix customization or not – the customization does not seem to apply anyway.
I checked the sysprep logs – there is nothing there besides the sysprep and shutdown.

If I don’t sysprep the machine and use that as a template – the customization applies. But when I log in with the new admin password from the customization explorer does not start (crashes in event log).

Seems like sysprep on Windows Server 2025 is simply a disaster.

Jeroen,
I have done some more testing, and I found out a workaround :
1. In the temporary VM, after performing the required update and before shutting it down, delete the following file:”C:\Program Files\Nutanix\config\ngt_config.json »
2. Shut down the VM and proceed with “Complete Guest OS Update” as per Nutanix instructions.

From this new version of the template, you can deploy Windows VM using Sysprep Guest Customization Profiles, and after power on, the Customize Guest VM will take place successfully like with the original version of the template.

Thats should work yes. But I havent tried it yet. I have this in the agenda to test this friday. I will update the blogpost when I have the information.

I have NGT Version 4.5 (and the Template is for Windows Server 2022 , also another one for Server 2025).
Did I understood correctly that with the Guest customization, I do not need to run Sysprep anymore ? (I tried both, but no success, as sson as I update the Template, Guest customization profile does not work anymore (for me).)

If you use the latest ngt version it must work. I will try to update the template blogpost when I have some spare time.