Unable to create Office 2016 AppStack on W10 LTSC 2019

[SummaCollege]

Running the following config:

• Horizon 7.7.0
• AppVolumes 2.15
• Windows 10 LTSC 2019
• UEM 9.6.0

Created a base image with Horizon, AppVolumes and UEM agents. Created a clone for Appstack Provisioning and uninstalled the Horizon agent.

When i then put this machine in provisioning mode and try to install Office 2016 it won't let me and stop with the following error (translated from dutch): "Setup: the system is unable to open the requested system or file".

Installing a different software package as AppStack like VLC player is working fine.

When not putting the machine in Provisioning mode, Office is installed without problems! So whats happening here.....??

Anyone have any ideas?

[SummaCollege]

The same issue when installing Office 2019 version. When the machine is in provisioning mode Office won't install. When the same machine is not in provisioning mode, installation is succesfull.

Strange behaviour... And again, when installing other software, the appstack is created succesfull.

[Jketels]

Same experience here, but with Office 365 ProPlus.
AppVolumes 2.15
Windows 10 1803

No error logs, nothing...

[josejjcv]

Same issue here, with Adobe Acrobat Standard XI (App Vol 2.15)

[josejjcv]

I have an existing Provisioning Machine that was cloned from "Parent" VM and removed Agents, apps, etc and it works there. I checked Distributables installed among other software from base and nothing sticks out. I have no idea as to why it works on that Provisioning machine, also running App Volumes Agent 2.15. I have a ticket open w/ support now and they have had me go as far as bare metal Windows 10 1803 nothing other than agent installed and still fails when in PROV mode.

Now they are asking me to remove all Windows Updates installed to date. SMH

[Ray_handels]

Okay, seems far fetched but try and look in the other topic (Custom Appstack ). There has been a patch released in February which breaks the installation of MSI installers when you are in provisiong mode. Apparently Microsoft does a check now on the installation file (apparently only with MSI files) and because you are installing on a virtual disk it fails because of this.

[jmatz135]

Yeah, pretty much all appstack creation is broken if you have the February updates applied to the VM you are capturing on.

[SummaCollege · Accepted solution]

After uninstalling KB4487044 provisioning is succesfull. Now hoping for a permanent fix from MS or VMWare.

[Ray_handels]

Last thing I heard is that there will be a fix from VMWare (as stated somewhere on the forum, to lazy to search, sorry ).

I hope it will be in the next 2.16 or 2.15.x version. For now uninstalling the patch seems to be the best way of dealing with it.