There was once a time when Windows 10 was not as bad at managing local network connections. Sure, it was a couple of orders of magnitude slower than Windows 7 in doing so, but at least, once sharing & etc. were “turned on” things were fairly easily (if, again, slowly) “seeable,” but as the inevitable and very nearly unavoidable “update” cycles have progressed, access to local network resources has regressed.
If saving a file from the internet, for example, it doesn’t matter what browser I use, whether a VPN is engaged or whatever, if I want to save it to anything BUT my local machine, I have to type in the IP address of the resource I want to save it to. Then, it I only have to just twiddle my thumbs waiting on Win10’s execrably slow access of LAN resources.
Similarly, if attempting to access other LAN resources (computers, NASes, etc.) via “Windows Explorer” file management. . . no network resources available, no matter WHAT I have set up in “Network and Internet Settings.” In fact, every now and then, at apparently random times, the stupid “Network Discovery is Turned off” error pops up. I check, and no, it is turned on. Turn off/back on anyway. Semi-fixed: no error popping up, but still have to either use manually-created shortcuts placed on desktop, on toolbar, etc., or type in the resource address. (Yes, as a result of Win10’s stupidity, I have finally given ALL LAN resources fixed IP addresses).
Oh, and yes, I have made sure all the dependent services, etc., are set to start automatically and are running, and that–again–network sharing is set properly for a “private” network, etc., etc. Me$$y$oft’s Win10 still screws it up, usually sooner than later.
It’s as though Me$$y$oft engineers have sat and thought, and thought, and thought, and said (collectively), “Here’s something that will REALLY screw with users. Let’s do it!”
#feh
Why couldn’t Me$$y$oft at least be like Linux developers and fix something and then move on to creating more problems.