Unable to launch Apple Diagnostics

Incredibly, it seems that Apple has just fixed this problem by completely updating the hardware test service for 2012 Macbook Pros so that 2012 MacBook Pros now use the most recent Apple Diagnostics service instead.

I'm gobsmacked. Not only has Apple fixed the problem but has done so by allowing 2012 MacBook Pros to access the new and modern diagnostics service.

I think that's very true.

When it comes to a self-repair for a Mac that Apple won't even touch for diagnosis, there's possibly some benefit in being able to access Apple Diagnostics but the information it provides when there is a problem is pretty limited. AHT is even more limited.

This episode probably says more about Apple's approach to supporting "legacy" hardware, even when the problem requiring solution was caused by Apple in the first place.

Have there been further updates?

I have a MBP 2013 w 2.9ghz i7 8GB ram and lately it's been hanging up or freezing much more than normal. When I tried to going into diagnostic I got the same error as the OP -Error: 0x8000000000000003, Cannot Load: 'EFI/Drivers/TestSupport.efi’

Status: 0x00000003

Is there any update pushed for this, or is it just SOL for now across the board?

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?

I have the same problem since at least Mojave (late 2012 iMac 21.5"). It's running very slowly since I did the Mojave upgrade and I can't do any hardware fault diagnosis. I upgraded to Catalina a few days ago to see if it would fix the speed problem (it didn't) and it also doesn't fix the problem here of not being able to run diagnostics (either D or Command-D) on boot up.

I've now given up completely and have just ordered a new iMac :(

not being able to run diagnostics in itself is not a major issue, but with my slow running / crashing weekly iMac that won't let me do a reinstall of Catalina (PKDownloadError 8), and I daren't wipe and do a clean installed in case I still get that same error or have problems rolling back to High Sierra... it's just too much (more) time and effort with no guarantees.

I guess 7 years is a pretty good run for a computer though. Outlasted several of my iPhones!

My imac is a late 2012 i regretted updating it to catalina, now my imac is whacked, cant run diagnostics, it gives me that error code, cant shut down at all, it restarts when i shut it down and not only that, when i manage to force shut it, the imac will have this weird loud spinning fan sound, guess its time to get a new mac

Mine is a late 2012 imac, totally regretted updating to catalina, its whacked now, it restarts when i shutdown, cant run diagnostics and when i force shut down it will have this loud spinning fan sound and i always have to unplug it, guess its time for a new imac

I was going to wait until December to upgrade to Catalina, but considering the problems that some have encountered, I think it would be wise to wait for an updated version of Catalina. (I have an iMac (21.5-inch, Late 2012.)

Especially since I have the same issue with boot rom version 258.0.0.0.0, which means it has being going on for a while...

And having 750+ people having the same issue does not make Apple emotional. There was a time when they cared...

750+ is too small of a number for a global company to notice. 750,000 might get their attention, or maybe not. To be fair Apple provides backward compatibility longer than any other computer manufacturer I can name. The issue always boils down to which other PC would you buy instead? That I am still mostly happy with my souped-up late 2012 Mac Mini speaks volumes about the Apple experience... also that I know better than to jump on OS 10.15 yet.

P.S., my boot rom version is 280.0.0.0.0

And you should feedback that problem here.

https://www.apple.com/feedback/mail.html

>My boot ROM version in System Report is 224.0.0.0.0 .

That's the criminal.

You should report the bug from here.

I got the same issue.

Is Apple still working on with this issue?