rickybobby14

@clowncracker thanks for your post about this obscure Windows Update setting! I "stumbled upon" your post while trying to diagnose an mDNS network storm that triggered the same avahi error messages that you had. In my case the errors were on my pfSense firewall, which runs the avahi package to manage discovery between vLANs. I didn't even suspect Windows as the source of the problem until I found your post, but turning off that Windows update setting stopped the problem instantly. Then I went back through my logs and found the whole thing started a couple of weeks ago, immediately after I reluctantly "upgraded" a Windows 10 PC to Windows 11. For anyone else stumbling upon this thread, in my case the first symptom of a problem was in my Matter server logs, which showed thousands of these errors: 2026-02-05 23:50:13.902 (Dummy-2) CHIP_ERROR [chip.native.DIS] DNSSD packet parsing failed (for non-srv records) 2026-02-05 23:50:13.902 (Dummy-2) CHIP_ERROR [chip.native.DIS] DNSSD packet parsing failed (for SRV records)Also should mention that my network also has a Home Assistant VM running. I don't think that has anything to do with this, but it seems like a coincidence worth mentioning in case there is some connection I don't understand.