Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the '10.5: Force FileVault to read Launch Services data' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.5: Force FileVault to read Launch Services data
Authored by: kopischke on Jul 03, '09 05:09:45PM
There is a problem with the brute force solution of resetting Launch Services data: besides re-reading the Launch Services bindings stored in the user's it will, among other things, also reset the cache storing the "safe" flag for applications that install protocol handlers (quite a lot of OS X apps do, I'll only mention Evernote, Pukka, Bwana...), which will result in the first call to the app or protocol triggering a "You are opening this application for the first time" alert. Resetting at every login means also dismissing this alert again every time, which is annoying. There are ways around this too, but they involve even more intrusive system tinkering (see the following Apple discussion thread, esp. pages 3 to 5).

The alternative is to sidestep the issue and not reset Launch Services at all, but to only selectively re-read the user's Launch Services bindings. lsregister won't help there, but with a bit of tinkering Andrew Mortensen's duti will. For everybody's convenience, I have created a shell script (with a few supporting files) that will do that exactly, adding a few extras like registration as a LaunchAgent. It's called GoodCompany (because it keeps your associations, and goes well with FileVault), it's free and it's available here (the shortened link is for statistical purposes only, as it helps me keep an eye on download numbers; if that bugs you, the original link is You can keep an eye on the hash tag #GoodCompany in my Twitter stream to keep abreast of updates.

[ Reply to This | # ]