3 ms·

This is 100% unacceptable behavior of windows. You hmare looking at it from the wrong angle. This isn't a case of "Windows is broken because it crashes when the

This is 100% unacceptable behavior of windows. You hmare looking at it from the wrong angle. This isn't a case of "Windows is broken because it crashes when the user does something and the work around is, 'dont do that's" The correct way to look at this is that the OP has discovered a significant flaw in the windows network stack. The correct description is: "A flaw in windows PnP discovery allows a denial of service attack against the windows networking stack. Windows PnP service track and caches the UUID and Mac address of all entities that appear in the local network and fails to purge old or outdated services until it deadlocks"

hnlmorg 2y ago
> This is 100% unacceptable behavior of windows. You hmare looking at it from the wrong angle. This isn't a case of "Windows is broken because it crashes when the user does something and the work around is, 'dont do that's" That isn’t remotely what I said though. My point was: It’s both vendors fault. If youd bothered to spend even 30 seconds longer to properly read my comment instead of knee jerk reacting to anything that’s even remotely sympathetic to evil Microsoft then you’d realise that I’m not letting MS off the hook for this. I’m just saying there’s enough blame to go round on this particular fault.