macOSSystemStatus Archives

Mojave 2019-001 Security Update Causing Data Loss (UPDATE!)

MrMacintosh.com - Mojave 2019-001 Security Update Causing Data Loss if Interrupted - 2019-001 FileVault can't login — Mojave 2019-001 Security Update Causing Data Loss if Interrupted – 2019-001 FileVault can’t login

UPDATE: 01/22/20 – This problem was reported as FIXED in the latest Mojave 10.14.6 Security Update 2019-002 (18G2022) & Catalina 10.15.2 Update. The fixed T2 BridgeOS version is 17.16.12551. Apple did not list the fix in the 10.15.2 or 2019-002 Security Update notes but DID put them in the AppleSeed 10.15.2 Beta 2 Update Notes. I can’t post them here, but you can check the AppleSeed Patch Notes portal or you can contact Apple Support to confirm if you need further information.

Final Verdict – After further investigation, the problem was NOT the user’s fault. After more users reported what happened during the update I found that the update stalled out during the BridgeOS update phase. The black screen is only supposed to last 2-5 minutes. In reality, the update stopped and the Mac would be on the same black screen for up to 1 hour. The user had NO CHOICE but to shut down the Mac. By that time it was already too late.

Users are Unable to Unlock FileVault 2 if the Mojave 2019-001 Security Update is Interrupted.

This issue was first reported about one month ago on the MacAdmins Slack. It was reported that after some users installed the Mojave 10.14.6 Supplemental Update #3, they were unable unlock their Mac with the FV2 Password or PRK. The issue was not widely reported though so it was thought to be a fluke.

Mojave 2019-001 Security Update

All this changed when the Mojave 2019-001 Security Update was released. MacAdmins started to report the problem again.

I have a Mac that just finished installing the 2019-001 Security Update. I can’t get past the FileVault 2 screen with the password or Personal Recovery Key.
MacAdmin User Report

More and more MacAdmins are starting to report this devastating 2019-001 FileVault can’t login issue.

Who, What, When, Where & Why Index

1. Affected Mac Hardware = T2 Machines
2. Affected macOS Build Versions UPDATE!
3. FileVault 2 Encrypted Machines Only. UPDATE!
4. Evidence? Reports of a Black Screen Followed by User Power Off
5. Can’t Login with FV2 Password or PRK
6. Investigation – Encrypted: ERROR -69808 – Confirmation?
7. Workarounds?
8. Should I block this update?
9. Will Apple fix this issue?
10. Issue Links
11. Credits

1. Affected Mac Hardware = T2 Machines

I have looked over many reports on the Apple Discussion Forums and MacAdmins Slack Chat and Jamf Nation Posts. It looks like only T2 Equipped Machines.

2019 MacBook Air
2018 MacBook Air
2019 15″& 13″ MacBook Pro
2018 15″ & 13″MacBook Pro
2018 Mac Mini
2017 iMac Pro

2. Affected macOS Build Versions

This issue affects the following macOS Updates.

(18G103) Mojave Supplemental Update #3 – 9/26/19
(18G1012) Mojave Security Update Released on 10/29/19
(17G9016) High Sierra Security Update 2019-006 – 10/29/19
(17G9016) High Sierra Security Update 2019-005 – 9/26/19

3. FileVault 2 Encrypted Machines Only. UPDATE!*

UPDATE! – We now have two separate reports of this happening when the Mac is NOT FV2 Encrypted.

If your Mac is unencrypted you should be fine.

* I have not seen any reports as of 11/09/19, that include a T2 Mac that was not encrypted.

4. Evidence? Reports of a Black Screen Followed by User Power Off

After the reports started to roll in, we started to investigate. One of the common threads is that users reported a problem with the update during the install.

Black Screen – Users reported that the Mac looked like it powered down. They would try to power it back on, interrupting the install process.
Black Screen with Apple Logo & Progress Bar Stuck – While the Update was installing, some users have reported that the update hung or stalled out. This was followed by a power down.

5. Can’t login with FV2 Password or PRK?

After the user powered down the Mac, they reported the following.

Can’t login past FileVault 2 with my Password.
Can’t boot the Mac up with the PRK.

In this situation the Mac is unable to boot up at all. The only thing that the user can do is boot to the Recovery Partition or Internet Recovery.

6. Investigation – Encrypted: ERROR -69808 Confirmation?

After booting to the Recovery Partition we tried to first mount the disk.

This did NOT work!

You can confirm the issue by typing in diskutil ap list

Volume disk4s1
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk4s1 (No specific role)
    |   Name:                      Macintosh HD (Case-insensitive)
    |   Mount Point:               Not Mounted
    |   Capacity Consumed:         171872342016 B (171.9 GB)
    |   Encrypted:                 ERROR -69808

We would expect that the Encrypted status line should be:

FileVault:                 Yes (Unlocked) 
or
FileVault:                 Yes (locked)

Note the Encrypted line. It should say LOCKED or UNLOCKED. Instead you get ERROR -69808

xartutil CLI Binary

You can also use the xartutil binary to check for the Encryption Keys.

xartutil --list

You should see 2 entries listed = This is a normal output

Total Session Count: 2

If you see

xartutil: ERROR: No supported link to the SEP Present = Not a T2 Mac

If you see

Total session count: 0 = The Encryption Keys are Lost.

7. Workarounds?

Currently no known workaround is available.

We have tried multiple things.

Mounting the disk in the Recovery Terminal
Mounting the disk in Disk utility
Target Disk Mode

8. Should I block this update?

After Reviewing Multiple Reports, the issue only looks to have affected a small number of users. One MacAdmin said out of 150 machines, the issue only affected 2 of them.

I tested this issue out on a 2018 MacBook Pro.

Powered Off during the first Black Screen.
Powered Off during the second Black Screen
Powered Off during the first Security Update Progress Bar
Powered Off during the second Security Update Progress Bar

The BridgeOS Update and the 2019-001 Security Update installed successfully!

If you move forward with the update you can ask users not to interrupt the install process.

9. Will Apple fix this issue?

The black screen BridgeOS update process has been around since 2018. Something must have changed in the 2019-001 Security Update.

If you have this issue please report it to Apple ASAP.

10. Issue Links

TidBits – Adam Engst

https://tidbits.com/2019/11/06/dont-interrupt-security-update-2019-001-mojaves-installation/

Apple Discussion Form

Jamf Nation

https://www.jamf.com/jamf-nation/discussions/33844/security-update-2019-001-mojave

11. Credits

Jamf Nation User jhalvorson for the diskutil ap list output
Jamf Nation User franton for the xartutil command.
All MacAdmins Slack users who answered multiple questions that I had since I do not have a problem Mac to test with.

12. Contact Me

Please Contact Me if you have more information on this issue.

2019-001 FileVault can’t login

10.14.6 Update Causes Kernel Panic When Using FaceTime Camera (UPDATE!)

MrMacintosh.com - 10.14.6 Update Causes a Kernel Panic When Using the Built-In FaceTime Camera. — *10.14.6 Update Causes a Kernel Panic When Using the Built-In FaceTime Camera.*

NEW UPDATE: 4/08/20 – I am getting multiple reports that users are having issues applications that use Hardware Accelerated Video with the latest 10.14 and 10.13 2020-002 Security updates. The system will 100% freeze up during video conference, video or heavy app usage and you will have to hard power down. I posted all the new information about the freezing issue in a new article here – https://mrmacintosh.com/2020-002-update-causes-some-macs-to-freeze-up-while-using-vid-conf-apps/

FINAL UPDATE: 1/22/20 – Multiple users have contacted me to let me know that the latest macOS Mojave 10.14.6 Security Update 2019-002 (18G2022) has fixed the issue for them! The T2 BridgeOS version is 17.16.12551 or newer.

UPDATE: 10/03/19 – I am hearing from readers and commenters that Zoom has confirmed that this issue is fixed in macOS Catalina 10.15. This could very well mean that we will not get a fix for Mojave. 🙁

UPDATE: 9/27/19 – Apple just released 10.14.6 Supplemental Update #3, but this does NOT fix the FaceTime Camera bug. – mrmacintosh.com/macos-updates-9-26-19-mojave-10-14-6-3-10-13-10-12-2019-005/

UPDATE: 9/18/19 – Added additional workarounds.

After Apple released the 10.14.6 Update, some users of 2019 & 2018 15″ MacBook Pros started to report Kernel Panics when using the Built-In FaceTime Camera.

I reported on a similar issue about a month ago when the 2019-004 Security Update for High Sierra and Sierra started causing a Kernel Panic after waking from sleep.

In this article, I will give you the lowdown of the issue. In the end, I will also give you a workaround until Apple releases a fix.

If you are interested in the 2018-004 Security Update Wake from Sleep issue you can read my report Below.

mrmacintosh.com/apple-pulls-2019-004-high-sierra-and-sierra-security-updates-after-kernel-panics/

Let’s dive right in and see what’s going on here.

Who, What, When, Where & Why Index

1. Affected macOS 10.14.6 Build Versions
2. Affected Mac Hardware
3. This issue does NOT affect most 10.14.6 users.
4. Kernel Panic Reports
5. Why rolling back will NOT work.
6 Built-In FaceTime Camera
7. Camera Software that causes the KP’s
8. Workarounds
9. Will Apple fix this issue? 10.14.6 Supplemental Update #3 ?
10. 10.14.6 FaceTime Camera Kernel Panic Links
11. 3rd Party Vendor Responses

1. Affected macOS 10.14.6 Build Versions

This issue affects all macOS Mojave 10.14.6 Build Versions.

(18G84) Update Released July 22nd, 2019
(18G87) Supplemental Update #1 Released August 5th, 2019
(18G95) Supplemental Update #2 Released August 26th, 2019

2. Affected Mac Hardware

I have looked over many reports on the Apple Discussion Forums and MacAdmins Slack Chat. It looks like the only affected Mac Hardware is…

MacBookPro15,1
2018 15″ MacBook Pro
2019 15″ MacBook Pro

If you have the issue on a 2018-2019 13″ MacBook Pro/Air Please do not hesitate to Contact Me.

3. This issue does NOT affect most 10.14.6 users.

I tried time and time again to reproduce this issue. Having both a 2018 and 2019 15″MacBook Pro for testing, I figured that I would be able to reproduce the issue. Having FaceTime.app open for hours and using Zoom Conference call for 4 hours, produced zero crashes. This could be a clue as to an additional cause on the reported users computers, but I’m not sure.

4. Kernel Panic Reports

What do the Kernel Panic Reports look like? Looking over the report it looks like BridgeOS is crashing. Below is a sample report.

{“caused_by”:”unknown”,”macos_version”:”Mac OS X 10.14.6 (18G84)”,”os_version”:”Bridge OS 3.6 (16P6568)”,”macos_system_state”:”running”,”incident_id”:”6DCB8540-C363-4FC9-999E-9E38E276621A”,”timestamp”:”2019-07-25 15:44:33.33 +0000″,”bug_type”:”210″} { “build” : “Bridge OS 3.6 (16P6568)”, “product” : “iBridge2,3”, “kernel” : “Darwin Kernel Version 18.7.0: Tue Jun 25 21:35:19 PDT 2019; root:xnu-4903.270.47~9\/RELEASE_ARM64_T8010”, “incident” : “6DCB8540-C363-4FC9-999E-9E38E276621A”, “crashReporterKey” : “c0dec0dec0dec0dec0dec0dec0dec0dec0de0001”, “date” : “2019-07-25 15:44:33.08 +0000”, “panicString” : “panic(cpu 0 caller 0xfffffff01bca5bec): \”void AppleEmbeddedPCIeUpLinkMgmt::_linkInterruptAction(IOInterruptEventSource *, int): \” \”A link timeout has been seen after 100000 microseconds and 49999 iterations.\”@\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/AppleEmbeddedPCIeUpLinkMgmt\/AppleEmbeddedPCIeUpLinkMgmt-76.260.2\/AppleEmbeddedPCIeUpLinkMgmt.cpp:3982\nDebugger message: panic\nMemory ID: 0x6\nOS version: 16P6568\nmacOS version: 18G84\nKernel version: Darwin Kernel Version 18.7.0: Tue Jun 25 21:35:19 PDT 2019; root:xnu-4903.270.47~9\/RELEASE_ARM64_T8010\nKernelCache UUID: DB4E28E6354462E8ADC412A804EB32E1\nKernel UUID: 9FC93C85-B7C5-3723-92B7-293273AB9C4F\niBoot version: iBoot-4513.270.14\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x0\nx86 Power State: 0x0\nx86 Shutdown Cause: 0x5\nx86 Previous Power Transitions: 0x40504000200\nPCIeUp link state: 0x94721611\nPaniclog version: 13\nKernel slide: 0x000000001559c000\nKernel text base: 0xfffffff01c5a0000\nmach_absolute_time: 0xa75d527f88\nEpoch Time: sec usec\n Boot : 0x5d37ad8f 0x000c3155\n Sleep : 0x5d39a45e 0x000defae\n Wake : 0x5d39ab5f 0x0006d1c2\n Calendar: 0x5d39ce41 0x000cb6eb\n\nPanicked task 0xffffffe000881680: 8160 pages, 207 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe000c4b3e0, backtrace: 0xffffffe01633b590, tid: 280\n\t\t lr: 0xfffffff01c6ae2a4 fp: 0xffffffe01633b620\n\t\t lr: 0xfffffff01c79b5a4 fp: 0xffffffe01633b760\n\t\t lr: 0xfffffff01c679610 fp: 0xffffffe01633b770\n\t\t lr: 0xfffffff01c6ad848 fp: 0xffffffe01633bae0\n\t\t lr: 0xfffffff01c6adbc0 fp: 0xffffffe01633bb20\n\t\t lr: 0xfffffff01c6ada14 fp: 0xffffffe01633bb40\n\t\t lr: 0xfffffff01bca5bec fp: 0xffffffe01633bbd0\n\t\t lr: 0xfffffff01cb35fc4 fp: 0xffffffe01633bc10\n\t\t lr: 0xfffffff01cb34ad8 fp: 0xffffffe01633bc50\n\t\t lr: 0xfffffff01cb3434c fp: 0xffffffe01633bc90\n\t\t lr: 0xfffffff01c684614 fp: 0x0000000000000000\n\n”, “panicFlags” : “0x2”, “otherString” : “\n** Stackshot Succeeded ** Bytes Traced 112560 **\n”, “macOSPanicFlags” : “0x0”, “macOSPanicString” : “BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available”, “memoryStatus” : {“compressorSize”:0,”compressions”:0,”decompressions”:0,”busyBufferCount”:0,”pageSize”:16384,”memoryPressure”:false,”memoryPages”:{“active”:8141,”throttled”:0,”fileBacked”:10933,”wired”:10886,”purgeable”:0,”inactive”:5798,”free”:3029,”speculative”:2344}},

5. Why rolling back will NOT work.

You might think, what if I roll back to a previous version of Mojave like 10.14.5? In the past, this might have worked! It will NOT work when the issue is caused by BridgeOS. Apple has made it impossible to roll back the version of your T2 BridgeOS.

After you updated to 10.14.6, your BridgeOS was also updated. If you try to reinstall 10.14.5, this version will still work but the newer BridgeOS will still be installed. This is also why if you got your MacBook Pro replaced at the Apple Store, the issue could STILL be happening to you.

The only way you could get this to work is if you got ahold of a 10.14.5 system on BridgeOS version 16.16.5601 or lower.

6. Built-In FaceTime Camera

The crash ONLY happens when you use the MacBook Pro Built-In FaceTime Camera. It does not matter what you do. From the many reports that I have looked through, the crash could happen the very second you activate the camera or 2 hours after. Most of the reports seem to be from 10min to 1 hour of use.

7. Camera Software that causes the KP’s

The following software can cause your Mac to Kernel Panic

FaceTime.app
WebEx
Zoom
Slack
Google Hangouts
Skype
Teams
gotomeeting
BlueJeans

You get the idea, basically ANY application that uses the Built-In FaceTime Camera.

8. Workarounds

Most issues like this have some type of workaround. Sometimes a workaround is found by accident or after hours of testing. This time around a few users on the Apple Discussion Forums found at least one workaround.

Plug in an additional Web Camera. This could be a USB Web Camera or even a monitor with a built-in camera like the Apple 27″ ThunderBolt Display.
You don’t even have to use the secondary camera. For some reason with the second camera plugged in reports say that you can use the built-in FaceTime Camera without crashes. Found by user edgonz305
Run a Windows Fusion VM with Skype in that VM. The problem does not occur using integrated camera. This is not a solution for everyone, but for me it works better than using an external camera. Additional workaround from OaSOakover
You can prevent the crashes by just disabling video on the meeting. (This one is pretty obvious if you don’t need to use the FaceTime Cam)
macOS Catalina Beta may fix the issue. Reported by Commenter Dave!

9. Will Apple fix this issue? 10.14.6 Supplemental Update #3 ?

With the end of support coming up fast for Mojave, will Apple fix this issue? I think the answer is YES. This is coming from reports that Apple DOES know about the issue and is still investigating. My guess is that Apple will release one final Supplemental Update to fix this.

If you or any of your users are having this issue, please contact Apple Support.

10. 10.14.6 FaceTime Camera Kernel Panic Links

6 Page Apple Discussions Forum Post https://discussions.apple.com/thread/250524925

15 Page Apple Discussions Forum Post https://discussions.apple.com/thread/250546239

11. 3rd Party Vendor Responses

Zoom Response -“We found it not only influences ZOOM but also FaceTime, Skype and other Camera involving Apps, we are still working with Apple to fix it but currently as a workaround, please turn off your video when joining ZOOM meetings or use external camera by USB.”

If you have any information on the 10.14.6 FaceTime Kernel Panic issue that you would like added to this article, please Contact Me.

10.14.4 Update breaks “Update Keychain Password” + Workaround

MrMacintosh.com - 10.14.4 Update breaks Update Keychain Password — 10.14.4 Update breaks Update Keychain Password

UPDATE: 11/17/19

This issue was fixed in 10.15.0, only to break again in 10.15.1! I’m covering the issue again here.

mrmacintosh.com/10-15-1-update-breaks-update-keychain-password-again-workaround/

If you are here for the 10.15.1 issue, you can follow the same 10.14.4 workaround instructions below.

UPDATE: 07/31/19

This will probably be the final update. Sadly the issue is NOT fixed in 10.146. Even worse, this will be the final update and the issue will not be fixed in Mojave. I submitted this issue right after it was found in 10.14.4 and it’s just a bummer that this will never be fixed in Mojave. The only good news I can give you is that this is fixed in macOS Catalina 10.15.

UPDATE: 07/09/19

The AD Mobile Account option to “Update Keychain Password” when resting your password outside the Mac is still broken in macOS Mojave 10.14.5. This issue is still not fixed in current 10.14.6 Beta! Be sure to contact Apple if you haven’t already done so!

10.14.4 Update password fixes/problems

I really like the 10.14.4 update, trust me I do! It arrived with so many fixes that have really helped MacAdmins. The problem is, it also broke a few things. Just when I thought we found all the fixes/problems a new one pops up. If you have been following along, this is now my 4th article on password fixes/problems in the 10.14.4 update. Lets quickly review

1. 10.14.4 will now sync your AD password to FileVault if forgotten
2. 10.14.4 update fixes AD Account/FileVault password change sync
3. 10.14.4 Update breaks local account password reset when using FileVault Recovery Key
4. 10.14.4 Update breaks “Update Keychain Password” + Workaround

10.14.4 Update breaks “Update Keychain Password” process for Ad Mobile Accounts.

This issue affects Active Directory Mobile Account users. If you use Mobile Accounts you have seen this message before.

Update/create keychain message — Which option should I pick? In 10.14.4 it doesn’t matter they both create a new keychain!

You will only see this message if you change your Active Directory Password outside the Mac. An example of this would be if you changed your AD password on a 2nd Mac, Windows PC or Web Portal. Logging in with the new password will sync that new password down to the Macs local cache but can NOT change the keychain password without the OLD password. You can click “Create New Keychain” and brand new login keychain will be created. But what if you have Xcode Developer Certs and Private keys or Wifi certs? In this case you need your old keychain intact.

Clicking “Update Keychain Password” just creates a new login keychain.

If you click “Update Keychain Password” you should see this. (10.14.0-10.14.3)

Update Keychain Password dialog — What you should see in 10.14.0-10.14.3

Instead, after clicking the update button you will not see this message and you are now at the desktop. If you open up keychain access you will see that your login keychain was wiped out.

Workaround – Find renamed keychain, change password and restore.

Good news, I have a workaround for you. The old login Kkeychain luckily still remains in ~/Library/Keychains

We will have to perform a few steps to restore your old login keychain

1. Find renamed keychain – located in ~/Library/Keychains and called login_renamed_1.keychain-db
2. Change password of login_renamed_1.keychain-db from old to new
3. Remove login.keychain-db
4. Rename login_renamed_1.keychain-db to login.keychain-db
5. Restore login.keychain-db to Keychain Access.app
6. Log out and back in.

1. Find renamed keychain

The old keychain is located in ~/Library/Keychains and called login_renamed_1.keychain-db

Your old login keychain and the new one that was just created.

2. Change login_renamed_1.keychain-db password

You used to be able to change the login keychain password through Keychain Access. This is no longer possible.

What if we clicked “Add Keychain” and tried to add the renamed keychain then try to change the password?

This looks promising but after clicking “change password for keychain login_renamed” nothing happens. I then tried to unlock it with the old password.

After unlocking I attempted to change the password again.

Still no go! After clicking change password nothing happened. At this point, I thought I was out of luck.

Enter CLI command security

Never give up a fight without visiting the Command Line Interface! The CLI can be your best friend. Let’s take a look at the security man page and see if anything will help us. Open terminal and type in man security

set-keychain-password Set password for a keychain.

Oh ya, now we are talking! Let’s take a look at the options.

Perfect, just what we are looking for. Lets try it out.

sudo security -v set-keychain-password /path_to_user_keychain

You will be prompted for your old and new password. Now that the old keychain has the same password as your AD account we can move it back into Keychain Access.app.

3. Remove login.keychain-db

Now we can just delete the empty login keychain.

Right click on login and select Delete Keychain “Login” then click “Delete References & Files”. You should now only have Local Items, System and System Roots.

4. Rename login_renamed_1.keychain-db to login.keychain-db

We now need to rename login_renamed_1.keychain-db to login.keychain-db. You can either do this in keychain access or in the finder. Let’s rename in the finder. Click once on login_renamed_1.keychain-db and change it to login.keychain-db.

5. Restore login.keychain-db to Keychain Access.app

Now all we need to do is add our old keychain back to Keychain Access.app. Right click in the keychain section and select “Add Keychain”.

Navigate to ~/Library/Keychains/login.keychain-db and select it. You will now see login in the keychain box! At this time it will be locked. You can test unlocking it now. Right click on login and select “Unlock Keychain login”

You will now be prompted to enter in your current password.

6. Log out and back in to confirm

You have now restored your old keychain. Log out and then back in to confirm. You are now good to go!

As always, we need to submit a bug report to Apple.

I can not stress how important this is. The more reports we put in the higher priority the issue gets. We are also running out time and only have about 3 weeks before 10.14.5 is released.

I have submitted a bug report to Apple at bugreport.apple.com. I also created an open radar at openradar.appspot.com

https://openradar.appspot.com/radar?id=4962927241068544

Credits

Thanks to hawkzhang45 from JAMF Nation forum for calling this issue out. Also to m.entholzner for conformation and submitting an Apple Enterprise Ticket. You can read the original thread here.

10.14.4 update keychain password

Introducing a macOS System Status & Version Info page for MacAdmins

I have been thinking for a while now of creating a one-stop-shop for macOS System Status & Version Info. The idea behind this is a page you can visit that has the latest information, from what’s broke in the latest macOS release to what forked build number the new 2019 iMac has. This page will follow the general idea of Apple’s System Status Page but include a lot more information.

I have received some really great feedback on my Updated List of Notarization Links page and how it has helped many MacAdmins. This page will be an extension on that. With the amount of work we are all dealing with, it’s very difficult to keep up. I can’t tell you how many times I have spent hours troubleshooting an issue only to find out that it was a known problem. If this page can save you that lost time it will be worth the effort!

Mojave Core System Status

This section will cover critical core macOS system functions. If something major is not working, it will be listed here. Most of the system functions listed are very important to MacAdmins. I verify each section myself and also include reports from other sources. NOTE: Be sure to verify in your own lab, I am providing a “best effort”service.

macOS System Updates/Versions

In the 2nd section, I will list the current Mojave Installer and the current Beta. Forked installers will also be listed. (A forked macOS installer is a special app installer that is only used for a new Mac Hardware releases). BridgeOS and built-in security versions (Malware Removal Tool, XProtect, Gatekeeper) are also listed.

Core Application updates/versions

In the final section, I included a list of core macOS Applications. The table contains size of the update, release date and patch notes.

Improvements ?

Should I add other sections? Add older OS’s like High Sierra or Sierra? What about including issues in previous Mojave Point releases? Could the layout be better? Let me know.

Status Page Location

You can find the new status page in the navigation bar in the upper right. You can jump to the new macOS SystemStatus page using this link.

Users are Unable to Unlock FileVault 2 if the Mojave 2019-001 Security Update is Interrupted.

Mojave 2019-001 Security Update

Who, What, When, Where & Why Index

1. Affected Mac Hardware = T2 Machines

2. Affected macOS Build Versions

3. FileVault 2 Encrypted Machines Only. UPDATE!*

4. Evidence? Reports of a Black Screen Followed by User Power Off

5. Can’t login with FV2 Password or PRK?

6. Investigation – Encrypted: ERROR -69808 Confirmation?

xartutil CLI Binary

7. Workarounds?

8. Should I block this update?

9. Will Apple fix this issue?

10. Issue Links

11. Credits

12. Contact Me

After Apple released the 10.14.6 Update, some users of 2019 & 2018 15″ MacBook Pros started to report Kernel Panics when using the Built-In FaceTime Camera.

Who, What, When, Where & Why Index

1. Affected macOS 10.14.6 Build Versions

2. Affected Mac Hardware

3. This issue does NOT affect most 10.14.6 users.

4. Kernel Panic Reports

5. Why rolling back will NOT work.

6. Built-In FaceTime Camera

7. Camera Software that causes the KP’s

8. Workarounds

9. Will Apple fix this issue? 10.14.6 Supplemental Update #3 ?

10. 10.14.6 FaceTime Camera Kernel Panic Links

11. 3rd Party Vendor Responses

UPDATE: 11/17/19

UPDATE: 07/31/19

UPDATE: 07/09/19

10.14.4 Update password fixes/problems

10.14.4 Update breaks “Update Keychain Password” process for Ad Mobile Accounts.

Clicking “Update Keychain Password” just creates a new login keychain.

Workaround – Find renamed keychain, change password and restore.

1. Find renamed keychain

2. Change login_renamed_1.keychain-db password

Enter CLI command security

3. Remove login.keychain-db

4. Rename login_renamed_1.keychain-db to login.keychain-db

5. Restore login.keychain-db to Keychain Access.app

6. Log out and back in to confirm

As always, we need to submit a bug report to Apple.

Credits

Table of Contents

Mojave Core System Status

macOS System Updates/Versions

Core Application updates/versions

Improvements ?

Status Page Location