nir Posted November 20, 2018 Share Posted November 20, 2018 The app crashes on startup, the company confirms It looks like Microsoft has released another botched update, as the company has recently confirmed that Outlook 2010 users may experience app crashes after the November 2018 rollout. The culprit is update KB4461529, which was released earlier this month for Microsoft Office users. A bug in this update is causing Outlook 2010 to crash or close right after launch, Microsoft says. Only the 64-bit installation of Microsoft Outlook 2010 is impacted, and by the looks of things, no other version of the app seems to suffer from a similar bug. The company says it’s currently investigating the issue and says users can switch to Outlook Web Access if they’re no longer able to launch Outlook 2010. And while the first workaround would obviously be the complete removal of the update, Microsoft says you shouldn’t do it. The security update For users who are trying to determine what’s causing the app crashes, Microsoft has also shared the event details recorded after the crash in the Application Event Viewer: Faulting application name: OUTLOOK.EXE, version: 14.0.7224.5000, time stamp: 0x5bcb80d1 Faulting module name: olmapi32.dll, version: 14.0.7224.5000, time stamp: 0x5bcb809a Exception code: 0xc0000005 Fault offset: 0x000000000001e4b9 Faulting process id: 0x3998 Faulting application start time: 0x01d47d3befb78cd8 Faulting application path: C:\Program Files\Microsoft Office\Office14\OUTLOOK.EXE Faulting module path: C:\Program Files\Microsoft Office\Office14\olmapi32.dll KB4461529 is a security update for Microsoft Outlook 2010 that was released on November 13, and according to the software giant, it resolves vulnerabilities that could allow an attacker to gain full rights on a vulnerable system. The remote code execution flaw can be exploited with a specially crafted Office file, so if you do decide to remove this security update in order to restore Outlook 2010, you should avoid opening any files coming from sources you don’t trust. There’s no ETA as to when a fix could land, but let’s just hope Microsoft won’t wait until the December Patch Tuesday cycle to ship it. Source Link to comment Share on other sites More sharing options...
The AchieVer Posted November 20, 2018 Share Posted November 20, 2018 Welcome to the mumbled jumbled world of Microsoft 😂 Link to comment Share on other sites More sharing options...
steven36 Posted November 20, 2018 Share Posted November 20, 2018 If you haven’t run update KB4461529 for Outlook 2010, don’t! Microsoft is in trouble again. In fact, I’m thinking of creating a template for my KB update articles with “Microsoft is in trouble again” at the beginning to save me a bit of time. The new problem is that a security update for Microsoft Outlook 2010, update KB4461529 to be precise, causes the program to crash on startup. Outlook 2010 crashes on startup after installing Update KB4461529 It was first reported by on the 15th November, but took Microsoft 24 hours to find out and respond to it, asking for a crash event report. A day later it got the log and immediate posted a known issue. As of the time of writing, this is where the issues stands for Microsoft: Quote STATUS: INVESTIGATING Microsoft is investigating the issue and we will update this page when further details become available. As a workaround, you could try using Outlook Web Access. Here is the bit that I don’t understand. At the bottom of the post is this: Quote Caution: We do not recommend removing security update KB4461529. Microsoft issues an update, it makes Outlook 2010 crash, Microsoft admits they have made a mess of things, but then tells everyone who is affected not to uninstall the update, which fixes the problem. Remember, this is four days after Microsoft got the news. What Is Everyone Supposed to Do Now? What is everyone, well, everyone using Windows 10/7 64-bit systems who has been affected, supposed to do in the meantime? I’m not sure what the statistics are here, but I am sure that Outlook is primarily used in a workplace environment. Are all these affected users just meant to wait till Microsoft eventually gets round to issuing a fix? Bizarrely, while the security update KB4461529, which has known issues, has not been pulled, Microsoft has pulled two other updates relating to the abdication of the Emperor and a change in the Japanese calendar. Quote Notice After you install this update, you may experience crashes in Microsoft Access or other applications. To resolve this issue, uninstall the update by following the instructions in the “More information” section. This update is no longer available. Particularly annoying since I wrote about these two updates 12 days ago. So, in other words, a non-security update to change the Japanese calendar is pulled but a security update, with a serious known issue is not… and nor is it fixed. Have you been affected by the KB4461529 update? Let us know in what way and what you have tried to fix the problem in the comments below. Source Link to comment Share on other sites More sharing options...
Karlston Posted November 20, 2018 Share Posted November 20, 2018 Shouldn't that read "Microsoft? Look out!" Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.