MacInTouch Amazon link...

macOS 10.14 Mojave

Channels
Apple
I did this just today (I am also running Mojave) and the download is initiated as you describe. The installer launches automatically after downloading. All you have to do is quit the installation process. The installer app will be in the /Applications folder.
[Thank you], your method worked perfectly.
 


I went to the App Store, searched for Mojave, downloaded “it” (it was the 6GB installer), quit the installer when it autostarted, and moved it outside the Applications folder....
I did just that and assume it is the full installer, based on the size... 6GB, as you state. However, there is a curious discrepancy: If I look at the size in list view in a Finder window, the size is given as 6.05GB. If, however, I select it and choose Get Info, the size is given as 6.07GB. Small difference, I know, but does anyone know the reason for it? I assume it does not indicate a problem with the file.
 


I did just that and assume it is the full installer, based on the size... 6GB, as you state. However, there is a curious discrepancy: If I look at the size in list view in a Finder window, the size is given as 6.05GB. If, however, I select it and choose Get Info, the size is given as 6.07GB. Small difference, I know, but does anyone know the reason for it? I assume it does not indicate a problem with the file.
I see 6.05GB in the Finder and with Get Info (2018 MacBook Pro, hence APFS, macOS 10.14.6).

I suppose one could validate the checksum on the download. Apple doesn't make this information easy to find, and I could not find anything on Apple web pages. I did find this site listing checksums, but it appears to not be up to date for the most recent installer for macOS 10.14.6 (for example, I am at build 18G95 and have not applied the "supplemental update 2).
 


I see 6.05GB in the Finder and with Get Info (2018 MacBook Pro, hence APFS, macOS 10.14.6). I suppose one could validate the checksum on the download. Apple doesn't make this information easy to find, and I could not find anything on Apple web pages. I did find this site listing checksums, but it appears to not be up to date for the most recent installer for macOS 10.14.6 (for example, I am at build 18G95 and have not applied the "supplemental update 2).
For what it's worth, here are the checksums I get for macOS 10.14.6 build 18G103. These were generated against each of two installers downloaded with the third-party downloaders that were mentioned on 2019-10-05 (post-22126).
Terminal effectively said:
shasum Install*OS*.app/Contents/SharedSupport/{Base,Install}*.dmg

82e147e9858a67336d8687d9cea616c76d50d373 BaseSystem.dmg
ca221c005c6f51be733128206de23aa43b9869a2 InstallESD.dmg
 


My Mojave App Store download says 6.05GB in Finder, and Get Info reports:
6,050,972,369 bytes (6.04 GB on disk)
Version: 14.6.06
 


For what it's worth, here are the checksums I get for macOS 10.14.6 build 18G103. These were generated against each of two installers downloaded with the third-party downloaders that were mentioned on 2019-10-05 (post-22126).
82e147e9858a67336d8687d9cea616c76d50d373 BaseSystem.dmg
ca221c005c6f51be733128206de23aa43b9869a2 InstallESD.dmg
Those are the checksums I saw, as well. I also see these match the build 18G103 checksums on the GitHub page. They either updated that list last night, or I was seeing it wrong.
 


Now that Catalina has been released I finally updated our MacBook Pro 9,2 (2012) to Mojave. Yes, I live on the trailing edge of technology.

I installed Mojave on an empty partition (no issues and no firmware updates) then did a migration. At the end, I got the following message:
Could not preserve the authentication state of the System Administrator. You may need to re-enable this account, though its files are not affected.
In addition, the password of the second (non-admin) user was changed to a temp password.

Anyway, on reboot the System Administrator account seemed okay, so this is more a curiousity than a problem. And I reset the password to its previous value on the second account.

Anyone out there who can shed some light on this?
 


Ric Ford

MacInTouch
I installed Mojave on an empty partition (no issues and no firmware updates) then did a migration. At the end, I got the following message...
... Anyone out there who can shed some light on this?
It's hard to do any assessment without more information. Did you boot into the clean-installed Mojave system before doing a migration? And how did you do the migration — as part of initial startup of a virgin Mojave installation, or later, via Migration Assistant? Also, which, if any, volumes had FileVault 2 enabled? And when did you do software updates? (And what updates were required?)
 


It's hard to do any assessment without more information.
Here is more information.
  1. Did you boot into the clean-installed Mojave system before doing a migration?
  2. And how did you do the migration — as part of initial startup of a virgin Mojave installation, or later, via Migration Assistant?
  3. Also, which, if any, volumes had FileVault 2 enabled?
  4. And when did you do software updates?
  5. And what updates were required?)
1. Yes.
2. As part of the initial startup.
3. None.
4. Software updates were done after the initial migration.
5. No system updates. Only iWork apps needing updating.
 


... I installed Mojave on an empty partition (no issues and no firmware updates) then did a migration. At the end, I got the following message:
Could not preserve the authentication state of the System Administrator. You may need to re-enable this account, though its files are not affected.
I got the same message Monday after the same install and migrate procedure. I ignored it and logged in. Everything related to authentication is working fine.
 


As it happens, last night I migrated almost 2 TB of accounts from a 2010 Mac Mini running El Capitan to a new Mini that's replacing it (used as a media center). It came with macOS 10.14.5, so, like David Blanchard, the migration was part of the initial setup.

After the migration was over, I encountered a lot of oddities and problems that took me over 3 more hours to fix. Among them: Mojave wanted me to assign new passwords to both user accounts (both are admin accounts). iTunes library did not migrate, I had to copy it manually. EyeTV had all sorts of problems; none of the previous preferences copied, nor did Scripts and LaunchAgents folders (in the user and user/library folders respectively) with custom programs to generate an EPG for an .xmltv-based listing (again after manual copying, they ran fine). The screen saver and desktop pictures also had to be manually reentered. Etc.

I talked this over with my son, a senior engineer at a large computer company. His theory is that the problems occurred because the previous computer was set up to be case-sensitive, whereas the APFS system to which I was migrating is case-insensitive by default (which in my ignorance I did not change). Does that sound like a possible cause of the problems experienced by me and by David Blanchard? (I lack the technical expertise to answer that question.)
 


Ric Ford

MacInTouch
... His theory is that the problems occurred because the previous computer was set up to be case-sensitive, whereas the APFS system to which I was migrating is case-insensitive by default (which in my ignorance I did not change)....
I don't know if all those problems were caused by using a case-sensitive file system, but I would characterize doing that as "asking for trouble", because Mac file systems (and virtually all Mac users) have been case-insensitive all along, with the extremely rare exception that you apparently have been exploring.

In fact, this is such a rare option, I can't recall it ever coming up in any significant discussions over more than 30 years of full-time Mac work with many, many thousands of people and organizations, even though I was aware it existed. Given Apple's increasingly bad software quality and testing, I'd be surprised if anyone at Apple ever even tried that scenario....

Here are samples of some of the problems that can arise:

In combination with Apple's deficient documentation and frequent changes to APFS, I wouldn't go anywhere near that case-sensitive variant for any serious Mac system. (Of course, Linux file systems are the opposite: case-sensitive is the standard.)
 


I talked this over with my son, a senior engineer at a large computer company. His theory is that the problems occurred because the previous computer was set up to be case-sensitive, whereas the APFS system to which I was migrating is case-insensitive by default (which in my ignorance I did not change). Does that sound like a possible cause of the problems experienced by me and by David Blanchard? (I lack the technical expertise to answer that question.)
Funny you should mention that, as I had to deal with this on a friend's computer just last week. The friend had an old iMac that was dying. Fortunately, they had a Time Machine backup. When they connected it to their new iMac, Migration Assistant refused to restore the data, because the original machine (for whatever reason) had been running a case-sensitive version of HFS, and the new machine was (as expected) non-case-sensitive Mojave. Migration Assistant flagged this as the specific reason it wouldn't work.

I don't know if it actually checks for possible file name collisions or just won't do it on principle.

They had business data they needed to access, so I took the easy way out, booted into the recovery partition, and reinstalled a case-sensitive Mojave. Migration Assistant then happily restored from the Time Machine backup.
 


Finally updated my MacBook Pro 9,1 from Mojave 14.4 to 14.6. I used the full Mojave Installer recently downloaded from the App Store. Started the install then, during the period where I think it does firmware updates, it hung.

After a lengthy period of time, I reluctantly restarted the machine, and it continued the update. However, upon logging in, it was using Build 18G95, so I ran the Supplemental Update to get to Build 18G103. Boot ROM version is 228.0.0.0.

Now, however, I'm having issues with a few applications crashing that never crashed before. Thinking this might be a macOS 14.6 issue, I rebooted from an external drive with Mojave 10.14.4. Same problem! Applications that ran fine earlier in the day are now crashing.

So I'm wondering if the firmware update was damaged. And, if so, how does one go about fixing it?
 


Finally updated my MacBook Pro 9,1 from Mojave 14.4 to 14.6. ... Thinking this might be a macOS 14.6 issue, I rebooted from an external drive with Mojave 10.14.4. Same problem! Applications that ran fine earlier in the day are now crashing. So I'm wondering if the firmware update was damaged. And, if so, how does one go about fixing it?
In answer to my own question... The Eclectic Light Company shows how to test the integrity of your EFI firmware:
The firmware checks out fine, which is a relief. So the problem remains: why an app that worked fine no longer works? That is an exercise for another day.

(Thanks, Eclectic Light Co. What a great site!)
 


Since upgrading to Mojave a while back, I have noticed that my 2018 Mac Mini keeps losing track of the Sound preferences, defaulting to my headset (even when it is not plugged in, which is usually the case) rather than to the Mac Mini speaker. Most recently it happened after I had a series of crashes (apparently caused by a flawed installer for the Calibre ebook software) that silenced the Mini. I often don't notice it, because I don't listen to much on the machine. Is anybody else seeing this? Any ideas how to fix it?
 


Since upgrading to Mojave a while back, I have noticed that my 2018 Mac Mini keeps losing track of the Sound preferences, defaulting to my headset (even when it is not plugged in, which is usually the case) rather than to the Mac Mini speaker. Most recently it happened after I had a series of crashes (apparently caused by a flawed installer for the Calibre ebook software) that silenced the Mini. I often don't notice it, because I don't listen to much on the machine. Is anybody else seeing this? Any ideas how to fix it?
When I hear of similar sound port issues, I recommend cutting a toothpick so the end isn't quite so sharp and jiggling it around in the port. If you actually use the port, sometimes the components contained therein get stuck in certain positions instead of releasing back to where they should be. The symptom is your Mac thinking you have a headphone or digital audio jack in the port. This issues goes back many years; Tim saves a penny on a component and we pay for it down the road.
 


Since upgrading to Mojave a while back, I have noticed that my 2018 Mac Mini keeps losing track of the Sound preferences, defaulting to my headset (even when it is not plugged in, which is usually the case) rather than to the Mac Mini speaker....
If you actually use the port, sometimes the components contained therein get stuck in certain positions instead of releasing back to where they should be. The symptom is your Mac thinking you have a headphone or digital audio jack in the port.
I have experienced this problem a few times in recent months, completely without any hardware changes, so it could have been software glitches. (I don't think I have experienced it recently.)
 


Since upgrading to Mojave a while back, I have noticed that my 2018 Mac Mini keeps losing track of the Sound preferences, defaulting to my headset (even when it is not plugged in, which is usually the case) rather than to the Mac Mini speaker....
I've had much the same problem since "upgrading" to Mojave a few months ago on a relatively new MacBook Pro, except in my case, 100% of the time I'm using the headphone jack to drive a stereo receiver and a pair of speakers. Once the MacBook Pro goes to sleep, there's a 50/50 chance that when it wakes up, no sound will come out of the external speakers, or the internal ones, either.

The only way I've found to get them going again is to use the speaker dropdown in the menu bar to choose the internal speakers, which instantly start to work again, then use the dropdown again to chose the external speakers.

I guess my next step, and maybe it should have been my first step, is to file a bug report with Apple.

#applequality #bugs
 


I am reluctantly transitioning to Mojave. Two things have stood out so far:

– Connected LAN server volumes are incredibly difficult to eject. Am constantly told the volume has open files on it and therefore is "busy" and will not unmount. Same exact server volumes are easily and quickly ejected with High Sierra macOS 10.13.x. (Obviously, I check to make sure no actual files on the server are in use by any of my apps before I attempt an eject.)​
– The default behavior for screenshots puts up a temporary thumbnail of the file in the lower right corner of the screen – not too annoying. If you're alert enough to click on this thumbnail, you enter the Screenshot editor, which allows you to dress up and tweak the screenshot before saving. But I'm baffled as to how to use this Screenshot editor (it's not a standalone app from what I can tell, even though it lives in the Utilities folder) after the file has been saved. In other words, how do I use this editor to open up existing .png files in order to edit them? Or, is this simply not an option?​
 


I am reluctantly transitioning to Mojave. ... Connected LAN server volumes are incredibly difficult to eject.
I've been plagued with Mojave not ejecting disks quickly from my cheese-grater Mac Pro. I've found that drives on USB 3 and FireWire are harder to eject than internal drives.

As with several of the last versions of macOS, Spotlight's mdworker is reluctant to stop indexing a drive. What's really infuriating is that I have all the backup drives listed in Spotlight's Privacy pane, yet Spotlight is still accessing these drives.
 


I am reluctantly transitioning to Mojave. Two things have stood out so far:
– The default behavior for screenshots puts up a temporary thumbnail of the file in the lower right corner of the screen – not too annoying. If you're alert enough to click on this thumbnail, you enter the Screenshot editor, which allows you to dress up and tweak the screenshot before saving. But I'm baffled as to how to use this Screenshot editor (it's not a standalone app from what I can tell, even though it lives in the Utilities folder) after the file has been saved. In other words, how do I use this editor to open up existing .png files in order to edit them? Or, is this simply not an option?​
The editor is built into "Quick Look", so:

Option 1: In the Finder, select the file you want to edit and press the spacebar to open the file in Quick Look, then click the pencil icon in the top right

Option 2: In the Finder, right-click/control-click. the file you want to edit and choose Quick Look xxx from the contextual menu, then click the pencil icon in the top right
 


As with several of the last versions of macOS, Spotlight's mdworker is reluctant to stop indexing a drive. What's really infuriating is that I have all the backup drives listed in Spotlight's Privacy pane, yet Spotlight is still accessing these drives.
Is it safe to simply kill -9 mdworker threads?
 


As with several of the last versions of macOS, Spotlight's mdworker is reluctant to stop indexing a drive. What's really infuriating is that I have all the backup drives listed in Spotlight's Privacy pane, yet Spotlight is still accessing these drives.
If you haven't done something like this already, you might want to run something like Sloth and search with it for your drives. Could be something else besides Spotlight holding it hostage.

Another option is to delete and add the drives back to Spotlight's Privacy pane. Or do the command line equivalents to disable Spotlight for each drive, delete the Spotlight index, etc. with mdutil.
 


Is it safe to simply kill -9 mdworker threads?
While it is safe to do this, it won't actually accomplish much. Most processes on the Mac use launchctl. One of the things launchctl does is to automatically restart any process under its care that exits unexpectedly.

You could disable Spotlight/mdworker completely using a launchctl command, but then you would have no Spotlight indexing on any drive.
 


The editor is built into "Quick Look", so:

Option 1: In the Finder, select the file you want to edit and press the spacebar to open the file in Quick Look, then click the pencil icon in the top right

Option 2: In the Finder, right-click/control-click. the file you want to edit and choose Quick Look xxx from the contextual menu, then click the pencil icon in the top right
Also the short and sweet Option 3:
Right-click/control-click then choose Quick Actions > Markup.
 


Amazon disclaimer:
As an Amazon Associate I earn from qualifying purchases.

Latest posts