Windows 10: Windows could not the start Peer Networking Grouping Service on Local Computer

Although Microsoft removed Homegroup from Windows 10 v1803, you can find this feature in the older build of Windows 10 as well as Windows 8/7. If you are using any Windows version, which has Homegroup functionality but you are getting [...]

This post Windows could not the start Peer Networking Grouping Service on Local Computer is from TheWindowsClub.com.

read more...

 

Can not Create Homegroup and error 1068 - Windows could not start the Peer Networking Grouping on Local Computer and

Hi Ken,

Thank you for posting in Microsoft Community, we appreciate your interest in Windows 10.

As per your concern is to create a HomeGroup, do let us know if you are facing the same issue with same error code?

If so, I suggest you to start the services for Peer Networking and check if it helps.

Three particular Windows services manage peer-to-peer networking, and all computers in you are trying to connect should have the same settings in order to reduce error messages and connection problems.

Step 1: Stop the services.

• Press Windows Key + R on the keyboard and type
  services.msc, Services window gets opened.
• Search for Peer Name Resolution Protocol service, right click on it and click on
  Stop.
• Do the same for Peer Networking Group
  and Peer Networking Identity Manager.
• Restart the computer.

Step 2: Start the service and set it to automatic:

• Press Windows Key + R on the keyboard and type
  services.msc, Services window gets opened.
• Search for Peer Name Resolution Protocol
  service, right click on it and click on
  Properties.
• Do the same for Peer Networking Group
  and Peer Networking Identity Manager.
• Start the service, set
  Startup type to Automatic.

Hope it helps. Reply to the post with an updated status of this issue for further assistance.

 

error 1068 - Windows could not start the Peer Networking Grouping on Local Computer.

error 1068 - Windows could not start the Peer Networking Grouping on Local Computer. ALSO, Windows could not start the Peer Name Resolution Protocol Service on Local Computer. Peer Networking Identity Manager IS started. All three are set to "automatic"
startup. I have a three computers, two are running windows10 pro and one is running windows 8.1 and my main system is running windows10 Pro 64 bit.

 

3 key peer services in local services will not start, blocking homegroup function

Hi Stephen,


Thank you for posting your query in Microsoft Community.

I understand the inconvenience you are facing currently. let me help you in resolving the issue.

I suggest you to start the services for Peer Networking and check if it helps.

Three particular Windows services manage peer-to-peer networking, and all computers in you are trying to connect should have the same settings in order to reduce error messages and connection problems.

Step 1: Stop the services.

• Press Windows Key + R on the keyboard and type
  services.msc, Services window gets opened.
• Search for Peer Name Resolution Protocol service, right click on it and click on
  Stop.
• Do the same for Peer Networking Group
  and Peer Networking Identity Manager.
• Restart the computer.

Step 2: Start the service and set it to automatic:

• Press Windows Key + R on the keyboard and type
  services.msc, Services window gets opened.
• Search for Peer Name Resolution Protocol
  service, right click on it and click on
  Properties.
• Do the same for Peer Networking Group
  and Peer Networking Identity Manager.
• Start the service, set
  Startup type to Automatic.

I would also suggest you to refer to these below Microsoft articles and check, if it works.

HomeGroup from start to finish

http://windows.microsoft.com/en-US/...-finish=windows-81&v1h=win81tab1&v2h=win7tab1

Note: Applies to Windows 10.

HomeGroup problems in Windows

http://windows.microsoft.com/en-IN/windows-8/homegroup-problems-in-windows

Note: Applies to Windows 10.

Hope the information helps. Keep us posted on Windows related queries and we will be happy to assist you further.