Windows 10: Home network discovery not working after latest W10 Update
Maybe, the next cumulative update will address your problem! At least for now,my home network is working properly. Still got the Wndows.old fragments hanging around on two systems but I can live with that. We'll see if it all goes away a month from the Version 1511 install date - whatever that was.
I tried messing around in the Registry deleting keys that referenced the Windows.old folder and ended up with an Error 1603! At least now I know Macrium Reflect restores W10 boot drives correctly from saved images!
Excellent point Ken! Before messing with the Registry either do an export it or best do a full image of your hard drive. It's really easy to mess up your PC if you do one little wrong thing to the registry. And create lots of Restore points also.
Macrium Reflect seems to be the most popular backup program now. I use Casper 8 which does very reliable hard drive images for backups.
How do you like Macrium? Any issues with it on Win 10? My Casper 8 works well on 10.
I used Acronis for years but it went bad with the release of W8.1 and of course they wanted $$ to pursue the problem I was having - goodbye Acronis. I then tried Easeus ToDo backup and that was a disaster. ProfJim on the Tweaktown Forum recommended Macrium Reflect and I have been using it for System and Scheduled Data backups. It ain't cheap and it ain't all that elegant in the way it interfaces the user but it does what it's supposed to do. Once you get used to the interface it's actually pretty neat. Macrium appears to be very much involved in fixing bugs or whatever that come up since there have been numerous upgrades and patches that have come my way since I have been using it.
I guess this is a side issue but how are you folks deleting the Windows.old directory? Are you just going into explorer and deleting it?
I use "Disk Cleanup" ( Run as Administrator ) and select: Previous Windows installation(s) and end up with no residual files.
I can confirm that the update did not fix this issue for me either.
As a side benefit of the update however after the reboot I was forced to reset my passowrd at account.live.com/password/reset because it had no idea who I was.
First I used: Start>Settings>System>Storage>This PC>Temporary Files>Previous Version of Windows>Delete. That worked for 5 of the 7 systems on my network as described in a previous post. I also in desperation tried Disk Clean Up and a bunch of other stuff but the fragments on the two systems would not go away.
Always good to have a boot CD that doesn't involve your main OS then you can delete anything. I have win PE diagnostic disks but a Linux bootable CD does the trick as well.
Ooops, sorry I used the dreaded word beginning with 'L'!!
Same here. These issues are driving me mad at work (with my 2 pcs and a small network). Sometimes it pseudoworks, then it all stop working altogether with no apparent reason (1 pc isn't even displaying itself under network).
I am wondering whether it would be useful or not to enumerate NIC brand of affected pcs.
In my case, I have two pcs (one newer i7 and an older AMD Phenom 1)
i7 has got two ethernet cards but I am currently using one. This is the master pc and it usually work fine 100% of the time. I think the NIC card is Realtek, but not 100% sure.
The AMD Phenom it's the offending one. It fails almost 99% of the time since I upgraded it to w10 (from w7). It has a nasty nForce chipset and the NIC card is also a not-so-good imho nVidia nForce network controller.
What are your nic cards in the pcs that are having these issues?. Those can be configured too. I remember to have changed a setting called "Priority and VLAN" to disabled on both NIC cards and the network was visible and working again, but it didn't last too much. After a few minutes (or after a reboot) it started failing again.
Any ideas on these type of parameters. Some of them seem very obscure.
I will try tinkering with Windows firewall tomorrow.
FWIW, mine's a Realtek PCIe GBE Family Controller.
My main comp still has the 1231 error with the net view command. Other comps don't.
It is a mystery, though, why only some are affected. I have five win 10 586 comps and they all suffer symptoms. But, as we all know, it is a bit of a moving feast.
I think MS must know what is going, after all, it only started with 586, so why it can't be fixed more quickly is a mystery.
I know this problem has been discussed with many variants but not quite the same as I'm experiencing, so I'm starting a new thread.
I did a clean install of Windows 10 pro 64 bit, and everything was running perfectly, that is until two days ago...
Win10 Home installed on 2 desktops and a laptop. They are networked together via ethernet cable. They belong to the same homegroup, and all "sharing" is working fine. .
My internet connection at home is a metered connection via Jetpack. My...
I've recently upgraded to windows 10. I use Bitdefender 2015, and have installed the latest compatible version for windows 10, after uninstalling previous using their uninstall tool, and also doing a repair.
In the Security and Maintenance panel...
Tried signing in with a pin number today following a bunch of updates.
Found my NAS server and other network shares.
It may have happened with an earlier update but I kept signing in with full MS account as I needed to see shares
C55-A5180 Toshiba laptop windows 10 preview 10122
After the latest windows 10 updates the laptop will remember the network but I have to manually click to connect the wifi. I have it set to auto connect, see picture. Any Ideas?