I saw the code for the registry error
here, preceded by the comment:
PHP Code:
* On kasan kernels, everything takes longer, so double the number of
* timeout extensions. This should help with issues like 41259215
* where WindowServer was timing out waiting for kextd to get all the
* kasan kexts loaded and started.
*
* On legacy/x86 systems give a bit more time since we may be
* booting from a HDD.
The problem with not having the secure token on the clone is that I can't encrypt the data with File Vault. I don't like to have external disks lying around unencrypted.
I think I might have been able to repair that, but now I can't because it doesn't boot anymore.
I also think the secure token problem was created because I installed macOS over the cloned System.
It seems the use cases for bootable clones are reduced down to two now:
- Reinstall OS from clone <- can't anymore
- Boot when the internal SSD is completely toast <- can't anymore
- Boot to check things out on the data as it was at the time of the clone
- Boot when something goes catastrophically wrong with the data on the internal drive