I cannot open files(especially PDF files) after update ventura 13.2.1 to 13.3

Are you sure you're having the same root problem most of the discussion here is about? Which is:

Files created with non-Latin characters in the filename encoded in an unusual way by the software that generated the file won't open when double-clicked. If you edit the file name at all in the Finder (which re-encodes in the more common way) it will open normally. Files with only basic Latin characters also open fine regardless, and opening via an Open file dialogue also works, only Finder double-clicking or dragging and dropping onto a Dock icon fail.

On my M1 Max MPB 13.5 is fine, and that problem has not returned, either with old or newly-created files. It was 100% replicable with the tools I use prior to the fix, so if the same problem existed I'd be able to replicate it. Could be that it's affecting Intel systems differently or there's some other factor, of course.

13.3 is generally busted.

For example MSO cannot open any recent docs due to the Sandbox: ScopedBookmarkAgent(717) deny(1) file-read-data <path to the file>. Something went utterly wrong with this release.

In case anybody inside Apple is reading this, you can easily reproduce as follows.

In Terminal:

echo "Hello World" > $(printf "\xc3\xbc").txt

Now try to open "ü.txt", TextEdit will launch, but will fail to resolve the file bookmark due to a sandbox issue.

Failed to resolve bookmark 0x12750ea70 for item F6D82F7E-E34F-4CD8-A7B6-E331894336B8 with error: Error Domain=NSCocoaErrorDomain Code=4

Sandbox: TextEdit(4924) deny(1) file-read-data /Users/iccir/Desktop/ü.txt

OFFTOPIC: He used the Office-Reset utility to remove PowerPoint the application. He did not lose data. Then he re-installed PowerPoint and that resolved the problem he was experiencing. The Office-Reset utility can reset 365 apps to factory and it can remove individual 365 Apps as well as all of Microsoft 365. It's merely advanced scripts written by Microsoft's Office Mac developers.

James Brickley -- a huge thank you for the technical explanation of this issue, both because I hate having problems and not understanding the cause, and because it saved me attempting a re-install on the assumption that this was some kind of filesystem corruption issue when it's not.

A note, it's entirely possible to end up in this situation without touching a NAS or other external filesystem or server. Specific example, the Video DownloadHelper plugin for Firefox, which does what it says on the tin, will generate files that have this problem if it generates a filename that includes complex characters (in my case, most Japanese kanji, although I was surprised that hiragana doesn't have the issue).

Which I might add are annoying since you now can't double-click the video you just downloaded to play it without touching the filename. It's obviously not that much work to hit return twice, but still annoying.

You've got bigger problems, start a new discussion question for your issues. Likely need to backup your data and start over then restore your data from backup.

I spoke with a Network administrator that told me resetting one drive solved this issue for another client. Has anyone tried this and did it work?

I thought that google drive is responsible for those errors.. renamed all folders that startefd with "_" (it helped).. moved all important files away from goolge.. than i thought that adobe is responsible for all problems... broke all my modified dates for folders after dubliceting.. and it turned out that it is macos update problem... so much wasted time.. lets hope apple will fix it soon.

I cannot open and PowerPoint files. It crashes each time.

Thats the report below.

Any suggestions?

-------------------------------------

Translated Report (Full Report Below)

-------------------------------------

Process: Microsoft PowerPoint [15735]

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

Identifier: com.microsoft.Powerpoint

Version: 16.71 (16.71.23031200)

Code Type: X86-64 (Native)

Parent Process: launchd [1]

User ID: 501

Date/Time: 2023-05-02 15:52:33.9743 +0200

OS Version: macOS 13.3.1 (22E261)

Report Version: 12

Bridge OS Version: 7.4 (20P4252)

Anonymous UUID: 8BCFA67A-26A0-ED2C-7C78-29379808FA5F

Time Awake Since Boot: 1100 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: <0A4EF18C-48EB-3E59-919C-0BB1744FEB67> /Applications/Microsoft PowerPoint.app/Contents/MacOS/Microsoft PowerPoint

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 PowerPoint.app/Contents/MacOS/../Frameworks/ADAL4.framework/Versions/A/ADAL4' (code signature invalid in <BFCA477B-1DD1-39E2-B4D0-AB88EB1644BE> '/Applications/Microsoft PowerPoint.app/Contents/Frameworks/ADAL4.framework/Versions/A/ADAL4' (errno=1) sliceOffset=0x00004000, codeBlobOffset=0x000CCCA0, codeBlobSize=0x0000A1C0), '/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 PowerPoint.app/Contents/MacOS/../Frameworks/ADAL4.framework/Vers

(terminated at launch; ignore backtrace)

Thread 0 Crashed:

0 dyld 0x7ff80f27ec42 __abort_with_payload + 10

1 dyld 0x7ff80f298fd7 abort_with_payload_wrapper_internal + 82

2 dyld 0x7ff80f299009 abort_with_payload + 9

3 dyld 0x7ff80f21d8f0 dyld4::halt(char const*) + 375

4 dyld 0x7ff80f21ab71 dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 4526

5 dyld 0x7ff80f2193bd start + 1805

Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x0000000002000209 rbx: 0x0000000000000000 rcx: 0x00007ff7b21de418 rdx: 0x00007ff7b21de880

rdi: 0x0000000000000006 rsi: 0x0000000000000001 rbp: 0x00007ff7b21de460 rsp: 0x00007ff7b21de418

r8: 0x00007ff7b21de480 r9: 0x0000000000000000 r10: 0x0000000000000087 r11: 0x0000000000000246

r12: 0x0000000000000087 r13: 0x00007ff7b21de880 r14: 0x0000000000000001 r15: 0x0000000000000006

rip: 0x00007ff80f27ec42 rfl: 0x0000000000000246 cr2: 0x000000010fe02000

Logical CPU: 0

Error Code: 0x02000209

Trap Number: 133

Binary Images:

0x10dd20000 - 0x10f8b7fff com.microsoft.Powerpoint (16.71) <0a4ef18c-48eb-3e59-919c-0bb1744feb67> /Applications/Microsoft PowerPoint.app/Contents/MacOS/Microsoft PowerPoint

0x7ff80f213000 - 0x7ff80f2ab5a7 dyld (*) <f22a1143-9732-3e23-a8b7-cbade6bb8301> /usr/lib/dyld

External Modification Summary:

Calls made by other processes targeting this process:

task_for_pid: 0

thread_create: 0

thread_set_state: 0

Calls made by this process:

task_for_pid: 0

thread_create: 0

thread_set_state: 0

Calls made by all processes on this machine:

task_for_pid: 0

thread_create: 0

thread_set_state: 0

VM Region Summary:

ReadOnly portion of Libraries: Total=200.9M resident=0K(0%) swapped_out_or_unallocated=200.9M(100%)

Writable regions: Total=8596K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8596K(100%)

VIRTUAL REGION

REGION TYPE SIZE COUNT (non-coalesced)

=========== ======= =======

STACK GUARD 56.0M 1

Stack 8192K 1

VM_ALLOCATE 8K 2

__DATA 859K 3

__DATA_CONST 2260K 2

__DATA_DIRTY 7K 1

__LINKEDIT 172.7M 3

__TEXT 28.2M 2

dyld private memory 260K 2

shared memory 4K 1

=========== ======= =======

TOTAL 268.2M 18

Although this question is off-topic and an entirely different problem. There is a Microsoft utility you can use to reset Office 365 Apps such as PowerPoint. Or otherwise, completely uninstall so it be re-installed.

Try this: https://office-reset.com/

I hope that Apple fixes it soon.

mu-on wrote:

Of course, it is impractical to convert every file name. This is an obvious bug in 13.3 and let's hope it will be fixed in the near future :-)

What James said.

This is most unlikely to happen with files generated on the mac; besides, it would only affect files with names including non-ASCII characters. If you are having problems with files that were already on your mac before the update, it is very unlikely (if not impossible) that the issue is the aforementioned NFC/NFD situation.

From GoogleDrive, Safari solves it fine, but from other platforms like Moodle, 
it has some problems. For example, a file named "Gramáticas y Aotómatas.pdf" 
remains as "Gramáticas y Autómatas.pdf", however the Finder can open it.
The worst situation is when using Chrome, where the Finder cannot open the file