I recommend to try the first solution in which basically we remove the Authorization Database. Downside, however, is that the Recovery mode is an advanced environment and is not as friendly.

As the name implies, this mode provides the user with a very limited set of tools to recover the operating system in case of serious problems. Instead, the only interface by which you can fix this, is the Terminal app which is accessible in the Mac Revocery Mode. When this happens, you would not have access to any standard interface or application, like Finder, to access the file system. 😉 Solutions (Updated on Dec 10, 2019)Īll you need to do is to either have the macOS forget about it (suggested by Jack Bryant, in the comments) or give it what it wants, which is the missing file.Īlthough these solutions are simple, the implementation seems a bit complex, especially for non power-users. Therefore, in the next boot, the macOS still expects to load the authorization plugin but it can’t find respective files, TeamViewerAuthPlugin.bundle, in /Library/Security/SecurityAgents/. However, if one doesn’t use the builtin uninstaller and removes the applicaton manually or by CleanMyMac, the plugin woul not get de-registered. To be more specifc, TeamViewer registers an Authorization plugin during the installation. I assume this happenes as the CleanMyMac’s uninstaller removes the TeamViewer along with all related files without the operating system being aware of the changes. In my case, this occured when I removed the Teamviewer manually by the CleanMyMac application. Security Agent was unable to create requested mechanism TeamViewerAuthPlugin:start.

When the Mac gets restarted after the uninstallation, following error box pops up and avoids the boot process from being completed.

In this post i’m going to provide two solutions for a recent issue with MacOS Catalina, where the macOS can’t boot after removing the Teamviewer.

Uninstall teamviewer mac completely