Macos High Sierra 10.13.1 -
Perhaps the most urgent fix in 10.13.1 involved a severe logical flaw in the initial High Sierra release. Previously, a user could request a password hint for any account—including the root administrator—without authentication. Version 10.13.1 closed this hole, requiring a valid password before revealing any hint.
The most visible change in 10.13.1 was the introduction of over 70 new emoji characters. Following Apple’s tradition of using point updates to refresh the character viewer, this release added:
While superficial, this update signaled Apple’s commitment to keeping the OS culturally current without waiting for a full .2 or .3 release. macos high sierra 10.13.1
Ironically, while 10.13.1 fixed the password hint flaw, it was not the version that patched the infamous “root login with empty password” bug. That security catastrophe was discovered and patched in a supplemental update released on November 29, 2017. If you are running 10.13.1 without the subsequent security update 2017-001, your Mac is critically vulnerable: anyone with physical access (or remote screen sharing) could log in as root by leaving the password blank.
The launch of macOS High Sierra (10.13) marked the controversial shift from HFS+ to the new APFS (Apple File System) for solid-state drives. However, the initial rollout had gaps. 10.13.1 improved the compatibility and reliability of APFS, specifically addressing issues with FileVault-encrypted volumes and external drives. Perhaps the most urgent fix in 10
For users who had hesitated to upgrade to High Sierra due to fears of file corruption, 10.13.1 served as a stability anchor, proving that the new file system was ready for daily driver status.
While point updates often focus on stability, 10.13.1 introduced several user-facing changes, primarily centered around emojis and enterprise security. 10.13.1 served as a stability anchor
Backing up to a network SMB share (e.g., a Windows server or a Linux NAS) remained slower than with macOS Sierra. 10.13.1 improved reliability but not speed; initial backups could take 2–3x longer than HFS+ equivalents.