Matt Warner

Forgot to add: Packer host is Linux (RHEL7) and target is Windows 2016

I reverted to 0.7.0 and it seems to be working now.

Output when using 0.7.0: ``` ==> vsphere-iso: Running Windows update... 2019/05/15 18:05:17 packer-builder-vsphere-iso.linux: System.Management.Automation.PSCustomObjectSystem.Object1Preparing modules for first use.0-1-1Completed-1 2019/05/15 18:05:17 [INFO] starting remote command: PowerShell -ExecutionPolicy Bypass -OutputFormat Text -File...

I may have declared victory too soon. It's doing the 1.4GB cumulative update and seems to be stuck, which is what I believe the fix in 0.7.1 addressed...

I let it run for hours and finally started poking around. In the Event Log I see over and over, "Package KB4494440 failed to be changed to the Staged stage....

This VM has 12GB, so I'm thinking that's not it. After Packer failed, I rebooted the VM and tried to have it install KB4494440 via Windows Update, and it failed...

I'm contemplating excluding this patch and copying it over via Ansible and installing it that way. Unfortunately, win_updates doesn't allow for specifying an offline source, so I'll have to use...

I'm not sure if I'm making progress, but I think it's safe to say this has nothing to do with 0.7.1. Notice in the output below the provisioner starts to...

Just a guess, but when the first update failed, it looks like the windows-update provisioner stopped execution and the next provisioner ran?

I appreciate the effort you've put into creating and maintaining this! I found [a script](https://gallery.technet.microsoft.com/scriptcenter/Reset-WindowsUpdateps1-e0c5eb78) to reset the Windows Updates internals. I'm going to run that, do a windows-restart, and...