Forum Discussion
Outlook (Office 2019) crashes when Send of From clicked
Since the evening of Sunday 19th I have been unable to send emails from Outlook on my PC. I can compose an email and select recipients. However when I try to send the message it hangs for a few seco...
manzp
As far as I can see my most recent updates were on 16th November and I was sending emails quite happily until the evening of 19th. If there was an identifiable update to roll back I'd try that, I guess.
Which other websites are you seeing similar reports on please? It would be useful to see what others are experiencing and think.
I'm a newbie when it comes to posting on this forum. Would we expect someone from MS to respond with a solution, or at least an acknowledgement that something has been broken? If we are talking months for a solution I'll be migrating elsewhere, though I don't really fancy reinputting all the details of three accounts. If I were being supercynical I might think that the idea was to tell us all would be hunky dory if only we took out a shiny new 365 sub...
As far as I can see my most recent updates were on 16th November and I was sending emails quite happily until the evening of 19th. If there was an identifiable update to roll back I'd try that, I guess.
Which other websites are you seeing similar reports on please? It would be useful to see what others are experiencing and think.
I'm a newbie when it comes to posting on this forum. Would we expect someone from MS to respond with a solution, or at least an acknowledgement that something has been broken? If we are talking months for a solution I'll be migrating elsewhere, though I don't really fancy reinputting all the details of three accounts. If I were being supercynical I might think that the idea was to tell us all would be hunky dory if only we took out a shiny new 365 sub...
Would be nice if MS gave an answer... I saw one person said they changed from Microsoft exchange to IMAP/SMTP and it worked for them. Another said they changed to the "New" view for Outlook desktop app which I am pretty sure I declined when prompted within the last week. Issue started after that. Searching on the web I can't find any information on changing to this new view as I would like to try that. I saw a post on reddit and on another MS forum.
I don't post that often, but hoping we can get a resolution on this issue.
I don't post that often, but hoping we can get a resolution on this issue.
I am having the exact problem starting today. Sending an email it spins for a few seconds, crashes and restarts. No sign of sent email anywhere. Sending from phone app works fine.
Please can anyone advise if Microsoft have a clear procedure for handling this type of issue.
In the absence of this, do folk wait until some helpful, technical savvy individuals investigate and volunteer solutions?
It seems odd that this is a clear issue related to an upgrade. Is it straightforward to revert to a previous version?
Has anyone tried to revert back? Does this resolve it?
I am not technical and can only wait until the best advice with clear instruction is kindly posted.
- Luke_Porter1
I believe the MS procedure is as follows.
"Ignore it and keep telling everyone about the new Outlook."
Even a simple acknowledgement would be an advance on deathly silence.
To be constructive rather than cynical, what have recent updates changed? The last Windows update (16 November for me) brought Copilot preview, which I don't want but can tolerate being there. Unless it screws up other programs and there has been a reference to Copilot insisting you use the new Outlook or some such imposition. I know we only have the preview but might this be related?
The most recent Office update (14 November for me but possibly overtaken by an Office repair a few days ago) said this about Outlook:-
"We fixed an issue that caused Outlook to fail to comply with the default browser settings for some users.
We fixed an issue that caused the labels from protected PDF files to not be applied to the email that they were attached to."
Neither seems a likely cause of the issue but I am well aware that changes elsewhere in the software can have unexpected impacts elsewhere.
