"The properties of the message have been changed" prompt when forwarding/replying in Outlook

Anonymous
2021-05-21T21:28:23+00:00

When users open a message in its own window that has a pdf attachment and replies or forwards the message; when they close the original window, outlook prompts "The properties of the message <email_subject> have been changed. Want to save your changes to this message?"

Steps to recreate this issue:

  • Message must have pdf or txt attachment
  • Open the original message in its own window
  • Reply-to or forward the message
  • Closing original message that was previously opened in its own window

Attempts to disable add-ins or running outlook in safe-mode do not resolve this issue.

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
Answer accepted by question author
Anonymous
2021-06-16T08:16:59+00:00

Hi All，

First, apologize for the inconvenience caused by this problem in Outlook Client. Microsoft has realized this issue and the dedicated outlook teams are working on this problem to fix it. It is a known issue in the current Outlook Clients, and a fix will be released to Office version 2106 on 2021/6/17. For the affected users please navigate to Outlook Web App as temporary workaround and wait for the new fix release with some more patience, thanks. For more details, please refer to "The properties of the message have been changed" prompt when forwarding/replying in Outlook.

Thanks for your understanding and patience.

Best Regards,

Oliver

Was this answer helpful?

20+ people found this answer helpful.
0 comments

157 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Diane Poremsky MVP 17,526 Reputation points MVP Volunteer Moderator
    2021-05-28T13:37:54+00:00

    If any of you have a support contract or use Office 365 business, and can repro it easily, please open a support case. If you are using the beta build of office 365, you can report it too.

    I 'm reporting it using my repro steps, but it seems to be unrelated to the addin I use and may not help them identify the cause.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2021-05-28T13:36:36+00:00

    Hello All,

     

    Thanks for updating here. Seems many users are reported with the same issue, we need to collect below information for further investigation.

     

    • Does affected users are belongs from on-premises or Exchnage online (pure cloud)?
    • Does this issue only occurs with reply and forward email when it has attachment or all emails (without attachment).
    • Detail version of affected user's Outlook with build information (by open Outlook > File tab > office account and share entire page screenshot with remove your email id).

     

    Your co-operation will be highly appricated. Thank you so much for your precious time

     

    Stay safe and healthy.

     

    Regards,

    Ankita Vaidya

    on-premise

    all emails. regardless of reply or forward, opening an email message then closing it will prompt with the properties window.

    tried the latest channel down to this version. same issue

    Image

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-05-28T13:30:03+00:00

    On-Premise,

    Occuring when replying or forwarding message without attachements.

    Version 2014 (build 13929.20386)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2021-05-28T12:58:58+00:00

    -On-Premise Exchange.

    -All emails, regardless of attachment. If you open the email in it's own window and reply or forward, you will get the request to save when closing the original email window. If you close Outlook and reopen the application, the message will show up on the 2nd reply or fwd. The first one will work as intended.

    -Have tried several build versions, but here is an example 13901.20462

    On a side note, this seems to coincide with the Exchange security patch that was released on May 11th. KB5003435.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments