2016 MacBook Pro 15" touch-bar, Sierra 10.12.6. Following last night's updates, a wake-from-sleep (open up lid) initiates a reboot and the "your computer shutdown because of a problem" box with the invitation to send Apple a report (yes, please). The log seems to indicate a kernel panic. Once up and running, haven't had any surprise shutdowns.

This has happened about a half-dozen times so far. Did not notice (but will look for) the Bluetooth issue. To this date (going back to Mac OS 9), I have not ever had a post-update problem. The streak is over.

After installing the Security Update 2019-004 for High Sierra on a 2017 MacBook Pro with Touch Bar, if I close the lid of the computer to put it to sleep, then wake it by opening the lid, it will kernel panic 100% of the time. if I click on Sleep from the Apple menu, then wake it up by any means, it works just fine.

Interesting that iOS is shown as updated for the iPad Mini (1st Gen) from 9.3.5 to 9.3.6 but the iPod Touch 5th Gen is not included in that same upgrade. Both are (were?) limited to iOS 9.3.5. I checked the both my iPod and my iPad Mini and it didn't show 9.3.6 as an available upgrade for either. I wonder if they have not been actually released yet.

After installing the Security Update 2019-004 for High Sierra on a 2017 MacBook Pro with Touch Bar, if I close the lid of the computer to put it to sleep, then wake it by opening the lid, it will kernel panic 100% of the time. if I click on Sleep from the Apple menu, then wake it up by any means, it works just fine.

In my case (2016 Touchbar MacBook Pro 15" running macOS Sierra), I’m having to do a full restart, no matter how I put it to sleep. Now, after closing lid, presumably into Sleep, the case bottom gets very, very hot. I have to do a full Shut Down to keep this from happening.

FWIW, at every single bad restart, I’m doing the Send Report to Apple bit. Was going to call the local Apple Store, but I’m pretty sure, as of now, they’ll claim to know nothing of this and will do much of the same troubleshooting I’ve done, and will want to reinstall OS, etc. etc.

I also re-downloaded the updater from Apple website and started the Install .pkg, which ran for about 5 sec., then nothing.

In my case (2016 Touchbar MacBook Pro 15" running macOS Sierra), I’m having to do a full restart, no matter how I put it to sleep. Now, after closing lid, presumably into Sleep, the case bottom gets very, very hot. I have to do a full Shut Down to keep this from happening.
FWIW, at every single bad restart, I’m doing the Send Report to Apple bit. Was going to call the local Apple Store, but I’m pretty sure, as of now, they’ll claim to know nothing of this and will do much of the same troubleshooting I’ve done, and will want to reinstall OS, etc. etc.
I also re-downloaded the updater from Apple website and started the Install .pkg, which ran for about 5 sec., then nothing.

Same problem here with a 2018 MacBook Pro 15" after installing the latest Mojave security update. This happens after sleep overnight. I have not yet experienced forced shutdowns after closing the lid for a few hours and then awakening with finger touch upon opening. I have FileVault enabled.

Same problem here with a 2018 MacBook Pro 15" after installing the latest Mojave security update. This happens after sleep overnight. I have not yet experienced forced shutdowns after closing the lid for a few hours and then awakening with finger touch upon opening. I have FileVault enabled.
This is likely a bug that will be fixed shortly with another update.

Users are reporting that putting an affected MacBook Pro to sleep, such as by closing its lid, causes it to suffer a kernel panic and reboot. The only solution to this, other than preventing it from going to sleep, is to shut the Mac down instead. Which isn’t what you bought a MacBook Pro for, exactly.

If your Mac is affected by this, you should contact Apple Support, who by now should now what’s going on, and when the fix is coming.

Apple has also now pulled one of the BridgeOS updates necessary for the Mojave 10.14.6 update for certain models of Mac. Users who haven’t applied one of these recent updates are therefore wisest waiting now until Apple has addressed these problems properly.

Users are reporting that putting an affected MacBook Pro to sleep, such as by closing its lid, causes it to suffer a kernel panic and reboot. The only solution to this, other than preventing it from going to sleep, is to shut the Mac down instead. Which isn’t what you bought a MacBook Pro for, exactly. ...

In view of the removal of both the recent Security Updates 2019-004 for Sierra and High Sierra, it is probably wisest not to apply any of these latest macOS updates until Apple has resolved these issues – that now includes the Mojave 10.14.6 update. ...

I'm not seeing a sleep problem on four Sierra security updates on older machines:

iMac 12,2

iMac 13,2

Mac Pro 5,1

MacBook Pro 8,2

Knock on wood. I explicitly waited a few days before applying, too, in case of trouble reports. I always find it curious that companies say they test extensively before releasing, but upon release, instantly a flood of user complaints come out with such basic problems.

So I found an interesting issue: attempting to update to macOS 10.14.6 using the downloaded Combo updater on a 2018 Mac Mini on an isolated network (internal only, no internet access), the update fails.

Looking at the Log, it identifies that it needs a bridgeOS update (10.16.6568.0.0.0 or newer) but can't get it.

I'm contacting Apple Support now to find out how they suggest I update completely offline systems like these.

No problems so far with this one. I updated a 2015 iMac 5K (27-inch) and a 2018 MacBook Pro (Touch Bar) with this update. Both of these machines have High Sierra 10.13.6. While it did finally complete the update, the update was not smooth.

On the iMac, the update took almost an hour to finish and restarted at least 4 times. After that, it appears to be working fine.

On the MacBook Pro, the update went all the way through (with 2 or 3 restarts), then rebooted and appeared to have failed, as evidenced by the fact that it showed up again in Software Update. There was no warning or indication that the update failed. This update contained both the 2019-004 security update and a Safari update. The Safari update worked but the security update did not. So I ran it again, this time with only the security update. It ran through again, this time with no restarts, and appears to have worked.

Updated a 2015 iMac 5K to macOS 10.14.6 this morning with no issues — a couple of restarts, but it was done in about 10-15 minutes. I did not see anything mentioning the 2019-004 Security Update, but perhaps this is because I waited until I saw that it was pulled from distribution.

Apple contractors 'regularly hear confidential details' on Siri recordings
Although Apple does not explicitly disclose it in its consumer-facing privacy documentation, a small proportion of Siri recordings are passed on to contractors working for the company around the world. They are tasked with grading the responses on a variety of factors, including whether the activation of the voice assistant was deliberate or accidental, whether the query was something Siri could be expected to help with and whether Siri’s response was appropriate.

... The whistleblower said: “There have been countless instances of recordings featuring private discussions between doctors and patients, business deals, seemingly criminal dealings, sexual encounters and so on. These recordings are accompanied by user data showing location, contact details, and app data.”