OK, but do you see the bug with Language & Region I am reporting, or is it unique to my setup?
I have it on two SSDs set up separately—not cloned.
MacPro 3,1 with HS beta 9 booting APFS and set up using dosdude1's 2.1.2 patcher
[doublepost=1504929095][/doublepost]
OK, but do you see the bug with Language & Region I am reporting, or is it unique to my setup?
I have it on two SSDs set up separately—not cloned.
MacPro 3,1 with HS beta 9 booting APFS and set up using dosdude1's 2.1.2 patcher
As a test, I went through the procedure below to re-run the Setup Assistant and create a new account on the affected SSD, and the problem is gone.
No idea why it was happening and on two separate SSDs too.
Removing .AppleSetupDone
To remove this file, we need to boot the Mac into
Single-User Mode. This provides a method of interacting with OS X via the command-line, with full root privileges.
Start up the Mac whilst holding down ⌘-S. After a few moments, you'll see the Mac boot to the command line.
Before continuing, the filesystem must be checked and mounted, so files aren't immediately accessible to interact with. To do this, enter the two commands that are displayed within the prompt, one at a time.
The following command will check the filesystem to ensure there are no problems. Enter:
/sbin/fsck -fy
The next command will then mount the filesystem for it to be accessible:
/sbin/mount -uw /
With the filesystem mounted and accessible, it's time to remove the file so OS X will re-run Setup Assistant:
rm /var/db/.AppleSetupDone
After that, simply enter reboot and your Mac will restart and boot normally. Only this time, Setup Assistant will launch.