TechNet Forum Windows 7 Support Team

http://social.technet.microsoft.com/Forums/en-US/category/w7itpro

"Peer Name Resolution Protocol" Service Could not be Started and HomeGroup Is not Working

"Peer Name Resolution Protocol" Service Could not be Started and HomeGroup Is not Working

  • Comments 25
  • Likes

 

SYMPTOM

 

You cannot join a HomeGroup with an error message "Windows cannot set up a HomeGroup on this computer. Error code: 0x80630801".

 

In addition, you may observe the issue that "Peer Networking Grouping" service cannot be started on this computer.

 

CAUSE

 

The error code 0x80630801 means PEER_E_CERT_STORE_CORRUPTED. The Identity Store has been corrupted.

(Location: "C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking\idstore.sst")

 

SOLUTION

 

To resolve this issue, we need to delete idstore.sst from the %appdata%\peernetworking folder. Please follow the steps below:

 

1.     From an elevated CMD prompt, type in the following command:

 

Net stop p2pimsvc /y

 

2.     Delete the following file:

 

"C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking\idstore.sst"

 

3.     Reboot the computer.

 

Then you should be able to join HomeGroup.

 

REFERENCE

 

http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/a85eaa65-d73a-4324-ad0c-e9a2c1469bd7

http://social.technet.microsoft.com/Forums/en-US/w7itpronetworking/Thread/6B5A72EB-6523-4AF9-85AB-3694D7CC457A

http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/932e85c6-b141-4bc5-8be7-daa7e0ff714b

http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/79ce2aad-0508-478b-b2d7-b89f70821c37

http://social.technet.microsoft.com/Forums/en/w7itpronetworking/thread/62491022-bd42-4e0e-bfaf-7fb172f70e78

Comments
  • DID NOT WORK FOR ME

  • Hi,

    It didn't work for me either.

    I couldn't see my password.- fixed by deleting idstore

    I can't add a reinstall PC to the homegroup.

    Test on the host cant find/start group.

    Im hoping to fix it soon

  • I cannot start the Peer Name Resolution Protocol service either. It is preventing me from starting a HomeGroup. I received the error message: "Windows could not start the Peer Name Resolution Protocol service on Local Computer. Error 0x8009000f: Object already exists."

    Does anyone have an idea as to which object already exists? How do I delete the existing object? I have tried deleting the idstore.sst file without success. I have tried starting the computer in Safe Mode with Networking without success. I have tried a clean boot without success. No matter what I try, the service will not start.

    Any ideas?

    Technical Specifications:
    System Manufacturer: TOSHIBA
    System Model: Satellite S875
    System Type: x64-based PC
    OS Name: Microsoft Windows 7 Home Premium
    Version: 6.1.7601 Service Pack 1 Build 7601
    Processor: Intel(R) Core(TM) i7-3610QM CPU @ 2.30 GHz, 2301 Mhz, 4 Cores, 8 Logical Processors
    BIOS Version/Date: Insyde Corp. 6.80, 10/1/2013
    SMBIOS Version: 2.7
    Boot Device: \Device\HarddiskVolume1
    Installed Physical Memory (RAM): 16.0 GB

    Thank you, in advance, for your assistance.

  • Worked for me. Thank you.

  • I'm having this problem, too. The problem is the exact same as Don's above. The solution here does not work. The resolution is to delete the idstore.sst file so the computer can remake the file on reboot. The problem for me is that idstore.sst does not exist, at all, on my computer (my dad's, really). Can't delete what is not there.

  • This was the fix for me;

    Go to "C:\ProgramData\Microsoft\Crypto\RSA\" and then rename "MachineKeys" folder to "MachineKeys-old".
    Create a new folder "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" and right click the "MachineKeys" folder , select "Properties" and click "Security" tab. then set "Full Control" permissions to "Everyone".

    Cheers,
    Matthew Kerfoot
    https://www.theovernightadmin.com

  • Fixed after two days of trying everything I could find on the web.
    I took Matthew Kerfoot (Thanks) advise, but instead of renaming and creating a new "MachineKeys" folder I set "Full Control" permissions to "Everyone" to the existing "MachineKeys" folder.

  • I set "Full Control" permissions to "Everyone" to the existing "MachineKeys" folder.
    This simple change worked for me too.

  • Full Control worked perfect!

  • Worked for me. Thanks Matthew!

  • And when the idstore.sst is missing? Nah this did not help me either.

  • NOW it's working :) As a last effort i tried giving MachineKeys folder a full access and now everything is ok. :) Ha ha THANKS!!!!

  • This worked for me, thanks!!

  • Matthew Kerfoot 26 Jul 2015 6:07 AM

    This was the fix for me;

    Go to "C:\ProgramData\Microsoft\Crypto\RSA\" and then rename "MachineKeys" folder to "MachineKeys-old".
    Create a new folder "C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys" and right click the "MachineKeys" folder , select "Properties" and click "Security" tab. then set "Full Control" permissions to "Everyone".

    Cheers,

    Thank you Matthew. this worked. thanks again.

  • Patrick Mills solution worked for me too.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment