Dec 13 2021 10:29 AM
Dec 13 2021 10:29 AM
Latest version of Office Desktop - for some new email, when we reply, we get an error message popping up: This is not a valid file name.
There is no attachment on the email, we're just replying to the email. It is random why this occurs.
We have tried removing signatures, checking images in the email, it is random. If we set the email format to plain text, we can reply but all formatting, links etc. are lost. We can reply to the email in OWA with no problem so why is Outlook Desktop unhappy?
Have tried creating new Outlook profile on new machine, creating new .OST file, removing AV software, removing MalwareBytes, clearing the Outlook cache, deleting temp files, clearing Microsoft Edge cache.
Have opened a case with Microsoft Support back in early November, but no help there.
Thanks for any help!
Dec 13 2021 02:43 PM
@gt-seaI also get this and it has only started happening in the last month or less I think. Only happens in desktop version of Outlook
If I reply or forward some emails I get the same "This is not a valid file name" error message.
Fix is to look for and delete any images that are in the body of the email then it will send ok. I think it has to do with broken image links but not sure.
Dec 13 2021 03:06 PM
Dec 14 2021 03:25 AM
@gt-sea Ah, someone else experiencing the same issue, I really struggled to find any info on this around the web before now.
I have done some digging myself, it seems also that if you click away from the email (quick reply/forward) so it remains a draft email in the list of emails for whatever folder you're in and then switch back, the entire email body vanishes and becomes totally blank.
It acts as if wherever it caches this while writing the reply is beyond the windows character limit, however, I have tried outlook in online mode with no caching enabled, I have cleared appdata, cleared temp files, checked while writing emails for anything generated in temporary internet files or other locations and not found anything.
Hope we can find a solution to this, but also somewhat glad to see it's not just me going crazy!
Dec 14 2021 07:47 AM
I have also been getting this error for about a month now. For some reason, it is only out of a specific inbox folder. The same user can forward or reply from the web app and from their phone but gives the error from the desktop app. (We have tried both office 2019 pro and M365). Reinstalling will work for about two weeks until the issue pops up again. @gt-sea
Dec 14 2021 03:56 PM
Thanks @ITGDaryl. Sorry you are having similar problems but kinda glad others are reporting this issue - maybe Microsoft will put some resources behind trying to solve this. I have an open support ticket with Microsoft about this issue and the ticket was opened on 11/9 and Microsoft really has done nothing to resolve the issue. I'm on my 4th ambassador (the last one went on holiday and I found out 2 days later when ambassador #4 introduced himself).
I would think they could have an Outlook Desktop SME look at this issue and see what is triggering the error in the desktop software. Email message is fine in OWA and/or on Phone APPS - so what in the email does Outlook Desktop not like?
Dec 16 2021 08:46 AM
I've been having this same issue for a couple of months now. Desktop Outlook 365. For me, it's when I try to forward an email.
Dec 20 2021 06:09 AM
Dec 22 2021 05:16 AM
Jan 07 2022 08:06 AM
Jan 07 2022 08:28 AM
Jan 20 2022 04:05 AM