![pdf preview for outlook 2013 pdf preview for outlook 2013](https://freepdf-books.com/doc-images/4332.png)
Delete the key for the file types you don't want to automatically preview and press F5 to.
#Pdf preview for outlook 2013 pdf#
PDF attachment in Outlook for the solution. When you attempt to 'live' preview an attachment in Outlook 2007, Outlook 2010, or Outlook 2013's reading pane and uncheck the box to 'Always warn before previewing', this type of file if you want to restore this setting, you'll need to edit the registry. On a few PCs we also have Adobe Acrobat XI Pro update 23 installed and with this in place the preview works in Outlook but that is only on a small number of machines as it is a licenced product. If PDF files wont preview in Windows 64-bit, see Cant open or preview. Corruptions and similar problems with the temporary/cache files might be the reason behind this issue. Restart Outlook and check if you can preview PDF attachments now. There was a preview utility hack that used foxit - not sure if it works with 2013.
![pdf preview for outlook 2013 pdf preview for outlook 2013](https://dwnloadhunter485.weebly.com/uploads/1/2/4/7/124782252/308832940.png)
I know abode reader or acrobat will add preview - Im surprised the windows app doesnt (i use acrobat). The issue also occurs on our Windows 10 PCs with the same version Adobe Acrobat Reader DC installed but we have the same GPO DCOM settings in place for W10. Make sure that it's the default app to open PDF files. if the pdf app supports preview, it should automatically work with outlook. The Anti Virus Software is Symantec Endpoint Protection V12.1.6 even if we uninstall SEP the Outlook preview does not work.
![pdf preview for outlook 2013 pdf preview for outlook 2013](https://i0.wp.com/www.pstviewer.com/blog/wp-content/uploads/2018/05/outlookPstViewer1-1.gif)
Thanks for your reply, this is on Windows 7 SP1 and the version of Adobe Acrobat Reader is 2018.011.20040 the issue is happening on thousands of our PCs and we have tested the resolutions suggested in your post on several PCs along with any other fixes and workarounds we could find on the Adobe Forum but the issue persists.