New
#10
New Microsoft 365 Current Channel v2104 build 13929.20372 - May 11 Office
-
-
New #11
If memory serves they will withdraw this botched release pronto and re-issue the previous one.
Were I in their shoes I would not hesitate for too long either, there will be outrage.
- - - Updated - - -
OK, fair point, was too quick with jumping to conclusions.
But can't imagine a lot of people faffing with XML files - at least I have other (better) things to do.
-
New #12
-
New #13
You can also roll back to a previous Click-To-Run version with a single line at an Admin Command Prompt:
If you are using Outlook 2016, 2019, or 365, copy the following line, then right click in the command prompt window to paste it. Replace xxxx.yyyy with the build number you want to revert to. You can look up build numbers at Version numbers of update branches for Office 365 clients.
"C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.xxxx.yyyy
Uninstall Updates in Office 'Click to Run' [Slipstick.com]Last edited by Brink; 11 May 2021 at 16:28. Reason: fixed link
-
New #14
I have one user in my office with this issue. His version says Version 2104 (Build 13929.20296 Click-To-Run). However mine also says the exact same thing, and I do not have the issue. Weird.
-
New #15
This retarded updated forced me to do a repair install on two new builds in order to get it to load but it still won't display any emails.
Edit: I'm rolling her back to last month.
-
New #16
Yup it is affecting all of my machines still on 13929.20296 (dated April 29th) and the ones I've updated to this latest version today. However I downgraded to the update released on 23rd April: 13901.20462 and the emails all display normally again. Obviously not ideal as this version is two behind, and is probably missing security patches.
The fix for me was to run an elevated command prompt: "C:\Program Files\Common Files\microsoft shared\ClickToRun\officec2rclient.exe" /update user updatetoversion=16.0.13901.20462
It runs the installer and voila, you're back in business.
EDIT: Looks to be all fixed now, including on the machines that had already received the update and I didn't perform the above workaround.Last edited by catspyjamas; 11 May 2021 at 18:45.
-
New #17
It just started working again. Guess Microsoft changed something.
Ak
-
New #18
We’ve identified the root cause and are applying a fix, which will reach affected users over the next 3 to 4 hours. Users will need to restart the Outlook client to apply the fix after it's received. We expect to restore service to affected users by May 12, 2021, at 3:00 AM UTC.
The deployment of our fix is progressing as expected and we continue to anticipate that it'll complete on Wednesday, May 12, 2021 by 3:00 AM UTC.
Tweet
— Twitter API (@user) View on Twitter
-
-
New #19
I wonder how the fix got into my computer. Maybe those people that wear tinfoil hats aren't crazy after all.
Quote
Related Discussions
