VMware Horizon Community
LukaszDziwisz
Hot Shot
Hot Shot

BSOD when provisioning with AppVolumes agent 2.15

Hello Everyone,

Does anyone encounter often BSOD while provisioning with with APpVolume agent 2.15. Here is what happens in my case. We are using Windows 1809 LTSC, the packaging machines are clones of the Base image stripped down to the minimum. I'm trying to provision Departmental appstacks and consolidate as many common Departmental apps as I can. Sometimes after installing an application I need to reboot the machine while still capturing and when that happens I'm getting BSOD and have to cancel provisioning and start over again. It appears to be happening on many different/random  occasions with different application. If I don't reboot at all and simply after being done complete provisioning the machine reboots fine and I can complete the process. If I provision on the same packaging machine with downgraded agent 2.14 I don't see that problem however don't want to go that route either because AppVolumes agent 2.14 doesn't support windows 1809.

Any help would be appreciated,

25 Replies
Anobix67
Enthusiast
Enthusiast

Skocza wrote:

Guys, have you tried to update any appstack with this version of appvol agent 2.15 + applied that registry fix ("OptimizationLevel" REG_DWORD 0) ? Since I have applied it all, it looks that appstack is not fully loaded on my capture machine and its really slow to load the machine after restart. I am still investigating what it could cause, just trying to find out if anyone of you experinced teh same. Thanks

I have not tried that yet as I just built them on the agent. I can try that out tomorrow though to see if I have any issues.

I occasionally see the slow to load on the machine after a restart (even on 2.14 as well). Sometimes I just wait for a minute or so after a reboot to try logging in, making sure that everything is started and network is connected/good on the login screen.

Reply
0 Kudos
Skocza
Enthusiast
Enthusiast

Thanks Anobix67.

So what I have found so far.

When completely on 2.15 appvolume env. (manager + agent) + applied these registry fix (from 2.14 btw. - OptimizationLevel=0, Hidepopups=1, Asyncmount=1, IgnoreIrpQueryInformation=1 in parameters on svservice and svdriver) + Win 10 1709 = updating of any appstacks created on 2.14 or 2.15 does not work on capture machine at all, means when you provision teh appsatck for the capture machine it looks like not loaded fully or better said you can see apps in start menu and desktop if captured that way, but when you look into program and features you will see nothing added from apps or partially added only. If you uninstall any app that you want to replace it with newer version and you reboot the capture machine to replicate (as apps requires it) it is not going to boot properly, its slow and ends with totally screwed all. When you change key for 1 or remove the key ("OptimizationLevel" REG_DWORD 1), its going to end up with BSOD again, so unsable as well. Also, I have application whcih failed to install since the appstack is provisioned.

When on 2.15 manager + 2.14 agent (applied registry without OptimizationLevel=0 one) = it is much better, but it still some smaller issues after reboot the machine, but anyway, this is not recommended by vmware to use differ version of env. vs agent as advised one of the member here earlier.

So the result is that the 2.15 version of appvolume is not fully working for me, at least not as previous version 2.14, which I remember I had not kind of similar issues as on now on 2.15.

You are guys all have good experince with updating appstacks on version 2.15 with applied fix OptimizationLevel=0 in param on svdriver inregistry?

Thanks for your try!

Reply
0 Kudos
Skocza
Enthusiast
Enthusiast

...or need to add also, not only with updating appstacks, but also with installing any software when appsatck is provisioned (all on version 2.15 + OptimizationLevel=0 applied)

OptimizationLevel=0 fixes the BSOD during capture machine reboot during appstacking, but it consequenses into another issue with installing apps into appstack as well, for me :slightly_smiling_face:

Anyone with similar?

Thanks

Reply
0 Kudos
LukaszDziwisz
Hot Shot
Hot Shot

On 2.14 we never had to change the registry for OptimizationLevel. For 2.15 it fixed our BSOD. So far I was able to provision appstacks with no major issues but I agree that the boot up is much slower when we are finishing provisioning. We did have couple of issues with some applications but I did not correlate that with the registry entry. I will try those failed applications on 2.14 and see if there is any difference

Reply
0 Kudos
Skocza
Enthusiast
Enthusiast

Tanks LukaszDviwisz.

I think I have found what I was reffering to, see here Custom Appstack I have experinced the same with installing apps I thought that its related with 2.15 version of appvol, but looks that is more related with MS Feb updates as well.

Reply
0 Kudos
LukaszDziwisz
Hot Shot
Hot Shot

We did not apply February updates so I would definitely agree that is probably the culprit