Hi Guys
We have been plagued by this issue as well for quite sometime, though it was hard to pin down as it was happening to a lot of users but not all.
I finally figured it out.
If you add the Image path name and Command line fields to task manager and launch Adobe Reader, for the users who are getting this issue it will show it launching from their writables volume. However for users that weren't having this issue it was just launching from c:\program files (x86)\Adobe...
I assume that for the people affected at some point an auto-update ran and thus Adobe Reader became virtualized for them causing the failed to load core .dll error.
To fix I added the following lines to the writable snapvol.cfg file to exclude Adobe Reader:
# Adobe Reader
exclude_uwv_file=\Program Files (x86)\Adobe\Acrobat Reader DC
exclude_uwv_file=\REGISTRY\MACHINE\SOFTWARE\Wow6432Node\Adobe\Acrobat Reader
Hope this helps!
