You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a windows server build based around packer and ansible. This has been working for a few years now. Packer builds a base windows template (for ESXi,, this includes updating and installing base software like AV, Splunk forwarder, nsclient etc. This VM is cleaned up and a template created. This runs all ok, has for years.
This template is then used to build additional templates, for specific roles. One of them includes the installation of .net 4.8 on server 2019 standard (with GUI). This has worked up until this month. After creating a new base template with October updates, the dot net installer now fails, running it manually works.
There are 2 error codes:
0x800706d9: Failed to open the current cluster
0x80004005: Failed to extract all files out of box container #0.
With selecting the directory to extract to between.
I have tested this with the previous template, that builds with last months updates, but after installing this months, the above happens.
I have a windows server build based around packer and ansible. This has been working for a few years now. Packer builds a base windows template (for ESXi,, this includes updating and installing base software like AV, Splunk forwarder, nsclient etc. This VM is cleaned up and a template created. This runs all ok, has for years.
This template is then used to build additional templates, for specific roles. One of them includes the installation of .net 4.8 on server 2019 standard (with GUI). This has worked up until this month. After creating a new base template with October updates, the dot net installer now fails, running it manually works.
There are 2 error codes:
With selecting the directory to extract to between.
I have tested this with the previous template, that builds with last months updates, but after installing this months, the above happens.
This is being installed with the all in one offline installer : https://go.microsoft.com/fwlink/?linkid=2088631
installed via ansible, onto a windows server 2019 standard:
Switching to the .msu files from the update catalogue works fine.
The text was updated successfully, but these errors were encountered: