Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Security Update 2020-007 for 10.14.6

@jbarley or others – if you had had the standalone updater available, how would you suggest getting past that "Unable to find installer resources" error?

Because just double-clicking the standaloner installer package and going through with the update this way gets me into the exact same trouble. Is this something like manually extracting pkg's and running them?
 
malthe123 said:
@jbarley or others – if you had had the standalone updater available, how would you suggest getting past that "Unable to find installer resources" error?

Because just double-clicking the standaloner installer package and going through with the update this way gets me into the exact same trouble. Is this something like manually extracting pkg's and running them?
Click to expand...
All I can suggest is the single boot drive method I used as in post #32.
 
  • Like
Reactions: malthe123
FarmerBob said:
Before this update fiasco I have never ever had any issues updating a DosDude1 install. After the 005/Safari update explosion my current working partition stopped booting on its own. I just get a blank screen.
Click to expand...
I feel your pain, That Security update stopped my ssd drive from booting on a spare MacBook air late 2010, therefor i did not install that on the "go to" Macbook from the same year. i guess this is a snafu or hinderance we can live with and still use Mojave on our unsupportive macs.
 
  • Like
Reactions: FarmerBob
aegisdesign said:
This update killed an external monitor attached to my 2012 Air. A Dell U2412M connected via DisplayPort. It wasn't being detected at all after the update and a couple of restarts.

I had to boot into safe mode (hold shift down on reboot) and it was detected then. Restarting normally seems to have worked.
Click to expand...
I still have found that my external hard drives are not initially recognized at boot up and if I don't run my rig for a week it is a slow bootup. I then shutdown and restart and then the drives are found. I will try safe mode when I come back tonight, Im on 2020-07 firmware and noticed this back at 2020-05 firmware. Also staying at safari 14.0 and ignored all other updates to keep my attachments.
 
FarmerBob said:
I'd like to try your script. How do I access it? The link is broken.
Click to expand...
Sorry about that ... I decided to take it down for some other reasons.
Easiest way to remember how to find the steps is that they are in Post 1 of the High Sierra on unsupported Macs Thread.
 
After installing this latest security update, my SD card is automatically ejected the moment I close the lid. It is a flush mount Transcend SD card, and prior to this update, closing the lid wouldn't eject it. I was able to use it, without having to load it again, but not anymore. Disk Utility does not see it.

The only way to re-load it, short of pulling it out and inserting it back in (which is a huge pain in the neck), is either restarting the computer, or putting it into sleep mode, from the main menu. Once I select "sleep", I have to leave it for at least 10-15 seconds (anything shorter than that won't do it). Once I wake it up, the SD card shows up again. Annoying bug, to say the least.

I wonder if there is any way of removing this latest update, and rolling it back to one of the previous ones. Also, I have backed up the system a few weeks ago, when everything was working fine. If I restore this backup, would that be enough, or do I have to re-install Mojave?

Thanks!
 
pb_1 said:
After installing this latest security update, my SD card is automatically ejected the moment I close the lid. It is a flush mount Transcend SD card, and prior to this update, closing the lid wouldn't eject it. I was able to use it, without having to load it again, but not anymore. Disk Utility does not see it.

The only way to re-load it, short of pulling it out and inserting it back in (which is a huge pain in the neck), is either restarting the computer, or putting it into sleep mode, from the main menu. Once I select "sleep", I have to leave it for at least 10-15 seconds (anything shorter than that won't do it). Once I wake it up, the SD card shows up again. Annoying bug, to say the least.

I wonder if there is any way of removing this latest update, and rolling it back to one of the previous ones. Also, I have backed up the system a few weeks ago, when everything was working fine. If I restore this backup, would that be enough, or do I have to re-install Mojave?

Thanks!
Click to expand...
Your system should have made an APFS snapshot before the update which you can return to within 24 hours of the update.
 
avz said:
Your system should have made an APFS snapshot before the update which you can return to within 24 hours of the update.
Click to expand...
I updated it about a week ago. Is it too late to roll it back?
 
pb_1 said:
I updated it about a week ago. Is it too late to roll it back?
Click to expand...
And I'm afraid the answer is yes, it is too late. I just checked the list of APFS snapshots, and the oldest one was created yesterday. Anything else I can do?
 
pb_1 said:
And I'm afraid the answer is yes, it is too late. I just checked the list of APFS snapshots, and the oldest one was created yesterday. Anything else I can do?
Click to expand...
I am afraid re-installation is the only way if you don’t have time machine backups.
 
avz said:
I am afraid re-installation is the only way if you don’t have time machine backups.
Click to expand...
I have a time machine backup from about 3 or 4 weeks ago, when everything was working fine. If I restore that one, will it revert back to whatever security update I had at that time, and ignore this latest one?
 
pb_1 said:
I have a time machine backup from about 3 or 4 weeks ago, when everything was working fine. If I restore that one, will it revert back to whatever security update I had at that time, and ignore this latest one?
Click to expand...
Yes that’s the whole point of time machine.
 
Update from my previous post of not having my external drives recognized at bootup, I switched both my esata cables to new ones and added a additional esata pci card to my rig. I then ran both my esata connections to two separate pci cards and now my drives are recognized at bootup. Both esata cables on the primary setup. High Sierra nor any other OS did this until I installed Mojave. I wonder if it is in the programming language in Mojave trying to switch out of older programming for 64 bit that makes certain hardware not perform. Makes one not want to update to a new OS anymore, like the 2020-05 debacle.
 
The funny thing is that now my SD card is seen without any problem, even though I haven't done a thing. It's been like that for the last 2 days. Go figure! :rolleyes:
 
  • Like
Reactions: AppleSmack
In my case, that would be more than a week, almost two weeks. But it's working now. 🤷‍♂️
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back