Software Conflicts with LockDown Browser on Mac (Complete Reference)

LockDown Browser maintains a "blacklisted application" list - running processes that prevent the exam from launching. Beyond the explicit blacklist, several Mac-side tools cause subtler conflicts. Below: every common conflict, the technical reason behind it, and the pre-exam neutralisation procedure.

How blacklist enforcement works

Before LDB launches the exam, it enumerates running processes via NSWorkspace.runningApplications + a sysctl probe and checks each against an institution-configured deny list. The default list, set by Respondus and overridable per-institution, includes:

If anything blacklisted is running, LDB shows a "Close these applications" dialog naming each. Quitting them via the dialog is sufficient - LDB re-scans after each click.

Per-conflict dedicated pages

Beyond the explicit blacklist, four categories of subtler conflicts cause exam-flow problems:

Articles in this section