4 ms·
I had the same thing. I forget the exact course of action, but from what I remember: - ~/Library/LaunchAgents/com.microsoft.update.agent.plist - ~/Library/Ap
by FredPret 2y ago
I had the same thing.
I forget the exact course of action, but from what I remember:
- ~/Library/LaunchAgents/com.microsoft.update.agent.plist
- ~/Library/Application\ Support/Microsoft\ AU\ Daemon/
- /Library/Application\ Support/Microsoft/MAU2.0/Microsoft\ AutoUpdate.app
Nuke all of that, though for the last one you may have to chmod 000 it.
Then do a search for everything with Microsoft Update in it and delete that too.
This process kind of reminds me of removing spyware infestations from Windows XP.
- schrodinger 2y agoIn case this is new to some people: you can run $ mdfind [thing] like $ mdfind microsoft from the command line and it was an ultra-fast search using the index that Spotlight search uses. It's great to find pesky files when trying to rid yourself of an app and can't figure out what's left. I usually pipe it into a text editor (mdfind 1password | subl), use my editor to put rm or so rm at the beginning of each one, then paste it into terminal to run. That lets me audit the files first as opposed to xargs but I'm sure there's a million ways—the point is mdfind can be useful.