Unable to launch Apple Diagnostics

Does you or anyone know what this means?

Read (or at least browse) the thread, and you'll have the answer to your question.

…if I should be concerned or take it to get repaired before it completely stops working.

I don't know about Internet issues (though from reading on other forums I gather people are having a lot of issues with Mojave), but in regard to being unable to run Apple Diagnostics, yes, if you can take it to a Genius Bar (Apple Store) and ask about this problem, that would help not only you but everybody here. (See my posts here and here.)

Of the 18 (now 19) posters on this thread who identified their Macs which are unable to load EFI to run Apple Diagnostics / AHT, all (a) are 2012 or 2013 models, and (b) have been upgraded to High Sierra or Mojave. It looks like the issue may not occur with later year models, as when I installed Mojave on a 2014 MBP it did not change the firmware, and the computer was still able to load Apple Diagnostics.

So the problem does appear to be something in the installation of High Sierra or Mojave (the two OS versions in which the new APSF was introduced) which changes the Boot ROM on 2012 and 2013 Macs. It may not occur with Late 2013 models; all the 2013 MBPs reported here are Early 2013 (like my MBP). The late 2013 (MacBookPro11,2/3) has more in common with the 2014 model (also MacBookPro11,2/3) than with the Early 2013 (MacBookPro10,1/2, same as the 2012 models).

babowa wrote: Also, complaining about a 7 year old machine not being fixed is not helpful. It is what it is.

Well, my machine is a 2013, i.e. 6 years old, and though I see in the link that it is now regarded as "Vintage" ("denoting something of high quality, especially something from the past or characteristic of the best period of a person's work" – New Oxford American Dictionary, included with macOS), it is also supported for upgrade to the latest Mojave OS. In fact, not only supported, but Apple will continuously nag me to do the upgrade (unless I figure out how to turn it off). Only doing so trashes the computer's Boot ROM. If Apple is going to provide a Mojave installer for this model, it shouldn't do any damage.

mmehrle wrote: "I hope Apple is paying attention."

To reiterate: Though some Apple staff may browse this forum now and then, Apple does not pay any official attention to anything posted here. To get that attention, the information/complaint must go through the designated Apple Support or Genius Bar channels.

I'm about to do a complicated HW swap out of logic board because of something which has been caused by a **** firmware update!!!

What do you think?

As for your problems in addition to the AHT issue, I can't say; maybe they will require replacing the logic board. However, if those other problems also appeared only after you did the OS upgrade, they may indeed be related to the Boot ROM change, i.e. there's nothing wrong with your present logic board. If that's the case, why go to all the trouble of replacing it?

In any case, if you want a solution to the Cannot load 'EFI/Drivers/TestSupport.efi'  issue, I think you should not do the logic board swap now. Replacing the logic board might "solve" the AHT problem, if the replacement board is from a computer that has not been upgraded to High Sierra or Mojave, but the next time you install either on your iMac, the AHT problem will probably reappear, as the Boot ROM will then be "upgraded" again.

Instead, if at all possible, take your iMac to a Genius Bar and tell them about (1) the AHT issue, which is also a problem for over 200 other users (bring along the link to this thread, in case anybody there might be willing to look at it) and (2) your other issues. They will run their diagnostic, and if it says there are actual hardware problems with the logic board, then is the time to do the swap (if you're up for it; it's beyond my skills). If their diagnostic shows no hardware problems, you can ask "Then why can't I run AHT?" And maybe we'll get some action on this issue.

If you do need to replace the logic board, and doing so "solves" the AHT issue, i.e. you can now load and run Apple's diagnostic software, it will be of interest to see if it reports any issues with the replacement logic board. If it does not, your other issues should be solved. However, the AHT issue probably will not be solved. If you do another install of High Sierra or Mojave, you will probably once again be unable to run AHT afterward. Then, if you're up for it, you can take the iMac again to the Genius Bar: see paragraph above.

babowa wrote:

…having the Genius Bar run it. Except for having to drive there….

I don't know where you live, but the nearest Genius Bar to me is 60 miles away, a trip I haven't made in over 20 years due to chronic illness. I do hope to be up to it sometime this summer, but in the meantime I'm stuck with this computer I can't sell, as I can't show a prospective buyer a clean bill of health.

Apple has discontinued hardware service for vintage products….

So far as any of us have been able to tell, this is not a hardware issue. It is a software issue, caused by an upgrade from Apple, which Apple urges me (and everybody else here) to do. If you have no problem with that, that's good for you. I do have a problem with it, and I see no reason why Apple shouldn't solve it, since they caused it.

BDAqua wrote:

I hear from a reliable source that the Original ASDs that weren't available to the public still run on updated iMacs that have had the Firmware Updates & all Security Updates through 2019-003.

Did your reliable source specify that the EFI version of ASD v.3S152 (for the 2 Late 2012 iMacs) or ASD v.3S155 (for the single Early 2013 iMac) (these three are the only Ivy Bridge based iMacs) runs on these iMacs with all current updates? What OS version has been installed on these iMacs? Are they on Sierra or older, or has High Sierra or Mojave been installed?

I don't have an iMac, but as I wrote above, the OS version of ASD 3S155 runs fine on my Early 2013 MacBook Pro, but the EFI version shows the same Cannot load 'EFI/Drivers/TestSupport.efi'  error that appears when trying to run Apple Hardware Test. 

ConJeXture wrote:

I just had my Mid 2012 Macbook Pro motherboard replaced and it came back with MacOs Sierra. AHT currently works but we all know once I upgrade to Mojave its going to be gone. I am from South Africa and we don't have any Apple stores or Genius bars in the country - only approved re-sellers. If I filmed a video showing AHT working, the upgrade process and then not working after the upgrade, would someone be willing to take the footage to a Genius bar in the USA ?

Suggest you (a) run AHT and take a photo of the screen (video not necessary).

(b) Have you applied Security Update 2019-003 (Sierra)? If you have, and the computer still runs AHT, then that's not the problem (I have no way to test this). If you haven't, then download and run this Update, and see if you can run AHT. If you then get the Cannot load 'EFI/Drivers/TestSupport.efi'  error, xr7zk2001 is correct (that the 2019-002 & later Security Updates cause this error, as does upgrading to Mojave – and possibly upgrading to High Sierra).

(c) If you can still run AHT after applying the 2019-003 Security Update, next I was going to suggest upgrading the computer to High Sierra, to determine if that update causes the problem. But… I can't find any way to get the Installer; the link I have for Apple's High Sierra page reroutes to Mojave, and a search for High Sierra in the App Store shows no results. I assume if you have a 2011 model Mac you can get it, as it's the last version that will run on that generation hardware. But it seems Apple really doesn't want you to use HS if your Mac can run Mojave.

(d) So the next step is to install Mojave, and try to run AHT again. Which will probably (certainly?) result in the the Cannot load 'EFI/Drivers/TestSupport.efi'  error.

(e) At that point, if your logic board was replaced by an Apple "approved re-seller", I would take the Mac back to them and ask why it won't run AHT; show them the photo of when it did, and tell them what you've done since that appears to have produced the error. If they have a relationship with Apple, and used an Apple part to fix your Mac, they have standing to bring the problem to Apple's attention, and ask for a solution. You might show them this thread to make it clear that (a) you are knowledgeable about the problem (do read the thread; all the information is here) and (b) you are only one of at least 225 Mac users who've encountered it (now up to 217 here, plus 8 on the thread I started), but keep in mind that posting here does not bring the problem to Apple's attention. See below.

A recent development might provide another option:

Apple partners with Best Buy for expanded repair service - Apple

Although the Apple press release makes it sound like the Best Buy program is all on line ("With nearly 1,000 Best Buy stores across the US now providing expert service and repairs for Apple products…."), I just had a chat with an Advisor, who told me: "It really depends on the stores, the agreement is complete, and once they have finished the necessary trainings then they will be added to our providers list." So for instance, my local Best Buy (60 miles closer than the Apple Store) is not yet on the list, but will eventually be listed as an Apple Authorized Service Provider. YMMV, of course.

BDAqua wrote:

Yeah, one can hope, but I doubt Apple worries what old Macs can do. :(

No, of course Apple doesn't worry much about what old Macs can or cannot do. They're into enough trouble with the current models (can anybody say "keyboard"?). And of course, they need you to buy a new Mac every few years – though they seem to be determined to continue alienating long-time users from doing so.

I'm sure there are some at Apple who know about this problem. However, merely "hoping" they'll do something about it is pointless if they have no incentive to do so.

I see that now 257 people have checked "I have this problem too" on this thread. (The thread I started has been closed, and the "I have this problem too" number removed, but it was nearing 20 last time I looked.) So far as I'm aware, not a single one of these 250+ Mac users who have this problem has taken the trouble to bring it to Apple's attention through the proper channel, which is the only way to get Apple to do something about it. In fact, as I mentioned in another post, an Apple Advisor actually told me that he would lose his job if he took official notice of anything he saw in one of these Apple Communities discussions.

The facts:

1) Ivy Bridge based Macs are listed among those models which can take the upgrade to Mojave. Personally, I'm surprised at this, since they are so old; but Apple does provide Mojave installers and updaters for these Macs.

2) Apple provides instructions for using Apple Diagnostics (or Apple Hardware Test) and recommends doing so if you are having trouble with your Mac.

3) However, if Mojave is installed on an Ivy Bridge based Mac, it then becomes impossible to run AD or AHT on it. (The problem may also be caused by Sierra and High Sierra security updates, but I don't have any way to test this.)

Given these facts, certainly the owner/user of an Ivy Bridge Mac has good reason to ask Apple to solve this problem. However, you have to actually ask – and quite likely insist a little – if you want action. Merely complaining on this forum is a waste of time.

In my case, I am dealing with serious illness, and simply don't have the energy/time to do anything about it. I'm hoping I might in a few months, but right now it's just not on my list of things to do besides surviving for another day. I'm pretty sure this problem is solvable, but somebody is going to have to actually put in a little effort.

See my earlier post for more detail. And my other posts for even more.

One addendum: As noted in another earlier post, Best Buy is now officially an AASP. Not all Best Buy stores are yet qualified – people have to be trained – but most are. So if like me you're not close to an Apple Genius Bar but do have a Best Buy nearby, you can try them.

I've not seen a way to run Diagnostics once you've done the Firmware updates that are included in some Security updates.

Are you using the AppStore? If so try downloading them first & installing...

https://support.apple.com/kb/DL2010?viewlocale=en_US&locale=en_US

https://support.apple.com/kb/DL2015?viewlocale=en_US&locale=en_US

I can't run AHT or AD on an iMac13,3 (early 2013) running the latest Mojave. I get the same "Cannot Load 'EFI/Drivers/TestSupport.efi'" error. Additionally, the serial number is now missing (see my post here).

I took it in to an AASP so we'll see what their hardware test yields.

I have a bunch more iMac 13,3s at work (that have their serial numbers!) and I'll try AHT/AD on them tomorrow to see if they have the "Cannot Load 'EFI/Drivers/TestSupport.efi'" error. All of the other iMacs are running the latest High Sierra.

Brian

Hello,

If you have:

An Apple Hardware Test CD:Start up from it as you would any other bootable disc:

Then:

1.Insert the Apple Hardware Test disc that came with your Mac into your Mac's optical drive.2.Restart your Mac by either:

• Selecting Restart in the Apple menu.
• Pressing the Command-Control-Eject keyboard shortcut.

3.Immediately press and hold the C key on your keyboard.4.Release the C key after the Apple Hardware Test appears on your display and indicates that it is loading

http://www.thexlab.com/faqs/aht.html

Hi everyone. I came across this thread and it seems relevant to my problems with my Late 2012 27" iMac not booting (and not letting me install, run diagnostics tests etc)...

Ok... I'll try and keep this concise:

Late 2012 3.4Ghz 8MB iMac worked great for years - started to get some random restarts last year - was running High Sierra

Tried an update to Mojave - failed - and iMac no-longer would boot / kept power re-cycling

Took it in for repair at good authorized Apple repair center. They managed to get all data off the Fusion drive (128GB original SSD/NVME + 1TB HDD). They tried reinstalling OS (I think they put original Snow Leopard on there). But kept getting re-boots.

Told me it was likely a Logic Board fault which would cost $800 or I could leave with them for recycling...

I decided I wanted to try and save the machine - I had read that the PSU boards on late 2012 iMacs often caused this sort of problem - so I brought the iMac home - learned how to open it up (iFixit) - bought a refurbished different PSU board for $100 and fitted it.

Did a quick test - and it booted ! hurrah.

At this point I thought I would give the machine a bit of boost so bought a 1TB SSD (Samsung EVO 860) and swapped out the HDD for the SSD. I expected this to kill the fusion drive setup - and it did - but I was ready to install Mojave from external USB disk I had made

This didn't seem to work - but when I tried Recovery mode from Internet, It remade fusion drive, installed High Sierra - and booted! So was super happy, re-sealed screen to machine and had a working iMac again.

So then... I tried installing Mojave again (10.14.4)... seemed ok to begin with then crash... then didn't boot

wouldn't even get to disk utilities or Terminal with my Mojave USB install disk

So I thought maybe the fusion disk setup was the culprit - and therefore if I could reset that - maybe unfuse the drives and install OS X to NVME and use the 1TB for applications and user data...

I bought a firewire cable (and a new Mac book Air....) and used Target Disc Mode - I could see drives - I ran first aid on them - no errors. I tried lots of different boot options - in the end I erased them both to try and get rid of fusion setup (pic is before erase).

Everything I did hasn't helped getting past a stuck progress bar on the Apple Logo.

I can't do internet recovery, USB recovering, Paragon Hard Disk Manager USB Key, Apple diagnostics (via internet) - I get same error about Can't load EFI...

So then I thought if its nothing to do with my internal drives (which should be blank) - maybe its my memory... so I tried removing one 4GB bank - same results. tried other... same results...

The only thing I can get into is Single User Mode - but not sure what to do there to help....

Before I start believing it is a logic board problem I really want to rule out some kind of SW/Firmware issue - or test HW somehow and check it works - but remember - I have NO OS installed at the moment

Any advice really appreciated.

Thanks

Can't run diagnostics

from the earlier posts I thought going back from 10.14.4 was not helping? If I want to try 10.13.6 how should I make such a USB installer please?

BTW - things are getting worse - now I can't even see the drives in Target Disk Mode :( - the host is showing Firewire symbol - but no driver appearing on my iMac (which I just upgraded to 10.14.5 - hope that hasn't caused that). If I use Single User Mode (with as USB 10.14.4 key in) I see the drives are there - but I don't seem to be able to run fsck on them (only the USB 'root')

What do I need to to in Single User Mode to be able to a) check other drives, b) see them in Target Disk Mode please?

Read until the end, this pretty much proves it is the firmware update in Mojave. I am having the same problem. I got this computer from a friend who only sold it because he upgraded to a new macbook. He asked that I scrub his drive so I gave him his old one and installed an SSD. I am now having two problems since I installed Mojave:

1) I cannot book to diagnostics, either with d or option d

2) I am having the memory error another user reported occasionally.

This computer ran fine prior to Mojave. It also worked well while running Mountain Lion after the SSD install. Once Mojave was loaded, I began having these issues. Could I have messed up the board? Not likely, but as a logical person cannot rule out the possibility. But it seemed to run fine on Mountain Lion prior to me upgrading to Mojave.

Here is the proof:

I just so happen to have three mid 2012 Macbook Pros, two 13” and one 15”

Two of them, the 13”s, are now experiencing the inability to load diagnostics. Any Apple

employee who sees this is welcome to check out my Apple user ID which is the same email

as I have attached to this username, and you can see that I do in fact have three mid 2012 MB Pros. I also checked the HD cables, replaced all 3 hard drives, tried installing new memory on one, and ran third party hardware testing on all of them with no failures. I do have other computers, but these are the ones I allow my family to haul around and use, so I’d like someone at Apple to work on a patch for this problem. While I am only one person reporting this problem, I have it on two of my machines, and my third proves I am not incapable. Something is wrong with the Mojave update for the 13” mid 2012 Macbook Pro.

I see that the post recommending the GitHub article on AHTs has been promoted to "Helpful" – I don't by whom.

There is only one person that can award points associated with a solved or helpful on any of these forums - and that is the OP. Anyone can click the little helpful button, but unless there are many (don't recall the exact number), it won't result in any points.

And, it was not the post you mentioned, but this one:

I am unsubscribing from this thread.

Gets more interesting.

The MacBook Pro 2012 boot ROM version and SMC version have been updated (see photo). The boot ROM version is now different to the 226 version that was thought to be the cause of the problem. It is now version 228.

The iMac 2012 boot room version has also been updated - and has a higher version number than the MacBook Pro version. It is now version 285.

The SMC version is however different between the MacBook Pro and the iMac.

I'm not sure that this is good news for the iMac because it suggests that the problem was not with the boot ROM version and may be to do with something more specific to particular hardware. In the case of the 2012 iMac, the hardware is no longer supported by Apple. The 2012 MacBook Pro still is (because it was made/sold until 2014).

I have a macbook air, with macOS High Sierrra installed. I want to upgrade the OS however I am concerned about this problem.

Can anyone please clarify is this problem will affect my macbook air if I upgrade the OS?