Homegroup removed! How to get network sharing work with Windows 10 v1803.

Anonymous
2018-05-11T04:03:57+00:00

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

https://learn-attachment.microsoft.com/api/attachments/f7770a4f-8e37-48c9-a436-2fe4e8e12ca0?platform=QnA

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

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

![](https://learn-attachment.microsoft.com/api/attachments/d9a66593-0cd1-499b-908f-36a6854f27c1?platform=QnA

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:

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

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

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

0 comments No comments

326 answers

Sort by: Newest
  1. Anonymous
    2018-05-21T18:10:43+00:00

    When service is in manual and it is needed first time it takes some time to start and locate shared recourses. If this service is already running this time can be avoided.

    "DHCP Dynamic IP DNS with created shortcuts with IP address. "

    Why user should would create shortcut with IP address when Dynamic addressing is used? As soon as router/modem deside give your PC new IP address then that shortcut is dead!

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-05-21T17:56:25+00:00

    HMMM, there is no delay accessing through DHCP Dynamic IP DNS with created shortcuts with IP address.

    It is Instant connection.

    there is a delay from incorrect configurations between the PC's and the Modem and/or Modem/Router having to be sorted out upon connections. Seen it and did it 100 times.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-05-21T17:21:28+00:00

    Go back to dynamic and try creating shortcuts to connect using my method. If you can, then all good.

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

    If you still can not connect try this:

    Also for advanced sharing options>>groups and users>>add  the user "NETWORK:. Set Permissions, restart PC.

    This is explained in my article under Private Sharing, but you can not use "NETWORK SERVICE" for sharing through the network folder. You use "NETWORK"

    I bet of you reset your configuration that Paul mentioned and create shortcuts with IP address's you will get connected without even doing what I mentioned above adding more users.

    In 3 weeks, I have updated over 100 PC's and worked on about 30 networks and my method works every time. Then you are not messing with peoples network settings. You can make TEMP shortcuts to access shared content, and when Microsoft fixes this issue, you can delete the shortcuts and use the default method.

    Reboot modem and restart all pc's after making changes.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-05-21T16:47:40+00:00

    Wish I wouldn't have watched it -- it just reminds me of how Microsoft continues to screw loyal customers like myself. Case in point:  the new "Continue on PC" in build 1803.  It looks like exactly like feature I've been dreaming of forever, but it's not available on Windows 10 phones**,**it's only available for Android & iPhones.  WTSF,MS?!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-05-21T16:45:04+00:00

    I tried the static IP approach suggested by Pauli O to try to resolve my inability since Win 10 V1803 to share folders between a Win 10 host and a Win 10 VM running under Hyper-v on that host.  The VM is using the "Default Virtual Switch" (i.e. "internal").   From the VM the host machine appears under the "Network" node in File Explorer, but I still cannot drill into shared folders like I could prior to release 1803, even when applying the "Static IP" approach suggested by Pauli O.  Sincerely hope Msft releases a correction to this bug and does not claim it is a new "feature" in an attempt to make everyone route their work through the cloud.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments