Rui Lopes

There is something strange going on while detecting if the machine completed the reboot (while the updates are installing the machine sometimes restarts multiple times and this provider is not...

Can you please try again with 0.6.0 and packer 1.2.5?

Also do not set any options on the provision step, i.e. use: ```json { "provisioners": [ { "type": "windows-update" } ] } ```

Please try [v0.14.0](https://github.com/rgl/packer-plugin-windows-update/releases/tag/v0.14.0) and let us known how it goes.

Its not wrong per-se, its [showing you the maximum download size](https://github.com/rgl/packer-provisioner-windows-update/blob/70636b2de4df6082f59755c624f7d87f27e54fe1/update/windows-update.ps1#L191) of that update as reported by the windows update api. If you want another information you should submit a...

Can you provide an example on what variables are needed to configure windows updates for that?

Its a known bug that sometimes manifests itself. Essentially, something seems to be disconnecting the WinRM connection (or restarting it), and this provider is not detecting that, so it just...

With my images from https://github.com/rgl/windows-2016-vagrant it works fine, so I'm not sure why its not working there. How long did you wait? It should not take more than an hour....

I my experience the different Windows editions/versions, Windows Updates, the Windows Update, the Windows Servicing Stack are a slippery slope and they are way too obscure/fragile/slow to work with. The...

Please try [v0.14.0](https://github.com/rgl/packer-plugin-windows-update/releases/tag/v0.14.0) and let us known how it goes.