I just built a new pc recently and I've been getting this same error mesage, however bonjour does seem to be functioning properly from what I've tested. Is there any reason to be concerned or should I just click "Don't show this message again"?

 

Thanks for the lessons, friends.

 

Just to be clear. "EOL" is a red flag that the industry uses in an attempt to enforce their standard planned obsolesce process on all those who are gullible enough to swallow the cool aid. There is no earthly reason that you "need" to rebuild or "upgrade" systems simply because they say so. If there is some technical hardware or other software reasoning behind an upgrade to an even more deficient system like win11 then so be it. But simply forcing yourself to endure an obtuse process of upgrades simply because they are no longer giving out free "updates" or stopping "updates" all together is a fools errand. "Updates" are simply a method for OEM's to force all their system garbage to run and makes certain any attempts made by the end user to reverse engineer their shit are thwarted. Nothing more...

 

Amen to that, mate... That's why on my personal pc i'm still on 21H2 LTSC but the machine i'm talking about is a workstation that I use for working remotely so if they upgrade I'll have to stick with the company policies.

 

edit- I thought I found a solution but I just got the mdnsNSP.dll error again today so nevermind

 

Last edited: May 5, 2025

https://learn.microsoft.com/en-us/w...=intune#disable-virtualization-based-security

https://learn.microsoft.com/en-us/w...itional-lsa-protection#disable-lsa-protection

Disablin' the VBS and then LSA has solved my problem entirely (and I also got some improvements in terms of performances). It could be a security risk but well... I've used W10 for years without all these fancy security stuff, I could care less about that honestly...

 

I have those services running, BUT they are only allowed local lan access because I run a windows domain on my backend lan. Any/all internet access to those services (as well as the PDC and backend lan) is disabled completely. If it wasn't for the PDC I would simply disable them outright.

Fantastic you found the solution!

 

Last edited: Saturday at 11:47 PM