Solution to error message when Excel won't open at all on new MacBook Air. Was working fine a couple of days ago.

Question

I have a new MacBook Air with M2 and Office 365. All of a sudden Excel won't open at all. It states Excel quit unexpectedly. The error message report references Namespace DYLD, Code 1 Library missing. Library not loaded. I have tried restarting, closing other apps. I don't have antivirus. Thoughts? Would removing Excel and then redownloading be the best option at this time?

---

Translated Report (Full Report Below)

---

Process: Microsoft Excel [10848]

Path: /Applications/Microsoft Excel.app/Contents/MacOS/Microsoft Excel

Identifier: com.microsoft.Excel

Version: 16.69 (16.69.23010700)

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

User ID: 501

Date/Time: 2023-01-13 07:40:38.9019 -0500

OS Version: macOS 13.1 (22C65)

Report Version: 12

Anonymous UUID: A07817C2-B07B-D1C6-A159-2AE825090363

Time Awake Since Boot: 66000 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_CRASH (SIGABRT)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Termination Reason: Namespace DYLD, Code 1 Library missing

Library not loaded: @rpath/ADAL4.framework/Versions/A/ADAL4

Referenced from: <3F91AC51-E307-3B07-8B90-CACB01DAC189> /Applications/Microsoft Excel.app/Contents/MacOS/Microsoft Excel

Reason: tried: '/usr/lib/swift/ADAL4.framework/Versions/A/ADAL4' (no such file, not in dyld cache), '/System/Volumes/Preboot/Cryptexes/OS/usr/lib/swift/ADAL4.framework/Versions/A/ADAL4' (no such file), '/Applications/Microsoft Excel.app/Contents/MacOS/../Frameworks/ADAL4.framework/Versions/A/ADAL4' (code signature invalid in <66304266-FE51-36AA-B002-9B3945363535> '/Applications/Microsoft Excel.app/Contents/Frameworks/ADAL4.framework/Versions/A/ADAL4' (errno=1) sliceOffset=0x000DC000, codeBlobOffset=0x000C4C50, codeBlobSize=0x0000A0C0), '/usr/lib/swift/ADAL4.framework/Versions/A/ADAL4' (no such file, not in dyld cache), '/System/Volumes/Preboot/Cryptexes/OS/usr/lib/swift/ADAL4.framework/Versions/A/ADAL4' (no such file), '/Applications/Microsoft Excel.app/Contents/MacOS/../Frameworks/ADAL4.framework/Versions/A/ADAL4' (code signa

(terminated at launch; ignore backtrace)

Answer 1

Hi Shakiru,

Sorry, but pointing users to 12 year old information about how to deal with a crash in Office 2011 does not help anyone using a current build of Microsoft Office. Therefore, I am removing your reply as not relevant to the question asked.

Answer 2

Hi Joe,

Sorry about bum steer you got from the Microsoft Advisor. The advisors and agents seem to think using a search engine instead of having actual product knowledge is the way to go. My thought is I wish the Microsoft advisors and agents were able to read and comprehend the web pages they refer people to. They are unable to perform these actions.

It's unusual for a file that is undisturbed to suddenly be missing, but it's not impossible. The cause could be an error in the Mac OS file system, or a hardware issue where a block of memory went bad and no longer has the content it once had.

Mac OS constantly checks for bad memory and removes bad blocks from service. If that's what happened here, then reinstall of Excel would most likely solve the problem. However, if the file system is messed up, then reinstall could result in a big mess.

Therefore, I think you should verify the startup volume using Disk Utility first:

How to repair a Mac disk with Disk Utility

Reinstall is fairly simple:

1. In the Applications folder, right-click Microsoft Excel.app and choose Move to Trash
2. Restart your Mac
3. Empty the Mac OS Trash
4. Use this installer to reinstall Microsoft Excel version 16.69: Install package

Answer 3

Thanks Jim, I had started down the road of the first response, but quickly realized the files I was supposed to be looking for didn't exist. Reading through the process to use Disk Utility now. Everything else is working, including other Office apps.

Answer 4

Hi Joe B!

Good to know everything is working.

The article was last updated in 2022.

Once again, Thank you Jim Gordon for the simplification and correction.

Kind Regards