asebotrades.blogg.se - Visual studio 2018 crashes on startup

#VISUAL STUDIO 2018 CRASHES ON STARTUP INSTALL#
#VISUAL STUDIO 2018 CRASHES ON STARTUP SERIES#
#VISUAL STUDIO 2018 CRASHES ON STARTUP WINDOWS#

The whole procedure could last a few minutes or even a few hours, depending on the connection speed and/or the number of messages to be recovered. ost files related to the IMAP accounts that you identified earlier.ĭuring its startup phase, Outlook should automatically retrieve all the IMAP messages from the configured mail accounts from the mail server, reconstructing the.

Create a new BACKUP_yyyyMMdd folder within the folder containing the.

ost files (you can easily do that from the Data Files panel using the Open file location button).

Navigate through the folder containing the.

In the popup window that will appear, take note of all the IMAP accounts ( E-Mail panel) and the.

Go to Control Panel> Mail > E-Mail Account.

This is a procedure that, other than being extremely slow when dealing with multiple IMAP accounts, doesn’t seem effective in a vast majority of scenarios where this annoying problem actually occurs.įor this very reason we’re suggesting an alternative workaround, which is much simpler to put into practice than the previous one and, most importantly, has a 100% success rate (at least until now – and we had to pull it off quite a lot ):

#VISUAL STUDIO 2018 CRASHES ON STARTUP SERIES#

Outlook 2016 Event ID 1000 – Random Crashes (OUTLMIME.DLL) (SpiceWorks Community Forums, October 2018)īasically, such workaround is based on a “double change” of the root folder in the offending IMAP account’s configuration settings, with the aim of forcing Outlook to “acknowledge” the (double) change and perform a series of internal activities which, in turn, should fix the root issue.

Outlook 2013 IMAP Troubles (SlipStick Systems, April 2016).

Outlook 2013 crashes on IMAP sync (Microsoft Community forum, Bob Hyman answer, January 2016).

The most common and widespread workaround that can be found online nowadays is described in the following posts: Once we confirm that the problem concerns our scenario, we can proceed with the solution. If the error shows the OUTLMIME.DLL library, then it’s very likely that we’re dealing with the issue described in this post otherwise, it there could be other reasons (such as this one) that could cause the same kind of crash. Name of the module that generated the error: OUTLMIME.DLL, version. Name of the application that generated the error: OUTLOOK.EXE, version.

#VISUAL STUDIO 2018 CRASHES ON STARTUP WINDOWS#

The best way to do this is to take a look at the Windows Event Log ( Control Panel> Administrative Tools> Event Log), which should present the following error entry within the “Applications” panel: Needless to say, since there is a ton of other common scenarios that could cause such kind of crash, the first thing to do is to make sure that we’re actually dealing with this one. Not surprisingly, the problem tends to occur in all scenarios where there are a lot of different IMAP accounts installed on the system and/or with a large number of e-mails (and/or used space). This is a rather common issue that occurs in most pre-365 versions of MS Outlook (up to Outlook 2016 included): in all these versions the IMAP protocol has been implemented, to put it mildly, in as rather “problematic” way, which often causes synchronization issues and other nasty bugs. The problem, as you can easily guess by the post title, is that MS Outlook abruptly crashes during the startup (either immediately or after a short while), with the typical error popup message warning the user that “Microsoft Outlook has stopped working”:

#VISUAL STUDIO 2018 CRASHES ON STARTUP INSTALL#

Or, manually download and install the update from the Microsoft Download Center: Update for Microsoft Outlook 2010 (KB4461585) 64-bit Edition.In this post, we’ll address a common issue occurring with most versions of MS Outlook with one or more IMAP accounts configured locally ( IMAP is an acronym for Internet Message Access Protocol – for more info, read here). Use Microsoft Update to automatically download and install the update. This problem was fixed with the November 21, 2018, update for Outlook 2010 (KB4461585). 5000, time stamp: 0x5bcb809aįaulting application start time: 0x01d47d3befb78cd8įaulting application path: C:\Program Files\Microsoft Office\Office14\OUTLOOK.EXEįaulting module path: C:\Program Files\Microsoft Office\Office14\olmapi32.dll 5000, time stamp: 0x5bcb80d1įaulting module name: olmapi32.dll, version. In the Application Event Viewer the following event details are observed:įaulting application name: OUTLOOK.EXE, version. The issue only affects 64-bit installations of Outlook 2010. After updating Outlook 2010 to the November 2018 Public Update KB 4461529, Outlook crashes or closes suddenly on start up.