none
Outlook 2010 fault in uiautomationcore.dll after upgrade to Win 10 1703 (15063.13)

    Question

  • I had no problems with Outlook 2010 in Windows 10 version 1511 or 1607. But since upgrading last week to Creators Update 1703 (15063.13, via the Upgrade Assistant) Outlook has been frequently crashing with an application error:

    Log Name:      Application
    Source:        Application Error
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Description:
    Faulting application name: OUTLOOK.EXE, version: 14.0.7172.5000, time stamp: 0x5785a873
    Faulting module name: uiautomationcore.dll_unloaded, version: 7.2.15063.0, time stamp: 0x9df0d385
    Exception code: 0xe0435555
    Fault offset: 0x00001704
    Faulting process id: 0x20d0
    Faulting application start time: 0x01d2b2689b0ef62d
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office14\OUTLOOK.EXE
    Faulting module path: uiautomationcore.dll
    Report Id: 322c9d1d-1a0d-4853-a38a-7ab5f8e80164
    Faulting package full name: 
    Faulting package-relative application ID: 
    

    I mainly have it open with an Exchange profile connecting to an Exchange 2010 server. It doesn't crash immediately -- only after perhaps 20 to 40 minutes of inactivity. FWIW, when I left it open with a profile that has only a PST file loaded it did not crash for over an hour.

    I wondered why Outlook was involved with uiautomationcore.dll, but Process Explorer shows Outlook having a thread running for uiautomationcore.dll!UiaDisconnectProvider...

    I've disabled all non-essential Add-Ins, but the problem continues. It's not fatal, but it's a problem.

    Any thoughts?

    Thanks,

    JW

    Tuesday, April 11, 2017 3:41 AM

All replies

  • Hi,

    What action did you do before the crashes issue occurred? Such as opening a specific email, sending a email or moving a email? Please share more information about this.

    The crash issue with uiautomationcore.dll is generally occurred when there are meeting request or cancellation items in your Inbox. Please try the following these steps.

    1. Start Outlook.
    2. If there are any meeting request items in your inbox, act on them by accepting the meeting, declining the meeting, or proposing a new time.
    3. If there are any meeting cancellations in your inbox, act on them by clicking the Remove from calendar option.
    4. Going forward, work in Outlook as normal. However, immediately act on any new meeting requests or cancellations that arrive in your Inbox.

      Note If Outlook continues to crash after completing these steps, check your other folders for meeting requests and cancellations and act on them accordingly.

    Regards,

    Winnie Liang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, April 12, 2017 6:11 AM
    Moderator
  • Thanks for your reply, Winnie.

    But I've seen the help article (3174003) about crashes due to meeting requests, and it doesn't apply here. I rarely receive meeting requests, and certainly have none pending.

    As I mentioned, the only change I made was upgrading Windows 10 from 1607 to 1703. I never had this problem before upgrading, but since upgrading Outlook crashes multiple times per hour.

    It seems likely that the problem is due to the new version (7.2.15063.0) of uiautomationcore.dll installed with Win10 1703. But only Microsoft can know whether the fix is needed there or in Outlook 2010...

    Regards,

    JW

    Wednesday, April 12, 2017 8:37 AM
  • Just checking in to see if there has been any resolution to this problem.  
    Wednesday, April 19, 2017 5:52 PM
  • Hi,

    Recently, some client users encounter the Office Crashes issue after upgrading Windows 10 to 1703. For example:

    https://social.technet.microsoft.com/Forums/en-US/80a87d39-c370-45f2-81d1-7d7d0375bdfb/office-2016-on-windows-10-build-1703-freezes-when-trying-navigate-local-folders?forum=Office2016setupdeploy

    But there is no specific documents state whether the new Windows update 1703 is the root cause about the Office crashing issue because it is the latest version update just released several days ago. I would like to collect more information about it:

    How many users encounter this Outlook crash issue, only one user or all users who have upgraded Windows 10 to 1703.

    For Outlook 2010, please go to Control Panel > Programs and Features, select Office 2010, click Change > Repair to have a try.


    Regards,

    Winnie Liang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, April 20, 2017 6:09 AM
    Moderator
  • I continue to have Outlook crash (when it is in the background) in uiautomationcore.dll:

    Faulting application name: OUTLOOK.EXE, version: 14.0.7180.5001, time stamp: 0x58dcb9e8
    Faulting module name: uiautomationcore.dll_unloaded, version: 7.2.15063.0, time stamp: 0x9df0d385

    but also sometimes in other Windows 10 modules that look to be related to credentials:
    Faulting application name: OUTLOOK.EXE, version: 14.0.7180.5001, time stamp: 0x58dcb9e8
    Faulting module name: certCredProvider.dll_unloaded, version: 10.0.15063.0, time stamp: 0x28e97767
    
    and 
    
    Faulting application name: OUTLOOK.EXE, version: 14.0.7180.5001, time stamp: 0x58dcb9e8
    Faulting module name: ngccredprov.dll_unloaded, version: 10.0.15063.0, time stamp: 0x3b6f2a4d
    I will try repairing Office.

    Thursday, April 20, 2017 6:50 AM
  • I repaired Office 2010 and restarted Windows, but the Outlook crash happened again, this time in a different Windows 10 credential module:

    Faulting application name: OUTLOOK.EXE, version: 14.0.7180.5001, time stamp: 0x58dcb9e8
    Faulting module name: BioCredProv.dll_unloaded, version: 10.0.15063.0, time stamp: 0x576866fe

    Note that I enter my Exchange password each time I start Outlook, but I don't use any biometric or other unusual credential system...

    Thursday, April 20, 2017 8:29 AM
  • I have also tried a repair of Office 2010 and still have random crashes.  This is affecting several machines in my environment that have taken the 1703 update.

    Faulting application name: OUTLOOK.EXE, version: 14.0.7180.5001, time stamp: 0x58dcb9a8
    Faulting module name: uiautomationcore.dll_unloaded, version: 7.2.15063.0, time stamp: 0x62299436
    Exception code: 0xe0435555
    Fault offset: 0x0000000000103e28
    Faulting process id: 0x27b8
    Faulting application start time: 0x01d2b9cd102c44c1
    Faulting application path: C:\Program Files\Microsoft Office\Office14\OUTLOOK.EXE
    Faulting module path: uiautomationcore.dll
    Report Id: e3e71c2d-c4c1-434f-9eda-b3fd9d1cdc43
    Faulting package full name: 
    Faulting package-relative application ID: 

    Thursday, April 20, 2017 12:55 PM
  • Hi,

    Thanks for all your feedback, Bryan and JWit. It is highly recommended to perform a Windows clean boot for Windows 10 to narrow down if the problem is related to any software conflicts with new Windows update: https://support.microsoft.com/en-us/kb/929135 

    Also disable protection for Office apps. There are some articles mentioned that in Windows 10 Creators Update with Malwarebytes 3.0 installed, Office may crashes when saving files. Not sure if it is related to Malwarebytes, it is better to disable it if you have installed on Windows.


    Regards,

    Winnie Liang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, April 21, 2017 2:16 AM
    Moderator
  • I would like to report that I have tested the Clean Boot and still have Outlook crashes.  We also do not run Malwarebytes in our environment.  This is affecting every machine (65+ Computers) that have taken the 1703 update.  These machines are fully patched and running Outlook 2010 connecting to Office 365.  The crashes happen very randomly throughout the day but many have reported when they get back to their desk and unlock the computer they have a message stating Outlook has stopped responding and then I can check the Event Viewer and get the event error as noted above.

    I would also like to mention that I have 20+ Computers running Windows 10 Enterprise LTSB that do not get the Windows Feature Updates and are running Outlook 2010 and have no issues. 

    Friday, April 21, 2017 1:51 PM
  • Change permissions on both uiautomationcore.dll in system32 and syswow64 in order to rename them (something like uiautomationcore-old.dll.  Then replace them with  the older version of the same file from the windows old directory from before the upgrade to 1703.  Reboot - problem solved. 
    • Proposed as answer by daddylonglegs71 Tuesday, April 25, 2017 2:28 PM
    • Unproposed as answer by JWit Tuesday, April 25, 2017 11:55 PM
    • Proposed as answer by Roy van den Berg Wednesday, June 21, 2017 2:50 PM
    Sunday, April 23, 2017 4:47 AM
  • Hi,

    Have you tried Bartucca's suggestion?

    We are still pending research on the issue. If there is any news in your side, please feel free to post back for more discussion.


    Regards,

    Winnie Liang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, April 25, 2017 2:13 AM
    Moderator
  • I too have been bashing my keyboard for a couple of days. I too had no pending calendar requests and had removed all add-ons. I then tested this out with a diffrent outlook account on a diffrent PC and was not seeing the issue so I did another clean install and still had problems. One thing I should mention is my crashes were mostly the UIautomationcore.dll but I was seeing other dll's unloading too. The other PC I tested had an outlook/exchange account whose .ost was only 256 KB mine is 2 Gigs. So there is some relation to a beefier account.

    I went about renaming and replacing my dll's in those 2 folders and seems to be better. I have had outlook loaded for 2 hours now with now crashing. Thank you for this! 


    Tuesday, April 25, 2017 2:26 PM
  • I can confirm that replacing the UIAutomationcore.dll in the System32 and SysWOW64 folders with the old version from 11/2016 does keep Outlook from crashing.  I however do not think this is a great resolution when you have over 70 Computers affected by this problem.  I have of course wrote a script to do this but it is still very time consuming.

    Tuesday, April 25, 2017 2:47 PM
  • The issue can't be related to OST size, at least not directly, as I'm having the issue but I'm not using cached mode.
    Tuesday, April 25, 2017 11:55 PM
  • Bartucca's suggestion is a useful workaround, but it's not the answer to this issue, especially for larger deployments. The answer is for Microsoft to release an update or provide a configuration change that fixes this issue.
    Tuesday, April 25, 2017 11:59 PM
  • Hi,

    Currently, please roll back 1703 to a earlier version (1511 or 1607) for Windows 10 as a workaround for all affected Outlook 2010 users.


    Regards,

    Winnie Liang


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, April 26, 2017 2:52 AM
    Moderator
  • FWIW I just installed KB4016240 to update to build 15063.250, but this did not update (or revert) UIAutomationcore.dll.
    Saturday, April 29, 2017 9:30 PM
  • I have tried repairs, uninstall and reload, and uninstall then use clean office 2010 tool and then reload office.  None if it works problem comes back.  This issue started with creator's update version 1703 was installed on my system.  I did not have any problems before this version was installed.
    Thursday, May 4, 2017 2:25 PM
  •  I am encountering the same thing.  Hopefully a solution is found soon.  In the meantime, I will try to copy the uiautomationcore.dll from the windows.old directory and see if that fixes the issue.
    Friday, May 12, 2017 5:01 PM
  • Perhaps I have the same issue in my own software product (C++, MFC 12, VS2013, using wininet, client certificates and TAPI). My customers said, that the app began crashing after installation of win10 1703, the event log shows the above symptoms. The crashes occur unexpected and independent from work in the app. Before 1703 the app ran years without any errors.

    Now, my customers have rolled back to 1607 and the problem is gone.

    I installed 1703 version 15063.296 (current version) on my developer pc and tried  to reproduce the problem while debugging the app. The error occurs sometimes, when the app was minimized in the background for several minutes and MS Edge is started. Now, in version 15063.296, the crash occurs in the "CoreUIComponents.dll" (it references a NULL-Pointer), but there is no call stack (and no symbols: "SYMSRV:  http://msdl.microsoft.com/download/symbols/CoreUIComponents.pdb/920E1CB9A125FAF86DF345F598F506391/CoreUIComponents.pdb not found"), so I have no hint - and not any idea - why the error occurs. Is there any way to get the "CoreUIComponents.pdb" from MS?


    • Edited by ssp297 Monday, May 15, 2017 6:33 PM
    Monday, May 15, 2017 6:24 PM
  • Winnie,

    I did what you stated on 5-4-17 and it fixed the issue. (used .dll file from 1607 iso) Nothing else stated in this thread and other searches fixed it.  Now I was pushed by Microsoft another Cumulative Update KB4020102 (on 5-30-17) and it has replaced my UIAutomationCore.dll.  Now the problem is back.  There is no way I can even begin to think about pushing out Windows 10 to my company until this is fixed.  We have standardized on Office 2010.  Now I have to go back and replace UIAutomationCore.dll again from the 1607 ISO.

    Is Microsoft trying to fix this issue?

    Tuesday, May 30, 2017 2:20 PM
  • Hi,

    I think I could reproduce the issue with a minimal self written program, which I described here:

    https://social.technet.microsoft.com/Forums/en-US/c0cee7cb-c70f-4a3c-851b-9006b4ae41ee/fault-in-uiautomationcoredll-after-upgrade-to-win-10-1703-1506313-in-coreuicomponentsdll-in?forum=outlook

    Apparently Win10 1703 does a premature unload of the uiautomationcore.dll after it is loaded implicitly by a program using the MS crypto / certificate - functionality.

    An effective workaround is loading the uiautomationcore.dll by the program to prevent the premature unloading, but the problem should be fixed in Windows.

    Thursday, June 1, 2017 10:29 AM
  • So Just to make sure... there is no solution right now... by that I mean a patch for Outlook 2010 or Windows 10 1701?  The only solution is to replace the uiautomationcore.dll   If we replace it what does that break if anything?
    Thursday, June 8, 2017 10:45 PM
  • Interesting result! But since reverting uiautomationcore.dll to the 14393 version resolves the problem, it seems that the issue must be internal to the DLL. I'm not a dev -- can the DLL be unloading itself prematurely?
    Friday, June 9, 2017 6:36 AM
  • Reverting to the 14393 version of the DLL hasn't broken anything for me.

    And I've also seen the same result as as AU89Barron: installing KB4020102 installs a new version of uiautomationcore.dll with version 7.2.15063.332, which still has the problem. So Microsoft has changed something in the DLL but have not fixed this issue.

    Friday, June 9, 2017 6:40 AM
  • I've had nothing break.  The only problem is when patch Tuesday comes along and Microsoft replaces the DLL again and has not fixed this issue.

    It's like playing Russian roulette with Microsoft.  You don't know in the cumulative updates if they have "updated" uiautomationcore.dll.  The only way to find out is check the dll version after patching or wait for Outlook 2010 to start crashing every 20 - 30 minutes.

    Monday, June 12, 2017 1:30 PM
  • (Good news, todays update to Win10 1703 15063.413 has fixed the issue for me.)

    Update: Checked it again today and the problem is back... the update to 15063.413 does not solve the problem (sorry).
    • Edited by ssp297 Thursday, June 15, 2017 10:18 AM new test
    Wednesday, June 14, 2017 2:52 PM
  • Folks, I've been having the same issue and have discussed it a bit in the Community area: https://answers.microsoft.com/thread/5812f96f-7248-426e-8c27-e318cf03aea0

    As you can see, my theory is that the crashes are not random, but linked to certain UI actions related to Windows 10's new look.  Clicking the clock crashes it.  Clicking Edge on the Taskbar crashes it.  Clicking the Start button crashes it.  And even a pop up from Notification crashes it.  Notably, clicking older apps on the Taskbar don't crash it (but the new Calculator does).

    I'm not a tech guy, but maybe these observations will give you an idea.

    I am looking forward to checking out this 15063.413 update.  Fingers crossed!

    Wednesday, June 14, 2017 7:04 PM
  • Unfortunately, not for everyone. I am still experience multiple crashes. Actually it's ngccredprov.dll_unloaded error, though. But quite similar.

    Also, I'd say that the comment by Admiral Huje above is very agreeable. My case this morning was very likely associated to the actions on Windows Setting UI. It has "Windows 10's new look".

    Thursday, June 15, 2017 2:00 AM
  • I just updated to 15063.413 and it had no impact on the issue. The reverted (14363) version of UIAutomationCore.dll is unchanged.
    Thursday, June 15, 2017 8:27 AM
  • Yeah, I still get the same error too, even after that update.

    I would add that the problem, which I too-well know how to trigger (certain "new Windows" UI functions), does not happen immediately after starting Outlook 2010.  It does not crash soon after opening, and it does not crash soon after re-opening after a crash.  It takes a while to build up.  Perhaps analogous to a memory leak?

    Or, I suppose, there's a function of Outlook 2010 that I am not activating right away which once eventually used sets the trigger for a crash.  (E.g., writing an email, checking a calendar.)  I haven't noticed a correlation yet, so I am going with my first theory for now.

    I hope my lay observations help.  Thanks.

    Here's my new Event Viewer report:

    Faulting application name: OUTLOOK.EXE, version: 14.0.7182.5000, time stamp: 0x59357f0b
    Faulting module name: uiautomationcore.dll_unloaded, version: 7.2.15063.332, time stamp: 0x62299436
    Exception code: 0xe0435555
    Fault offset: 0x0000000000103e28
    Faulting process id: 0x3fe0
    Faulting application start time: 0x01d2e6372e465fa9
    Faulting application path: C:\Program Files\Microsoft Office\Office14\OUTLOOK.EXE
    Faulting module path: uiautomationcore.dll
    Report Id: 6a75083a-1299-42b9-a1fd-fb1f02e8f008
    Faulting package full name:
    Faulting package-relative application ID:


    Here's my May 16, 2017 Event Viewer report.  Check out how the .dll's version changed but the time stamp didn't:

    Faulting application name: OUTLOOK.EXE, version: 14.0.7181.5000, time stamp: 0x58ee72bb
    Faulting module name: uiautomationcore.dll_unloaded, version: 7.2.15063.0, time stamp: 0x62299436
    Exception code: 0xe0435555
    Fault offset: 0x0000000000103e28
    Faulting process id: 0x93c
    Faulting application start time: 0x01d2ce87cb0acf40
    Faulting application path: C:\Program Files\Microsoft Office\Office14\OUTLOOK.EXE
    Faulting module path: uiautomationcore.dll
    Report Id: bdd75a08-a710-4b90-ab0e-8e0e9aec1580
    Faulting package full name:
    Faulting package-relative application ID:
    Friday, June 16, 2017 1:46 AM
  • Bartucca's suggestion is a useful workaround, but it's not the answer to this issue, especially for larger deployments. The answer is for Microsoft to release an update or provide a configuration change that fixes this issue.

    Ofcourse Bartucca's answere is not a solution, but at least it's something to get back to work normally. Microsoft didn't even come up with this work-around, so for as long as Microsoft doesn't fix this, Bartucca's answere is the best answere out there.

    For the statistics: Yes, I also have this problem with Outlook 2010, connecting to Exchange Server 2010, started happening after I upgraded to Windows 10 1703.

    Wednesday, June 21, 2017 2:53 PM
  • I had also been using Bartucca's solution in my office.  Every single PC upgraded to 1703 has had problems with Outlook 2010 randomly crashing since the upgrade.

    If I revert to an earlier version of uiautomationcore.dll, my Outlook 2010 will work properly, but any PC that has SQL Management Studio install on it will no longer be able to run that program...

    Would be nice if Microsoft addressed this problem!

    Thursday, June 22, 2017 7:11 PM
  • Same issue here, very difficult to find the root cause and very annoying problem. I got crashes when I receive some notifications in the taskbar, sometimes when I modify the volume level, systematically when I lock the screen.

    I understand after 3 months no solution yet, right?

    Friday, July 7, 2017 8:02 AM
  • Well,

    It's 7-11-17 just received patches from Microsoft.  The problem is back.  I had manually replaced my uiautomationcoredll per the instructions above.  The patches installed today "upgraded" the dll to version 10.0.1563.447 and the issue is back outlook crashing.  Windows 10 will not be going on my companies pcs until this issue is fixed.

    Tuesday, July 11, 2017 7:28 PM
  • Yes, same here after installing this month's KB4020102 - Outlook started randomly crashing again. I've reverted to the 14363 version of UIAutomationCore.dll.

    Any hope for a fix for this?

    Saturday, July 15, 2017 3:48 AM
  • Hi,

    Hope this can help.

    I face same issue in my outlook 2010 after windows 10 latest windows update my outlook keep on crashing. Same error message you got. I check the system events i find there is application office software protection platform running. So i go to services and disabled it and stop the services then i run the outlook after that  outlook is working for me now. 


    

    • Proposed as answer by Doix Saturday, July 15, 2017 8:25 AM
    Saturday, July 15, 2017 8:25 AM
  • Change permissions on both uiautomationcore.dll in system32 and syswow64 in order to rename them (something like uiautomationcore-old.dll.  Then replace them with  the older version of the same file from the windows old directory from before the upgrade to 1703.  Reboot - problem solved. 

    This worked great for us until the latest round of forced updates (early Jul2017) overwrote the uiautomationcore.dlls.  Further, it deleted the Windows-old directory so we no longer have the older versions of uiautomationcore.dll that work. Any thoughts on finding these two files elsewhere?

    EDIT: Ok, found the older .dlls in a backup on another machine.

    BEWARE THAT SUBSEQUENT WINDOWS UPDATES MAY DELETE THE "Windows.Old" DIRECTORY, SO BE SURE TO GRAB THESE FILES AND SAVE THEM ELSEWHERE FOR THE NEXT UPDATE!

    • Edited by stm-usa Tuesday, July 18, 2017 9:46 PM
    Tuesday, July 18, 2017 7:24 PM
  • Well,

    It's 7-11-17 just received patches from Microsoft.  The problem is back.  I had manually replaced my uiautomationcoredll per the instructions above.  The patches installed today "upgraded" the dll to version 10.0.1563.447 and the issue is back outlook crashing.  Windows 10 will not be going on my companies pcs until this issue is fixed.

    I replaced the UIAutomationCore.dll at Syswow64 folder and it works like charm now! 

    I  used UIAutomationCore.dll from an other PC in my companys Windows domain. If you need it I can provide it. 

    • Proposed as answer by MikeSum Monday, July 31, 2017 9:37 AM
    Monday, July 31, 2017 9:37 AM
  • That would be awsome, please @MikeSum host those somewhere!
    Monday, July 31, 2017 11:52 AM
  • If you have a touch screen device, don't update uiautomationcore.dll in System32. It is required to use the touch screen and will fail if it is back level. I found this out the hard way trying to sign in after making the change! Good thing I had a paired BT KB. If you are using Outlook 32 bit only the SYSWOW64 version needs to be updated.

    I have now done this fix on 6 desktops and laptops. They all failed before and now work OK. I haven't yet tried this on the Fall update but will need to begin testing soon.


    • Edited by PhilVancWA Tuesday, August 1, 2017 2:26 AM Typos
    Tuesday, August 1, 2017 1:17 AM
  • Hi,

    Hope this can help.

    I face same issue in my outlook 2010 after windows 10 latest windows update my outlook keep on crashing. Same error message you got. I check the system events i find there is application office software protection platform running. So i go to services and disabled it and stop the services then i run the outlook after that  outlook is working for me now. 


    

    I tested this solution extensively. It is only a very short term fix. The service gets restarted for multiple actions and Outlook again fails.
    Tuesday, August 1, 2017 1:25 AM
  • Can anyone please share the correct file to replace?

    Thanx in Advance

    Tuesday, August 1, 2017 9:50 AM
  • Look for an old version of uiautomationcore.dll.
    Boot OS with command prompt only.
    Rename windows\system32\uiautomationcore.dll to uiautomationcore.dll.0.
    Copy the old version of uiautomationcore.dll to windows\system32.
    Restart the OS.
    Monday, August 7, 2017 8:29 AM
  • I repaired Office 2010 and restarted Windows, but the Outlook crash happened again, this time in a different Windows 10 credential module:

    Faulting application name: OUTLOOK.EXE, version: 14.0.7180.5001, time stamp: 0x58dcb9e8
    Faulting module name: BioCredProv.dll_unloaded, version: 10.0.15063.0, time stamp: 0x576866fe

    Note that I enter my Exchange password each time I start Outlook, but I don't use any biometric or other unusual credential system...

    I get the BioCredProv.dll issue regularly since the Creators Update. But there's no pattern - no errors for a few days, and then I'll have a dozen in a single day. I also get faults with ngccredprov.dll
    Friday, August 18, 2017 1:54 PM
  • I have the same issue with Outlook 2007. Reverting the DLLs worked for me. But the latest Windows 10 Cumulative update (KB4034674) includes the uiautomationcore.dll, and the problems reappeared as soon as that Update installed.

    So, still a problem with the latest Windows 10 Creator version of this DLL.

    Faulting application name: OUTLOOK.EXE, version: 12.0.6774.5000, time stamp: 0x5970d241
    Faulting module name: uiautomationcore.dll_unloaded, version: 7.2.15063.447, time stamp: 0xbc5ca1eb
    Exception code: 0xe0435555
    Fault offset: 0x00001704
    Faulting process id: 0x286c
    Faulting application start time: 0x01d31c184d2c194a
    Faulting application path: C:\Program Files (x86)\Microsoft Office\Office12\OUTLOOK.EXE
    Faulting module path: uiautomationcore.dll
    Report Id: 03a71ca8-1412-4483-b4b5-ccfe93ba7d10
    Faulting package full name:
    Faulting package-relative application ID:

    Wednesday, August 23, 2017 6:45 PM
  • Having the same issue as everyone else here on my 70+ Windows 10 workstations..  This issue was originally reported in April, has anyone gotten a response from Microsoft that they acknowledge this is a problem and if they are actively working to fix it?

    Thursday, August 24, 2017 4:02 PM
  • Is there any way to get this issue brought to Microsoft's attention before their October update?
    Tuesday, September 12, 2017 12:07 AM
  • Having the same issue too. Five test computers all running clean wipe and load Windows 10 v1703. Outlook is crashing with different .dll module failures each time. Really wish Microsoft would address this.  
    • Edited by hansoac58 Wednesday, September 20, 2017 7:28 PM
    Wednesday, September 20, 2017 7:28 PM
  • Same here, although not on all PCs. 

    It's rather annoying, especially seeing Microsoft is not interested in solving it. I am now used to save e-mails while writing them as a crash may force me to rewrite pages. Maybe the answer is newer Office versions are not affected?

    Tuesday, October 3, 2017 9:19 AM
  • This was reported in April. We are now in October. Multiple cumulative patches have come and gone over several months.

    We have clear, reproducible steps from multiple people on this thread showing the problem is directly caused by a DLL update, and that reverting back to an older version of the DLLs resolves the crashes.

    When will we see a corrected set of DLLs provided in a Cumulative patch?

    Tuesday, October 10, 2017 9:32 PM
  • I also experience the same issue with Outlook 2010 crashing/restarting - under Win10 Creators update. The

    issue is the same as reported here (uiautomationcore.dll). Yesterday I tried the remedy proposed by Bartucca, to use an old version of the dll. It worked, no Outlook crashes!

    But since then I discovered that Skype for Business (Lync) will not work with the old dll version, it simply refuse to even start.

    So I had to revert to the original dll to be able to - somehow - get both Outlook and Skype to work.

    I am also waiting eagerly for a fix from Microsoft...

    Thursday, October 12, 2017 5:21 AM
  • I can confirm that we also have this issue, running Outlook 2010

    Enfo Zipper
    Christoffer Andersson – Principal Advisor
    http://blogs.chrisse.se - Directory Services Blog

    Thursday, October 12, 2017 8:13 AM
  • The same problem here, Outlook 2010 + Windows 10 (15063.674).

    I noticed that I can continue use Outlook with no crash if I don't use Edge. 

    Not a fix but a workaround

    Friday, October 13, 2017 8:05 AM
  • Does your Outlook crash when you click on Windows Start icon? When you say, "don't use Edge" does that mean you unpin it from your taskbar? 

    Thanks

    Friday, October 13, 2017 1:48 PM
  • Federico, I suspect that if you do other things involving the "new" look elements of the Windows 10 interface, you can get Outlook to crash as well.  Try right-clicking on the taskbar, double-clicking on the clock, clicking on the Start button, opening the notifications pane, etc.

    (That is, if you want to crash Outlook.)

    Friday, October 13, 2017 8:47 PM
  • The same problem here, Outlook 2010 + Windows 10 (15063.674).

    I noticed that I can continue use Outlook with no crash if I don't use Edge. 

    Not a fix but a workaround

    I never use Edge as well, what do you mean by don't use? Have you uninstalled it? I would do it with pleasure.
    Monday, October 16, 2017 8:18 AM
  •  

    I worked a full day with no crash using visual studio, Hyper-v client, MSTSC and so on with no crash. As suggested by Admiral Huje I finally crashed outlook just starting weather app. No problem using task bar, menu, notification or double clicking the clock/calendar.

    My suggestion was to not run Edge browser, not necessary dis-install it. Unfortunately also other new W10 applications are starting modules that are crashing outlook.

    Monday, October 16, 2017 3:18 PM
  • I've managed to open a case with MS support on this issue. 2 questions:

    1. Is anyone experiencing this without Exchange cached mode?

    2. Is your Exchange hosted at MS - Office 365 hosted Exchange?

    Phil

    Tuesday, October 17, 2017 2:16 AM
  • I have this problem using Cached Exchange mode. The Exchange is NOT hosted at MS - Office 365 Exchange.
    Tuesday, October 17, 2017 6:09 AM
  • Based on your choice of wording "...without Exchange cached mode", I started a test with Cached mode unchecked in my Outlook client. So far no crashes...
    Tuesday, October 17, 2017 1:28 PM
  • Thanks for your responses. I had tested overnight without Exchange and had no failures. I usually can't go more than an hour without a crash using Exchange. Like you I'm running without a cache right now too. Seems to me that this is related to cached Exchange. Will you share what version of Exchange you're using? That's the next question I'm going to be asked...

    I'd really like to include you on the dialogue with MS about this issue. Will you send me an email at i s e n s e e p {at} outlook {dot} com?

    Tuesday, October 17, 2017 4:23 PM
  • Mostly on a whim, with the release yesterday of Win 10 1709-16295.19, I installed it on one computer and have been successfully using Outlook 2010 for several hours. I need to leave Outlook running overnight before I declare tentative success but I wanted to inform those who are following this thread that there might be hope!

    I'll post a more detailed update in a day or two including some comments about my experience with MS about this issue.

    Phil

    Thursday, October 19, 2017 2:21 AM
  • Outlook 2010 without cached Exchange mode ran fine for a while. Then it crashed too, just as when running it in cached mode. So at least for me, this wasn't a solution.
    Thursday, October 19, 2017 5:07 PM
  • As I noted, I installed Windows 10 1709-16299.19 - the 1st release version of the Fall Creators Update. I have now had over 36 hours of solid Outlook 2010. No crashes (verified by no Windows 1000 events). I believe that the issue is fixed in 1709. I had carefully tracked the announced changes all through the Insider’s Preview of 1709 and never found anything that seemed to affect this, but something certainly changed!

    I have also tried back porting uiautomationcore.dll from build 16299.15 to a 1703 machine and it also cures the crash issue.

    I had fine support from MS once I was able to find a kind soul to open a case for me. It was the support rep who casually mentioned trying 1709. It was a great suggestion before I went off to test with Office 2013 which was their next suggestion, noting that Outlook 2010 is in Extended Support and it was likely no fix would be developed to support it. (I guess like the rest of my life, I'm living on borrowed time with Office 2010.) Since it was resolved by a Windows update, they are not even charging for the case!

    I know many of you experiencing this problem won't be able to move to 1709 right away. I still have quite a bit of work to do before I move other machines and clients - mostly getting the changes in scripts to fix the new options how I want them. On the other hand, you can extract uiautomationcore.dll from the current (1709) Media Creation and use it. No more having to keep an old 1607 version around. Note that since I'm using 32 bit Office, I have only done replacing in the SYSWOW64 folder. See my earlier post about issues with replacing it in System32. I haven't tested replacing the System32 version with the 1709 version because I have no need to. If you are using 64 bit Office then you'll need to test that. .

    Happy Computing!

    Phil


    P.S. Thanks to oldmantoo who helped verify that this was not an MS hosted Exchange issue nor related to whether or not the mailbox was cached.
    • Proposed as answer by PhilVancWA Friday, October 20, 2017 6:03 PM
    • Edited by PhilVancWA Friday, October 20, 2017 6:05 PM Add thanks.
    Friday, October 20, 2017 6:01 PM
  • I wasn't going to say anything yet lest I jinx it, but it seems fixed for me too with that Fall update.

    Friday, October 20, 2017 6:15 PM
  • Thanks Phil,

    for taking this issue to a happy ending (as it seems :-).

    In the meanwhile, I made two changes: moved to version 1709, and also moved to Office 2013 64-bit. I experience none of the previous crashes, now I am only struggling with becoming friends with Office 2013...not sure that can be managed simple by changing a dll.

    Regards, Carl

    Sunday, October 22, 2017 9:08 AM
  • Phil,

    So many thanks. Yes, I updated to Fall Creator update 1703 last week, and have seen no crashes since then.

    Again, SO many thanks to you.

    Monday, October 23, 2017 10:51 PM