Outlook 365 keeps corrupting PDF and Office files

Anonymous
2023-05-10T02:49:12+00:00

Since April we started a new EA agreement with Microsoft and added all of our users to E5 licenses of M365 on top of the E3 licenses they already had - we were told that the E3 licenses would disappear anyway.

We don't know if that is related, however since mid-April we started to have numerous users who find their email attachments to get corrupt in Outlook. Whether it's with Outlook 2016 or 365, and Windows 10 or 11 Pro, the symptoms are always the same: the size of the attachments decrease significantly and they cannot be opened in their usual application (Adobe PDF Viewer, Word, Excel, PowerPoint, etc.).

Attachments in emails are oftentimes received already corrupt and are therefore unusable, sometimes they are good to be viewed or opened, then later on get corrupt. Sometimes

the attachments get corrupt when their related emails get forwarded to other users (who also find corrupt attachments in the emails they received).

We noticed that Outlook sometimes get even in a state where no file can get attached to a new email, or no attachment from a received email can get saved on any drive.

Whenever a user tries to open a corrupt attachment, an error message similar to this appear: "there was an error opening this document. The file is damaged and could not be repaired". No useful details get logged in the Event Viewer, all we see at the time of the error is "An unexpected error has occurred".

We tried the SaRa diagnosis program on some users' workstations with no luck, the SaRa program gets to vanish before the issue is seen again.

We tried to run Desktop Outlook in Safe Mode, the issue has not been seen. We tried to disable all of our add-ins one by one in normal mode, the issue was seen with every add-in being disabled....

We have hundreds of users and are out of ideas. Can you please help.

Outlook | Windows | Classic Outlook for Windows | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2023-06-16T19:36:36+00:00

Our Office 365 version is 2303.

We solved the issue here by deploying the following Known Issue Rollback (KIR) to over a thousand of workstations:

Windows 11, version 21H2: KB5023774 230222_032017 Known Issue Rollback

Windows 10, versions 21H2/22H2: KB5023773 230222_032013 Known Issue Rollback

See: Windows 10, version 22H2 | Microsoft Learn

Was this answer helpful?

2 people found this answer helpful.
0 comments No comments

48 additional answers

Sort by: Most helpful
  1. Anonymous
    2023-06-14T14:12:20+00:00

    @AM_493, @Menyelek Thomas,

    Are you seeing the issue occurring with new attachments or are those possibly already corrupted? Here is the guidance from Windows about existing attachments:

    "Where the April or May Windows Updates caused the corruption of attached files, the June 13th, 2023 Windows Updates are preventative vs. retroactively “corrective”, meaning that the install of the June 13th updates will prevent the corruption of attached files after installation but will NOT correct already corrupt attached files."

    Here is the note about the fix:

    This update addresses a known issue that affects 32-bit apps that are large address aware and use the CopyFile API. You might have issues when you save, copy, or attach files. If you use some commercial or enterprise security software that uses extended file attributes, this issue will likely affect you. For Microsoft Office apps, this issue only affects the 32-bit versions. You might receive the error, "Document not saved."

    Since it only affects 32-bit apps double check if you are seeing this with 32-bit or 64-bit Outlook Desktop.

    To see the released June 13 KBs here are the links:

    Windows 10, Windows 10 - release information | Microsoft Learn

    Windows 11, Windows 11 - release information | Microsoft Learn

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-05-31T16:33:55+00:00

    OMG please bring this patch ASAP!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-05-31T13:46:07+00:00

    This is caused by a known issue in Windows patch in April and May:

    May 9, 2023—KB5026361 (OS Builds 19042.2965, 19044.2965, and 19045.2965) - Microsoft Support

    The fix will be included in Windows patch in June.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-05-22T16:26:06+00:00

    Is there an update ? We have the same issue as well .

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments