How to uninstall DisplayLink Manager on Mac

Before removing DisplayLink Manager, record wanted display arrangement and rotation settings and make sure the Mac's built-in or directly connected display can be used. A login-screen extension requires the vendor's component removal flow, not just moving the Manager app.

Use the vendor remover for installed components

The official removal instructions distinguish two cases. With no login-screen extension, quit Manager through its Quit control and move the app from Applications to the Trash. With the extension installed, run DisplayLink Software Uninstaller from Applications to remove both. Keep the installed bundle until that flow completes.

The newer End-User Cleaner removes components and user data. Its actions are enabled by default, including Reset Screen Layout, which resets macOS display arrangement and rotation. Review those actions first and leave the layout reset off if keeping that configuration; component removal also removes the login-screen extension. Complete any requested restart.

For a Homebrew installation, the displaylink cask supports:

brew uninstall --cask displaylink

Ordinary uninstall unloads its listed services, quits the agent, processes com.displaylink.* package receipts and deletes its listed installed directories and launch files. Zap additionally targets the main container and scripts plus the DisplayLinkShared group container and scripts. Direct --zap ignores Mole choices and can erase retained preferences.

ls -ld "$HOME/Library/Containers/com.displaylink.DisplayLinkUserAgent"
ls -ld "/Library/LaunchAgents/com.displaylink.loginscreen.plist"

Printed paths remain. Missing-path errors apply only to those locations; permission errors leave them unknown. These checks do not verify every package receipt, service or display behavior.

What Mole lists

The selected app and exact main container/scripts are normally checked when present and unprotected. The team-prefixed DisplayLinkShared group is reviewed and unchecked by default, with deletion still subject to ownership checks. Remove data and settings with apps is off by default; do not assume that enabling it selects this group or removes every separately installed component. Keep a guarded container rather than bypassing protection.

What this test covered

The official package installation was removed with the official Mole release on September 23, 2026. App, login-screen launch-agent file, scripts and temporary cache removal were covered. The main container and shared group remained, two package receipts were not cleared, and an unclaimed XpcService container was not collected. Vendor uninstaller/Cleaner execution, populated display settings recovery and complete package removal were not tested.