on your provisioning machines do you have windows update disabled, and are you rolling back to a clean state after capturing applications.
Yes and yes.
I even rebuilt our provisioning machine (Windows 10 1803) in the event the Windows Installer service was corrupt.
Hermanac01 - After OS reinstallation ( assuming your image didnt contain that update ) did provisioning work ?
It failed on the rebuilt VM but I did have the latest Windows Updates installed.
I rolled it back to having no updates installed (Windows 10 1803 build 17134.1) and I didn't get the issue. Definitely some issue between the latest Windows Updates and the App Volumes agent.
I do have a case open with support about this as well.
Let me give it a shot and let you know
First - my machine does not have that same MS update specified earlier.
But we do have a few updates installed on 17th Feb.
Quite unsure whether these updates are related. I do not have new machine so I have to wait a little longer to test it
I did a little more testing and here's what I've found.
From build 17134.1, I installed January's Windows Updates and the problem didn't exist. These are the two updates I installed which took me to build 17134.556.
From build 17134.1, I installed February's Windows Updates and the problem occurred. These are the two updates I installed which took me to build 17134.590.
Created a new packaging machine and the same thing happened here as well. Digging into it to see what is happening. My guess is Microsoft is doing something funcky with security again looking at the fact that someone has the exact same issue with 188.8.131.52 and I did package correctly with that version up until now.
If anyone has a solution please post ..
I need to go through my emails, there is another post about other permission errors, and it looks like a set of updates in February is breaking the provisioning process. The post is either in here or the Horizon forum. They identified patches that if weren't installed allowed them to continue. I have yet to test this myself
I just got off of a call with VMware regarding this issue. Uninstalling just KB 4487017 on Windows 10 1803 resolved the issue for me. Apparently this breaks MSI based provisioning only and is not exclusive to 2.15 as we downgraded to 2.14.2 and had the same issue. .EXE based installs still work without issue (we tested with NOTEPAD++ while on the call).
What sconley said, thank you very much for the update.
For people not as adventurous and still using version 1703 of Windows, you need to uninstall KB 4487020. Long live Microsoft....
I was looking at a solution and after removing the specific patch I found out that it has been preceded by https://support.microsoft.com/en-us/help/4487011 (still, 1703 build also for 1803 it has been preceded). Anyone already tested that new version? I am in the process of upgrading the machine and hopefully will find out that the issue has been fixed....
Will keep you guys posted. If anyone else has a solution before that please let me know ..
I got this update from support this evening regarding this issue.
This is just to update you that, I have checked internally and found that this issue has been taken care in next release of App volume version 2.16, which is planned to release in first week on march (tentative).
Thanks for the update. Uninstalling the specific patch and installing the preceding patch did NOT resolve the issue so for now it's either uninstalling the patch or waiting for 2.16.
2 people found this helpful
I ran into the same issue working with a customer running the following:
Windows 10 1809 LTSC
App Volumes 2.15
We successfully created App Stacks prior to the February Microsoft patches were installed but once they were, we were unable to install any applications when updating an App Stack or even creating a completely new one. I noticed that KB4487017 was specific to Windows 10 1803 but also saw that some of the same fixes were deployed in KB4487044 which is specific to 1809. Once we removed this from the Packaging machine everything started working properly. Hope this saves some of you deploying Windows 10 1809 with App Volumes some headaches....