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: Oldest
  1. Anonymous
    2018-06-14T05:03:47+00:00

    HomeGroup was a joke and useless.

    Network folder network sharing has been the norm and default all the way back to windows 95.

    Yes there is the issue in v1803 with PC's not connecting on some networks but Paul's or my solution is an easy fix. If Paul's seems to hard, you can just create shortcuts by right click on desktop>>create shortcut. In the Wizard type in

    \\PC IP ADDRESS

    to another PC on your network

    Example:

    \192.168.0.5

     You can access most modems device table by doing this

    type in 192.168.0.1 into your browser address bar and press enter

    look in device table and it lists all devices and usually with the PC name next to the IP address.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-06-16T05:15:01+00:00

    We had an issue where the various notebook & desktop PC's running Windows 10 Home and Pro were unable to access shared folders mounted on another PC running Windows 10 Pro after Windows 10 1803 April Update was installed... even after following the steps outlined by Pauli.

    The workaround we used for a few weeks was to map network drives to the static IP of the sharing PC as seahawks65 posted - but today, I've found a new solution that seems to be working reliably.

    Change the Computer Name to something with lower case letters. (eg "officePC01" or "officepc01")

    Open the Settings App >System > About > Rename this PC - then restart the PC.

    If you want to keep the same name, you'll need to change the name to a temporary one first (eg officePC01a), restart the PC, change it to the caps adjusted name (eg officePC01), and then restart the PC again. This is because Windows 10 won't allow you to re-use the same name with different case letters.

    This was done after following the steps outlined by Pauli - including enabling both Function Discovery SSDP Discovery, and UPnP Device Host services; checking Windows File Sharing settings in the Network Sharing Centre; and re-enabling File Sharing... which are probably good things to do all the same.

    I found, though, that I didn't have to re-install SMB 1.0 file sharing services under Windows Features as others have recommended.

    Interestingly, when we look for the PCs and shared folders under Network - we still see the computer names shown entirely in uppercase letters, even though the name is displayed in lower or mixed case letters in the System Settings or Control Panel. But this time - double clicking on the icon goes straight into a list of all the shared folders; without the "Windows cannot access \OFFICEPC01" error message.

    I always feared that it was something to do with File Sharing settings or Firewall settings or the 3rd party security software we use... but it turns out that it seems to be a weird glitch in Network Discovery that doesn't like uppercase computer names. Maybe it's a conflict with the NetBIOS name (which insists on uppercase)?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-06-16T05:57:12+00:00

    ya be careful renaming your pc. You can create a big mess. Just warning you.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-06-16T07:52:56+00:00

    "Change the Computer Name to something with lower case letters. (eg "officePC01" or "officepc01")"

    That's quite odd behavior if it work that way? I have to test it someday.

    "I found, though, that I didn't have to re-install SMB 1.0 file sharing services under Windows Features as others have recommended."

    I haven't add SMB there because I haven't tested it. (I don't have any device that need SMB).

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-06-16T08:27:39+00:00

    I don't have SMB on either. But it really can not hurt anything.

    And I am suspect that since the v1803 connection issue can be on and off or intermittent, that the same PC name with small letters might not actually be doing anything,

    Probably just connecting now until someone does a restart and then back to no connection again.

    But, you never know.

    Was this answer helpful?

    0 comments No comments