- Jun 19, 2017 Outlook 2016 Crashes IMMEDIATELY after MacOS High Sierra upgrade Hi, Ever since I upgraded to MacOS High Sierra, Outlook 2016 crashes immediately when I open it up.
- Office 2016 for Mac is fully supported on macOS 10.13 High Sierra. If you encounter issues using Office 2016 for Mac, please send us feedback so we can address them. In Word, Excel, PowerPoint and OneNote, you can click on the Send a Smile icon in the top-right of the app. For Outlook, choose Contact Support from the Help menu. 15.34 and earlier.
Note
Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. For more information about this change, read this blog post.
Summary
Microsoft Office 2016 - High Sierra (Macbook) - Duration: 2:51. Saura Tech 25,635 views. Mar 12, 2018 Besides, I noticed that High Sierra 10.13.1 is not the latest version of Mac OS, how about upgrading to the new version of Mac OS to check the result? I tried to test in my Outlook fro Mac 10) on High Sierra 10.13.3, but didn't see the issue.
Existing Office 2016 for Mac customers will be seamlessly upgraded to 64-bit versions of Word, Excel, PowerPoint, Outlook, and OneNote as part of the August product release (version 15.25). This affects customers of all license types: Retail, Office 365 Consumer, Office 365 Commercial, and Volume License installations.
Deployment options for the 64-bit update
AutoUpdate (MAU)
Customers who use Microsoft AutoUpdate (MAU) to keep their Office applications up-to-date will see a 'regular' monthly update notification when their selected channel is upgraded to 64-bit builds. Depending on which version is installed on the local computer, MAU will offer either a delta or full update. The update package size does not change between 32-bit and 64-bit versions. Also, MAU can deliver a delta update when applicable to update a user from 32-bit to 64-bit applications. Therefore, customers won't experience a sharp increase in download activity. For the release to the Production channel, customers will see '(64-bit)' in the update title to make them aware that this is a 64-bit update.
For information about how to use the MAU, see Check for Office for Mac updates automatically.
Manual updates
The August release of Office for Mac is available for manual download. The following file provides a 64-bit package to replace existing 32-bit applications with 64-bit variants during installation:
Download the Microsoft Office 2016 for Mac August update package now.
Virus-scan claim
Microsoft scanned this file for viruses, using the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to it.
Volume License Service Center
Volume License customers typically get their Office 2016 software from the Volume License Service Center (VLSC). These builds are refreshed infrequently and are typically aligned with new language editions. The VLSC will continue to offer 32-bit installers (15.23) until November 2016. However, all updater packages that are released after August will be based on 64-bit builds. Therefore, a VLSC customer who updates either manually or through AutoUpdate will be transitioned to 64-bit builds.
More Information
64-bit only
The Mac operating system has been 64-bit for several years. Unlike for Windows, there's no choice between running a 32-bit or 64-bit version of the Mac operating system. Similarly, we won't offer a choice between 32-bit and 64-bit versions of Office 2016 for Mac. After each 'channel' is transitioned per the rollout schedule, only 64-bit builds will be available.
Effect on third-party applications and add-ins
The transition to 64-bit Office for Mac was announced in April 2016. IT Pros will want to understand which compiled add-ins are deployed to the users whom they manage so that they can assess the effect of the upgrade. The following Microsoft Office website summarizes the issues that affect the more common add-ins that are used together with Office 2016 for Mac:
Tools for inspecting product architecture
To verify the architecture of an Office application (that is, to understand whether you have a 32-bit or 64-bit build), start the application, open the Activity Monitor, and then enable the Kind column.
You can also use the file command in a terminal session to inspect the binary. For this use, type file -N <path of binary>.This method can be used with for any binary file, including third-party add-ins.
The file command returns one of three values.
| Return value | Meaning |
|---|---|
| Mach-O 64-bit executable x86_64 | 64-bit binary |
| Mach-O executable i386 | 32-bit binary |
| Mach-O 64-bit executable x86_64 | FAT binary (compatible with both 32-bit and 64-bit processes) |
| Mach-O executable i386 | FAT binary (compatible with both 32-bit and 64-bit processes) |
Options for reverting to 32-bit installations
There may be situations in which the customer has to change code that's not 64-bit ready. If customers can't immediately move forward to 64-bit builds, we will make available a one-time 32-bit update for the 15.25 release in addition to the default 64-bit updates. The 32-bit updates will be available only for manual download from the Office CDN.
The latest 32-bit release of Office 2016 for Mac (15.25.160818) can be downloaded from https://go.microsoft.com/fwlink/?LinkId=823192.
Customers who manually install the 32-bit release won't be offered the 64-bit version of 15.25 through MAU. However, MAU will offer the 64-bit version of 15.26 in September 2016. Therefore, customers have a limited time to remain on 32-bit builds.
If a customer has already upgraded to the 64-bit update of Office for Mac 15.25 and wants to revert to the 32-bit version, follow these steps:
- Exit all open Office 2016 applications.
- Start Safari, and then browse to https://go.microsoft.com/fwlink/?LinkId=823192 to start the download of the 32-bit installer.
- Double-click the downloaded package, and then follow the instructions.
The 64-bit installation has a build date of 160817. The 32-bit version has a build date of 160818.
Hi Experts,
Outlook for Mac 2016 crash on High Sierra 10.13.3 with the crash log below:
Error Signature:
Exception: EXC_BAD_ACCESS
ExceptionEnumString: 1
Exception Code: KERN_MEMORY_ERROR (0x00000001132f7548)
Date/Time: 2018-01-25 08:38:19 +0000
Application Name: Microsoft Outlook
Application Bundle ID: com.microsoft.Outlook
Application Signature: OPIM
Application Bitness: x64
Application Version: 16.9.0.18011602
Crashed Module Name: libicucore.A.dylib
Crashed Module Version: 1.0.0.0
Crashed Module Offset: 0x0000000000002b4c
Blame Module Name: OutlookCore
Blame Module Version: 16.9.0.180116
UnsymbolicatedChecksum: D514AED1B112FEB4C54B253561E164F0
Blame Module Offset: 0x0000000000148067
StackHash: ae07566b67a9950d-dm_1_main
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Build Type: SHIP
Crashed thread Stack Pointer: 0x_00007ffeed0c0f20
Crashed thread: 0
I have completely uninstalled and reinstalled the client, but it doesn't help.
And, the crash still occurs in the Safe Mode with the crash log below:
Error Signature:
Exception: EXC_BAD_ACCESS
ExceptionEnumString: 1
Exception Code: KERN_INVALID_ADDRESS (0x0000000000008800)
Date/Time: 2018-01-25 14:45:06 +0000
Application Name: Microsoft Outlook
Application Bundle ID: com.microsoft.Outlook
Application Signature: OPIM
Application Bitness: x64
Application Version: 16.9.0.18011602
Crashed Module Name: libsystem_platform.dylib
Crashed Module Version: 1.0.0.0
Crashed Module Offset: 0x00000000000016b7
Blame Module Name: OutlookCore
Blame Module Version: 16.9.0.180116
UnsymbolicatedChecksum: 57BC8C04856C0433DB6BA7FCEE162257
Blame Module Offset: 0x0000000000148067
StackHash: 5c9c76c240255887-dm_1_main
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Build Type: SHIP
Crashed thread Stack Pointer: 0x_00007ffeec930f20
Crashed thread: 0
Thread 0 crashed:
# 1 0x00007fff7fdc36b7 in __platform_strcmp + 0x00000017 (libsystem_platform.dylib + 0x00000000000016b7) 0x0000000000000000
# 2 0x00007fff7e765055 in icu::ResourceArray::internalGetResource(ResourceData const*, int) const + 0x000000AF (libicucore.A.dylib + 0x00000000000c8055) 0x0000000000000000
# 3 0x00007fff7e69f9a5 in _res_getTableItemByKey + 0x0000008D (libicucore.A.dylib + 0x00000000000029a5) 0x00007ffeec930f70
# 4 0x00007fff7e6a18d7 in _ures_getByKey + 0x0000008A (libicucore.A.dylib + 0x00000000000048d7) 0x00007ffeec930fe0
# 5 0x00007fff7e6af0e9 in icu::OlsonTimeZone::OlsonTimeZone(UResourceBundle const*, UResourceBundle const*, icu::UnicodeString const&, UErrorCode&) + 0x000000E3 (libicucore.A.dylib + 0x00000000000120e9) 0x00007ffeec931040
# 6 0x00007fff7e81a9fd in icu::TimeZone::getIDForWindowsID(icu::UnicodeString const&, char const*, icu::UnicodeString&, UErrorCode&) + 0x0000036D (libicucore.A.dylib + 0x000000000017d9fd) 0x00007ffeec931220
# 7 0x00007fff7e6aee68 in icu::TimeZone::createTimeZone(icu::UnicodeString const&) + 0x00000018 (libicucore.A.dylib + 0x0000000000011e68) 0x00007ffeec931320
# 8 0x00007fff7e831133 in _ucal_setDefaultTimeZone + 0x000000AD (libicucore.A.dylib + 0x0000000000194133) 0x00007ffeec931340
# 9 0x00007fff7e6aed5b in _ucal_open + 0x0000003B (libicucore.A.dylib + 0x0000000000011d5b) 0x00007ffeec9313d0
# 10 0x00007fff5819f4c5 in -[__NSTimeZone secondsFromGMTForDate:] + 0x00000175 (CoreFoundation + 0x00000000000904c5) 0x00007ffeec9315f0
# 11 0x00007fff5819f2d9 in _CFTimeZoneGetSecondsFromGMT + 0x00000049 (CoreFoundation + 0x00000000000902d9) 0x00007ffeec931640
# 12 0x00000001080f6067 in (OutlookCore + 0x0000000000148067) 0x00007ffeec931670
# 13 0x0000000108097ff2 in (OutlookCore + 0x00000000000e9ff2) 0x00007ffeec9316c0
# 14 0x0000000108097e3b in (OutlookCore + 0x00000000000e9e3b) 0x00007ffeec931970
# 15 0x0000000108136764 in (OutlookCore + 0x0000000000188764) 0x00007ffeec9319a0
# 16 0x0000000107ff50ce in (OutlookCore + 0x00000000000470ce) 0x00007ffeec9319d0
# 17 0x0000000108097dda in (OutlookCore + 0x00000000000e9dda) 0x00007ffeec931a10
# 18 0x000000010803ef2f in (OutlookCore + 0x0000000000090f2f) 0x00007ffeec931a50
# 19 0x000000010803ee46 in (OutlookCore + 0x0000000000090e46) 0x00007ffeec931a90
# 20 0x00000001080448b5 in (OutlookCore + 0x00000000000968b5) 0x00007ffeec931ae0
# 21 0x0000000108041c1c in (OutlookCore + 0x0000000000093c1c) 0x00007ffeec931b20
# 22 0x0000000108041316 in (OutlookCore + 0x0000000000093316) 0x00007ffeec931bc0
# 23 0x0000000108136764 in (OutlookCore + 0x0000000000188764) 0x00007ffeec931c30
# 24 0x0000000103c5d52e in (Microsoft Outlook + 0x000000000099152e) 0x00007ffeec931c60
# 25 0x00000001080410b2 in (OutlookCore + 0x00000000000930b2) 0x00007ffeec931ca0
# 26 0x00000001032d6c22 in (Microsoft Outlook + 0x000000000000ac22) 0x00007ffeec931d50
# 27 0x0000000107fb3db3 in (OutlookCore + 0x0000000000005db3) 0x00007ffeec931d90
# 28 0x00000001032d6728 in (Microsoft Outlook + 0x000000000000a728) 0x00007ffeec931de0
Microsoft Outlook 2016 High Sierra Version
# 29 0x00000001032d66d4 in (Microsoft Outlook + 0x000000000000a6d4) 0x00007ffeec931ec0
Microsoft Outlook Email
# 30 0x00000001032d60d6 in (Microsoft Outlook + 0x000000000000a0d6) 0x00007ffeec931f00
# 31 0x00000001032d3cbd in (Microsoft Outlook + 0x0000000000007cbd) 0x00007ffeec9320a0
# 32 0x00000001032d3a57 in (Microsoft Outlook + 0x0000000000007a57) 0x00007ffeec932440
Microsoft Outlook 2016 High Sierra Version
# 33 0x00000001032d3916 in (Microsoft Outlook + 0x0000000000007916) 0x00007ffeec932480
# 34 0x00000001032d3778 in (Microsoft Outlook + 0x0000000000007778) 0x00007ffeec9324a0
# 35 0x00007fff581a628c in ___CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 0x0000000C (CoreFoundation + 0x000000000009728c) 0x00007ffeec932550
# 36 0x00007fff581a617a in __CFXRegistrationPost + 0x000001BA (CoreFoundation + 0x000000000009717a) 0x00007ffeec932560
# 37 0x00007fff581a5ec2 in ____CFXNotificationPost_block_invoke + 0x00000032 (CoreFoundation + 0x0000000000096ec2) 0x00007ffeec9325d0
# 38 0x00007fff58164af2 in -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 0x00000722 (CoreFoundation + 0x0000000000055af2) 0x00007ffeec932610
# 39 0x00007fff58163b8c in __CFXNotificationPost + 0x0000028C (CoreFoundation + 0x0000000000054b8c) 0x00007ffeec932d00
# 40 0x00007fff5a262467 in -[NSNotificationCenter postNotificationName:object:userInfo:] + 0x00000042 (Foundation + 0x0000000000006467) 0x00007ffeec932f40
# 41 0x00007fff5589b60a in -[NSApplication _postDidFinishNotification] + 0x00000139 (AppKit + 0x000000000017460a) 0x00007ffeec932f70
# 42 0x00007fff5589b253 in -[NSApplication _sendFinishLaunchingNotification] + 0x000000DC (AppKit + 0x0000000000174253) 0x00007ffeec932fc0
# 43 0x00007fff5576df13 in -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 0x00000232 (AppKit + 0x0000000000046f13) 0x00007ffeec933000
# 44 0x00007fff5576db49 in -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 0x000002B2 (AppKit + 0x0000000000046b49) 0x00007ffeec933090
# 45 0x00007fff5a2a5404 in -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 0x0000011F (Foundation + 0x0000000000049404) 0x00007ffeec9330e0
# 46 0x00007fff5a2a5282 in __NSAppleEventManagerGenericHandler + 0x00000066 (Foundation + 0x0000000000049282) 0x00007ffeec933130
# 47 0x00007fff59290dd0 in aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 0x000006FC (AE + 0x0000000000009dd0) 0x00007ffeec933170
# 48 0x00007fff59290677 in dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 0x00000029 (AE + 0x0000000000009677) 0x00007ffeec933300
# 49 0x00007fff59290565 in _aeProcessAppleEvent + 0x0000017F (AE + 0x0000000000009565) 0x00007ffeec933340
# 50 0x00007fff574ad5e0 in _AEProcessAppleEvent + 0x00000037 (HIToolbox + 0x000000000003f5e0) 0x00007ffeec9333a0
# 51 0x00007fff5576921e in __DPSNextEvent + 0x00000AE4 (AppKit + 0x000000000004221e) 0x00007ffeec9333e0
# 52 0x00007fff55efeb4c in -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 0x00000BE4 (AppKit + 0x00000000007d7b4c) 0x00007ffeec933820
# 53 0x00007fff5575dd6d in -[NSApplication run] + 0x000002FC (AppKit + 0x0000000000036d6d) 0x00007ffeec933aa0
# 54 0x00007fff5572cf1a in _NSApplicationMain + 0x00000324 (AppKit + 0x0000000000005f1a) 0x00007ffeec933b50
# 55 0x00007fff7fb42115 in _start + 0x00000001 (libdyld.dylib + 0x0000000000001115) 0x00007ffeec933ba0
x86_64 Thread State(64bit):
__rax: 0x0000000000000074 __rbx: 0x0000000000004537 __rcx: 0x0000000000000000 __rdx:0x0000000000004537
__rdi: 0x00007fff7e8bcb66 __rsi: 0x0000000000008800 __rbp: 0x00007ffeec930f20 __rsp:0x00007ffeec930f20
__r8: 0x00007ffeec931008 __r9: 0xffffffff00000000 __r10: 0x00007fffb83d1f50 __r11:0xffffffffff582892
__r12: 0x0000000000000000 __r13: 0x00007ffeec931258 __r14: 0x000000000000229b __r15:0x0000000000008800
__rip: 0x00007fff7fdc36b7 __rflags: 0x0000000000010206 __cs: 0x000000000000002b __fs:0x0000000000000000
__gs: 0x0000000000000000
Can you give me any suggestion?
Thanks in advance.
R.X
Posted on Jan 28, 2018 1:00 AM