Windows 11 does not build with VMWare Workstation Pro

[lootem]

Version

5.0.1

Environment

• Windows 11 Pro 25H2
• Packer v1.14.3
• Vagrant v2.4.9
• VMware Workstation 17.6.4 Pro (build-24832109)
• oscdimg.exe (added to Path System variable)

Scenario

Build a Windows 11 box.

Steps to Reproduce

From within the bento directory with a packer binary: .\packer.exe build -only="vmware-iso.vm" -var cpus=4 -var memory=8192 -var headless=false -timestamp-ui -warn-on-undeclared-var -var-file=".\os_pkrvars\windows\windows-11-x86_64.pkrvars.hcl" ".\packer_templates\"

Expected Result

Box builds.

Actual Result

Autounattend.xml is not found and Windows 11 is stuck on language selection. Packer is stuck "Waiting for WinRM to become available..."

Things I've tried:

• headless=true/false
• Lowering default VMware hardware compatibility.
• Upgrading to VMware Workstation Pro 25H2, v25.0.0.24995812
• Using Virtualbox (this works).

Complete log:

2025-11-28T17:58:27-07:00: ==> vmware-iso.vm: Retrieving ISO
2025-11-28T17:58:27-07:00: ==> vmware-iso.vm: Trying https://software-static.download.prss.microsoft.com/dbazure/888969d5-f34g-4e03-ac9d-1f9786c66749/26200.6584.250915-1905.25h2_ge_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso
2025-11-28T17:58:27-07:00: ==> vmware-iso.vm: Trying https://software-static.download.prss.microsoft.com/dbazure/888969d5-f34g-4e03-ac9d-1f9786c66749/26200.6584.250915-1905.25h2_ge_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso?checksum=sha256%3Aa61adeab895ef5a4db436e0a7011c92a2ff17bb0357f58b13bbc4062e535e7b9
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: https://software-static.download.prss.microsoft.com/dbazure/888969d5-f34g-4e03-ac9d-1f9786c66749/26200.6584.250915-1905.25h2_ge_release_svc_refresh_CLIENTENTERPRISEEVAL_OEMRET_x64FRE_en-us.iso?checksum=sha256%3Aa61adeab895ef5a4db436e0a7011c92a2ff17bb0357f58b13bbc4062e535e7b9 => C:/ProgramData/bentotesting/bento/builds/iso/windows-11-x86_64-25f79562.iso
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Configuring output and export directories...
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Creating CD disk...
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: OSCDIMG 2.56 CD-ROM and DVD-ROM Premastering Utility
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Copyright (C) Microsoft, 1993-2012. All rights reserved.
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Licensed only for producing Microsoft authorized content.
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Scanning source tree
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Scanning source tree complete (1 files in 1 directories)
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Computing directory information complete
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Image file is 73728 bytes (before optimization)
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Writing 1 files in 1 directories to C:\Users\lootem\AppData\Local\Temp\packer2305549899.iso
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Storage optimization saved 0 files, 0 bytes (0% of image)
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: After optimization, image file is 73728 bytes
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: 100% complete
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Done.
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Done copying paths from CD_dirs
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Creating virtual machine disks...
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Generating the .vmx file...
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Starting HTTP server on port 8189
2025-11-28T17:58:42-07:00: ==> vmware-iso.vm: Powering on virtual machine...
2025-11-28T17:58:46-07:00: ==> vmware-iso.vm: Connecting to VNC...
2025-11-28T17:58:47-07:00: ==> vmware-iso.vm: Waiting 1s for boot...
2025-11-28T17:58:48-07:00: ==> vmware-iso.vm: Typing the boot command over VNC...
2025-11-28T17:58:49-07:00: ==> vmware-iso.vm: Waiting for WinRM to become available...

[Stromweld]

on line 246 the cd_files are being set if they are not being overriden by your setup. Can you verify the configuration of the VM while it's running that you have a cdrom called cidata configured in the VM settings?

[Stromweld]

are you also using the latest version of bento code? can you run a git pull on main branch to verify you are up to date?

I just tested on Intel MacOS 26.1 system with packer 1.14.3, vagrant 2.4.9, and vmware-fusion 25.0.0.24995814(aka 25H2) and current code in Main works on my system.

Here's the command I ran: packer build -timestamp-ui -force -only=vmware-iso.vm -var-file=os_pkrvars/windows/windows-11-x86_64.pkrvars.hcl packer_templates

[lootem]

are you also using the latest version of bento code? can you run a git pull on main branch to verify you are up to date?

Pulled the latest from main and ran .\packer.exe build -timestamp-ui -force -only="vmware-iso.vm" -var headless=false -var-file=".\os_pkrvars\windows\windows-11-x86_64.pkrvars.hcl" packer_templates

Can you verify the configuration of the VM while it's running that you have a cdrom called cidata configured in the VM settings?

There is only one CD hardware entry for the W11 iso.

[lootem]

I've tried some different combinations of host/guest OS and providers:

• Windows Host with VBox/VMware/Qemu
• Fedora 43 Host with VBox/Qemu
• Ubuntu 24 LTS Host with VBox/Qemu

all with the same results: Windows guests (11, 2019, etc.) are stuck on language selection. With Qemu I am able to see multiple ISOs added, but Autounattend does not start. I'm not sure what I am missing here...

@Stromweld if I understand correctly, there should be an Autounattend file added to the root of one of these ISOs, can you confirm where I should be seeing that to troubleshoot further?