I now experience daily kernel panics and crashes at every point on Big Sur, Catalina was already bad, but Big Sur has brought out a new quality there. Most of the bugs were in the betas of Big Sur and are still in the "stable" release 11.4 and the latest beta 11.5 beta 1. Almost all of them have already been included in the Big Sur betas before 11.0 release. The highlight is actually that even with Apple's latest M1 hardware, external displays can't be used without running into problems every day. What's the reason for that? Does Apple simply not prioritize bug fixing anymore? Are there too many bugs in the meantime, so that only the few zero day exploits are getting fixed? What's the point of the Feedback Assistant if the response time takes years? Is that to passively teach users that problems don't matter at Apple anymore? Does anyone at Apple still work with these Macs? Or did someone secretly port Xcode to Linux so they can work with it? The software quality looks like Apple is about to kill the Mac. Is no one asking this question because the marketing is so great? How to approach here? Just keep wasting time and doing this crap where you disconnect and reconnect monitor cables every day and then experience a kernel panic that doesn't help to get the monitor working again? And the Support doesn't answer anymore because they know the issues already, but don't fix them. Just closing the tickets after a while without any response. Isn't that, the quality that was delivered by Apple after Steve Jobs left Apple back in the day? Through which Apple almost went bankrupt?

Hey, is there anything that works for you with Big Sur, on legacy Intel hardware or Apples M1? I can't even shut down one of my Macs without a kernel panic occurring. Feedback Assistant is useless as no bugs I reported are fixed and I never get a reply or a request for more informations. Level 2 support takes hours to write everything in a ticket, only to have no one respond. This Input field here on 'Ask a Question' doesn't show any text because it is broken. Nothing seems to get fixed at Apple. Most of the bugs and kernel panics I encounter are in forums where people described them last year in the beta phase. Is there a why to push Apple to increase the software quality? Thanks, Martin

Hello, can anyone, with a blank SSD, reinstall via Internet Recovery Big Sur on an Intel Mac? Usually I get the error "An error occurred loading the update.". Then looking into the logs from the installer I see with various files, after the 12 gigabytes have been downloaded, errors such as: "CRC mismatch; got: 0x3372a3be expected: 0x922f74d8 for file AssetData/boot/EmbeddedOSFirmware.pkg". Also all other files come here randomly as errors. But if the installer works, you are guaranteed to get the error "An error occurred preparing the software update." afterwards. On an empty Mac, with a 1 terabyte SSD, of which, after the 12 gigabyte image is downloaded, mostly 980 gigabytes are still free. I contacted Apple support and never received a response. Best, Martin

macOS Ventura introduced a new bug: bookdatastored is trying to create a directory but it can't, crashes and restart and trying again. This bug also occurred in the first 13.1 beta. ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: bookdatastored [1333] Path: /System/Library/PrivateFrameworks/BookDataStore.framework/Support/bookdatastored Identifier: bookdatastored Version: ??? Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 248 Date/Time: 2022-10-26 23:53:34.9205 +0200 OS Version: macOS 13.0 (22A380) Report Version: 12 Anonymous UUID: 57878A12-2EC0-4242-BC23-1BFB44BBB61F Time Awake Since Boot: 400 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.bookdatastored.xpc-listener-ready Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Application Specific Information: abort() called Application Specific Backtrace 0: 0 CoreFoundation 0x000000018fa98418 __exceptionPreprocess + 176 1 libobjc.A.dylib 0x000000018f5e2ea8 objc_exception_throw + 60 2 Foundation 0x000000019091e800 -[NSFileManager createDirectoryAtPath:withIntermediateDirectories:attributes:error:] + 0 3 bookdatastored 0x000000010040de10 bookdatastored + 237072 4 bookdatastored 0x000000010040db60 bookdatastored + 236384 5 bookdatastored 0x000000010040d694 bookdatastored + 235156 6 bookdatastored 0x000000010040d57c bookdatastored + 234876 7 bookdatastored 0x000000010041dab4 bookdatastored + 301748 8 bookdatastored 0x000000010041d9fc bookdatastored + 301564 9 libdispatch.dylib 0x000000018f7b7504 _dispatch_client_callout + 20 10 libdispatch.dylib 0x000000018f7b8d50 _dispatch_once_callout + 32 11 bookdatastored 0x000000010041d9dc bookdatastored + 301532 12 bookdatastored 0x00000001003fde60 bookdatastored + 171616 13 bookdatastored 0x00000001004366d0 bookdatastored + 403152 14 libdispatch.dylib 0x000000018f7b7504 _dispatch_client_callout + 20 15 libdispatch.dylib 0x000000018f7b8d50 _dispatch_once_callout + 32 16 bookdatastored 0x0000000100436660 bookdatastored + 403040 17 bookdatastored 0x00000001004361b0 bookdatastored + 401840 18 bookdatastored 0x0000000100436958 bookdatastored + 403800 19 bookdatastored 0x0000000100436050 bookdatastored + 401488 20 bookdatastored 0x00000001003d9904 bookdatastored + 22788 21 bookdatastored 0x00000001003d9540 bookdatastored + 21824 22 libdispatch.dylib 0x000000018f7b7504 _dispatch_client_callout + 20 23 libdispatch.dylib 0x000000018f7c6a9c _dispatch_lane_barrier_sync_invoke_and_complete + 56 24 bookdatastored 0x00000001003d9470 bookdatastored + 21616 25 bookdatastored 0x00000001003d906c bookdatastored + 20588 26 dyld 0x000000018f613e50 start + 2544