Windows 10 build 1909 Network borked again.

[hashcake]

Yet again another Windows 10 update has buggered up seeing other devices on my network.
My desktop is fine although the last update available was 1903 which if I remember correctly, was the first time MS ballsed up networking, it's my laptop that won't play ball with 1909.
Thankfully my laptop can still see my NAS shared folders which is more important but it can only see itself under network.
Has anyone else experienced this?
I've tried every possible fix included making sure SMB is fully enabled.

 

[ChrisH]

My older WD Mycloud doesn't even show up on my network with all the SMB settings sorted. The only way I can use it sensibly is to map it by IP address to a drive letter, then it works fine.
Windows has become supposedly more secure but in my opinion its now gone a bit too far for the home user.

 

[hunnymonster]

Or conversely WD are playing really fast & loose with your data by snot releasing firmware that supports current protocols, rather favouring you dropping the security on your PC to let miscreants run riot.

If you buy a WD MyPassport Wireless Pro today it still doesn't support anything other than SMBv1 (the most insecure variant) forcing you to enable that on your PC that you may take and put on public WiFi where the above miscreant is waiting... The firmware hasn't been updated since 2017 against any vulnerabilities. How is that Microsoft's fault? (And trust me, I'm no fan of Microsoft)

 

[Snapsh0t]

MS broke W10 networking in 1709 (or whatever it was called then) and it's never been fixed.