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




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.




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")




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:




3.     Reboot the computer.


Then you should be able to join HomeGroup.









Comments (27)
  1. Anonymous says:


  2. nick says:


    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

  3. Don says:

    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: DeviceHarddiskVolume1
    Installed Physical Memory (RAM): 16.0 GB

    Thank you, in advance, for your assistance.

  4. Kura says:

    Worked for me. Thank you.

  5. nik says:

    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.

  6. This was the fix for me;

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

    Matthew Kerfoot

  7. John M says:

    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.

  8. Patrick Mills says:

    I set "Full Control" permissions to "Everyone" to the existing "MachineKeys" folder.

    This simple change worked for me too.

  9. MarteG says:

    Full Control worked perfect!

  10. Pere says:

    Worked for me. Thanks Matthew!

  11. ToddeSwe says:

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

  12. ToddeSwe says:

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

  13. Desmond says:

    This worked for me, thanks!!

  14. jesse says:

    Matthew Kerfoot 26 Jul 2015 6:07 AM

    This was the fix for me;

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


    Thank you Matthew. this worked. thanks again.

  15. jmpkgr says:

    Patrick Mills solution worked for me too.

  16. jmpkgr says:

    John M many thanks!

  17. Steve says:

    Many thanks. Spent hours trying to resolve this and the solution is simple if you know how!!

  18. Jackald1918 says:

    Thanks Matt, the solution worked for me also. The headache is relieved!~!!!!

  19. christiaan says:

    Matthew Kerfoot solution worked for me!! thanks!!!

  20. GJ says:

    The folder was empty, even after turning on hidden files. HomeGroups and WorkGroups are a terrible idea that never worked right as with many other Microsoft ideas. Time to switch to Linux.

  21. Clay says:

    Sounds silly, but wiggling the mouse and hitting the spacebar during startup solved it for me.

  22. Clay says:

    That is, being stuck at the startup screen with no touch monitor, no usb keyboard or mouse.

  23. Jon says:

    machinekeys worked for me too – same issues – unable to share folder, couldn’t login to this pc from another pc despite username and password being correct) – i wanted to be able to see a folder on PC no1. Joined homegroup fine now. Thx Matt!

  24. TomD says:

    I had 1 computer out of 5 that would not join my homegroup. After trying everything on every forum I could find, the solution that worked for me was to make sure all computers were on the same "type" of network connection. In my case 1 computer was connected
    via wireless adapter the rest via ethernet. After making an ethernet connection the computer joined immediately. Switching back to wireless made the homegroup disappear although it reappeared when ethernet connection was restored.

  25. dellamae says:

    I’ve have been trying for months to set up a Homegroup since upgrading to Windows 10 and nothing worked. Until today – changing permissions on MachineKeys to Full Access for Everyone solved my problem. Thank you!!

  26. Toscosurf says:

    The idstore.sst file also wasn´t there. Mattews’s solution also worked for me. Thanks Matthew!!!

  27. Steven says:

    It works for me. thanks a lot.

Comments are closed.

Skip to main content