Did this issue only just start after app volumes 4.0? Because I've had printer driver issues for a while, and all seem to be related to Windows automatically looking for printer drivers in Windows Update (and the Microsoft Store)
We experience the same issue on some, not all, VDIs.
We block and deactivate the Windows Update service (which is best practice).
Of course the Windows Update service in Windows 10 is quite a headache, because it activates itself in some time, but this is another topic.
Could this be the issue (Windows Update service not running)?
can i ask, which browser you are using to access Horizon Admin panel 7.11. i cannot login by chrome latest verstion...
Take a look at the the latest version of the Horizon Optimization Tool. They recently added a checkbox for disabling checking Windows Update for drivers when a new device is added. I found this helped resolve a lot of the printer issues
We have the exact same issue with Windows 10 1909 and App Volumes 4.01. If i unassigned all my app stacks and attempt to then install a network printer it will work fine (with App Volumes still running as a service). The moment i just add one app stack,here comes the 0x00000006 error. I have verified the app stack in an update to see if it introduces problems with "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider" ... but this is not the case.
I am stumped too, for now.
Thanks, I have tried it and followed the KB article exactly, but unfortunately it didn't fix the issue. I am still getting the 0x00000006 error when installing network printers that are served by a print server in our network (and only occurs when app stacks are assigned).
Its a floating instant clone pool of Windows 1909 vdi machines, with everything latest and greatest: horizon 7.12 agent & app volumes 4.01.
Thanks for the update.
Please follow below action plan and let me know:
Note: First test it on a test pool/ test machine before moving to production.
Power on master VM.
Navigate to C:\Program Files(x86)\CloudVolumes\Agent\Config.
Create a new folder called "Custom"
Then create two folders called "app"
Create a notepad file, open the file and below lines:
exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider
Save the file as snapvol.cfg. Make sure file extension is correctly set to '.cfg' not '.cfg.txt'.
Reboot the VM, Shutdown the VM and take a snapshot and recompose/publish the pool with this snapshot.
Let me know if this resolves the problem.
Please mark reply as answered/correct if resolves your issue.
Ok, Tested it just now and that fixed the problem! Thanks a lot.
Can i consider this custom folder to be a permanent fix or is it something that will make its way into a future release of App Volumes?
This is a fix for now.
VMware support is already aware of this issue and working with App Volumes dev team to roll out an external KB article very soon. You can keep an eye on next App Volumes release notes if it is included there as permanent fix.
Please mark my answer as correct if it helped you.
I can't mark it as correct, unfortunately, i didn't start this thread.