Rui Lopes

The updates can take a lot of time to install (3h+ but YMMV). To be sure, you need to enter the VM and see if the CPU is busy or...

After I've increased the VM memory from 2G to 4G the windows updates were installed successfully. I've also used the latest VMware-tools-windows-10.3.10-12406962.iso file (this way windows updates does not try...

Let me known how you do it. I'm also looking for an offline one. There's wsusoffline... maybe some day I'll make an packer builder for it.

Indeed. It seems something in the windows update machinery is crashing and on top of that this windows update provisioner is not detecting/retrying the updates, and it just ignores the...

It seems the powershell process that is installing the updates is still running, but something is disconnecting/killing the WinRM connection that is used by the provider; on top of that,...

It might really be that Servicing stack update (KB4498947); it updates the Windows update machinery, and in a way that messes with the provisioner. Though, in my local VMware setup,...

Hummm this might be related to https://github.com/hashicorp/packer/issues/7655 (as of 0.7.0 I've started to use the new packer retry logic). Can you try with https://github.com/rgl/packer-provisioner-windows-update/releases/tag/v0.6.1?

Your packer template is fine. It seems there's a bug somewhere in this provider implementation. It seems that sometimes the update script (or the winrm connection) is being terminated by...

What was the actual output? Did it say "Skipped"? The last time I've looked at it, the Windows Update UI had a different button/workflow for doing feature upgrades, so maybe...

So it really seems that to install feature upgrades some other api (or flag) needs to be called/used. But I do not known which api is that, and since I...