WinRM issue?

[tivanov-qb]

When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.

With 1.5.0 version, I started seeing issues in post-processor.
Please note that this issue does not happen in 1.4.0
Not sure whether this is WinRM issue or sysprep, or something else, but it looks like it was implemented by #573

snippet from my build:

provisioner "windows-shell" {
inline = [""%programfiles%\amazon\ec2Launch\ec2launch.exe" sysprep --shutdown=false"]
}

provisioner "windows-shell" {
inline = ["shutdown -s "]
pause_before = "5m0s"
}

post-processor "manifest" {
}

Reproduction Steps

Init 1.5.0 version

Plugin and Packer version

1.5.0

Simplified Packer Buildfile

If the file is longer than a few dozen lines, please include the URL to the
gist of the log or use the Github detailed
format
instead of posting it directly in the issue.

Operating system and Environment details

I use Docker container image 'hashicorp/packer running on Amazon Linux 2023

Log Fragments and crash.log files

Error without debug:

21:37:01 1758825421,,ui,say,==> amazon-ebs.windows-L1-ami: C:\Users\vagrant>"C:\Program Files\amazon\ec2Launch\ec2launch.exe" sysprep --shutdown=false
21:37:01 1758825421,,ui,say,==> amazon-ebs.windows-L1-ami: agent ran successfully
21:37:01 1758825421,,ui,say,==> amazon-ebs.windows-L1-ami: Sysprep sub-command: shutdown: false clean: false
21:37:01 1758825421,,ui,say,==> amazon-ebs.windows-L1-ami: 2025-09-25 18:37:00 Info: Preparing items to run Sysprep.
21:37:01 1758825421,,ui,say,==> amazon-ebs.windows-L1-ami: 2025-09-25 18:37:00 Console: Message: Successfully disabled hibernation
21:37:01 1758825421,,ui,say,==> amazon-ebs.windows-L1-ami: 2025-09-25 18:37:00 Info: Run sysprep
21:37:01 1758825421,,ui,say,==> amazon-ebs.windows-L1-ami: 2025-09-25 18:37:00 Info: Sysprep command: C:\Windows\System32\Sysprep\Sysprep.exe /oobe /quit /generalize /unattend:C:\ProgramData\Amazon\EC2Launch\sysprep\unattend.xml
21:37:47 1758825460,,ui,say,==> amazon-ebs.windows-L1-ami: Pausing 5m0s before the next provisioner...
21:42:54 1758825760,,ui,say,==> amazon-ebs.windows-L1-ami: Provisioning with windows-shell...
21:42:54 1758825760,,ui,say,==> amazon-ebs.windows-L1-ami: Provisioning with shell script: /var/tmp/windows-shell-provisioner858587302
21:47:45 1758826062,,ui,say,==> amazon-ebs.windows-L1-ami: Provisioning step had errors: Running the cleanup provisioner%!(PACKER_COMMA) if present...
21:47:45 1758826062,,ui,say,==> amazon-ebs.windows-L1-ami: Terminating the source AWS instance...
21:49:52 1758826183,,ui,say,==> amazon-ebs.windows-L1-ami: Cleaning up any extra volumes...
21:49:52 1758826183,,ui,say,==> amazon-ebs.windows-L1-ami: No volumes to clean up%!(PACKER_COMMA) skipping
21:49:52 1758826183,,ui,say,==> amazon-ebs.windows-L1-ami: Deleting temporary keypair...
21:49:52 1758826183,,ui,error,Build 'amazon-ebs.windows-L1-ami' errored after 45 minutes 30 seconds: Command has already been closed
21:49:52 1758826183,,ui,say,\n==> Wait completed after 45 minutes 30 seconds
21:49:52 1758826183,,error-count,1
21:49:52 1758826183,,ui,error,\n==> Some builds didn't complete successfully and had errors:
21:49:52 1758826183,amazon-ebs.windows-L1-ami,error,Command has already been closed
21:49:52 1758826183,,ui,error,--> amazon-ebs.windows-L1-ami: Command has already been closed
21:49:52 1758826183,,ui,say,\n==> Builds finished but no artifacts were created.

A paragraph or two about the issue you're experiencing.

Set the env var PACKER_LOG=1 for maximum log detail.

Please see the attached file

packer_debug.txt

[tivanov-qb]

@kp2099 @mogrogan tagging you both as you used to help me before

[tivanov-qb]

@kp2099 @mogrogan may I ask for some help with this please?

[kp2099]

Hi @tivanov-qb Which packer version are you using?
Can you test with latest packer version and with plugin version 1.4.0?
And also with packer version 1.13 ?

[tivanov-qb]

Hi @tivanov-qb Which packer version are you using? Can you test with latest packer version and with plugin version 1.4.0? And also with packer version 1.13 ?

hey @kp2099 thank you for looking into it!
I see this postprocessor issue only in 1.5.0. I've tested both 1.4.0 and 1.13 -- they work

[tivanov-qb]

@kp2099 may I ask for some help with this one?

[tivanov-qb]

ok, so this is definitely broken by 1.5.0 and above but i can't trace the exact reason/code change. i'm confident this is winrm issue happening after sysprep, but not always. it would be great if someone has time to take a look into it

[anurag5sh]

Hi @tivanov-qb ,
Since version 1.5.0, we improved WinRM error handling by catching previously uncaught errors. This shouldn’t cause issues unless sysprep or WinRM return a non‑zero exit code, in which case the build fails. Earlier, such errors may have been missed, allowing the build to pass.