topic Re: Outlook 2016 and Acrobat Reader DC in Horizon Desktops and Apps

Outlook 2016 and Acrobat Reader DC

QCBenPetersen — Wed, 15 Aug 2018 19:57:30 GMT

So I have been wrestling with this little issue for a while and figure i would throw it out there

Envirometn

Horizon: 7.5.1

UEM 9.4

Appstacks 2.14

Windows 10 LTSB 2016

I have adobe acrobat reader dc installed on the GM. I then load office 365 from the appstacks. If i open outlook and try to open a .pdf, it works the first few times. Then after that I get a failed to load core .dll. This only happens from Outlook. If i preview the file in outlook it works just fine. If i save it and then open it, works just fine, if i change it over to google chrome to be the default pdf viewer, works just fine. I have tried all of the fixes from the adobe site of the house, registry fixes for protected mode do not seem to help.

I should just let it be and keep telling them to use chrome or save it then open it, but i figured maybe i can shut the complainer up. Any help would be appreciated.

Thanks in advance

Re: Outlook 2016 and Acrobat Reader DC

AoSIt — Thu, 11 Oct 2018 10:07:10 GMT

Exactly the same issue here. Pretty much the same Versions of Horizon, UEM and Appvol. It seems Users are able to open .pdf files for a while until the "failed to load Core dll" appears. Only a relog seems to help. AR DC is installed on the golden image and not deployed via appstack.

Any help is appreciated

Re: Outlook 2016 and Acrobat Reader DC

LibRick — Tue, 16 Oct 2018 08:38:09 GMT

Same issue here. Almost identical setup except Outlook 2016 is in the base image and appvols just handling the OST.

Re: Outlook 2016 and Acrobat Reader DC

gpenunuri — Fri, 18 Jan 2019 18:44:59 GMT

Same here. Office and Reader is installed on the Base Image. Seems to work after deleting the users writable profile but that's not the solution.

Re: Outlook 2016 and Acrobat Reader DC

LibRick — Wed, 15 May 2019 15:45:16 GMT

I have found that if the user goes to apps & features then modify on acrobat reader then does a quick repair it fixes the issue. A bit annoying as you have to do it for everyone who has the issue but it's the best I've found so far.

Re: Outlook 2016 and Acrobat Reader DC

robgj821 — Wed, 29 May 2019 02:36:24 GMT

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!

Re: Outlook 2016 and Acrobat Reader DC

mcdaidh — Tue, 07 Jul 2020 16:41:13 GMT

I had an issue with PDF files not opening from email attachments. We ended up having to disable Protected Mode in Acrobat Reader. This can be achieved using the following steps.

Open Acrobat Reader, got Edit | Preferences (or press Ctrl+K).
Navigate to Security (Enhanced) in the Categories list.
Unselect "Enable Protected Mode at startup".
Close both Acrobat Reader and Outlook.
Open Outlook and try opening the PDF file. Should open without any issues.

There is also a Group Policy ADMX file you can download from Adobe to manage this using a GPO. Sorry, I don't have the link of hand.

Regards,

Hugh

Re: Outlook 2016 and Acrobat Reader DC

boast1570 — Mon, 19 Jul 2021 15:46:58 GMT

Hi robgj821,

We had a similar issue with Adobe Reader installing it's updates on the UIA writable and breaking with a Master image update. Any reason you didn't use the exclude_path option in the snapvol.cfg? The way I'm reading it is exclude_uwv_file will process in the order of install to Writable -> AppVolume -> Base Image, so it doesn't remedy the issue, as it'll update each login, but then be deleted at logoff. I'm testing the exclude_path option now to see if it reads directly from the base image instead of writable. I added the exclude_process line for AcroRd32.exe as well.... just to be safe!