On November 11, 2025, the November monthly security update "KB5068861Has been released.
This update is very important as it fixes several "flaws" caused by last month's preview update "KB5067036" that troubled many users (including me).
In this article, I tested in my environment what KB5068861 fixed and whether any new problems had occurred.
1. [Good news] The bug in KB5067036 has been fixed
First, the good news is that the following serious issues caused by last month's preview update "KB5067036" have been fixed by applying this "KB5068861" update.Fully resolvedI have confirmed that.
① Fixed the issue where the Task Manager remained (became a zombie)
After applying "KB5067036", even if you close the Task Manager with the "x" button, the process (Taskmgr.exe) does not end, and there was a risk of memory leak.It was nicely fixed.
② Fixed the problem of file extension display in Explorer
In my environment, I confirmed that "KB5067036" caused "Even if you set the extension to hidden,.dll,.cplThere is also a bug in Explorer that causes file extensions such as ".It has been corrected to normalI have confirmed that.
(Microsoft's official release notes mention the Task Manager issue, but don't specifically mention this fix for Windows Explorer.)
2. [New phenomenon] LSA Protection (Local Security Authority Protection) blocks DLL loading
The problem was fixed, and I thought I could finally relax, but unfortunately, in my environment,Another new phenomenonhas been confirmed.
After installing KB5068861, some apps (such as third-party tools) that previously worked without problems now display a Program Compatibility Assistant dialog box when launched.
"This module has been blocked from loading by the Local Security Authority: ….mdnsNSP.dll'
This is a phenomenon in which the Local Security Authority (LSA) Protection, an important feature of Windows security, determines that a specific DLL file (program component) required by an app is "untrusted" and blocks it from being loaded into memory.
Attention! How to check if Windows 11 "Local Security Authority Protection" is enabled
mdnsNSP.dllIt is,Apple's Bonjour serviceis a component of.
Popular apps:
- iTunes: It is used by PCs to communicate with Apple TV and the "Remote" app on iPhones/iPads.
- iCloud for Windows: Used for printer sharing (AirPrint), photo syncing, etc.
- Some third-party software, such as Adobe Creative Suite, may also install it for network functionality.
2025/11/13 Update:
This blockedmdnsNSP.dllis the file for Apple's Bonjour service,Backup software with NAS detection, such as Acronis True ImageIt may be installed by.
*In the author's environment, it was confirmed that it was installed at the same time as installing Acronis True Image 2025 (permanent version).
Why does LSA protection block this DLL?
- Enhanced LSA protection: This update enables the Local Security Authority (LSA), the core of Windows security, to:DLLs that are not signed by Microsoft or safety verified is loaded into its own memory space,Stricter BlockingI guess that's what they started doing.
mdnsNSP.dllHow it works: This Apple DLL acts as a network service provider (NSP) and appears to be heavily involved in Windows networking (and the authentication process involving the LSA).- Blocking occurs: LSA Protection (based on its new, stricter rules) has determined that this Apple DLL is "untrusted code" andBlocked from loading due to "potential security risk"It was.
This phenomenon appears to have occurred in the past.
Summary: Should it be applied?
This "KB5068861" fixes serious issues caused by "KB5067036" (such as zombie Task Manager).Important monthly updatesIf you have installed "KB5067036" (preview version),Must be applied.
However, if you encounter an "LSA Protection" issue where a specific app stops working properly after applying "KB5068861," it's possible that the app is not compliant with LSA Protection (i.e., is operating in a security-shady manner).
In that case,
- App developerPlease update to support Windows 11 LSA protection.Recommendation)
- (Not recommended and at your own risk) If you absolutely need to use the app, temporarily disable "Local Security Authority Protection" from "Windows Security" -> "Device Security" -> "Core Isolation" details.offTo
(Note: Operation 2 is not recommended as it will lower the security level.)
If you have any information about whether DLL blocking due to LSA protection is occurring in your environment, we would appreciate it if you could let us know in the comments section.

