10.13.5 install resumes after first login

New Contributor III

Testing on an iMac with a fusion drive bound to AD with 10.12.6. This is for a multi user classroom, the students SMB share mounts in the dock.

With the HS installer in /Applications, I push startosinstall with agreetolicense and nointeraction (via ARD) to update to 10.13.5. All seems to work fine but on first login, the install resumes and runs for about 15 minutes.

If I run the HS installer manually, the installer does not resume after the first login. Any thoughts?


New Contributor II

We've got what sounds like the same problem: Run an in-place upgrade; Installer runs, appears to complete, prompts for login, user logs in, installer pops back up, 13 minutes to go.

What we've learned so far is that it looks to be prompted by /System/Library/CoreServices/Setup Assistant.app/Contents/MacOS/Setup Assistant.app kicking off, despite the presence of /var/db/.AppleSetupDone. If you rename/delete Setup Assistant.app, the issue doesn't crop up and the user logs into a fully upgraded machine. The trouble is that it's protected by SIP, so not a proper solution. We've been playing with restricting the process through JAMF's 'restricted software' feature or killing it by script & forced reboot on login, and that pathway is so far looking like it might work but isn't fully tested.

All ears if anyone has a solid solution!

New Contributor II

Create a policy targeted to machines that have just had the upgrade installed, with a trigger for Login, frequency of once per machine, and a Files and Processes execute command of "shutdown -r now"

The login window will appear, login, shortly afterwards the machine will reboot and you'll be able to login again, where the installer does not continue. Doesn't cure the cause, but does bypass the delay.