At mid-morning Wednesday within the U.S., Outlook stopped working. Dead in its tracks. Both the Click-to-Run model of Office (er, Microsoft) 365 and the put in (MSI) model of Outlook refused to start out:
Today after I went to verify my electronic mail, Outlook wouldn’t open; it will load the “Starting Outlook…” splash display, which might shut with out opening the Outlook window itself, and the taskbar icon went away. Looking in Reliability History, it states that Outlook has crashed.
I attempted opening in secure mode (it does the very same course of as described above) and restarting the pc to no avail. I even tried the total restore (not the short one), redownloading and reactivating MS Office 2019, however no go.
Then, four or so hours later, Outlook all of a sudden began working once more.
There are so many packages working round referred to as “Outlook” that it’s tough to nail down which variations of Outlook went AWOL. But it seems to be like all the latest variations of Microsoft 365 Click-to-Run Current Channel – courting lower back to June 30’s Version 2006 Build 13001.20266, a minimum of – in addition to Office 2019 packed their baggage and left the station.
Microsoft, in its inimitable means, left a path in its @MSFT365Status tweets:
We’re investigating a problem affecting consumer entry to Outlook. We’re investigating whether or not a lately deployed replace might be the supply of this situation. As a workaround, customers can make the most of Outlook on the internet or their cellular purchasers… (four hours later) We’re rolling out a repair for this situation, and we count on the mitigation to succeed in all prospects over the following few hours.
So for four hours yesterday, you can get at your Outlook electronic mail via your iPad, or by hitting the web site, however the model of Outlook you most likely use in your PC had taken the morning off.
Ends up the sudden disappearance was attributable to the Outlook.exe program crashing with an error 0xc0000005. Lawrence Abrams at BleepingComputer has full particulars.
Two apparent questions current themselves:
- What broke? There weren’t any new variations of Office pushed out yesterday. Yet, everywhere in the world, thousands and thousands (if not a whole lot of thousands and thousands) of Outlook customers all had the rug pulled out from underneath them.
- How did Microsoft repair it? There was no patch delivered, no new C2R model, no emergency replace for Outlook 2019. Microsoft’s resorted to some odd patch supply mechanisms currently (notably utilizing the Microsoft Store) and it’s had multiple-cumulative-update issues. But this repair apparently didn’t contact PCs in any respect.
Microsoft’s proffered clarification doesn’t move the sniff take a look at:
There is a brand new symptom of Outlook crashing on launch beginning on 7/15/2020. A repair has been revealed however will take time to propagate to worldwide availability. Outlook will mechanically look for the repair on launch, so if this situation persists via a number of launches please use Outlook Web Access (or your suppliers webmail interface) for an hour then attempt once more. This downside shouldn’t be related to any of the 7/15/2020 safety patches so there is no such thing as a must uninstall them if Outlook won’t launch.
In truth, there weren’t any modifications made to any PCs. Individual customers didn’t get new variations. Administrators didn’t push something out on their networks. Outlook simply all of a sudden began working once more.
Many individuals found that they may get Outlook working by rolling lower back a number of variations. Older variations of Outlook (each C2R and MSI) labored. The newer ones didn’t. The bug had nothing to do with particular patches.
I used to be considering the mysteries of life, the universe and Outlook appcrashes, when an nameless submit appeared on AskWoody:
Woody – can’t let you know my supply however mainly rumor is one thing was pushed server-side on Microsoft’s conclusion with regard to a safety or authentication change (who is aware of what particularly) and in that change it reduce off communication with Outlook purchasers previous a sure patch. I confirmed this was not final evening’s patch that contained these modifications, however one beforehand issued. I have no idea something extra particular about this patch in query. This is why rolling lower back labored – it went to a shopper model that was earlier than that change in the way it talked to their servers. Why this was executed in the midst of the day, I don’t know. Very uncommon. All I’m keen to enter proper now.
That explains it. (Thank heaven for nameless posters!) As @NetDef says:
Admins: don’t must verify for updates or re-apply updates. Just begin Outlook. If you rolled lower back earlier in the present day it’s secure to roll ahead once more to deliver you lower back to present patched standing.
The bug was a mix of a brand new safety verify on the shopper, and a back-end server patch/change. For now the back-end server change has been reverted for Office 365 Exchange tenants.
Translating that into English: Microsoft constructed some fancy new checking mechanism into the newer variations of Windows-based Outlook. It was working simply nice till, yesterday morning U.S. time, anyone modified one thing on Microsoft’s servers. Kaboom. No extra Outlook.
Root trigger: A latest change to the Outlook shopper inadvertently resulted on this situation.
That’s sorta true. What clobbered all people was some silly change on a server.
– We’re reviewing our replace procedures to isolate these points previous to our deployment cycle.
– We’re analyzing our telemetry information to raised determine these points earlier than they affect our prospects. We’ll publish a post-incident report inside 5 enterprise days.
I may ask the plain questions – most starting with, “What within the blue blazes…?” or one thing extra colourful – however you’ll be able to fill these out your self. Bottom line: Somebody at Microsoft modified one thing on a server, with out testing the change, and it introduced down Windows-based Outlook all over the place.
Deployment “cycle”? Puh-leeze. We noticed the identical stupidity with the Windows Search field bug lower back in February. Somebody threw a monkey wrench (er, spanner) within the server. Everybody received clobbered.
Kinda makes you’re feeling heat and fuzzy.
If you thought an put in Windows model of Outlook can be extra steady than a cloud model – or an iPad or Android or iPhone model, for that matter – that is what’s referred to as a comeuppance.
We’re all the time trying for solutions on AskWoody.
Copyright © 2020 IDG Communications, Inc.