After imaging 2016 MBP with a 10.12.1 image (built from the same model) the computer boots up and I immediately get a white square with a spinning gear for several minutes. Then I get the error above. There's no indication of what it's doing and I can't access the log to see what's wrong. The Mac is completely unusable because I have to shut it down or click Try again that never works. What the heck is going on? Anyone know what this is?
Page 2 / 3
Just to keep this thread updated like I said I would... I've made some headway.
Referencing this post above: https://www.jamf.com/jamf-nation/discussions/22727/critical-update-won-t-install-after-imaging#responseChild137386
I can say we have enabled the following URLs at our firewall, as well as *.apple.com over DNS to 17.x.x.x only and touchbar Macs now work normally, with one exception. Here are the URLs:
gs.apple.com
gg*.apple.com
skl.apple.com
albert.apple.com
phobos.apple.com
swscan.apple.comOut of those, gs.apple.com seems to be the main URL that the touchbar uses. The one exception I mentioned is erasing the parent drive and completely wiping the disk. If you just erase the Macintosh HD partition, the touchbar partition remains and it can still reach out to Apple for only activation or apart of any OS update from 10.12.x to 10.12.x.
I am still getting the error with completely wiping the drive and putting a fresh OS image on it but wanted to at least update with what I had so far. As I get a solution for that, I will update this thread again.
Hi guys,
Not sure if anything has been done, but today I was able to update 2 new Touchbar Macbooks out of the box and I didn't have this problem (it had been a problem for me up until now). It's possible Apple have changed their update procedure?
Thought it worth mentioning.
@perrycj Do you think there is a workaround besides firewall exceptions for those of us in a very secure environment?
I have been scouring the web for other blog posts etc... on this topic and so far, you have the most helpful solution here with the firewall exceptions. Thank you for that.
@clegger06 I do not, no. Those URLs seem to be needed. I also work in a highly secure, government regulated environment.. so it can be done.
If you're on Slack and in the Macadmins channel, you can PM me there at @cp. And then we can talk more.
Apple finally posted a TechNote on this behavior HT207567
If you’re using a network with a firewall. Make sure that you can access to the following hosts on the corresponding ports:
Server TCP Port
gg.apple.com 80 and 443
gnf-mdn.apple.com 443
gnf-mr.apple.com 443
gs.apple.com 80 and 443
ig.apple.com 443
skl.apple.com 443
At least it states explicitly that a proxy cannot be used. I'll be able to take that to our network security people to justify the need for an un-proxied port in our setup lab. If they actually do it or not is another story.
@nateboggs Even though I marked your reply as a solution, I'm keeping hope alive for another possibility.
we're starting to see this too. It's going to be a pain to get the FW opened up. Clearly Apple needs to fix this ASAP.
We have a proxy on our network and it works fine with those URLs open on the firewall. Both with a re-image or an OS update from 10.12.x to 10.12.4.
It's safe to say that this is the solution from Apple so I'm not sure you will see another "official" workaround from them.
yeah I get it... but seems like its a pretty poorly engineered process. It also seems sporadic, which doesn't make sense. Some of our machines work fine. Fact of the matter is, Apple sure doesn't make things easy for business. Our firewalls are a bit antiquated, and don't accept URLs...
yeah I get it... but seems like its a pretty poorly engineered process. It also seems sporadic, which doesn't make sense. Some of our machines work fine. Fact of the matter is, Apple sure doesn't make things easy for business. Our firewalls are a bit antiquated, and don't accept URLs...
Hey guys, please help a desperate soul, I got this update loop on my MPB with Touchbar and tried all kinds of clean install without success. That's the log I got. I'm using home wifi. I can't ping gs.apple.com neither by wifi or 4G. What else should I try?
2017-04-06 16:46:36.409949-0700 0x885 Error 0x8000000000000a85 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Couldn't find memboot image in ESP: file:///Volumes/EFI/EFI/APPLE/EMBEDDEDOS/combined.memboot
2017-04-06 16:46:36.410628-0700 0x884 Default 0x8000000000000a83 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSSerial]
2017-04-06 16:46:36.410712-0700 0x885 Default 0x8000000000000a83 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Unmounting ESP
2017-04-06 16:46:36.560141-0700 0x885 Fault 0x8000000000000a88 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Boot failed with error: Error Domain=EOSErrorDomain Code=1201 "No memboot image was found in the EFI system partition." UserInfo={NSLocalizedDescription=No memboot image was found in the EFI system partition.}
2017-04-06 16:46:36.560142-0700 0x885 Activity 0x8000000000000a88 195 EmbeddedOSInstallService: (EmbeddedOSInstall) %@ failed with error: %@%@
2017-04-06 16:46:36.560237-0700 0x885 Default 0x8000000000000a83 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Diagnostic summary: Boot ((null) -> (null) ((null)), preflighted = 0, prod fused = 1, user auth = 0, retries = 0, after boot failure = 0, failing phase = 20, client = (null), uuid = 2E91FCB6-572C-4427-BC2B-E6B2EA132B98): Error Domain=EOSErrorDomain Code=1201 "No memboot image was found in the EFI system partition." UserInfo={NSLocalizedDescription=No memboot image was found in the EFI system partition.}
2017-04-06 16:46:36.560747-0700 0x885 Default 0x8000000000000a83 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Releasing idle sleep power assertion (pid=195, id=0x8005)
2017-04-06 16:46:36.560838-0700 0x885 Default 0x8000000000000a83 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] ---- End Embedded OS Boot ----
2017-04-06 16:46:36.560882-0700 0x885 Default 0x8000000000000a83 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Resetting the device into recovery mode since an error occurred during boot
2017-04-06 16:46:36.560941-0700 0x885 Default 0x8000000000000a83 195 EmbeddedOSInstallService: (EmbeddedOSSupportHost) connection with driver establish (connect: 361b, service: 490b)
2017-04-06 16:46:37.179007-0700 0x885 Default 0x8000000000000a83 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Waiting for recovery mode device
2017-04-06 16:46:38.618447-0700 0x884 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Device connected: EOSDevice <mode: recovery mode, boardID: 0x12, chipID: 0x8002, locationID: 337641472, secure: YES, prod fused: YES>
2017-04-06 16:46:38.618537-0700 0x884 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] recovery mode device matches (using device type)
2017-04-06 16:46:38.618618-0700 0x885 Default 0x8000000000000a83 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Done waiting for recovery mode device
2017-04-06 16:46:38.618771-0700 0x885 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Waiting for device boot
2017-04-06 16:46:38.619909-0700 0x9f8 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSSupportHost) registered for 'com.apple.EmbeddedOS.DeviceConnected' darwin notification
2017-04-06 16:46:38.619919-0700 0x9f8 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSSupportHost) registered for 'com.apple.EmbeddedOS.DeviceUnresponsive' darwin notification
2017-04-06 16:46:38.620445-0700 0x884 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Device connected: EOSDevice <mode: recovery mode, boardID: 0x12, chipID: 0x8002, locationID: 337641472, secure: YES, prod fused: YES>
2017-04-06 16:46:38.620510-0700 0x884 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] recovery mode device matches (using device type)
2017-04-06 16:46:38.620590-0700 0x885 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Done waiting for device boot
2017-04-06 16:46:38.620627-0700 0x885 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Found recovery mode device (after reboot attempt)
2017-04-06 16:46:38.620645-0700 0x885 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Checking for healing overrides
2017-04-06 16:46:38.621361-0700 0x885 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] SMC is in app mode
2017-04-06 16:46:38.621410-0700 0x885 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Should heal: YES, Found recovery mode device (after reboot attempt) (took 5.064 seconds)
2017-04-06 16:46:38.622828-0700 0x885 Default 0x0 195 EmbeddedOSInstallService: [com.apple.mac.install.EmbeddedOSInstall] Enqueuing restore
2017-04-06 16:46:38.622898-0700 0x886 Default 0x0 195 EmbeddedOSInstallService: [com.apple.mac.install.EmbeddedOSInstall] Starting restore
2017-04-06 16:46:38.622977-0700 0x886 Default 0x0 195 EmbeddedOSInstallService: [com.apple.mac.install.EmbeddedOSInstall] Disabling retrying with AC for loginwindow
2017-04-06 16:46:38.623004-0700 0x886 Default 0x0 195 EmbeddedOSInstallService: [com.apple.mac.install.EmbeddedOSInstall] Setting bootFailedAfterShouldHeal
2017-04-06 16:46:38.623033-0700 0x886 Activity 0x8000000000000a89 195 EmbeddedOSInstallService: (EmbeddedOSInstall) Embedded OS Restore
2017-04-06 16:46:38.624528-0700 0x886 Default 0x8000000000000a89 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Took idle sleep power assertion (pid=195, id=0x8026)
2017-04-06 16:46:38.624591-0700 0x886 Default 0x8000000000000a89 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Getting information about current device for diagnostics
2017-04-06 16:46:38.625614-0700 0x9fe Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSSupportHost) registered for 'com.apple.EmbeddedOS.DeviceConnected' darwin notification
2017-04-06 16:46:38.625621-0700 0x9fe Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSSupportHost) registered for 'com.apple.EmbeddedOS.DeviceUnresponsive' darwin notification
2017-04-06 16:46:38.625892-0700 0x884 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Device connected: EOSDevice <mode: recovery mode, boardID: 0x12, chipID: 0x8002, locationID: 337641472, secure: YES, prod fused: YES>
2017-04-06 16:46:38.625964-0700 0x884 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] recovery mode device matches (using device type)
2017-04-06 16:46:38.708908-0700 0x886 Default 0x8000000000000a89 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] ---- Begin Embedded OS Restore ----
2017-04-06 16:46:38.712452-0700 0x886 Activity 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) locate preflight container
2017-04-06 16:46:38.712457-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] ---- Starting locate preflight container ----
2017-04-06 16:46:38.712499-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Waiting for device to be connected
2017-04-06 16:46:38.713351-0700 0xa01 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSSupportHost) registered for 'com.apple.EmbeddedOS.DeviceConnected' darwin notification
2017-04-06 16:46:38.713358-0700 0xa01 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSSupportHost) registered for 'com.apple.EmbeddedOS.DeviceUnresponsive' darwin notification
2017-04-06 16:46:38.713827-0700 0x888 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Device connected: EOSDevice <mode: recovery mode, boardID: 0x12, chipID: 0x8002, locationID: 337641472, secure: YES, prod fused: YES>
2017-04-06 16:46:38.713889-0700 0x888 Default 0x0 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] recovery mode device matches (using device type)
2017-04-06 16:46:38.713933-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Finding a suitable restore bundle since none was specified in the request
2017-04-06 16:46:38.715010-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) AMAuthInstallPlatformCreateBufferFromNativeFilePath: open failed: No such file or directory
2017-04-06 16:46:38.715018-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Got error 4 from AMAuthInstallBundleCopyPublishedVariantsArray when populating device types and variants
2017-04-06 16:46:38.719108-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) AMAuthInstallPlatformCreateBufferFromNativeFilePath: open failed: No such file or directory
2017-04-06 16:46:38.719114-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Got error 4 from AMAuthInstallBundleCopyPublishedVariantsArray when populating device types and variants
2017-04-06 16:46:38.719332-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Choosing between bundle specifiers: (
"EOSRestoreBundle </usr/standalone/firmware/iBridge1_1Customer.bundle/Contents/Resources> (14Y565: PKBundleComponentVersion <565.0.0-565.0.0-565000000000000-3>)"
)
2017-04-06 16:46:38.719422-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Current bundle specifier: (null)
2017-04-06 16:46:38.719486-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] No build variant specified and device is prod-fused, choosing customer variant
2017-04-06 16:46:38.719543-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Chose EOSRestoreBundle </usr/standalone/firmware/iBridge1_1Customer.bundle/Contents/Resources> (14Y565: PKBundleComponentVersion <565.0.0-565.0.0-565000000000000-3>)
2017-04-06 16:46:38.719614-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Using restore bundle: EOSRestoreBundle </usr/standalone/firmware/iBridge1_1Customer.bundle/Contents/Resources> (14Y565: PKBundleComponentVersion <565.0.0-565.0.0-565000000000000-3>)
2017-04-06 16:46:38.719658-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Attempting to locate preflight container for restore bundle
2017-04-06 16:46:38.719773-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Preflight container repository URL doesn't exist; creating it (file:///Library/Updates/PreflightContainers/)
2017-04-06 16:46:38.719918-0700 0x886 Default 0x8000000000000a8a 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] No matching preflight container found
2017-04-06 16:46:38.720060-0700 0x886 Activity 0x8000000000000a8b 195 EmbeddedOSInstallService: (EmbeddedOSInstall) network reachability check
2017-04-06 16:46:38.720063-0700 0x886 Default 0x8000000000000a8b 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] ---- Starting network reachability check ----
2017-04-06 16:46:38.720307-0700 0x886 Default 0x8000000000000a8b 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Checking for reachability to gs.apple.com
2017-04-06 16:46:38.720859-0700 0x886 Default 0x8000000000000a8b 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Waiting for reachability to gs.apple.com
2017-04-06 16:46:38.720866-0700 0x888 Activity 0x8000000000000a8c 195 EmbeddedOSInstallService: (SystemConfiguration) processing SCNetworkReachability notification
2017-04-06 16:47:08.725943-0700 0x886 Default 0x8000000000000a8b 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Timed out waiting for reachability to gs.apple.com
2017-04-06 16:47:08.726223-0700 0x884 Default 0x8000000000000a89 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSSerial] (null)
2017-04-06 16:47:08.726512-0700 0x886 Fault 0x8000000000000a8d 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Restore failed with error: Error Domain=EOSErrorDomain Code=101 "Can't continue the restore because you are not connected to the Internet." UserInfo={NSLocalizedDescription=Can't continue the restore because you are not connected to the Internet.}, client=loginwindow (pid = 83, uid = 0, path = /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow)
2017-04-06 16:47:08.726512-0700 0x886 Activity 0x8000000000000a8d 195 EmbeddedOSInstallService: (EmbeddedOSInstall) %@ failed with error: %@%@
2017-04-06 16:47:08.726577-0700 0x886 Default 0x8000000000000a89 195 EmbeddedOSInstallService: (EmbeddedOSInstall) [com.apple.mac.install.EmbeddedOSInstall] Diagnostic summary: Restore ((null) -> (null) ((null)), preflighted = 0, prod fused = 1, user auth = 0, retries = 0, after boot failure = 1, failing phase = 4, client = loginwindow, uuid = D5E8700C-F3E5-45BF-A8D3-9CACD73611B9): Error Domain=EOSErrorDomain Code=101 "Can't continue the restore because you are not connected to the Internet." UserInfo={NSLocalizedDescription=Can't continue the restore because you are not connected to the Internet.}@leodeleon22 Are you able to plug in to Ethernet on your home network? After you did a clean install and rebooted, were you prompted to input a password for your home wifi? When I went through this, I did briefly see a prompt to connect to WiFi but there were no network listed. When I plugged in to Ethernet on my home network, it instantly connected and installed the EmbeddedOS.
@AVmcclint thanks for your response. The actual problem is no matter how I reinstall the system it always asks for the wi-fi for this "Critical update". From what I understand asking for the Wi-fi already means that it didn't find the EmbeddedOS in the EFI folder. I don't have the ethernet/USB-C dongle to try. I'm waiting for a response for the so called "engineers" from the Apple Support and this Friday there will be a technician on my local Apple store. I'm gonna wait to see how it goes. If you have any other idea that I should try please let me know
Unfortunately the one thing that seems to have the best chance of success is to plug in to ethernet and not have any firewalls or proxy in between the computer and the internet. If you take it to the Apple Store, they will probably plug it in to Ethernet so it can download the EmbeddedOS. Apple does really need to improve this experience.
I have an open case with Apple on this. This is sloppy Q/A on their part. We're going to halt all new orders of the touch bar laptops if they do not resolve this issue, as they're clearly not compatible with Enterprise networks.
Went through initial pain getting these touchbar MBP's to work within our infrastructure. Learnt not to nuke the LV and all appeared to be ok. We could partition the LV into our "default" boot and user volumes without wiping the embeddedOS. Imaging worked fine albeit with cheap dumb Ethernet to USB-c dongles which could see our NetBoot set.
Decided to update NBI to 10.12.4 and also Base OS to same and now see that when booting into the NBI there is the progress bar downloading and installing the touchbar OS. Eventually gets there then post imaging goes through the same process and again after the final reboot and gets stuck as we are behind corporate proxy. We have external DMZ networks to get around this but that is a painful process. Will go back to the 10.12.3 NBI and base OS and see if that works.
Has the location of the embedded OS changed with 10.12.4? We resolved our issues as we believed the embeddedOS in the EFI was wiped when destroying the LV.
DEP doesn't suit our environment ( that may have to change in the future) we like mass imaging, when it works, it's simple and quick as we need fast turn around times. We don't have the 6+ hours required to reinstall via Recovery mode.
Definitely now a 10.12.4 issue. reverted NBI and Base OS back to 10.12.3 and the issue goes away. Called Apple and logged it.
Ironic, can't use the 10.12.4 for the OS in either NBI or the Base and can't update our Touch Bar machines to 10.12.4 from or internal SUS as they kernel panic upon reboot. Go Apple!
@TimC Are you sure you're not just holding it wrong? 
But seriously, my organization builds on a non-internet connected network; our current workaround is to tether to a smartphone for each device as it's rebuilt. To add insult to injury, external Apple resources are generally blocked on our network and when we run OS Updates some - but not all - of the touchbar Macs experience this. What's more, a launchDaemon on the affected Macs then seems to prevent the touchbar from re-establishing its connection to the Mac after downloading the update it thinks it needs to fix EmbeddedOS so we get stuck in a loop of Try Again or Shut Down until we go into Single User mode and disable the implicated LaunchDaemon.
Today I think I found an opportunity to convince Apple to address this correctly - at the screen where you'd choose your WiFi network you can choose <--> "Other Network Options" and the radio button for "My computer does not connect to the Internet." This also drops into the same loop of Shut Down / Try Again but with no way to back out beyond shut down.
Apple clearly needs to address this scenario; they cannot render your device inoperable if it is unable to connect it to the internet. It's one thing to leverage something like Find My iPhone or Back to my Mac to brick a stolen device, but the presumption that these Macs with EmbeddedOS hardware connected to them must be internet-connected by legitimate owners is unacceptable. There are many applications where for data security purposes organizations or individuals may want to keep their Macs air-gapped and isolated from the the Internet!
they cannot render your device inoperable if it is unable to connect it to the internet
That was exactly my issue with the current setup. And apparently they feel they can and people will continue to purchase their products (not me!). During this connection process, they are validating the OS to confirm it's safe and is secure which is good motivation, but still has a significant cost. Besides the air gap issue you mentioned, what happens when Apple feels your hardware is 'obsolete' and removes support for it?
Hi guys, please help..
I bought a 2017 13in MBP with Touchbar while on holiday in the USA 2 weeks ago. I brought it back to my home country (Indonesia) and promptly migrated everything from my 2011 Macbook Air...
A few days ago, I ran into this Critical Update Loop problem. I have disabled the firewall of my wifi router, and SOMETIMES it allows me to complete the update & log in normally (other times, it will keep looping and I have to hit RETRY several times until it completes or I give up and try some other time)
Even if it manages to complete, the next time I power off and on again, it will take like 2-3 minutes to boot & that is a sure sign the Critical Update loop is back.
I seriously doubt the local Apple engineers will have a clue. Even if they do, they may be unwilling to help coz I did not purchase my MBP from them... and thus returning my MBP for a replacement is also not an option :(
My OS is already 10.12.5 btw..
How can I resolve this issue once and for all?
@bvrooman: can you please give detailed instructions how to create the package (/usr/standalone/firmware/iBridge1_1Customer.bundle) and add it as a before-reboot package in layman's terms?
Thanx so much for any help...
Wasn't this issue resolved with the 10.12.6 update?
@rqomsiya On 10.12.6 and I don't think we've seen it much, but I'm very concerned by Apple's assertion in this technote HT208020 that we will be seeing more of this in the future:
"You must be connected to the Internet when you upgrade your macOS. After your Mac confirms your connection, the Installer uses the model number of your Mac to locate and download a firmware update specific to only that Mac.
Only the macOS Installer can download and install the firmware update. Firmware updates can't be done on external devices, like those connected via Target Disk Mode, Thunderbolt, USB, or Firewire."
I'm stuck in the loop and while our firewall is open to all going traffic (and incoming traffic initiated by an outgoing request) I can't get the critical software to install. I've tried our in-house ethernet network and our public facing wifi. Nada.
I was able to use Eric Gomez's blog post to mount the EFI volume from a working machine, copy the contents to a flash drive, boot my problem machine from an external boot drive, and mount it's EFI partition. The problem EFI volume was missing several pieces, so I copied the backup from my flash drive over. Crossed my fingers and restarted. It worked. Yay.
...insert list of expletives directed at apple here...
Hey everyone.
I know this isn't a new topic, but we just started piloting TouchBar MacBooks and hit into this issue.
Draws my attention that nobody has said if High Sierra has this "cool feature" of mandatory online activation. Does anybody know if MB with TouchBar also have this problem, or has a better solution came up?
Thanks.
Hi Everyone,
The integrated ssd in macbook pro 13" w/touchbar was broken and can't be used anymore so I did install sierra from internet recovery into external ssd and stuck with this kind of problem ( A critical software update is required for your mac, but an error was encountered while installing this update). I've checked all the site & port were open.
gg.apple.com 80 and 443
gnf-mdn.apple.com 443
gnf-mr.apple.com 443
gs.apple.com 80 and 443
ig.apple.com 443
skl.apple.com 443
Is there solution for this? please help as I can't use macbook anymore unless I have to get it work by reinstalling.
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.