In our environment we believe the upgrade of the 2.13.2 to 2.14.2 agent on our Capture and Build VM (which we do all of our provisioning on) has made every AppStack update after the agent upgrade change the Windows Search service to disabled inside the AppStack, which has been causing our issues. We believe this is due to the new HKLM\Software\CloudVolumes\WSearch hive keys which upon the AV Agent starting on the Capture and Build VM is setting the Windows Search service to disabled, and provisioning is capturing that as a change.

We can update an AppStack that was previously updated using the 2.13.2 AV Agent and the Windows Search service is set to Automatic (Delayed Start) after it has been attached to a machine, but any AppStack that we update with the 2.14.2 AV Agent, the Windows Search service is set to Disabled after it has been attached to a machine.

Our workaround right now is to update the AppStack and in provisioning change the Windows Search service to Automatic (Delayed Start)

Anyone else experiencing this?