SOLVED: Downgrade to BigSur - cannot open some apps or native folders

[shynepoe]

Solution:
1) This line of terminal code does the trick:
"/usr/sbin/softwareupdate --install-rosetta --agree-to-license"
2) PS 3: solution to the native folders - One has to access the folders from the profile of the user "/Users/Username/" and add them to the sidebar. I guess MacOS pathnames are different (also the symbols were different).


I had bought an used M1 mac with Beta software... I used it for some weeks. After downgrading I cannot open several apps and even the folders "Documents" give an error. I did the second recovery now. Problem remains:

Spoiler: Error

Process: Skype [5576]
Path: /Applications/Skype.app/Contents/MacOS/Skype
Identifier: com.skype.skype
Version: ???
Code Type: X86-64 (Translated)
Parent Process: ??? [1]
Responsible: Skype [5576]
User ID: 501

Date/Time: 2021-08-07 10:56:44.967 +0400
OS Version: macOS 11.5.1 (20G80)
Report Version: 12
Anonymous UUID: C7BA2416-51A1-0A2A-0260-D3A2672D9A06


Time Awake Since Boot: 30000 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: EXC_ARM_BREAKPOINT at 0x00007ffdffe7ed38 (brk 1)
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [5576]

Application Specific Information:
assertion failed [header->version <= kProjectSourceVersion]: runtime library is newer than runtime
(Library.cpp:99 init)


Thread 0 Crashed:
0 runtime 0x00007ffdffe7ed38 0x7ffdffe62000 + 118072
1 runtime 0x00007ffdffe7e720 0x7ffdffe62000 + 116512
2 runtime 0x00007ffdffe6fc7c 0x7ffdffe62000 + 56444
3 runtime 0x00007ffdffe66440 0x7ffdffe62000 + 17472
4 ??? 0x0000000000000003 0 + 3

Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000003 x2: 0x000000000000003c x3: 0x000000000000002c
x4: 0x0000000000000303 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000490
x8: 0x00007ffdffe9e000 x9: 0x0000000000000000 x10: 0x00007ffdffe9404a x11: 0x0000000000000000
x12: 0x00000000ffffffff x13: 0x0000000000000039 x14: 0x000000010aa73fe8 x15: 0x00007ffdffe85758
x16: 0xffffffffffffffe1 x17: 0x00007ffdffe8e7b6 x18: 0x0000000309775043 x19: 0x00007ffdffe93fd0
x20: 0x00007ffdffe8dba9 x21: 0x0000000000000063 x22: 0x00007ffdffe8db6d x23: 0x0000000309773fb0
x24: 0x000000010aa202e0 x25: 0x0000000202d96000 x26: 0x0000000000000009 x27: 0x0000000000000248
x28: 0x0000000000000001 fp: 0x0000000309773f70 lr: 0x00007ffdffe7ed30
sp: 0x0000000309773f50 pc: 0x00007ffdffe7ed38 cpsr: 0x60000000
far: 0x00007ffdffe93fd0 esr: 0xf2000001


Binary Images:
0x202cf2000 - 0x202d8dfff dyld (852.2) <57DB2053-BFD5-3683-97C6-F1DB2A1F1D09> /usr/lib/dyld
0x7ffdffe62000 - 0x7ffdffe91fff runtime (203.58) <52A2E5D0-FAA3-34EF-8BB7-07F73718C034> /usr/libexec/rosetta/runtime

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=1048K resident=0K(0%) swapped_out_or_unallocated=1048K(100%)
Writable regions: Total=136.3M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=136.3M(100%)

VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Rosetta Generic 8K 2
Rosetta IndirectBranch (reserved) 32K 1 reserved VM address space (unallocated)
Rosetta JIT 128.0M 1
STACK GUARD 56.0M 1
Stack 8176K 1
VM_ALLOCATE (reserved) 40K 3 reserved VM address space (unallocated)
__DATA 288K 4
__DATA_CONST 32K 1
__LINKEDIT 272K 4
__TEXT 816K 2
mapped file 1024K 10
=========== ======= =======
TOTAL 194.4M 30
TOTAL, minus reserved VM space 194.4M 30

Model: MacBookAir10,1, BootROM 7429.0.207.141.1, proc 8:4:4 processors, 8 GB, SMC
Graphics: kHW_AppleM1Item, Apple M1, spdisplays_builtin
Memory Module: LPDDR4
AirPort: spairport_wireless_card_type_airport_extreme, wl0: Jul 7 2021 00:48:27 version 18.50.40.10.7.8.121 FWID 01-f5ad2691
Bluetooth: Version 8.0.5d7, 3 services, 25 devices, 1 incoming serial ports
Network Service: Wi-Fi 2, AirPort, en0
USB Device: USB 3.1 Bus
USB Device: USB3.1 Hub
USB Device: USB3.0 Card Reader
USB Device: BUP Portable
USB Device: USB2.1 Hub
USB Device: BillBoard Device
USB Device: USB 3.1 Bus
Thunderbolt Bus: MacBook Air, Apple Inc.
Thunderbolt Bus: MacBook Air, Apple Inc.

Anybody any idea? Such a pain...

 

[allan.nyholm]

I believe you should see if there's still a beta notice in the Software Update section inside System Preferences if with beta software you mean macOS Monterey?

In the above mention place there's a Restore defaults link that isn't a link per say, but it works by disconnecting the beta profile from your second hand M1 Mac.

I then would download Big Sur from the Mac App Store. Search "Big Sur" - click Download or Get and wait for the ~12 GB to download. Now create a USB key using the "createinstallmedia" command line tool that the "Install Big Sur" application provides.

This command line is inside the application.. Close out of the initial installer that opens by just Command+Q it

Now Show Package Contents on the sucker from where the installer is downloaded to. Hint, it's in /Applications.

Dig down to /Contents/Resources/ and locate the createinstallmedia command line. Open a Terminal window;
type in sudo then make a space using the spacebar. Drag the above-mentioned command line to the Terminal window, hit your return key, and follow what the syntax is for making a USB key for Big Sur.

I wouldn't expect any problems after doing this. You will have to make complete backups of every file you have using either Time Machine(for the purpose of copying the whole OS - including Applications and personal files in an automated fashion) Or you can copy out files by hand if you feel like doing so

Why make a complete backup? Because I believe that you should re-format the drive rather than installing over the existing installation of Big Sur. That's just my opinion of course. I know that there are many people on this forum that can do a better job at deciphering that crash report than me.

One last thing you could try is make a new APFS container using Disk Utility and then install Big Sur on that container.
You can test out that free installation, using the previously downloaded full Big Sur installer from the Mac App Store(You don't have to be logged in to Mac App Store to be able to download Big Sur)

Or, lastly - create a new user - make this one Administrator or just a regular user. Then test a few things there. Does Skype open and so on. However, since Skype is available to all users I don't think this does anything that's beneficial to you.

Edited to ask about the Documents folder not opening situation.. what happens there? What does the Finder do? Does macOS give you any error message?

 

[shynepoe]

Thank you so much for responding quickly!
As I understood, you suggest making a bootable medium and installing Big Sur (after making a Backup and deleting the previous system partition).
This is what I did. I work now with a clean installed Big Sur + Full Recovery (I recovered the system twice in the hope it would help)

This is an attampt to open another App:

Spoiler: Another App error

Process: Microsoft To Do [9446]
Path: /Applications/Microsoft To Do.app/Contents/MacOS/Microsoft To Do
Identifier: Microsoft To Do
Version: ???
App Item ID: 1274495053
App External ID: 843253164
Code Type: X86-64 (Translated)
Parent Process: bash [9440]
Responsible: Terminal [5043]
User ID: 501

Date/Time: 2021-08-07 14:45:53.837 +0400
OS Version: macOS 11.5.1 (20G80)
Report Version: 12
Anonymous UUID: C7BA2416-51A1-0A2A-0260-D3A2672D9A06

Sleep/Wake UUID: E8DBFF24-4682-46F1-BFAE-7C5DCECBADBB

Time Awake Since Boot: 31000 seconds
Time Since Wake: 420 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: EXC_ARM_BREAKPOINT at 0x00007ffdfff55d38 (brk 1)
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [9446]

Application Specific Information:
assertion failed [header->version <= kProjectSourceVersion]: runtime library is newer than runtime
(Library.cpp:99 init)


Thread 0 Crashed:
0 runtime 0x00007ffdfff55d38 0x7ffdfff39000 + 118072
1 runtime 0x00007ffdfff55720 0x7ffdfff39000 + 116512
2 runtime 0x00007ffdfff46c7c 0x7ffdfff39000 + 56444
3 runtime 0x00007ffdfff3d440 0x7ffdfff39000 + 17472
4 ??? 0x0000000000000003 0 + 3

Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000003 x2: 0x000000000000003c x3: 0x000000000000002c
x4: 0x0000000000000303 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000490
x8: 0x00007ffdfff75000 x9: 0x0000000000000000 x10: 0x00007ffdfff6b04a x11: 0x0000000000000000
x12: 0x00000000ffffffff x13: 0x0000000000000039 x14: 0x000000010b6b5fe8 x15: 0x00007ffdfff5c758
x16: 0xffffffffffffffe1 x17: 0x00007ffdfff657b6 x18: 0x000000030a546f23 x19: 0x00007ffdfff6afd0
x20: 0x00007ffdfff64ba9 x21: 0x0000000000000063 x22: 0x00007ffdfff64b6d x23: 0x000000030a545e90
x24: 0x000000010b6622e0 x25: 0x0000000203638000 x26: 0x0000000000000009 x27: 0x0000000000000248
x28: 0x0000000000000001 fp: 0x000000030a545e50 lr: 0x00007ffdfff55d30
sp: 0x000000030a545e30 pc: 0x00007ffdfff55d38 cpsr: 0x60000000
far: 0x00007ffdfff6afd0 esr: 0xf2000001


Binary Images:
0x203594000 - 0x20362ffff dyld (852.2) <57DB2053-BFD5-3683-97C6-F1DB2A1F1D09> /usr/lib/dyld
0x7ffdfff39000 - 0x7ffdfff68fff runtime (203.58) <52A2E5D0-FAA3-34EF-8BB7-07F73718C034> /usr/libexec/rosetta/runtime

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=1048K resident=0K(0%) swapped_out_or_unallocated=1048K(100%)
Writable regions: Total=136.3M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=136.3M(100%)

VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Rosetta Generic 8K 2
Rosetta IndirectBranch (reserved) 32K 1 reserved VM address space (unallocated)
Rosetta JIT 128.0M 1
STACK GUARD 56.0M 1
Stack 8176K 1
VM_ALLOCATE (reserved) 72K 4 reserved VM address space (unallocated)
__DATA 288K 4
__DATA_CONST 32K 1
__LINKEDIT 272K 4
__TEXT 816K 2
mapped file 8232K 10
=========== ======= =======
TOTAL 201.5M 31
TOTAL, minus reserved VM space 201.4M 31

Model: MacBookAir10,1, BootROM 7429.0.207.141.1, proc 8:4:4 processors, 8 GB, SMC
Graphics: kHW_AppleM1Item, Apple M1, spdisplays_builtin
Memory Module: LPDDR4
AirPort: spairport_wireless_card_type_airport_extreme, wl0: Jul 7 2021 00:48:27 version 18.50.40.10.7.8.121 FWID 01-f5ad2691
Bluetooth: Version 8.0.5d7, 3 services, 25 devices, 1 incoming serial ports
Network Service: Wi-Fi 2, AirPort, en0
USB Device: USB 3.1 Bus
USB Device: USB3.1 Hub
USB Device: USB3.0 Card Reader
USB Device: BUP Portable
USB Device: USB2.1 Hub
USB Device: BillBoard Device
USB Device: USB 3.1 Bus
Thunderbolt Bus: MacBook Air, Apple Inc.
Thunderbolt Bus: MacBook Air, Apple Inc.

Spoiler: Another App

Process: Atom [10515]
Path: /Applications/Atom.app/Contents/MacOS/Atom
Identifier: com.github.atom
Version: ???
Code Type: X86-64 (Translated)
Parent Process: ??? [1]
Responsible: Atom [10515]
User ID: 501

Date/Time: 2021-08-07 14:55:30.056 +0400
OS Version: macOS 11.5.1 (20G80)
Report Version: 12
Anonymous UUID: C7BA2416-51A1-0A2A-0260-D3A2672D9A06

Sleep/Wake UUID: E8DBFF24-4682-46F1-BFAE-7C5DCECBADBB

Time Awake Since Boot: 32000 seconds
Time Since Wake: 990 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: EXC_ARM_BREAKPOINT at 0x00007ffdffdf7d38 (brk 1)
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [10515]

Application Specific Information:
assertion failed [header->version <= kProjectSourceVersion]: runtime library is newer than runtime
(Library.cpp:99 init)


Thread 0 Crashed:
0 runtime 0x00007ffdffdf7d38 0x7ffdffddb000 + 118072
1 runtime 0x00007ffdffdf7720 0x7ffdffddb000 + 116512
2 runtime 0x00007ffdffde8c7c 0x7ffdffddb000 + 56444
3 runtime 0x00007ffdffddf440 0x7ffdffddb000 + 17472
4 ??? 0x0000000000000003 0 + 3

Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000003 x2: 0x000000000000003c x3: 0x000000000000002c
x4: 0x0000000000000303 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000490
x8: 0x00007ffdffe17000 x9: 0x0000000000000000 x10: 0x00007ffdffe0d04a x11: 0x0000000000000000
x12: 0x00000000ffffffff x13: 0x0000000000000039 x14: 0x000000010af92fe8 x15: 0x00007ffdffdfe758
x16: 0xffffffffffffffe1 x17: 0x00007ffdffe077b6 x18: 0x000000030a0c4043 x19: 0x00007ffdffe0cfd0
x20: 0x00007ffdffe06ba9 x21: 0x0000000000000063 x22: 0x00007ffdffe06b6d x23: 0x000000030a0c2fb0
x24: 0x000000010af3f2e0 x25: 0x000000020319c000 x26: 0x0000000000000009 x27: 0x0000000000000248
x28: 0x0000000000000001 fp: 0x000000030a0c2f70 lr: 0x00007ffdffdf7d30
sp: 0x000000030a0c2f50 pc: 0x00007ffdffdf7d38 cpsr: 0x60000000
far: 0x00007ffdffe0cfd0 esr: 0xf2000001


Binary Images:
0x2030f8000 - 0x203193fff dyld (852.2) <57DB2053-BFD5-3683-97C6-F1DB2A1F1D09> /usr/lib/dyld
0x7ffdffddb000 - 0x7ffdffe0afff runtime (203.58) <52A2E5D0-FAA3-34EF-8BB7-07F73718C034> /usr/libexec/rosetta/runtime

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=1048K resident=0K(0%) swapped_out_or_unallocated=1048K(100%)
Writable regions: Total=136.3M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=136.3M(100%)

VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Rosetta Generic 8K 2
Rosetta IndirectBranch (reserved) 32K 1 reserved VM address space (unallocated)
Rosetta JIT 128.0M 1
STACK GUARD 56.0M 1
Stack 8176K 1
VM_ALLOCATE (reserved) 44K 4 reserved VM address space (unallocated)
__DATA 288K 4
__DATA_CONST 32K 1
__LINKEDIT 272K 4
__TEXT 816K 2
mapped file 852K 10
=========== ======= =======
TOTAL 194.3M 31
TOTAL, minus reserved VM space 194.2M 31

Model: MacBookAir10,1, BootROM 7429.0.207.141.1, proc 8:4:4 processors, 8 GB, SMC
Graphics: kHW_AppleM1Item, Apple M1, spdisplays_builtin
Memory Module: LPDDR4
AirPort: spairport_wireless_card_type_airport_extreme, wl0: Jul 7 2021 00:48:27 version 18.50.40.10.7.8.121 FWID 01-f5ad2691
Bluetooth: Version 8.0.5d7, 3 services, 25 devices, 1 incoming serial ports
Network Service: Wi-Fi 2, AirPort, en0
USB Device: USB 3.1 Bus
USB Device: USB3.1 Hub
USB Device: USB3.0 Card Reader
USB Device: BUP Portable
USB Device: USB2.1 Hub
USB Device: BillBoard Device
USB Device: USB 3.1 Bus
Thunderbolt Bus: MacBook Air, Apple Inc.
Thunderbolt Bus: MacBook Air, Apple Inc.

I will also upload some screenshots with the prompts I get. If I try to open a native folder is says, that "the original" could not be found. My guess is (regarding the Apps), it cannot open Rosetta Apps.



The last "solution" would be, going back to "Beta MacOS 12" hoping that everything will work again (except the Apps which do not work with Macos 12 yet and some other minor problems (wifi unstable, chrome chrashing) compared to the situation now). Probably it will become a non Beta very soon so...

PS: "chsh -s /bin/zsh" does not help. I tried but it does not fix the problem.
PS 2: The Apps also do not work from an account of a new user. But the "native" folders open.

PS 3: solution to the native folders - One has to access the folders from the profile of the user "/Users/Username/" and add them to the sidebar. I guess MacOS pathnames are different (also the symbols were different).

Now I have to start the Apps somehow and the system would work....


It is a real mass...

 

[Mike Boreham]

Starting with a second hand machine with beta software and problems, I would use Apple Configurator 2 to completely reload the machine with Big Sur.
This can't be done on M1 macs with a bootable USB.

 

[shynepoe]

Starting with a second hand machine with beta software and problems, I would use Apple Configurator 2 to completely reload the machine with Big Sur.

The problem is the "recovery" (of data) from Macos 12 into the system of MacOS 11. I cannot start from scratch.

Completely reloading the machine wouldn't solve this problem I guess, as Big Sur works fine after deleting the partition and installing it form scratch.

As the problem with the folders was solved easily I guess the other one has also a simple solution, which I do not know yet.

 

[Mike Boreham]

The problem is the "recovery" (of data) from Macos 12 into the system of MacOS 11. I cannot start from scratch.

Completely reloading the machine wouldn't solve this problem I guess, as Big Sur works fine after deleting the partition and installing it form scratch.

As the problem with the folders was solved easily I guess the other one has also a simple solution, which I do not know yet.

The only way to completely roll back from Monterey to Big Sur is to use Apple Configurator 2. Yes, you can reinstall Big Sur with a USB but you will still have Monterey Recovery. Since you have problems and it is a second hand machine I would completely restore Big Sur with Apple Configurator 2. This will put Big Sur Recovery and OS on the machine. There is no other way.

 

[Mike Boreham]

The problem is the "recovery" (of data) from Macos 12 into the system of MacOS 11. I cannot start from scratch.

Yes you would have to restore your data from your backup using Migration Assistant or Setup Assistant after using Apple Configurator 2. Why is that a problem?

 

[shynepoe]

Yes you would have to restore your data from your backup using Migration Assistant or Setup Assistant after using Apple Configurator 2. Why is that a problem?

I never used it and I am not sure how much time it takes and if it really can help. Generally all the procedures take a lot of time, what annoys me a lot.

Because of that, I am not sure if I'd rather just go back Monterey Beta cause (generally) it works. And that would take the smallest amount of time.

And I am still hoping for the magic trick as for the folders. I am sure there must be a small, minor tweak which brings all to normal. I might be wrong, but this idea or hope holds me back from investing even more time (potentially without any results).

I am not very familiar with installing MacOS Software.


Do you think the Big Sur Recovery could be the (relevant) difference between making the recovery work on BigSur or not?

PS: Still I'm downloading "Apple Configurator 2"
PS2: If I need to Macs to use this software, I'm already done. Where I am, I have only one Mac.

 

[Mike Boreham]

I never used it and I am not sure how much time it takes and if it really can help. Generally all the procedures take a lot of time, what annoys me a lot.

Because of that, I am not sure if I'd rather just go back Monterey Beta cause (generally) it works. And that would take the smallest amount of time.

And I am still hoping for the magic trick as for the folders. I am sure there must be a small, minor tweak which brings all to normal. I might be wrong, but this idea or hope holds me back from investing even more time (potentially without any results).

I am not very familiar with installing MacOS Software.


Do you think the Big Sur Recovery could be the (relevant) difference between making the recovery work on BigSur or not?

PS: Still I'm downloading "Apple Configurator 2"
PS2: If I need to Macs to use this software, I'm already done. Where I am, I have only one Mac.

My answers have really been based simply on the fact that you have a second hand mac with beta software and problems. I usually buy my Macs second hand but always start completely fresh with them back to factory state. With Intel Macs this was easy. With M1 Macs you need Configurator run from a second Mac.

I don't have a suggestion for your specific issues...there may be a magic trick/silver bullet as you suggest. I assume you have tried standard things like booting from Safe Mode, which clears out caches and runs First Aid?

It may well be that an erase and install of Big Sur using a bootable USB will solve your problem. I am not sure whether you have achieved this yet? I see you have done this. That must have involved restoring your data from a backup.

I doubt that the Recovery being on Monterey is the problem. Big Sur should be OK. Being on Monterey Recovery mainly means you can't reinstall Big Sur from Recovery, which will reinstall Monterey.

If you haven't got access to a second mac you can't use Configurator, but you could try taking it to an Apple Store. Since the Mac is less than a year old they may well handle it under warranty even though second hand. Explain the situation to them as it is.

Which ever route you end up going you will need a proper backup of your data to restore from. You said this was a problem before but not sure why. I have done several restores from Time Machine recently and it works well.

 

[shynepoe]

It may well be that an erase and install of Big Sur using a bootable USB will solve your problem. I am not sure whther you have achieved this yet? It will also require restoring your data from a backup.

Yes, this worked I also have a backup.

You said this was a problem before but not sure why. I have done several restores from Time Machine recently and it works well.

So the last backup I have is from Monterey and this causes problems in Big Sur. One of them is already solved. The other one remains: I cannot open certain apps and I get an error message, more details.


My guess, but it is a blind guess, it has to do something with Rosetta.

In short the problem is the following:

Spoiler: Problem

Application Specific Information:
assertion failed [header->version <= kProjectSourceVersion]: runtime library is newer than runtime
(Library.cpp:99 init)

I think MacOS 12 uses a different Version of Rosetta. And this causes problems in BigSur for Apps which were "optimised" in Monterey.




If I can't solve this, I'll go back to Monterey again.

 

[shynepoe]

It may well be that an erase and install of Big Sur using a bootable USB will solve your problem. I am not sure whther you have achieved this yet? It will also require restoring your data from a backup.

Yes, this worked I also have a backup.

You said this was a problem before but not sure why. I have done several restores from Time Machine recently and it works well.

So the last backup I have is from Monterey and this causes problems in Big Sur. One of them is already solved. The other one remains: I cannot open certain apps and I get an error message

 

[Mike Boreham]

One last thing you could try is make a new APFS container using Disk Utility and then install Big Sur on that container.


Or, lastly - create a new user - make this one Administrator or just a regular user. Then test a few things there. Does Skype open and so on. However, since Skype is available to all users I don't think this does anything that's beneficial to you.

OP did you try these good suggestions?

 

[shynepoe]

I want to clap on my shoulder and call myself a genius
I found the magic trick!
This line of terminal code does the trick:
"/usr/sbin/softwareupdate --install-rosetta --agree-to-license"

source: https://osxdaily.com/2020/12/04/how-install-rosetta-2-apple-silicon-mac/

OP did you try these good suggestions?

Yes, but it did not help.

So my explanation is the following: Somehow Monterey Apps, already optimised for Rosetta, did not kick off the Rosetta installing process so the Apps would not open. As one installs Rosetta manually, the Apps work again.


So problem solved!


Thank you so much for you help Mike and Allan ♥♥♥

 

[Mike Boreham]

I cannot open certain apps and I get an error message, more details.


My guess, but it is a blind guess, it has to do something with Rosetta.
I think MacOS 12 uses a different Version of Rosetta. And this causes problems in BigSur for Apps which were "optimised" in Monterey.




If I can't solve this, I'll go back to Monterey again.

You could try uninstalling and reinstalling the problem apps?

Rosetta is part of the OS, not Recovery so if you have rolled back to Big Sur you are not using Monterey Rosetta.

Yes you could go back to Monterey if everything was OK there.

 

[Mike Boreham]

I want to clap on my shoulder and call myself a genius
I found the magic trick!
This line of terminal code does the trick:
"/usr/sbin/softwareupdate --install-rosetta --agree-to-license"

source: https://osxdaily.com/2020/12/04/how-install-rosetta-2-apple-silicon-mac/


Yes, but it did not help.

So my explanation is the following: Somehow Monterey Apps, already optimised for Rosetta, did not kick off the Rosetta installing process so the Apps would not open. As one installs Rosetta manually, the Apps work again.


So problem solved!


Thank you so much for you help Mike and Allan ♥♥♥

Well done. You found the solution yourself 👍🏻👍🏻

 

[dobbsta]

I literally love you, thank you, I would kiss you right now