Forum Discussion

Race_Coach's avatar
Race_Coach
Copper Contributor
Jan 20, 2020

Outlook crashing on statup

Hello all,

Since the Windows Update during week of January 13, 2020 my Outlook 2019 will not start up. It will not start in Safe Mode, either. I have done a complete removal and re installation of Office 2019. I have gone through all the Microsoft repair options I can find online. I have set up a new Profile that connects fine during the creation, and deleted the old profile. And I have updated all drivers and the bios (Dell XPS13, 9350).

Still when Outlook starts up, it gets to Loading Profile and then I get "Microsoft Outlook has stopped working" >Close program<

 

Does anyone have any more suggestions?  I'm really trying to avoid a completed wipe of the computer. Similar post on Dell Community site.

 

5 Replies

Sort By
  • Edson Rodriguez's avatar
    Edson Rodriguez
    Copper Contributor
    Feb 07, 2020

    Race_Coach 

     

    Possible fix (we're testing this now)

    https://support.microsoft.com/en-us/help/4494452/kb4494452-intel-microcode-updates

    • aletagroenig's avatar
      aletagroenig
      Copper Contributor
      Feb 25, 2020

      Edson Rodriguez 

      How has testing gone? I can't figure out which patch to install - I do not have access to a support team, it's just me, and I am out of my depth at this point.

      Have the Intel Pentium2127U, 64 bit system, but no idea how to drill down to which one of these I need beyond that. 

      Thanks

      • Edson Rodriguez's avatar
        Edson Rodriguez
        Copper Contributor
        Feb 25, 2020
        There's a new office update, this seems to have fixed our (reported) issue for the time being.
  • Edson Rodriguez's avatar
    Edson Rodriguez
    Copper Contributor
    Feb 07, 2020

    Race_Coach 

     

    There's another forum with this same problem (I believe).  

     

    https://www.dell.com/community/XPS/Outlook-2019-crashing-since-January-2020-Windows-Update/m-p/7463680/highlight/false#M47838

     

    "Noticing this issue on Windows 10 machines running 1803 or lower.  Upgrading to latest build seems to fix it--but as you probably know, the upgrade path isn't as easy as most would think."

Resources