Windows can’t set up a HomeGroup on this computer [SOLVED]

Fix Windows can't setup a HomeGroup on this computer

If you are trying to join or create a HomeGroup on Windows 10 and the following error message pops up “Windows can’t set up a homegroup on this computer”, then you’re at the right place as today we are going to fix this error. This problem mostly occurs in the system which has been recently upgraded to Windows 10.

Fix Windows can't set up a HomeGroup on this computer

Also, some other users have previously created a homegroup on their previous version of Windows. After upgrading to Windows 10, the HomeGroups are no longer detected and instead show this error message:

Windows no longer detect on this network. To create a new homegroup, click OK, and then open HomeGroup in Control Panel.

Windows no longer detect on this network. To create a new homegroup, click OK, and then open HomeGroup in Control Panel.

Now even if the earlier HomeGroup is detected, the user’s can’t add, leave or edit. So without wasting any time let’s see how to actually Fix Windows can’t set up a homegroup on this computer with the help of below-listed troubleshooting guide.

Windows can’t set up a HomeGroup on this computer [SOLVED]

Make sure to create a restore point just in case something goes wrong.

Method 1: Run HomeGroup Troubleshooter

1. Type control in Windows Search then clicks on Control Panel.

Type Control Panel in the search bar and press enter | Windows can't set up a HomeGroup on this computer [SOLVED]

2. Type troubleshoot in the Control Panel search and then click on Troubleshooting.

troubleshooting hardware and sound device

3. From the left-hand panel, click on View all.

Click on View all in the left pane

4. Click Homegroup from the list and follow the on-screen instructions to run the Troubleshooter.

Click Homegroup from the list to run the Homegroup Troubleshooter

5. Reboot your PC to save changes.

Method 2: Manually Start Peer Networking Grouping Service

1. Press Windows Key + R then type services.msc and hit Enter.

services windows | Windows can't set up a HomeGroup on this computer [SOLVED]

2. Now make sure the following services are configured as follows:

Service name Start type Log On As
Function Discovery Provider Host Manual LOCAL SERVICE
Function Discovery Resource Publication Manual LOCAL SERVICE
HomeGroup Listener Manual LOCAL SYSTEM
HomeGroup Provider Manual – Triggered LOCAL SERVICE
Network List Service Manual LOCAL SERVICE
Peer Name Resolution Protocol Manual LOCAL SERVICE
Peer Networking Grouping Manual LOCAL SERVICE
Peer Networking Identity Manager Manual LOCAL SERVICE

3.To do this, double-click on above services one by one and then from Startup type drop-down select Manual.

From Startup type drop-down select Manual for HomeGroup

4. Now switch to Log On tab and under Log on as checkmark Local System account.

Switch to Log On tab and under Log on as checkmark Local System account

5. Click Apply, followed by OK.

6. Right-click on Peer Name Resolution Protocol service and then select Start.

Right-click on Peer Name Resolution Protocol service and then select Start | Windows can't set up a HomeGroup on this computer [SOLVED]

7. Once the above service is started, again go back and see if you’re able to Fix Windows can’t set up a HomeGroup on this computer error.

8. If while starting Peer Name Resolution Protocol service you encountered an error saying “Windows could not start the Peer Networking Grouping service on Local Computer. Error 1068: The dependency service or group failed to start.” then follow this guide: Troubleshoot Can’t Start Peer Name Resolution Protocol Service

9. You could receive the following error message while trying to start PNRP service:

Windows could not start the Peer Name Resolution Protocol service on Local Computer.
Error 0x80630203: Unable to access a key.

The Peer Networking Grouping service depends on the Peer Name Resolution Protocol service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Error 1068: The dependency service or group failed to start

Error 1079: the account specified for this service is different from the account specified for other services running in the same process.

10. Again, all the above error could be fixed by following the guide mentioned in step 8.

Recommended:

That’s it you have successfully Fix Windows can’t set up a HomeGroup on this computer error but if you still have any queries regarding this guide then feel free to ask them in the comment’s section.

Posted by
Aditya Farrad

Aditya is a self-motivated information technology professional and has been a technology writer for the last 7 years. He covers Internet services, mobile, Windows, software, and How-to guides.

1 Comment

  1. I might add, and I found this through trial and error, many times this is a local network and discovery issue and (as everyone always says) a timing issue. After making sure sharing, connections, required services and dependencies, and other configurations are setup as previously described; make sure the function discovery services are set to delayed start.

    If both function discovery services are set to automatic; sometimes the the function publication service may start but miss connecting to the function discovery host. I guess they may be starting simultaneously. Setting them both to delayed start seems to allay that problem.

    Automatic start may cause your machine not to see itself on the network as well as any other members of the network. An indicator of this is some of the other network members can get to your machine via local network if they have shares mapped to your machine from theirs and sometimes if they type in the SMB address to one of your shares or other folders if permissions allow it. Restarting the function discovery publication service will fix this. Setting both function discovery services to delayed start should fix it permanently.

    Like I said I found this through trial and error and my suppositions as to why it happens may be hooha. But the fix appears to work dependably. I also was under the impression that there was some sort of problem using homegroup on later versions of win 10. I can’t verify this because I use regular file sharing and not homegroup. Hope this helps.

Leave a Reply

Your email address will not be published. Required fields are marked *