Well, cr-p. It didn't hold through reboot, however - still lit now with Bluetooth off. No joy after reboot even if I include disabling Bluetooth first in device manager. Any manipulation of on off status still leaves it in wrong status indication after reboot.
@Holydoc , is yours holding correctly through reboot?
Buils 1151 is a typo, should be 1511
still after build 10586 i did get updates and thanks to build 1511 my network is gone again...
Right now i have 3 pc's in the network and 4 in the Homegroup. But as you know, i made a shortcut in the Start Menu and it does not bother me anymore.
Can enter every pc in the network.
I did see some references to mapped network drives earlier in this thread, but didn't see (or missed) anything specific. I would like to report that KB3116908 seems to have fixed a problem I've had since the installation of W10. My several mapped drives were pretty regularly being dropped after wake-up from sleep or on reboot. When I would re-map the drives the previous mapping would appear in the list of available drive letters, so it was a rather simple exercise to reassign them to the drive letters had been previously used (necessary for many applications that access these drives). But manually re-mapping was time consuming and annoying, so I left many unmapped until they were needed. After installing and rebooting this morning, all six or so drives were mapped, like magic!
So score a real fix for this update, and hopefully this is fixed for good.
On another subject, I just got notice that this update was ready to install yesterday. Why is it that I am getting these updates just about a month on average after they are initially released? Is it that MS just has too many W10 installations to send this down to? Or what?