We have a brand new look! Take a tour with us and explore the latest updates on Adobe Support Community.
Extreme delays in Outlook when replying to or attaching files to emails. Delays ranged from 20 seconds to over 8 minutes before reply window would open. By uninstalling every Creative Cloud application one at a time, the culprit ended up being Acrobat DC, which is somehow connected to Outlook. Once uninstalled, Outlook worked perfectly. (After 4 tech support "experts" and 7 weeks of IT support calls.)
Other people in my work group who also use Creative Cloud do not experience this issue. My "guy" says it might be my laptop chipset which is creating a conflict for an Adobe update.
Can anyone shed some light on this?
I have a different but related problem. When I try to install Acrobat DC I get an error message which states I need to close out of Outlook however outlook is not open. I am thinking about uninstalling outlook just to install Acrobat for I currently don't use outlook. Any insight would be helpful.
Also had difficulty downloading Acrobat CC even though Outlook 2016 was closed. Adobe Support tried to download directly from the site and not the CC App, and when that didn't work, opened Task Manager > More details, and there was a Microsoft Outlook file running. So then ended the task and Acrobat downloaded and installed.
I have just ended two Microsoft Outlook tasks running on Task Manager, and I am so excited now because finally, Adobe Acrobat is installing!
This worked as well for me. Thanks for sharing!
Thank you for the golden answer. Was getting very frustrated with it not installing. Deleted two files and now it's installing ok.
Thanks again 🙂
I've been having the same problem and I too found the same thing. I ended task and it was resolved and Acrobat DC Pro is installing! Thank you!!
We also noticed severe Outlook lag since Adobe CC deployment. We solved it by disabling the Outlook add-in called "Adobe Send & Track for Microsoft Outlook - Acrobat".
Unfortunately Adobe doesn't seem interested in fixing this issue.