Hi Everyone,
We had a requirement wherein we needed a custom appstack template of size 60GB.
We had a Windows Server 2012 R2 machine which we used to create the custom appstack template of size 60GB using the 20 GB default template.
Once all done with the creation of new template, we started the capture using 60GB template.
While installing the app , msi installer says error 2755 unable to detect the file. Then I ended this failed capture session and disconnected the appstack.
Once again I tried to install application but this time on OS directly, then no such errors were reported.
Then I tried to connect the good old 20GB template and tried a capture, even then I get the same error.
Anyone came across such scenario , Please suggest.
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.
https://support.microsoft.com/en-us/help/4477137/servicing-stack-update-for-windows-10
https://support.microsoft.com/en-us/help/4480976
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.
https://support.microsoft.com/en-us/help/4485449/servicing-stack-update-for-windows-10
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 2.14.2.9 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....
https://support.microsoft.com/en-us/help/4487020/windows-10-update-kb4487020
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.
I ran into the same issue working with a customer running the following:
Windows 10 1809 LTSC
App Volumes 2.15
Horizon 7.7
UEM 9.6
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....
I am running into the same issue today with an 1809 image I built yesterday. We followed the VMware Windows 10 optimized image guide and it will not let me uninstall the KB. Currently working on creating a new image and disabling Windows update from the start.
I spent this morning testing. Confirmed removing KB4487029 has allowed me to provision w/out issue.
Support says this has been noted and 2.16 this should be resolved. No ETA as of now, but remove KB4487029 and you should be good.
If anyone else sees this beware of following the VMware techzone article on building a Windows 10 image.
The dism /resetbase command makes it impossible to uninstall the updates and you have to build the entire thing from scratch.
Warning
All existing service packs and updates cannot be uninstalled after this command is completed. This will not block the uninstallation of future service packs or updates.
I suggest understanding all of the commands used in that guide, there are issues that can occur based on different environments, especially the optimization tool
Just a small side note for those of you manually installing patches. You can also just hide the patches so they won;t be installed. Thus having the benefit of "just installing the patches" without thinking about removing one from installation afterwards. The tool is called wushowhide (the name does seem to be a clear giveaway )
I can confirm that uninstalling KB4489899 lets you provision MSI based installations without issues.
I just tested this with March's Windows Updates (17134.648 [1803]) and App Volumes 2.16.0 and I was able to install applications via MSI's once again.
Same experience here.
So what I am gathering is either keep not installing each months Cumulative Updates to Windows 10, or upgrade to 2.16 is the fix right?
Did everyone upgrade the Manager as well as agent to 2.16 to fix? Or just agent to 2.16 work as a temp workaround?
Not feeling all that comfortable going to 2.16 yet with the issues some have seen during the upgrade on the manager side where things disappear...
I just upgraded the agent and MSIs are working again. I have been using it in production for almost a full week and have not seen any issues.
As a side note, I am seeing a problem with the Horizon Agent 7.8. It seems to be video related. I have upgraded all other components (Connection Servers, Enrollment Servers, UAGs, UEM, App Volumes Agent) and everything is working well.