-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Server 2016 never finishes updates install. #105
Comments
I'm also clueless about the problem. I've noticed the memory usage might be too high. Maybe try to give it 8GB RAM to see if it helps. |
I tried increasing the memory to 8GB to no avail. I forgot to mention that this also happens with Windows Server 2016 with hyperv-iso builder. So I suspect something broke after latest rounds of WU. |
Maybe there are logs somewhere, but I never needed to look at them, so I do not known where to look exactly. There's one thing that you might need: install https://github.com/rgl/windows-vagrant/blob/master/windows-2016.pkr.hcl#L201-L208 |
That sounds promising! Let me try that! |
So far, I am not having a lot of luck with Windows Server 2016 Standard template. I tried installing Servicing Stack Update for Windows, uninstalling Windows Defender (In case defender updates were causing the issue), and running Disable-windows-updates.ps1 script. Unfortunately, the build is stuck on applying windows updates forever. The only difference I see between our templates is that you are using Datacenter edition ISO while I am using Windows Server Standard ISO. Out of curiosity if you run your build of Windows 2016 server does it complete successfully? |
Even though its using the datacenter ISO (has multiple windows editions), its actually installing the standard edition. The last time I've tried (couple of months ago), all of the images in the windows-vagrant repo worked. I'll try windows-2016 today, and will let you known. |
Hi @rgl. I was wondering if you had a chance to run Win2016 build? |
Sorry, forgot about this. Just tried it, and it worked:
PS The whole Windows installation finished in about 3h. PPS Windows 2019 (and 2022) Standard also worked. |
Thanks for checking. It looks like something related to my environment, where updates never finish downloading from MS. I will try switching to updates from WSUS, see if that makes any difference. |
I am having the exact same issue. I checked windows update and i too was stuck downloading and was stuck at 95%. This is also only happening for Windows Server 2016. |
I had the same behaviour, packer-plugin-windows-update detected on top of a vanilla image of Windows Server 2016 a first ste of few updates, installed these perfectly, and after the reboot it continued to search and download a second batch. Here it stuck... As observed by other above. Finally, I figured out, it depends on plugin version. With 0.12 it works as expected, while it doesn't do the job with 0.14. |
Damned, now I face 16001... like described here: |
"KB4589210: Intel microcode updates" should not be installed on VM |
I am able to consistently reproduce that the linux version of packer-plugin-windows-update v0.14 will hang up for me every time when updating a Win2016 guest. It appears to work for the rest of Win2012-2022. |
nice find, this works for me as well |
I recently encountered an issue, where updates on Windows Server 2016 never finish. Other Windows versions do not seem to be affected, so it could be related to a recent update. Windows Updates plugin is stuck after downloading updates and never proceeds to install. You can view the full log here. https://gist.github.com/FedorRub/5352c43be40a0a3c5bdbc1467a8a9221
When I login to vm console I see that updates are ready to be installed.
I use the following packer template for all windows builds. It has multiple calls to windows update provider for win2012-r2.
The text was updated successfully, but these errors were encountered: