Network Diagnostics app missing

Also, these files should be assigned to the "wheel" group, not "admin." If you examine all other System files/folders, they belong to wheel. The root user is the only member of the wheel group, while admin can have many users. Since we're trying to restore everything the way it was before Apple removed them, we might as well try to get it right, especially for security purposes. So:

sudo chown root:wheel [file]

sudo chown -R root:admin [folder]

I had the same question but I found that they have an application on the mac called Wireless Diagnostics.

Using your Finder window go to applications and search for Wireless Diagnostics and it will bring up an app. I just dragged and dropped it to my applications bar at the bottom so it will be easy to get to the next time I'm having network issues.

Hope this helps you and others out!

You are a legend Keith. Followed your instructions and Network Diagnostics is now back!

Just letting you and folks know, that there is a small (but important) typo in your instructions - the last two lines to change the ownership within Terminal have an errant space in the last word; they should read as:

sudo chown root:wheel /System/Library/PrivateFrameworks/SetupAssistantFramework.framework/Versions/A/ SetupAssistantFramework

sudo chown root:wheel /System/Library/PrivateFrameworks/SetupAssistantSupport.framework/Versions/A/Se tupAssistantSupport

I did have a heart-attack moment when I rebooted after disabling SIP, when my Finder just started a crash-loop - something about "Finder quit unexpectedly while using the SyncoCxtMenuSIMBL plug-in" whatever that meant but by quitting Chrome and restarting again I was able to open more than one Finder window without Finder crashing.

Other than that, your excellent instructions worked beautifully and am so happy that I have Network Diagnostics back - it was like I had lost a limb I never knew I really badly needed! 🙂

Thanks for the kind words. Just so you know, I didn't introduce the extra spaces. If you look at where they are, they occur at line breaks. Your own commands have them, too. But it highlights the importance of paying attention, to make sure there aren't extra spaces.

That is quite annoying, isn't it? And it seems one cannot edit one's post. That's... awkward. 🙂

sudo chown root:wheel /System/Library/PrivateFrameworks/SetupAssistantFramework.framework/Versions/A/ SetupAssistantFramework

sudo chown root:wheel /System/Library/PrivateFrameworks/SetupAssistantSupport.framework/Versions/A/Se tupAssistantSupport

I don't understand what is going on there. It seems no matter what size the text is those breaks are being inserted automagically.

I don't have this on Sierra or at least I can't find it now that I've upgraded. I've been using it for years and now it's gone. Weird, as I did have it with El Capitan. I wish I never upgraded. Sierra is way more annoying.

So far this is the only instance of this question I've seen online. I wish more ppl were asking it!

***Oh wait, there are 6 pages of ppl discussing this- why I was shown only one...

I'd never have written this otherwise.

Indeed this useful tool seems to be missing.

The solution is to create 2 Wifi frequencies. Usually this means adding a 5 GHz one. Whenever there are Wifi connection problems, just swap between the 2 Wifi frequencies and the problem is solved within several seconds.

I can't possibly solve an ISP-Internet connection failure. So it cannot work 100% of the time to fix a problem you have no control over. And it surely cannot diagnose the where the failure is. Your solution does not address the problem. Switching wifi connections sometimes resolves the handshake between the computer and the ISP. It does not tell you that the problem is between the ISP and the internet vs. between your wifi and the ISP. It does not diagnose the problem nor does it solve the exact problem I have. I need to know where the problem is so that I can decide to not waste time fixing something that is not the problem, like my wifi connection to the ISP provider.

@Keith Riggle - awesome instructions, worked perfectly and I now have Network Diagnostics and Network Setup Assistant apps working again in High Sierra. I copied them from /System/Library/CoreServices to the Utilities subfolder in the Applications folder on Finder so they're easily accessible. Thanks very much for your help with this - you're a star!

Steven, You're sure you're still on Sierra and not High Sierra, right? If all you want is Network Diagnostics, you need only the following 2 files:

/System/Library/CoreServices/Network Diagnostics.app

/System/Library/PrivateFrameworks/NetworkDiagnosticsUI.framework

Copy the path of each file without the file name (e.g., /System/Library/CoreServices/), then in Finder, press Shift-Command-G, which brings up "Go to the folder." Paste the path in the box and click Go. Then in each folder find the desired file and drag it to an external drive. Then follow the rest of the instructions.

Thanks, Keith. That will help. Yes, I only have one of my 3 macs updated to High Sierra. The others still have network diagnostics on the Sierra OS. Of course I updated my primary computer first . . . Sigh. Hope to get to this matter again tues or wed this week.

For the life of me I cannot understand why Apple would do this to their clients. I am not a programmer or a tech person but I enjoyed my Macbook Air right up until now. What would be the reasoning behind

A/ making something difficult or impossible from something that was easy,

B/ messing with something that worked .

Has anyone heard the term ,`` If it aint broke , don`t fix it `` .

Please return Net Diag .

Concerned , Dave

God love ya for this Keith-- unfortunately I'm going from 10.10 (Yosemite) to 10.13. No problem using time machine to grab the necessary files... but in 10.10, there is no SetupAssistantFramework.framework. (There is the SetupAssistantSupport.framework). Is the necessary file /System/Library/PrivateFrameworks/SetupAssistantFramework.framework/Versions/A/ SetupAssistantFramework located somewhere else on 10.10?

I join in the outrage of Network Diagnostics being eliminated. Can't operate without it-- so if I have to, I'll go back to 10.10. (Yeah, missed a lot of upgrades. But got a lot of macs, all working as they should be-- exactly why I decided to upgrade tonight on this machine is becoming more of a mystery by the minute.)

Thank you for any insight you have-- and again, you should be knighted for these instructions.

So... since I didn't have SetupAssistantFramework from Yosemite, I figured I'd just install the three files missing in High Sierra. I disabled SIP, inserted Network Diagnostics, Network Setup Assistant and Network diagnostics UI.framework

where they should be. I figured this wouldn't work so I didn't bother with changing ownership. Rebooted... and it DID work. Can't imagine why it's working, or when it will stop (obviously at the most critical time) but for now I'm a happy camper. Thanks again Keith.

You just saved me big time, Keith. I didn't think of what would happen when an update occurred without the ownership changes. Just made them. Thank you! Yeah, I know Net Assistant is a separate program from Net Diagnostics. As the information superhighway is a dirt road at best at this location, Network Diagnostics is used daily (some days, hourly), so I glommed on to that and in my glee that it worked, I didn't check Network Assistant. Just did, and the news isn't as good. Apparently the missing files do count there-- it doesn't work. But that'll be a problem later. Just having Network Diagnostics now takes a big thorn out of my paw. Rest assured I did make my feelings known to Apple-- in graphic detail. Here's hoping that our collective gripes will fall on sympathetic ears, soon. Thanks again!