
- #Kill finder terminal install
- #Kill finder terminal full
- #Kill finder terminal pro
- #Kill finder terminal mac
I’ve found that adding a bit of a pause is a safe bet to make sure it works every time. Now especially when following up an installation with a script, it is a good idea to do some testing on the timing. That way, directly after Box Drive is installed from Self Service, I know that the Finder Extension is going to load.
#Kill finder terminal install
So I can write up a script like the one above to enable the extension and include it in the install policy to run after. As stated before, I don’t want to have to logout and log back in for it to enable. For example, in my Box Drive install policy, I want to make sure that Box Drive’s Finder Sync extension enables directly after Box Drive installs.
#Kill finder terminal pro
Where I find these commands most helpful is in a Jamf Pro policy for installing or uninstalling the parent app. I suppose you could just manually run the script at various times, but that would defeat the purpose since it’s just as easy (or easier) to actually go into System Prefs and enable/disable the extension. Now, you may be wondering how this can be useful for you. If I wanted to enable this particular Finder extension, I would enter this: pluginkit -e use -i Īnd if I wanted to disable it, I’d run this: pluginkit -e ignore -i You can ignore the version number the important thing is the identifier. For example, if I’m looking for items that contain box, I’d run: pluginkit -m | grep "box"Īnd I get the result: ()

It’s usually easy enough to navigate this list manually, but if you want to tailor items to your specific needs, you can always use grep. What you’re looking for is the name of the developer or app name of whatever respective Finder Extension you’re trying to control. Now, you’re going to get a ton of com.apple entries that you shouldn’t touch and likely don’t care about. In order to get a list of Finder Extensions on your Mac, run this through Terminal: pluginkit -m So here’s a way you can enable or disable any app’s Finder Extension from the command line. But there are a number of applications that just expect you to manually turn on or off their Finder Extensions.
#Kill finder terminal full
Not to pick on Box, as their newest iteration of their sync client, Box Drive, does include a full uninstall script.

You would think this could be scripted somehow so it doesn’t have to be manually removed… 😉 Even Box has instructions for manually disabling the Box Sync Finder Extension in order to uninstall Box Sync completely in the instructions on their website: Unfortunately, the Finder Extension hangs around and even sometimes can prevent you from trashing it. Similarly, when you attempt to uninstall Box Sync, you’d think you could just quit it and throw the application in the trash. As you might imagine, that’s really annoying to do during every new employee setup. Unfortunately, this means if I am setting up someone’s computer for them and I want to introduce them to Box Sync, I have to logout and log back in so Box Sync can load the Finder Extension. It loads on every other subsequent launch… just not on the initial one. What it doesn’t do on its initial launch is enable its Finder Extension, and show all of the badges and menus. When I install Box Sync for the first time and sign in, it connects to the cloud and displays my files in the Finder, as it should.
#Kill finder terminal mac
You can find a list of the Finder Extensions installed on your Mac in System Preferences > Extensions.Ī common problem for administrators like me, however, is that these extensions may not always play nice when trying to automate a task. For example, the institution I work at utilizes Box Sync for file syncing. These extensions provide all sorts of additional functionality, from displaying badge icons to reflecting a file or folder’s sync status, adding a contextual menu, etc. macOS provides the developers of these applications with the ability to utilize a Finder Extension, or as Apple calls them in their dev note, Finder Sync Extensions.

Typically, these applications sync files from a cloud server down to the local machine and vice-versa. There are a number of applications for macOS that utilize a Finder Extension. I stumbled upon this about a month ago as I was trying to automate something, so this may be relevant information to some.
