Wednesday, October 4, 2017 [Tweets] [Favorites]

Your Device or Computer Could Not Be Verified

I got this error message a while ago, and suddenly none of my Mac App Store apps would launch, even after restarting the Mac. The App Store said that Tweetbot had been purchased on a different Mac, even though I had just downloaded an update for it minutes prior. Suddenly, I couldn’t even sign into the App Store app.

Eventually I traced the problem to something that happened a day or so earlier. We’d had a thunderstorm that damaged my iMac’s Ethernet port (amongst other equipment). At the time, I’d just switched the iMac over to Wi-Fi and started researching surge protection for my cable modem’s Ethernet output. All my apps continued to work.

But the Mac App Store uses the Ethernet MAC address for verification, even when connected via Wi-Fi. At some point it decided to verify things again, and my iMac’s Ethernet was broken enough to interfere with this.

The solution, MacBreaker explains, is a procedure to convince your Mac that it doesn’t even have an Ethernet port:

If neither of the above solutions fix the issue, open the System Preferences app and go to the Network section. On the left-hand column in the Network section, select each of the items and remove it by clicking the minus sign on the bottom of the column.

Then, go to /Library/Preferences/SystemConfiguration in your main hard drive and delete NetworkInterfaces.plist. Or alternatively, drag it to the desktop (as a backup, in case things go wrong).

By removing all of the Network items in System Preferences and deleting NetworkInterfaces.plist, you have effectively reset the network configuration for Mac OS X. Reboot (you may have to reconfigure your internet connection afterwards).

This worked for me. I was able to sign in and download new Mac App Store receipts tied to the Wi-Fi MAC address. And they continued to work after I started using an external Ethernet dongle.

Note: OmniFocus also uses the MAC address as a syncing identifier. After completing the above steps, it will see your Mac as two separate computers, one of which is no longer syncing. You’ll have to remove the Ethernet one or else syncing will get slower and slower because it can’t generate a new baseline without hearing from that Mac.

Previously: More Mac App Store Certificate Problems.

Update (2017-10-06): Howard Oakley:

It also bears pointing out that, in the event of a sudden loss of the Ethernet port, one of your first actions should be to ensure that port is properly connected to a network, and to restart in hardware diagnostics or AHT, as detailed here. You’ll also need to be within range of an active WiFi network, or you may find that you get a code CNWxxx reporting a WiFi hardware issue, rather than another error (unspecified, possibly CNxxxx series) pointing at the Ethernet port.

If your Mac returns a code ADP000, indicating hardware health, the cause is most likely to be software. Keep a watch on your software installations, because what has happened once could always happen again. If you want to read exactly what I experienced, the summary is here.

In those days of El Capitan, we had one major diagnostic advantage: the logs, which were still old-fashioned and relatively uncluttered. I’m not sure how we’d cope now with Sierra’s unified log, in which any useful information would be buried in a torrent of confusing error messages.

Update (2017-10-08): I’m not sure why, but Apple Diagnostics did not report any problems with my iMac’s Ethernet port.

Comments

Stay up-to-date by subscribing to the Comments RSS Feed for this post.

Leave a Comment