My thread has wander off in several directions and I still have no idea on what went wrong with 3 of the five systems I let MSFT update to the latest release of W10. I spent an hour on the phone yesterday with MSFT Technical Support. They seemed to indicate they might have a problem, put me on hold to further investigate and never returned! I will probably go down that path again today since I'm not getting much guidance on this site on what to do other than play with Homegroup (which will not do what I need to do and never has) and/or buy all new networking hardware!! Sure seems like someone out there who is a Windows networking expert should be able to give me some guidance on what to look for in the 3 systems that are crippled? Help would still be appreciated.
Have been messing with this since last Friday with no luck despite numerous suggestions. I am thinking MS will have to fix.
Keep the suggestions coming just in case. Maybe someone will hit on a solution.
I'm able to get everything functioning only on whichever of my 3 laptops I turn on first. That one can then see the others in File Explorer. But the other 2 can't see the Network.
I was able to get Media Streaming displaying properly in all 3.
I was able to setup a new Homegroup also that works.
But there is a definite BUG in Networking and Sharing with the Threshold 2 upgrade. Probably related to the fact they did a lot of setting resets, deleted all incompatible software without telling you until after the upgrade what got deleted, changed a bunch of defaults back to MS apps, and they added a lot of new security features to protect the core.
Expect some headaches after this upgrade.
has same issue; my computer does not show up when clicking "network" on start menu (or anywhere else) used troubleshooter which recited "files missing" winsock corrupted googled it MS staff post suggested deleting winsock and reinstalling TCP/IP in properties
of ethernet adaptors; however, at last step got message "cannot reinstall these filed" permission needed. what a bunch of crap!
same thing happened on my husband's computer. had to role both back to build 10240 for either of us to see each other's computer on network (we share filed). neither could see our OWN computer in network, even though we had file sharing checked, and all "services" related to networking and peers on "automatic" and running. very frustrating. I could not even access my OWN FILES which are in my "public " shared folder. after rolling back, I had to COPY all files and put them in my "documents" folder as I was too afraid of not being able to access MY OWN FOLDERS. this update to 10586 is a DISASTER. It destroys, or corrupts WINSOCK files which messes up all networking for the entire network, and then does not allow you to "fix" it by reinstalling them (stupid "permissions" does not allow it).
It is a disaster. Network in XP and Win 7 was always breeze; why has MS fouled it up completely? why is MS not "fixing" this issue.
IT IS UNACCEPTABLE! NETWORKING IS THE "CORE" OF WINDOWS OPERATING SYSTEM. WITHOUT IT WE CANNOT FUNCTION!
nightmare. neither I nor my husband could see each other's computer on network or even our own computers in our own network folder! impossible to fix. troubleshooter recited it was "winsock" problem; MS staff posted workaround to DELETE winsock files and reinstall TCP/IP, what she DID NOT TELL you is after you go through her "steps" the final one to "reinstall" DOES NOT WORK. get error message "cannot reinstall" "blocked, not allowed, no permissions" now totally screwed as already deleted winsock; fortunately I set system restore before her "worthless workaround" which DID NOT WORK and could then see some computers but NOT my OWN desktop. we had to roll back to build 10240 as 10586 was a DISASTER. TOTALLY DESTROYED NETWORK FUNCTIONS!
We don't care about "cortana" and "bells and whistles" WE JUST WANT BASIC NETWORKING, like we had in XP, win 7, and win 8.1!
MS NEEDS TO STOP WORKING ON MORE BELLS AND WHISTLES AND MUST FIX THE BASIC CORE NETWORK DISASTERS IN 10586!
@ geekgirl - I'd be hesistant to delete winsock files like that. If you're go into core files, def make a full image backup of your hard drive first to an external HD. MS Restore is not 100% reliable to bring things back.
I'd recommend using proven reliable 3rd party software to do the image backups. I've been using Casper 8 for my full drive image backups and works flawlessly. Casper has been around for years.
Casper 8 is at https://www.fssdev.com/products/casper/
Other popular full image backup programs are:
• Macrium Reflect 6 at www.macrium.com/product/7/macrium-reflect-v6-home-edition.aspx
• AX64 is at Tour Product | AX64 Time Machine Snapshot Imaging Backup