PDF file extension changes to PD file extension in Outlook email fault

[Stuart27993097tl2p]

Running Windows 10 on PC, I use the web browser to access Outlook email. 

When sending attachments via Outlook email I've just started seeing the first pdf file attachment changing to a PD file extension (blue), whilst the others stay the same, a pdf . The recipient can't view the file when opening it to view, as its a PD extension, however when they save the file then open it works fine, and similarly on my PC. If I delete the first file, the pd, the rest stay as pdf files, as they were originally.

I have re-installed Adobe Acrobat reader, no change with the fault, and have also uninstalled Acrobat and installed Adobe Pro, same issue.

Tried using Windows 10 email and pdf files show as normal.

Windows says its an adobe issue.

Any help on this would be great as Clients are complaining.

[AkanchhaS]

Hi @Stuart27993097tl2p 

Thank you for well elaborating on this issue.

Seems the issue occurred with Outlook on the web only, and at the same time, it works on Windows mail 

To further investigate this issue, a screen recording of your workflow would be super-helpful, which would cover how you attach the file on Outlook and how it suddenly converts to PD rather than PDF.

Meanwhile, have you tried changing the web browser and logging on to Outlook using a different one? If not, please do that.

In addition to this, please share the exact version of Acrobat, OS, and MS Outlook.

Thanks,

Akanchha

[ChollyPaka · Accepted solution]

I ended up here because a co-worker was exporting PDFs from InDesign files and one file in particular was creating a "PD" file as well as a 0k PDF (that Windows 11  recognized as a security threat.)  We triple checked her PDF export settings and did all the normal dignostics and it kept happening just to one file being saved in one particular folder. In frustration she opted to save the PDF to another location and all was fine.  Deleted the original destination folder and re-created it as new, problem did not come back.  

Our belief from this, and from what you shared, is that this has to be an issue somehow buried within the Windows file system itself, as it was very specific to that location (does not appear to be a "path" or "naming" issue as the other folders have similar paths and utilize same naming conventions -- which makes me think this falls under "Windows Glitch" territory because we could not recreate it.)