Windows 10: Update: "This computer can not join/create homegroup"

I started on win 8.0 then did the developer preview for 10 almost as soon as it was released. used homegroup the whole time. only when I moved and got a new att u-verse router did this start. I was thinking it was my router so I unplugged it and plugged it back in and noticed that my main pc went from seeing an old (not existing) homegroup, to not seeing one at all, still can not create one though. the error message is the title of this thread, depending if I'm trying to join or create.

hope this helps somehow :S

 

I think we are making progress. error message: Windows could not start the Peer Networking Grouping service on local computer Error 1068: The dependence service or group failed to start.

I thought all the necessary tasks were running, turns out the info found did not list all the possible "not running" options. thank you.

 

Yes my password changed to the default admin and yes i had my own password i used and after i rest i put my password back in the hardest thing was trying 2 remember how 2 put it back in. How did it go with you did it help any

 

I follow the path C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking to look for the idstore.sst file. It is not there and I believe I am viewing all hidden folders. I moved the Peer Networking folder to my desktop then tried to create homegroup and when the folder was remade it was still empty.

 

Is your computer the one witch you first started the homegroup with if so restart the computer sometimes it will show up the same error. I have 2 go into my modem/router and put my name and password in for my internet provider witch thay gave me when I singed up with them so I can get it to work again and I worried about the password later. Once I restart my computer with the homegroup I had started with before in I up graded to windows 10 then I tried it again and it worked, Then I whent to the other 2 computer and put the password in and it got it going.

 

Has anyone attempted to remove all previous computers from an existing HomeGroup prior to installing upgrading to W10? Additionally, removing all shared resources prior to updating?

I will be flipping 12 work systems over to W10 when all these problems are resolved and am collecting all my troubleshooting tips before the 90th day. ...that's when I plan to make the move. MS has some updating to do and I plan to leave Win7 alone until then.

Thanks for all the info everyone. These types of posts are what help us all!!

 

I have done the following and still cannot get Homegroup working in Windows 10:

1. In safe mode I deleted the files in C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking on the primary computer (a Dell Inspiron 570 desktop running Windows 10, with a printer attached by USB, that connects to router by cable).
2. I did the same on 3 laptops (that connect to router by wireless; 2 are Windows 10, 1 is Windows 7) via Safe Mode so that any in-use files could be deleted. Then shut down all 3 laptops.
3. I then created a new Homegroup on the desktop computer (with a new password, of course).
4. I tried to join laptops to the new homegroup with no success.
5. When I go back to desktop and click on Homegroup in Windows Explorer, it gives me the Join Now (which it shouldn't do since I already created it on this one). When I try to join it fails.

I have tried to verify that update KB 3081424 is installed but the Update listing in Windows 10 only lists the most recent ones which are dated 8/14/2015 or later.

 

I had the exact same problem. This may seem simplistic but here's what worked for me before I even saw this thread.

I told each of my machines to leave the Homegroup, then turned all of my machines off. Then I turned on just one machine to create a new Homegroup and this time it worked. After giving that single machine several minutes to load up and settle, I got the prompt to "Create" a Homegroup instead of "Join". Once I created the new Homegroup I turned my other machines back on and was easily able to join it with the new password.

Apparently Windows 10 requires there to be no other machines running on the network in order to create a new Homegroup.

 

Very interesting... I wonder if this will be the same cause of "Work Group" networked systems flipping to Windows10. I still think I am going to wait 3 months before I pull the trigger.

 

I've been chasing my tail on this all day today, and here's how I fixed the related problem of "I have an existing homegroup, but it's home to over 30 machines no longer around, so I want to create a new homegroup instead." Got that accomplished as follows:
1. Had all 7 machines on home LAN quit the current home group
2. Deleted all files in the %windir%\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking folder on each machine, then shut each machine down
3. Unhooked the home LAN from the central switch
4. Direct connected a laptop to the switch (direct connection to Internet -- DHCP is on boundary device)
5. Opened Homegroup to see that I had the option to create a new homegroup, then did so, printed password for new homegroup
6. After restarting each of the other machines, entering homegroup reported "Invitation to join a homegroup;" joined & provided new homegroup password
7. All machines are now in a new homegroup and the old one is no longer in use

Everything is now working as I think it should be, and the Homegroup is no longer full of stale/obsolete entries.
HTH,
--Ed--

 

Go to control panel / administrative Tools / Services.. Click on and stop Homegroup Listener and Homegroup Provider then restart your PC and create a new Homegroup. P.S. This was after win10 could not detect a Homegroup and I could not create a new one..

 

Much more elegant solution, Joe#Beast! Thanks for sharing this.
--Ed--

PS: what happens if you do this on the machine where you defined the homegroup in the first place? Doesn't it have "master" status for that group? Just curious...

 

I’m not sure. I replaced the hard drive on the machine where I defined the homegroup on and even though I had not been joined for sometime no one else could join or start one, so this was the method I used.

 

OK, then: thanks for clarifying. My own issue appeared to originate from the "master" machine having been decommissioned with the homegroup still active and working. It's always something!
Thanks again,
--Ed--

 

This fixed my issue.
T