[FIX] Windows Could Not Start The Peer Networking Grouping Service On Local Computer

We all know its quite handy to connect different Windows machines using HomeGroup so that files and other stuff can be shared on the go. Peer Networking Grouping service is one of the core technologies used in HomeGroup feature. It enables multi-party communication using peer-to-peer grouping. If this service is not running, HomeGroup won’t function at all.

When HomeGroup is not working and you try to start Peer Networking Grouping service, and you’ll get this warning message:

Another message that often users receive regarding this service is:

In this article, we’ll share you the resolutions for both of these errors. But before we move on, we hardly suggest you to run System File Checker scan once. This will fix corrupted system files, if any, and help you in solving the issue.

Now, here is how to solve these errors:

FIX : Windows Could Not Start The Peer Networking Grouping Service On Local Computer

FIX Error 1068: The dependency service or group failed to start

1. Make sure you’re enabled hidden items in File Explorer. Press  + R and type following location in Run:

C:\ProgramData\Microsoft\Crypto\RSA

*Substitute C: with your system root drive.

2. Then in RSA folder, you’ll find a sub-folder named MachineKeys. Rename this folder to MachineKeys.old.

Since this is a system folder, so you need to provide administrative privileges to rename it by clicking Continue option here:

3. Next, in RSA folder, create a new sub-folder and name it MachineKeys. Right click over this newly created folder and select Properties.

4. Then in the MachineKeys property sheet, highlight Everyone under Group or user names and click Edit button.

5. Moving on, in the Permissions for MachineKeys window, select Everyone under Group or user names and put check mark against all levels in Allow column under Permissions for Everyone. Click Apply followed by OK. Exit File Explorer.

6. Open Services snap-in. Make sure services named Peer Name Resolution Protocol, Peer Network Identity Manager and PNRP Machine Name Publication are running. If they’re not running, double click on them one by one and click Start. Then you can start Peer Networking Grouping service and it should work as expected.

Close Services snap-in. The issues you were facing in using HomeGroup should be resolved now.

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

1. Open Services snap-in. Right click Peer Networking Grouping service and select Properties.

2. Next, in the property dailog box, switch to Log On tab. Select This account option and type Local Service in the input box next to it. Keep the Password and Confirm Password field empty. Click Apply then OK.

You can now retry to start Peer Networking Grouping service and this time error will no longer appear.

Hope this helps!