jigocz
Contributor
Contributor

BSOD for Windows 10 with AppVolume agent 2.18.2

Jump to solution

Hello,

we have upgraded the AppVolume agent from 2.15 to version 2.18.2 and started a re-deployment for all VDI VMs, we use Automatic Desktop Pool with Floating assignement, Linked Clone

The Golden image

  • Windows 10 image LTSC - 1809 - OS Build 17763.1158 windows updates to 04/2020,
  • AppVolume Agent 2.18.2.27,
  • Vmware Horizon agent 7.11.0
  • Vmware Tools 10.3.5 - build 10430147

  • Appstack template used is 2.18.2
  • Writable volume used is 2.18.2 - uia_plus_profile

After some time we see the BSOD for SVDRIVER.sys is happening across the environment.

BSOD.jpg

Did you experienced the same issue? what troubleshooting can be done for that svdriver.sys?

Thank you in advance

0 Kudos
1 Solution

Accepted Solutions
julatoski
VMware Employee
VMware Employee

This problem has been addressed in App Volumes 2.18.4.  Please see VMware App Volumes 2.18.4 Release Notes for details.  We recommend all customers running 2.18.2 and using Writable Volumes to update their Agent version 2.18.4.

The 2.18.4 maintenance update to resolve the 2.18.2 BSOD issue does not require the App Volumes manager to also be updated to 2.18.4; however, we always recommend a good practice to keep App Volumes Manager on the latest maintenance version.  App Volumes 2.18.4 addresses a minor App Volumes Manager issue where erroneous "failed to find volume" and "volume does not exist" errors appear in the logs. 


Jeff Ulatoski
Product Line Manager, App Volumes

View solution in original post

6 Replies
Ray_handels
Virtuoso
Virtuoso

To be honest I have never seen this issue with Appvolumes.

When upgrading the Appvolumes agent is there anything else you updated?

0 Kudos
jigocz
Contributor
Contributor
  • Windows 10 image LTSC - 1809 - OS Build 17763.1158 is windows updates for April 2020,
  • Vmware Horizon agent is installed with 7.11.0
  • some other programs  - like antivirus has been updated too during Golden (Master) Image preparation.
0 Kudos
Ray_handels
Virtuoso
Virtuoso

My guess is that it is a combination of any of those elements that make the svservice crash. As said, I haven't seen this one before, we are also using agent installed virusscanning but it could be that it crashes while being scanned byt the virusscanner. Have you tried excluding it from the virusscanner??

Otherwise I would suggest creating a ticket with GSS and asking them if they can find anything from the logging.

julatoski
VMware Employee
VMware Employee

We have identified and fixed an issue in 2.18.2 when a user deletes multiple files or folders with a writable volume and one or more AppStacks attached.  An update to 2.18 that addresses this issue is planned to be released in the next few days.

Thank you for your patience.


Jeff Ulatoski
Product Line Manager, App Volumes
jigocz
Contributor
Contributor

Hello,

we have updated the appvolume agent in Golden image to version 2.18.4  and created a new desktop pool with one provisioned VDI VM and test user is logged in - with appstacks and writable volume attached.

We will leave the VDI Vms running for some time to see if the issue is reproducible there - and base on the results will collect and provide the required .vmem and .vmss files to opened vmware support case.

What do you suggest for upgrade the AppVolume manager server from 2.18.2 to version 2.18.4 please?

What is the compatibility between version 2.18.2 to version 2.18.4 ? -  like we have Appvolume manager server running now from version 2.18.2, appstacks captured with template for 2.18.2, Writable volume created from template for 2.18.2, AppVolume Agent running from provisioned VDI VM with version 2.18.4..

0 Kudos
julatoski
VMware Employee
VMware Employee

This problem has been addressed in App Volumes 2.18.4.  Please see VMware App Volumes 2.18.4 Release Notes for details.  We recommend all customers running 2.18.2 and using Writable Volumes to update their Agent version 2.18.4.

The 2.18.4 maintenance update to resolve the 2.18.2 BSOD issue does not require the App Volumes manager to also be updated to 2.18.4; however, we always recommend a good practice to keep App Volumes Manager on the latest maintenance version.  App Volumes 2.18.4 addresses a minor App Volumes Manager issue where erroneous "failed to find volume" and "volume does not exist" errors appear in the logs. 


Jeff Ulatoski
Product Line Manager, App Volumes