Unknown Provisioner when running Windows 11

[F1r3Blade]

Good Afternoon

I am running Packer to build templates, the Windows templates use your provisioner to update the boxes to the latest. I have working templates using your provisioner for Windows 7, 10, 2012R2, 2016, 2019 and 2022 but when trying to make a Windows 11 template I get the "Unknown Provisioner" error. I have checked to make sure the plugin is correctly installed and it's all looks ok from that end, I was just wondering if the Provisioner is available to be working with Windows 11?

Greatly appreciate any help!

[rgl]

It works on my machines built from https://github.com/rgl/windows-vagrant/blob/5dc65efc6e53aefc55790602454ea13c3a62179a/windows-11-22h2.pkr.hcl#L303-L304

[fanuelsen]

I have the same problem with windows 11 with the vsphere-iso on packer. I ran packer with PACKER_LOG=1 and this was the output before the failure. I'm not sure is its the vsphere-iso or the windows update plugin thats causing this. Building 2022 core and gui without problems.

vsphere-iso.windows: Installing Windows updates... vsphere-iso.windows: Waiting for operation to complete (system performance: 98% cpu; 30% memory)... vsphere-iso.windows: Waiting for operation to complete (system performance: 100% cpu; 28% memory)... vsphere-iso.windows: Waiting for operation to complete (system performance: 59% cpu; 27% memory)... vsphere-iso.windows: Waiting for operation to complete (system performance: 45% cpu; 26% memory)... vsphere-iso.windows: Waiting for operation to complete (system performance: 50% cpu; 33% memory)... vsphere-iso.windows: Waiting for operation to complete (system performance: 46% cpu; 34% memory)... vsphere-iso.windows: Waiting for operation to complete (system performance: 80% cpu; 35% memory)... vsphere-iso.windows: Waiting for operation to complete (system performance: 45% cpu; 35% memory)... vsphere-iso.windows: Waiting for operation to complete (system performance: 39% cpu; 40% memory)... vsphere-iso.windows: Waiting for operation to complete (system performance: 50% cpu; 37% memory)... 2023/09/15 10:42:15 <sensitive>-plugin-vsphere_v1.2.1_x5.0_linux_amd64 plugin: 2023/09/15 10:42:15 [INFO] command 'PowerShell -ExecutionPolicy Bypass -OutputFormat Text -File C:/Windows/Temp/<sensitive>-windows-update-elevated.ps1' exited with code: 0 2023/09/15 10:42:15 [INFO] 2224 bytes written for 'stdout' 2023/09/15 10:42:15 [INFO] 0 bytes written for 'stderr' 2023/09/15 10:42:15 <sensitive>-plugin-vsphere_v1.2.1_x5.0_linux_amd64 plugin: 2023/09/15 10:42:15 [INFO] RPC endpoint: Communicator ended with: 0 2023/09/15 10:42:15 [INFO] RPC client: Communicator ended with: 0 2023/09/15 10:42:15 [INFO] RPC endpoint: Communicator ended with: 0 2023/09/15 10:42:15 <sensitive>-plugin-windows-update_v0.14.3_x5.0_linux_amd64 plugin: 2023/09/15 10:42:15 [INFO] 2224 bytes written for 'stdout' 2023/09/15 10:42:15 <sensitive>-plugin-windows-update_v0.14.3_x5.0_linux_amd64 plugin: 2023/09/15 10:42:15 [INFO] 0 bytes written for 'stderr' 2023/09/15 10:42:15 <sensitive>-plugin-windows-update_v0.14.3_x5.0_linux_amd64 plugin: 2023/09/15 10:42:15 [INFO] RPC client: Communicator ended with: 0 2023/09/15 10:42:15 [INFO] (telemetry) ending windows-update ==> vsphere-iso.windows: Shutting down VM... ==> vsphere-iso.windows: Provisioning step had errors: Running the cleanup provisioner, if present... ==> vsphere-iso.windows: Clear boot order... ==> vsphere-iso.windows: Power off VM... ==> vsphere-iso.windows: Deleting Floppy image ... 2023/09/15 10:42:17 <sensitive>-plugin-vsphere_v1.2.1_x5.0_linux_amd64 plugin: 2023/09/15 10:42:17 Deleting floppy disk: /tmp/<sensitive>3372779355 ==> vsphere-iso.windows: Destroying VM... vsphere-iso.windows: Closing sessions .... 2023/09/15 10:42:17 [INFO] (telemetry) ending vsphere-iso.windows Build 'vsphere-iso.windows' errored after 37 minutes 25 seconds: Cannot shut down VM: ServerFaultCode: Cannot complete operation because VMware Tools is not running in this virtual machine.

[fanuelsen]

It actually states that the vmware tools is not running at the end. But it is, maybe this is related to windows update updating vmware tools and it stops working?

==> Builds finished but no artifacts were created. ==> Wait completed after 37 minutes 25 seconds 2023/09/15 10:42:17 machine readable: error-count []string{"1"} ==> Some builds didn't complete successfully and had errors: 2023/09/15 10:42:17 machine readable: vsphere-iso.windows,error []string{"Cannot shut down VM: ServerFaultCode: Cannot complete operation because VMware Tools is not running in this virtual machine."} ==> Builds finished but no artifacts were created. 2023/09/15 10:42:17 [INFO] (telemetry) Finalizing. 2023/09/15 10:42:17 waiting for all plugin processes to complete... 2023/09/15 10:42:17 /root/.config/<sensitive>/plugins/github.com/rgl/windows-update/<sensitive>-plugin-windows-update_v0.14.3_x5.0_linux_amd64: plugin process exited 2023/09/15 10:42:17 /root/.config/<sensitive>/plugins/github.com/hashicorp/vsphere/<sensitive>-plugin-vsphere_v1.2.1_x5.0_linux_amd64: plugin process exited