mdnsNSP.dll Blocked by Local Security Authority: Safe Fix

Brendan Smith
Brendan Smith - Cybersecurity Analyst
9 Min Read
Bonjour mdnsNSP.dll stopped by Local Security Authority protection on Windows.
Windows can block an outdated Bonjour module from Local Security Authority without classifying the file as malware.

mdnsNSP.dll is a namespace provider library associated with Apple Bonjour, used for local-network discovery. It commonly lives in C:\Program Files\Bonjour, but software such as Audinate can install its own copy elsewhere. The Windows message that it was “blocked from loading into the Local Security Authority” means LSA protection rejected that module; the warning alone does not prove malware. Keep LSA protection on. Verify the path and expected publisher signature (Apple for Apple Bonjour), identify which app installed Bonjour, then update or repair that app. Uninstall Bonjour through Windows only when no installed app needs it.

The warning often appears after a Windows 11 security or application update leaves an older Bonjour component installed. The number in a device path such as \Device\HarddiskVolume3\Program Files\Bonjour\mdnsNSP.dll is not a threat score and can differ between PCs.

What the mdnsNSP.dll LSA warning means

Local Security Authority handles Windows sign-in credentials and authentication tokens. LSA protection prevents untrusted or incompatible modules from running inside that sensitive process. Microsoft says that when LSA blocks software, Windows names the blocked file in a notification.1

Bonjour is a local-network discovery component used by Apple software and some audio, printing, and device-management applications. Windows can block its namespace provider DLL while the rest of the app still appears installed. That is a compatibility decision by Windows, not an instruction to turn the protection off.

Why can a valid Apple-signed DLL still be blocked?

A valid publisher signature and permission to run inside protected LSA are different checks. Microsoft requires plug-ins loaded into protected LSA to meet its Microsoft-signing and security requirements. An ordinary Apple signature can help identify a legitimate Bonjour file without satisfying that extra requirement. Repairing the same package may therefore leave the warning unchanged; it does not automatically mean the file is corrupt.4

Is mdnsNSP.dll malware?

An expected Bonjour copy is usually legitimate when all of these facts line up:

  • the file is under C:\Program Files\Bonjour or C:\Program Files (x86)\Bonjour;
  • Properties shows a valid digital signature from Apple for the Bonjour copy;
  • Bonjour, iTunes, Apple Devices, iCloud, or another known discovery-dependent app is installed;
  • the warning appeared after a Windows or vendor update and there are no other security symptoms.

A different vendor path needs context: Universal Audio documents this warning for \Device\HarddiskVolume3\Program Files\Audinate\Shared Files\mdnsNSP.dll. Match that path to the installed Dante package rather than treating it as malware merely because it is outside the Bonjour folder.5

Investigate further when the name appears unexpectedly in AppData, Temp, Downloads, an unexplained program folder, or a startup location; when its signature is missing or invalid; or when it arrives with unknown installers, browser changes, disabled security settings, repeated alerts, or unexplained network traffic. A filename alone is weak evidence. Our DLL safety guide explains why path, publisher, source, and behavior need to agree.

  • Expected vendor path and valid signature: check the matching application’s compatibility guidance; keep LSA protection on.
  • Known Bonjour installation that no app needs: uninstall through Installed apps or Programs and Features, then restart.
  • Unexplained path, invalid signature, or unknown installer: keep the DLL blocked and scan before deleting individual components.
  • Warning returns after repair or uninstall: compare the newly reported path with the original, then identify the package that still owns that copy.

Check the path, signature, and parent app first

  1. Read the complete path in the notification. Record the folder and filename, then locate the corresponding installed application in File Explorer. Do not assume every HarddiskVolume3 is the same drive on every PC.
  2. Open the file location. For Apple Bonjour, check C:\Program Files\Bonjour and, on some systems, C:\Program Files (x86)\Bonjour. If the warning names Audinate, check the matching vendor installation instead.
  3. Check the signature. Right-click mdnsNSP.dll, choose Properties, open Digital Signatures, and inspect the signer. For Apple Bonjour, a valid Apple signer supports the legitimate-copy verdict. For a copy bundled by another vendor, compare the publisher and version with that vendor’s supported package. Microsoft Sysinternals Sigcheck can show version and signature-chain details when the normal dialog is unclear.3
  4. Find the parent application. Open Settings > Apps > Installed apps and look for Bonjour and the Apple or device-discovery app that installed it. If an audio or hardware tool relies on Bonjour, check that vendor’s current installer before removing the component.

For the complete process decision—including what mDNSResponder.exe does, how to test whether an app needs Bonjour, and how to fix high CPU or remove the service safely—use our mDNSResponder.exe and Bonjour troubleshooting guide.

Choose the fix for the app that installed the DLL

Removing Bonjour is not equally harmless for every application. Check the app name and the exact path before choosing a branch:

  • Dante / Universal Audio: Universal Audio says this LSA warning has no known impact on Dante and UA product use in its documented case, and identifies Dante Controller 4.16 as the resolving update. Use the vendor’s current supported package; 4.16 is the cited fix, not a claim that it is today’s latest release. If you also run UAD Software 11.4.0–11.8.1, read the installation-compatibility note linked from that advisory before updating.5
  • Source-Connect 4: Bonjour supplies the optional Source-Connect I/O DAW connection. Source Elements warns that removing it leaves that I/O plugin unavailable. If you need that workflow, keep the component installed, follow the vendor’s current troubleshooting guidance and ask support for a compatible alternative before removal.6
  • iTunes or another Apple package: check the Store or Apple Software Update as appropriate, then try the supported repair below. An update to the parent app is not a guarantee that its bundled DLL now meets LSA requirements.
  • No Apple apps installed: that alone does not make Bonjour malicious. Audio, printing and other discovery software may supply it. If you cannot identify the owner or whether you need it, pause removal and ask that software’s support team.

You can close the notification while investigating and leave LSA protection enabled. Closing it does not update the DLL or establish that every dependent feature works; test the discovery, printing or audio function you actually use.

Program Compatibility Assistant blocks mdnsNSP.dll in Audinate Shared Files from Local Security Authority
This vendor example names Audinate\Shared Files, not the Apple Bonjour folder. Match the path to your installed application. Source: Universal Audio Support (reference 5).

How to fix mdnsNSP.dll blocked by LSA safely

  1. Keep Local Security Authority protection enabled. Do not weaken credential protection to make an old module load.
  2. Update the parent app. For current Apple apps on Windows, check Microsoft Store updates. Older Apple packages may use Apple Software Update.2 For Dante, audio, printing, or other discovery tools, install the vendor’s current supported package.
  3. Repair before removing. In Control Panel, open Programs and Features, select Bonjour or the parent application, and choose Repair or Change when available. Restart Windows and test the app.
  4. Uninstall only if Bonjour is not needed. Use Settings > Apps > Installed apps or Programs and Features. Remove the parent app only if you no longer need it; otherwise use its vendor-supported component repair or removal instructions. Restart after the supported uninstall.
  5. Confirm the result. Check that the warning no longer appears and that the app, device discovery, printing, or audio workflow you actually use still works.

If the warning returns after updating or repairing

Compare the full path in the new alert with the original. A different folder can point to another bundled copy. For a persistent warning from the same known app, collect the app version, DLL version from Properties, Windows version from winver, and the time of the warning for vendor support.

For an optional read-only check, open Event Viewer → Applications and Services Logs → Microsoft → Windows → CodeIntegrity → Operational. Microsoft documents event 3033 for a failed Microsoft-signing-level requirement and 3063 for shared-section security requirements. Inspect the event details for the actual process and DLL path; the number alone does not identify Bonjour or diagnose malware. Do not change registry or protection settings to collect this information.4

If a partial Bonjour removal breaks an app or networking

Do not download a replacement mdnsNSP.dll from a DLL mirror and do not copy it into System32. Reinstall the current parent application from its official source so Windows receives the matching Bonjour files and installer records. Then repair the application or uninstall it cleanly.

If the problem started immediately after manual service, registry, or DLL deletion, undoing those edits by hand can make the catalog less predictable. Reinstall the owning package first. If Windows networking itself remains damaged, use the built-in Network reset only after recording VPN, proxy, and custom adapter settings that you may need to restore.

When mdnsNSP.dll needs a malware scan

Scan the PC when the DLL path does not match a known installed vendor package, its signature is invalid or names an unexpected publisher, it returns after a supported uninstall, or the same incident includes unknown startup entries, scheduled tasks, browser changes, disabled security tools, or outbound connections you cannot explain.

Keep the suspicious copy blocked. Run a full Gridinsoft Anti-Malware scan to check the surrounding folder, startup entries, scheduled tasks, services, bundled apps, browser changes, and other persistence that could recreate the file. If a suspicious installer already ran, follow the broader Windows security audit after malware after the first scan.

Gridinsoft Anti-Malware
Scan an unexpected mdnsNSP.dll copy

Scan for hidden malware, unwanted services, and startup components.

Download Anti-Malware

For WindowsOfficial Gridinsoft download

What not to do

  • Do not disable LSA protection just to silence the warning.
  • Do not unregister or force-delete mdnsNSP.dll before checking which app uses Bonjour.
  • Do not delete the Bonjour service or edit Winsock/namespace-provider registry entries as the first fix.
  • Do not download a standalone DLL from a mirror.
  • Do not assume a valid signature proves the whole PC is clean; path, source, and behavior still matter.

FAQ

What is mdnsNSP.dll?

It is a Bonjour namespace provider library used for local-network service discovery. Apple Bonjour copies normally live in the Bonjour program folder with a valid Apple signature; some applications, including Audinate software, install a copy in their own vendor folder.

Why does Bonjour keep getting blocked?

Windows is preventing an installed Bonjour module from loading into LSA. The warning can repeat when the older component remains installed, a parent app reinstalls it, or a repair/update did not replace the incompatible copy.

How do I unblock Bonjour on Windows 11?

Do not bypass LSA protection. Update or repair the app that installed Bonjour. If no app needs Bonjour, uninstall it through Windows and restart.

Can I delete mdnsNSP.dll?

Do not delete it directly. Use the parent application’s repair or uninstall process so its service and networking registrations are removed consistently.

Does this warning mean my PC has a virus?

No. The warning alone means Windows blocked a module from LSA. Treat it as suspicious only when the path, signature, parent app, or surrounding behavior does not match a normal Bonjour installation.

References

  1. Microsoft Support. “Device Security in the Windows Security App.” Microsoft, accessed November 5, 2026. https://support.microsoft.com/en-US/Windows/Security/Windows-Security/device-security-in-the-windows-security-app
  2. Apple Support. “Update Apple software for Microsoft Windows.” Apple, updated June 8, 2026, accessed November 5, 2026. https://support.apple.com/en-us/118406
  3. Microsoft Learn, Sysinternals. “Sigcheck v2.93.” Microsoft, updated October 15, 2026, accessed November 5, 2026. https://learn.microsoft.com/en-us/sysinternals/downloads/sigcheck
  4. Microsoft Learn. Configure added LSA protection. Accessed November 5, 2026.
  5. Universal Audio Support. mdnsNSP.dll: This module is blocked from loading into the Local Security Authority. Accessed November 5, 2026.
  6. Source Elements Support. Bonjour error “This module is blocked from loading” for Source-Connect 4. Accessed November 5, 2026.
Share This Article
Cybersecurity Analyst
Follow:
Brendan Smith has spent over 15 years knee-deep in cybersecurity, chasing down malware from the gritty reverse-engineering of old-school trojans all the way to wrangling full-blown incident responses for small-to-medium businesses that couldn’t afford a full-blown breach. Over at Gridinsoft, he’s the guy piecing together those double-checked guides on nasty stuff like AsyncRAT, a remote access tool used in malware campaigns—helping readers make sense of the threat and work through cleanup without the extra headache.
Leave a Comment

AI Assistant

Hello! 👋 How can I help you today?