I just had to do the bit about setting the two Function Discovery services to automatic and then restart to get all the computers to re-appear. Hope that is enough for some others too.
Homegroup removed! How to get network sharing work with Windows 10 v1803.
Here is short description how I get my network sharing work with Windows 10 v1803.
(I haven't never use Homegroup so I start directly from step 2.)
- Only for those PC's which are still using Windows 10 v1709 or older:
Disconnect from non-existing Homegroup if you have used it.
2.1. All PC's: Check Network profile and Network discovery and Share settings
Sometimes this selection to change between Private and Public network profile is missing from Settings / Networks page. In that case profile must change by PowerShell. Right Click Windows Icon (Start button) and open PowerShell (Admin) and use following commands to get interface index number and change profile to Private (or Public):
Get-NetConnectionProfile
Set-NetConnectionProfile -InterfaceIndex <index number> -NetworkCategory Private
2.2. All PC's: Check Network Discovery and Share settings
- All PC's: Set Start type to Automatic and start following services that allow PC's to be visible on Network. (Reboot.)
Push Win Key and type "Services", locate these services.
- Function Discovery Provider Host
- Function Discovery Resource Publication
- SSDP Discovery
- UPnP Device Host
- Setting shares.
4.1. Check your current shares.
Open file explorer and type \localhost to address bar to see what shares are made in this computer.
4.2. Create new share (here I use folder "Test").
(Setting "Turn on sharing so anyone …" in Step 2.2. make share for folders in C:\Users automatic.)
Folder is now shared and Network share path is: \PCNAME\Test
4.3. Safe way to share folders.
Create user account to all users on your network to whom you want to give access to shared resources.
Use same user ID and password which they have on their own computers.
Right click "Test" and open Properties and select Security tab to see current settings.
Default security settings are shown in next picture.
Those settings allow access to shared folder(s) only for those users who have user ID on that computer.
4.4. Sharing folder "Test" to Everyone" (Very unsafe setting! Think carefully do you need to select this!)
If you want that everyone have access to that share then go to Security tab and:
- Click Edit
- On Permission dialog click Add.
- New dialog open and you can add "Everyone" to that list https://learn-attachment.microsoft.com/api/attachments/c1f22caa-ec01-4f49-8c76-01b18ed8061f?platform=QnA
- When back to Permissions dialog select which rights you want to give to "Everyone".
Now anyone on your home network should have access to shared folders without credentials or having user account on your computer.
- Now when click Network on File Explorer all your PC's should be visible in Computer and Network sections.
This should be cover the essentials to sharing your data over local network. This share is not limited to C:\Users folder, every folder can be handled like shown in steps 4.
Now your PC's should visible, but if not then try to reset all network settings:
Go to Settings / Network & Internet / Status, scroll down to find "Network reset, on next window click "Reset Now" button.
It will takes about 5 min to perform this reset and then PC reboot automatic.
When you sing in first time you get notification something like "Do you want your PC to be access by other computers", click Yes for that.
If you get error message "Windows cannot access \PC_NAME" when you try to connect shared folders then continue to step 6.
- There is some bug on Windows 10 1803 and because of that PC's can't always connect to each other by Name.
If you get error "\PCNAME path not found" you can solve this by adding your PC's and IP-addresses to hosts file.
6.1 New routers (or modems) may have feature to remember which IP-addresses are assign to each device, but with older routers (or modems) you have to check that your router or modem is set give predefined IP-addresses linked to each PC's MAC-address.
This way PC's will get same IP-address every time when it ask IP-address form router (or modem) DHCP-server.
There should be some kind of list of PC names with MAC addresses and given IP-addresses of each connected PC.
Picture show that list on my router. In my case with old router I had to select manual assignment in each line.
6.2. Add all PC's IP-addresses and Names to hosts file (C:\Windows\System32\drivers\etc\hosts).
You can check your IP-address and PC's name by opening command prompt (CMD)
For IP-address type command: ipconfig you get line like this: IPv4 Address ………. 192.168.100.101
For PC name type command: hostname
Write down IP-address and Name of each PC and add those to that hosts file.
To edit copy hosts file to some another location, right click it and use notepad to edit and save it. Replace original file with edited file. Because hosts file is located on system folder replace will ask administrators rights to perform it.
localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
192.168.100.101 PC1 # Ethernet
192.168.100.102 PC2 # Ethernet
192.168.100.202 PC2 # Wi-Fi
Windows for home | Windows 10 | Files, folders, and storage
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
326 answers
Sort by: Newest
-
Anonymous
2018-06-05T18:10:11+00:00 -
Anonymous
2018-06-03T18:15:10+00:00 Hi Pauli O,
Thanks much for your very detailed response to my issue. Why Microsoft made the bonehead decision to dump the HomeGroup facility is beyond me. It was an elegant and SIMPLE solution that we mere mortals could implement without having an IT technical degree to simply share photos or whatever among home network computers. Ridiculous in the extreme. I solved my issue temporarily by rolling back the 1803 version to a prior version and everything's the way I want it now. I know it's only temporary but, for now, I'm satisfied. Not everyone wants to dump their private stuff up to some hackable cloud storage facility in order to share stuff. That's the weak answer MS gives to why they made this stupid decision.
Lack of the home group in 1803 compilation breach the Win10 licence. Any way in line with the law to remove Home Group.
-
Anonymous
2018-05-23T02:27:38+00:00 I can't tell you how grateful I am for this solution. It worked for me. I hadn't even had homegroup set up, but I was having trouble accessing my shared directories across the network. The host file solution was the last missing piece of the puzzle. Thank you!
-
Anonymous
2018-05-23T00:07:56+00:00 Go back here, I revised the sharing for v1803 with PC connection issues. It was so obvious and simple and now it is so simple to share just like it was with no connection issues.
-
Anonymous
2018-05-22T05:21:28+00:00 "This is NOT a bug. Only Home Edition still supports NetBIOS Computer Browser as of 1803 -- Windows Pro just lost support as Enterprise Edition etc did before. MS announced that NetBIOS was obsolete and insecure and would be eventually be removed over 15 years ago (when Active Directory Services was released for enterprise networks). But phasing out NetBIOS has taken so long time most people forgot and most home users where never really directly informed."
Thanks, that was new info I haven't seen before and that explain "issue" I have try to solve this since I notice it about month ago when v1803 "RTM build 17134.1" was released to insiders.
I have to search more info or do you have any good links?
It shouldn't be big thing for manufacturers to add DNS server to home routers for serve LAN side connections.
Funny thing is that with every new release MS and press promote all new features, but they are not telling which features are deleted!