Lansti Posted July 31 Share Posted July 31 Hi. I'm testing a new Windows 10 22H2 image from my MDT to Horizon 8. I have upgraded FSLogix and the New Teams within the Master image. The installation process are ok, and deploy to my test pool in Horizon works. When i log on with my user, and an appstack is deployed - with Google Chrome, Chrome do not work at all. Other applications in the same appstack works. I created a new Capture Client, a clone from the master image mentioned above, where the new Teams and latest version (FSLogix_Apps_2.9.8884.27471) of FS Logix are installed. When i create a new clean package in AppVolume Master, and tries to install latest version of Chrome (127.0.6533.89), I do not get any error messages, but i can see that something is wrong. In my start menu i can see the Chrome icon is gone: When i run appwiz.cpl i can see that Chrome version is pretty old version... When i did a new capture with the same Capture Image, but downgraded FSLogix to an older version: 2.9.7979.62170 Chrome is installed as expected with no issues... Have you guys experienced something like this? Why do an FSLogix installation on a Master image break an AppVolume Capture? Best regards Lansti *********************** System: Horizon 2209 DEM 2209 AppVols 4, version 2212 Windows 10 22H2 FSLogix: 2.9.7979.62170 *********************** Quote Best regards Lansti Horizon 2209, DEM 2209,AppVols 4, version 2212 Windows 10 22H2, FSLogix 2.9.7979.62170 Link to comment Share on other sites More sharing options...
Employee Doug Arcidino Posted July 31 Employee Share Posted July 31 (edited) So, you mention "app stack" and other applications. Were these app stacks that came over from 2.x or were they captured natively on a modern version of app volumes? Generally speaking, with app volumes 4, it's better to capture individual applications rather than having these large app stacks. Have you tested with updating your app volumes agent? It would seem to me that the issue is some user state data that must be getting captured by fslogix. Have you tried disabling fslogix on a test image post upgrade? Edited July 31 by Doug Arcidino Quote Link to comment Share on other sites More sharing options...
Solution Ofir Dalal Posted July 31 Solution Share Posted July 31 (edited) Hi, Running the command to check order of svdriver: fltmc instances -v c: If FSLogix(frxdrvvt) filter driver priority is before App Volume Agent(svderiver), please modify the Horizon Golden Image using an admin command prompt to run the following command: reg add "HKLM\SYSTEM\CurrentControlSet\services\svdriver\Instances\App Volumes Instance" /v Altitude /d "132000" /f Take a new snapshot of the Golden Image following best practices and publish it to a test pool for testing. The workaround, lower the svdriver altitude below frxdrvvt. Edited July 31 by Ofir Dalal 2 Quote Link to comment Share on other sites More sharing options...
Lansti Posted August 1 Author Share Posted August 1 Thanks @Ofir Dalal, i have tested this ,and it seems to be running smooth again after i modified the priority list. Quote Best regards Lansti Horizon 2209, DEM 2209,AppVols 4, version 2212 Windows 10 22H2, FSLogix 2.9.7979.62170 Link to comment Share on other sites More sharing options...
Greg New Posted September 3 Share Posted September 3 @Ofir Dalal many thanks for this. Solved my issue 🙂 I made the change to the App Volumes packaging VM as well. Cheers, Greg Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.