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.)

1. 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



3. 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

4. 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 

- 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.


5. 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.

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

 

Discussion Info


Last updated June 16, 2019 Views 154,994 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

OK, I think I want to give this a try because I'm losing my mind trying different things that aren't working or are making things worse.  Plus, I already use static IP addressing tied to MAC addys, so maybe this might actually work in my environment.

Question, though:  can you please expand on the very last bit?  I'm clueless about how to add the IP addys & names to the file you reference.  Thanks.

To edit copy hosts -table to some another location, right click and use notepad to edit and save it. Replace original file with edited file. Because hosts is located on system folder replace will ask administrators rights to perform it.

Update = Replace old bugs with new ones.
Reply In reply to deleted message

Thanks Craig,

Even when this in manual it was running on my PC when I check it.

There is some delay, what I was wondering, when I connect to shared resources first time after reboot. Maybe this delay is caused by starting that service when it is needed first time. 

That service is linked to SSDP and UPnP which are also required (with Wi-Fi devices?) so it would be better to set this to start automatic as you wrote.

Update = Replace old bugs with new ones.

Pauli, I don't mean to shout, but I'M SO HAPPY!!!  THANK YOU!!! I almost have a fully functional LAN again with everything seeing & having access to all again.  For troubleshooting purposes, I pulled all but 2 PCs, 1 Surface Pro 3, and a NAS from the LAN after the initial 1803 debacle after following Andre's second response here didn't fix things, so now I just have to power the rest up & edit the hosts table on those & fix the sharing as you describe.

Pauli, your steps through 5a worked really well for me -- that's what made all the computers show up in File Explorer, Network, Computer.  For reasons that are far beyond my understanding, I think the removal of HomeGroups completely tanked the files & folder shares from all our Surface Pros.  If I had to guess, my guess would be that the PCs & laptops had originally been networked through Workgroup & those shares were preserved in the bowels of Windows somehow.

Your steps on unsharing & resharing worked for me -- I'd been trying the Share, Remove Access in File Explorer, which wasn't particularly successful & created a sharing mess from the SP3.  When the PCs would access it (sometimes they could do so successfully but mostly not), they only thing they could "see" was \\SP3\Users\XXX\OneDrive (which we don't use) & nothing else.  Arrgh!  Your steps helped me get that sorted.

The final success was editing the host - table!  Access to the SP3 is golden now -- I've tested & restarted & tested & restarted until I'm blue in the face, and it is all good!  Thank you so much!

Also, I'm going to try setting the Functional Discovery Services to automatic rather than automatic (delayed) as you suggest because on the SP3, I'm seeing the delay you mentioned -- on the SP3, the SP3 is the last thing to appear in File Explorer, Network, Computer while everything else appears promptly.

One final note:  on the SP3, I had to enable SMB 1 following 1803.  Prior to 1803, the NSA showed up correctly in File Explorer, Network as a Computer; following 1803 (and the corrections), it showed up only as a Media Device so many of the files were inaccessible.  I'm not sure why 1803 broke that (I recall having to do this on the PCs with the Fall Creator Update), but it was working fine on the SP3 without SMB 1 being enabled until 1803.

Thanks again, Pauli -- I'm breathing much more easily now!

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.  

Thanks. That worked.

I had tried all of the steps before, but I didn't think or know about changing those Services settings to Automatic (Delayed Start). Now all three of my machines are talking again.

I blame Microsoft for losing three to four hours over this. Good thing Users can't bill MS for time wasted over "Updates" - MS would be long bankrupt and gone.

Now if they would please fix the no choice change to mouse wheel actions imposed by Edge (lose focus and scrolling up and down becomes back and forth between previous pages - I can't imagine how much time I've wasted grappling with that.

Good luck with the next free Update, kids. I'm canceling that move to Surface Studio and looking for a Mac.

Hey, whatever...

Thank you for this step-by-step. I have two Win 10 machines, both with the latest update. I have completed each of the steps you outlined, up to and including 6.1a.

Computer A can see all of the shared folders on Computer B, but can only access the Users folder. I have stopped sharing the other folders and re-shared them giving all permissions to Everyone, but all shared folders excepting Users gives a "You do not have permission to access..." error.

Meanwhile, Computer B can see Computer A on the network, but cannot see any of the shared folders; the error is "The network path was not found."

I've spent hours on this and I'm desperate. Any help is appreciated.

"Everyone, but all shared folders excepting Users gives a "You do not have permission to access..."

I wrote my instructions to make shares look something like it was with Homegroup and use only Users folder, where OS set security settings.

Do you have same user name on both PC's? Then this shouldn't have any problem.

Share to Everyone make folder available, but Security settings define who can access to folders. Make these settings can be little tricky at first and tests is better to do with some temporary folder.  

Left: Access only named User. Middle: Access to all who have user account in this PC.

You can change these rights: Click Edit, and Add. 

Enter User name to whom you want to give access.

"The network path was not found."

Did you edit that hosts -table Step 6.2? When you try to connect from B to A this table tell Windows which is PC-A correct IP-address.

Update = Replace old bugs with new ones.

Little here and there right? I guess since you keep posting numerous comments and Tips (LOL) on my DISCUSSION THREAD that are …...., I will post a Great Link Here without all this ………….. you have posted above here.

https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/connecting-pcs-and-users-for-sharing/fb92e439-5dbc-4367-9857-1ef360e9ffdf

Because Microsoft's intentions are to "force" people to usie their so called "One Drive" feature.  The free lousy 5GB is not enough storage, and they know this. So the End User ends up shelling out money for additional storage.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.