Outlook not displaying email body of text and deletes text when pressing enter when moving to another line

We see similar questions here...
Also I see a lot of similar messages from other users on a local error reporting platform.
The numbers of errors jumped up starting 4h ago (20:00 CEST).
They report more or less the same issue.
This points possibly to a Microsoft Problem.

So possibly you need some patience now until MS has fixed it.
Due to the fact, that it seems only to affect Microsoft hostet services (Office 365, Exchange Online), On premises services should not affected as the patches were announced for today, but not published yet.

There was another hint from user DAN, you may try, if it works...., as a workaround.
Outlook Options - Advanced - Display - Uncheck "Disable Hardware Graphics Acceleration"  

User Jeff Glover reported:
You can fix it by reverting to the previuos version:
"C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.13901.20462.

Thanks so much for the response.

When you say Microsoft hosted services, not sure if you also mean exchange.  I have a client that has their e-mail hosted at Rackspace on exchange servers and it is also occuring.

Actually - the one Outlook client has exchange, gmail (imap), and an isp via imap optonline.net
Every single one of them have the same issue but they are within the same client - so perhaps it is not hosted services but an update.

FYI - if I configure the rackspace hosted exchange account on a local license of Office 2019/NOT the 365 license it too has the same issue!

Thanks!!!

Hey there

Question regarding this - so I understand it, I ran it without the last line below (that I have underlined in bold), and it seemed to work, what exactly does this do, or did I do it incorrectly?  
That being said, if it is an MS update which it appears to be - I would imagine for people that have auto-updates enabled it could break it again if MS doesn't fix it.

"C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.13901.20462.               

Thanks so VERY VERY much!!                   

There are usually two update sequences.
The Office 365, Exchange online and all other services hosted by Microsoft.
They are usually patched first.
Then they publish the updates during the patchday via Windows Updates as well as WSUS, which are patching the Office and Exchange (and all others) on premises solutions.
WSUS ist just a centralized solution to avoid, that every client downloads its own updates and to manage this more centralized.

Beside Microsoft, you can also book Exchange mailboxes offered by an internet provider, this is called hosted Exchange.
But the internet povider ususally using the same mechanism (WSUS).

Also you find providers, which are just resellers of Microsoft Online products, what is more or less the same than you book it directly on Microsoft.

The link above is for (temporary) reverting an Office 365 client to a older version than the current.
 
I just checked now again an do not see updates in WSUS, but my client offers updates via Windows Updates if I allow it. So even there is a difference between Windows Updates and WSUS.

And yes, autoupdating is disabled for all my systems. Because you are the first one, who gets the patches installed and the first one, which catches all the bugs. Its all the time a good idea to wait 1-2 days until installing updates.
It is not the first time, Microsoft killed some systems.

Hey Bembi

Super helpful I thank you. I just got word from someone I work with at Rackspace and this is what Microsofts statement is - however, really not making sense that it is definitely impacting locally installed licenses of Office.
Under GPOs I set autoupdate to disabled (any tips on how to prevent autoupdates), it seems as if MS always finds a way around it.  You are very brave waiting only a couple of days. I generally lag up to 4 weeks unless it is a zero day.

Thoughts on how it can affect a locally installed copy of office? Users did not install updates, other than running on 20h2 for days without ANY issue until this afternoon.
Thanks again!!

Using a GPO (if you do not use WSUS) ist the way to control it. If you use WSUS, the WSUS itself does offer the updates only, if approved by an admin.
So my clients are set to download and offer, but they depend on the approval via WSUS.
I see them is WSUS, but I approve them after 1-2 days.
The lack of a direct GPO is, that you have to change it all the time, because at the end you want to have them, if they are ok. But for the moment better to block them for some days.

If clients already catched them, you have to remove them possibly manually.
Also a job, WSUS can do.  

Hey there
So even for small environments 10-20 computers using wsus?  Does it have to be on a DC - I will review it yet again!

Thanks

Lets say, even for 10-20 computers it makes sense.
WSUS needs a little bit resources (file storage), round about 200 - 300 GB. But depends from what you enable for snychronization.
Putting additional services on a DC is not recommended at all due to security reasons, but depend a bit from what you have. The DC is also the heart of your infrastructure, so additional services may impact your infrastructure, if other services puts load on it. But on the other hand, sometime you  have to leave the church in the village.
At the end it means, leave your DC free as long as you have other options.  
You can also virtualize servers on an existing hardware, so just to setup virtual machines, one DC and one WSUS, which you can also use as file server.  

Microsoft introduced a bug this afternoon.  They've applied a patch and it should be fixed by 3am tomorrow.  
https://twitter.com/MSFT365Status/

Users just have to restart Outlook.

as per https://twitter.com/MSFT365Status/status/1392208966231355392, it should be fixed now:

Thanks guys!  The part that was super interesting, is, it would appear that even though your system shows that no updates have been installed, the GPO disabling updates is set to disabled (althought I am told it wont work), It would appear that Microsoft pushes out updates to all desktops anyway - WITHOUT disclosing it.  The reason I say this is, I had an office with locally installed versions of Office Home and Bus 2019, and they too were affected by this.  It would appear as if Microsoft updates whatever they want/whenever they want, without the end user being aware/informed in ANY way.  

Perhaps I need to look at WSUS even for smaller offices if it means I can have control and delay ALL updates for as long as the business dictates, due to obscure third party apps that could break and cripple the business - so we can handle it in a controlled manner.

I would have only thought Office365 would have been affected by this

Thanks again!!

Office 2019 is click to run, so also a different procedure like normal windows updates or WSUS.
This may be the reason, why you got it even the traditional updates are disabled.
Click to run means, that you do not get updates, you get a complete new prepatched package.
So I would expect, that you do not see it under updates.
But you can indetify it by the office build number.  

Hey Bembi

Thank you for that, super helpful.  So what are your suggestions for CONTROL of patch management,  prior to windows 10 was using an enterprise level third party all to deploy across multiple platforms.
I like to lag up to 30 days, perhaps do the computers representing different builds in an organization with the least impact first in a dept.  
Should I consider WSUS for this? I haven't looked at it in years.  In your opinion what is the smallest deployment you would consider that for? 10 end points? WSUS - is free with a server OS correct? I think you can also schedule reboots correct?
What about smaller clients where they can have less than 10 computers and it is basically P2P?  Still want to the ability to control updates.  Micrsoft breaks so much, from printing, third party apps, drivers etc.  I need to do it in a controlled fashion.


Thanks again!