Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Outlook is crashing worldwide with 0xc0000005 errors

bleepingcomputer.com

Post reply on HN
Print view View original

11–20 of 109 posts

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#13

Post by cosmie »

hs86 wrote: post #4

What is going on with Outlook for Windows? For years, it froze its entire UI whenever there was some network lag on the IMAP server, and the recent improvements for Outlook strangely focus only on their Mac, web, and mobile versions. Does the Windows version still have a future? It seems to be stuck in some maintenance limbo.

If you look at the release notes[1], Outlook for Windows is getting a lot of love too. The majority of updates are performance and bug fixes, but the UI issue you mentioned highlights the need for this type of TLC in the Windows client. That said, the frequency you receive these will be pretty dependent on which release cycle your install is set up for, as it can range from monthly to semi-annually.

The Mac, web, and mobile versions are getting a whole lot of feature releases in comparison to the Windows client, but virtually all of them are intended to bring those other clients to feature parity with the Windows client. I've interpreted this as more of Microsoft treating these alternate platforms as first-class citizens finally, rather than as neglect of the Windows clients.

This also isn't limited to just the Outlook client - it's a trend across the entire Office suite. For example, Power Query[2] is a really neat and powerful ETL system hiding within Excel (as well as used in PowerBI, and originating in SQL Server Analysis Services). It's been available for years in Excel for Windows, but only recently became usable on Excel for Mac thanks to a major refactor[3] to port it to .NET Core and strip out Windows dependencies. Eventually this will reach feature parity with and replace the legacy Power Query code in the Windows Excel client, then all net new development will be cross-platform and available on both clients simultaneously.

All things considered, I view the resource allocation across the platforms as a positive. Presuming the feature development happening for the non-Windows clients are as similarly cross-platform as the Power Query effort, it'll eventually lead to cleaned up Windows clients with decades of legacy cruft refactored out, feature parity and consistency across platforms, and substantially greater velocity as those resources currently split between platforms eventually consolidate and focus on a unified, cross-platform, and cleaned up codebase. And if the refactors continue to prioritize .NET Core, it also bodes well for an official Linux client eventually.

[1] https://docs.microsoft.com/en-us/officeupdates/semi-annual-e...

[2] https://docs.microsoft.com/en-us/power-query/power-query-wha...

[3] https://devblogs.microsoft.com/dotnet/using-net-core-to-prov...

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#14

Post by marricks »

I wonder if large companies get more of a pass with outages then small ones? Bias towards authority in a way.

If a service has a big enough base an outage could almost seem like a pass for everyone. “Oo couldn’t do that this morning GITHUB was down.” Whereas if my small GitLab server was down bosses could be “well why aren’t we on GitHub like everyone else, it’s up now?”

When google calendar was down a bit ago I tried looking at random people responses on twitter and many were “whew I get out of some meetings!”

Perhaps there is some accountability for large scale outages like these but it really feels like consensus is often “shit happens” which is totally reasonable just seems like it could hurt big companies a lot less.

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#15

Post by Shorel »

fortran77 wrote: post #9

Yup! I just updated Windows and got a crash. Relaunched it and it was ok Faulting application name: OUTLOOK.EXE, version: 16.0.13001.20266, time stamp: 0x5ef2a169 Faulting module name: mso98win32client.dll, version: 0.0.0.0, time stamp: 0x5ef2771f Exception code: 0xc0000005 Fault offset: 0x00000000000beef2 Faulting process id: 0x3be0 Faulting application start time: 0x01d65ad25f628bf7 Faulting application path: C:\Pr…

So that's why I have not been affected.

I only shutdown "my" work laptop on weekends.

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#16

Post by muststopmyths »

hs86 wrote: post #4

What is going on with Outlook for Windows? For years, it froze its entire UI whenever there was some network lag on the IMAP server, and the recent improvements for Outlook strangely focus only on their Mac, web, and mobile versions. Does the Windows version still have a future? It seems to be stuck in some maintenance limbo.

Windows is a second-class citizen in the new Microsoft. You only have to use it regularly to understand that.

Re: Microsoft Outlook is crashing worldwide with 0xc0000005 errors

#19

Post by SketchySeaBeast »

marricks wrote: post #14

I wonder if large companies get more of a pass with outages then small ones? Bias towards authority in a way. If a service has a big enough base an outage could almost seem like a pass for everyone. “Oo couldn’t do that this morning GITHUB was down.” Whereas if my small GitLab server was down bosses could be “well why aren’t we on GitHub like everyone else, it’s up now?” When google calendar was down a bit ago I trie…

I think with a smaller product you're trying to fight for market share and retaining a client - Microsoft is so large and with so much momentum and dug so deeply into their customers that this sort of thing doesn't cause them to want to find something else. If it hurts to change, it's easy to excuse something like this.
Post reply on HN