HomeGroup is gone in Windows 10 version 1803!

Anonymous
2018-05-02T17:42:48+00:00

My PC upgraded to Windows 10 Pro version 1803 yesterday during automatic updates. This morning I attempted to view files in my network. Home Group is no longer available in this newest update. It seems in their wisdom they decided it was not needed and provided other solutions to share files/directories. I following the instructions to share files/directories via Windows Explorer. Guess what? You can not share directories only individual files at one time. This is not acceptable. After much trial and error I found a work around. As long as you have the name of the PC in your network you can enter "\PCNAME" and it should give you access. Bring back Home Group to the Windows operating system!

Windows for home | Windows 10 | Windows update

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

70 answers

Sort by: Newest
  1. Anonymous
    2018-07-23T01:39:26+00:00

    edit:  My problem was with the host computer and password protected sharing being on and I could not turn it off.  I found my answer which involved deleting the password for a guest account (?).  It worked and now I have access to that computer but frankly there are still issues as I don't always see every computer on my network even though I enabled the needed services.  I solved this by creating shortcuts to specific computers.  Lots of workarounds for something that previously worked fine with Homegroups.

    I am so lost.  I am able to see my networked computers but I can not access files from them.  I enabled sharing but if I try to access I get "Windows can not access...  You do not have permission to access.  Contact your network administrator..."

    Homegroups previously worked fine.  Thank you Microsoft for destroying my computer experience.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Anonymous
    2018-07-14T06:36:03+00:00

    Awesome! It fixed my problem as well. Why on earth do we have to do this!? Crazy Microsoft

    Edit, It worked for a second and then disappeared again

    Was this answer helpful?

    0 comments No comments
  4. Pauli O 16,380 Reputation points Volunteer Moderator
    2018-07-13T10:39:34+00:00

    "Microsoft refers to 'Specific people' but fails to define who they are and how these people can be determined."

    "Specific people" are users on that computer where you  are making that share.

    Example:

    Desktop at home contain data you want to share for family members.

    Users on that desktop:

    • Me: User1 / password User1
    • Wife: User2 / password User2
    • Kid: User3 / password User3

    Other PC's:

    • My laptop: User1 / password User1
    • Wife laptop: User2 / password User2
    • Kid laptop: User3 / password User3 

    Now you can do shares from that desktop for your family members using "Specific people" and each user can have access to shared folders from their own laptops if he/she is that "Specific people".

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-07-13T09:47:13+00:00

    enter "\PCNAME" and it should give you access. 

    Sure it will - if you have a user account on that computer or know the password of that computer's user.

    Homegroup was temperamental but most of the time it worked on a LAN. Microsoft's change has made things far more complex and is particularly difficult if your connection to Internet is flakey. 

    Microsoft refers to 'Specific people' but fails to define who they are and how these people can be determined.

    Was this answer helpful?

    0 comments No comments