YES that is another bug I had where your login credentials apparenetly get deleted to access other PC's on the Network. And the bug also prevents the use of the original correct stored username/password and instead you have to set all your PC's to the same MS ACCOUNT to get the network passwords working again.
Just so I can keep track of all the sub plots in this tread:
** We have the original issue where you click on Network in explorer and it don't find nothin'
** Then we have the NAS issue ( which honestly sounds like it can only recognize ntlm and Win10 only speaks ntlmv2 or later )
** And now there's this credentials issue.
Holy Frijoles
Did I miss any?
Still have working and not sporadic issues. With my primary Laptop on only this morning after Boot it wasn't seeing itself in File Explorer's Network. Laptop 1 has been the one with the least amount of issues and this was the first time I've ever seen it NOT VISIBLE to itself with only it turned on.
I just went into services.msc and STOPPED Firewall and right then Laptop 1 became visible to itself, so something in the Firewall settings must be in play in the sequence of events. Interesting though when I RESTARTED Firewall, Laptop 1 was still visible now. So perhaps something in the process of Firewall starting it's impacting another Networking service process.
I'll add a couple of new issues (Windows.old won't delete and at least one screwed up boot drive) to my original Discovery problem. Just a recap of the W10 Version 1511 "adventure." Before the W10 update to Version 1511 all was well as far as I could tell on my home network. Now after the two cumulative W10 Version 1511 Updates...
GA-EP45-UD3P/Q9550 Win 10 Pro takes 33.8GB on 120GB SSD Boot Drive.
Office 2010 Installed.
Windows.old deleted OK.
Nvidia 560 TI.
Macrium Reflect backup file size 21.3GB.
GA-EP45-UP3P/E8500 Win 10 Home takes 32.7GB on 120GB SSD Boot Drive.
Office 2010 Installed.
Windows.old deleted OK.
Nvidia 9600 TI.
Macrium Reflect backup file size 21.2GB.
ASR Z77 Extreme4/2600K Win 10 Pro takes 47.0GB on 240GB SSD Boot Drive.
Office 2010 Installed.
Windows.old deleted OK.
System NOT visible on network.
Nvidia 560 TI.
Macrium Reflect backup file size 23.3GB.
ASR Z97 Extreme6/4790K Win 10 Pro takes 27GB on 240GB SSD Boot Drive.
Windows.old deleted OK.
Nvidia GTX 760.
Macrium Reflect backup file size 10.5GB.
ASR Z97 Extreme6/4790K Win 10 Pro Takes 43GB on 240GB SSD Boot Drive.
Windows.old deleted partially but left Point.64.sys in folder.
Nvidia GTX 960.
Macrium Reflect backup file size 25.6GB.
ASR Z77 OCFormula/3770K Win 10 Pro takes 78GB on 240GB SSD Boot Drive.
Office 2010 Installed.
Windows.old deleted partially but left IntcDAud.sys in folder.
Regedit hangs!
OnBoard Video.
Macrium Reflect backup file size 23.3GB.
ASR Z97 Fatal1ty Killer/Xeon ES-1246 v3 Win 10 Pro takes 28GB on 240GB SSD Boot Drive.
Windows.old deleted OK.
OnBoard Video.
Used for Home Server.
Macrium Reflect backup file size 23.3GB.
All of the systems have ~about~ the same software installed with the exception of Office and Plex on the Home Server. All of the systems have had CCleaner run to delete temporary files etc. All of the systems originally had a clean install of W10 with the exception of the ASR Z77 Extreme4/2600K.
Since no answers are coming, it looks like I got at least two systems that need a clean re-install of W10 and hope that it fixes whatever is going wrong! Does anybody know for sure if Version 1511 is available for download?
@Ken429
You'll get 1511 if you use the MCT. Just be aware of that there are several posts stating the a clean install does not help the networking issues.
Good Luck!
DoItJust,
MCT? Is this the site you are referring to?
https://www.microsoft.com/en-us/soft...load/windows10
MCT = Media Creation Tool; downloadable from MS.
DoItJust,
I assume that was a yes for the link. Anyway, I downloaded W10 via MCT on 11/21/15 and it still looked like the original version I downloaded day one. I downloaded it today and it looks like it's the latest version. So ... I'll take a few hours on a rainy day and install a clean copy and see if it fixes a few problems. At least there will be NO Windows.old to deal with!
Looks like the latest cumulative update (12/3/15) fixed Discovery on the one system that was still screwed up as far as Network Discovery was concerned. At least for the moment. Thank you MSFT. Now, on to the messed up .sys files that cannot be deleted from Windows.old.
The (KB3116908) update rolled out yesterday doesn't fix the Network issues. I can see all 3 Laptops only from the master started first.
That's really all I need, but it would be nice to have it working fully.
Quote