Fix: Peer networking error 1068 on Windows 10
Peer networking error 1068, how to fix it?
Peer networking error 1068 can be problematic and cause various issues on your PC. Speaking of issues, here are some similar problems that users reported:
- Peer networking grouping service not running Windows 10, 7 – This is a common problem that can occur on any version of Windows, and in order to fix it, you just need to start the required services.
- Peer networking grouping service isn’t running error 1068 – This is a variation of this error, and you can fix it by checking your antivirus.
- Peer networking grouping error 1079 – This is a slightly different error, but you should be able to fix it using one of our solutions.
- Peer networking grouping won’t start – Sometimes this service won’t start at all. To fix that, make sure that the depending services are able to start.
Solution 1 – Check your antivirus
Peer networking error 1068 is a network error, and sometimes this issue can appear due to problems with your antivirus. Antivirus can sometimes interfere with your system and cause this issue to appear, but you can fix the problem simply by disabling certain antivirus features. In some cases, you might have to disable your antivirus software altogether.
If that doesn’t help, your next step would be to uninstall your antivirus and check if that helps. If removing the antivirus solves the problem, you might want to consider switching to a different antivirus solution.
There are many great antivirus tools on the market, and if you want maximum protection that won’t interfere with your system, we suggest that you try out Bitdefender.
Solution 2 – Check if Peer networking services are running
Peer networking relies heavily on its services, and if one Peer networking service isn’t running properly you might get Peer networking error 1068. To fix this issue do the following:
- Press Windows Key + R and enter services.msc. Press Enter or click OK.
- When Services window opens locate Peer Name Resolution Protocol, Peer Networking Identity Manager, Peer Networking Grouping and PNRP Machine Name Publication services and enable them. To do that, simply right-click a service and choose Enable from the menu.
In addition to enabling the necessary services, users are also recommending to temporarily disable your antivirus and firewall before starting these services, so be sure to do that.
Solution 3 – Delete idstore.sst
According to users, you can easily fix Peer networking error 1068 by deleting the idstore.sst file. To do that, follow these steps:
- Go to C:\Windows\ServiceProfiles\LocalService folder.
- Go to the AppData folder. If that folder is missing, you need to show hidden files. To do that go to the View tab and check Hidden items.
- Now go to Roaming\PeerNetworking folder.
- Once you enter PeerNetworking folder locate and remove idstore.sst file.
- Optional: Some users are suggesting to delete all files from PeerNetworking folder, so you might want to try that as well.
Solution 4 – Edit the registry
In order to fix this error, some users are suggesting to change certain values in the registry. Changing the registry can sometimes lead to system instability, therefore you might want to create a backup of your registry in case anything goes wrong. To change the registry do the following:
- Press Windows Key + R and enter regedit.
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Peernet key in the left pane.
- Locate Disabled DWORD in the right pane and double-click it.
- Make sure the Value data is set to 0. Click OK to save changes.
- READ ALSO: Fix: ‘Windows sockets registry entries required for network connectivity are missing’ on Windows 10
In addition to editing the registry, users are also suggesting to use Local Group Policy. To do that, follow these steps:
- Press Windows Key + R and enter gpedit.msc. Press Enter or click OK to run it.
- In the left pane go to Computer Configuration > Administrative Templates > Network > Microsoft Peer-to-Peer Networking Services.
- In the right pane double-click Turn off Microsoft Peer-to-Peer Networking Services.
- When the properties window opens make sure that Not Configured option is selected.
- Click Apply and OK to save changes.
Solution 5 – Delete all files from MachineKeys directory
Users reported that Peer networking error 1068 can be fixed by removing files from MachineKeys folder. To do that, follow these steps:
- Go to C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys and delete all files from it. If you want, you can copy them to a safe location in case you need them for backup.
- After deleting the files restart your computer.
Users are also suggesting to run Homegroup troubleshooter, and you can do that by following these steps:
- Press Windows Key + S and enter homegroup. Select Homegroup from the menu.
- Once the Homegroup window opens click the Start the HomeGroup troubleshooter.
- Wait for the troubleshooter to finish the scan.
Lastly, users are also suggesting to delete your Homegroup or to leave the Homegroup, so you can try that as well.
Solution 6 – Change the security permissions for the MachineKeys folder
According to users, you can fix Peer networking error 1068 by giving the full control of the MachineKeys folder to Everyone. To do that follow these steps:
- Go to C:\ProgramData\Microsoft\Crypto\RSA\ folder.
- Right-click MachineKeys folder and choose Properties.
- Go to Security tab and click Edit.
- Select Everyone and check Full control option.
- Click Apply and OK to save changes.
Solution 7 – Use PowerShell
According to users, sometimes Peer networking error 1068 can be caused by IPv6. However, you can fix that issue simply by running a single command in PowerShell. To do that, you just need to follow these steps:
- Press Windows Key + S and enter powershell. Right-click Windows Powershell from the list of results and choose Run as administrator from the menu.
- Now enter the following command: PowerShell Get-NetConnectionProfile.
After running this command, the issue should be resolved and everything will start working again.
Solution 8 – Change Peer Name Resolution Protocol settings
Sometimes certain settings can cause Peer networking error 1068 to appear. However, you can fix this problem simply by changing a couple of settings in the Services window. To do that, follow these steps:
- Open Services window.
- When Services window opens, double-click Peer Name Resolution Protocol to open its properties.
- Navigate to Log On tab and select Local System account. Now click Apply and OK to save changes.
After doing that, the problem should be resolved. Alternatively, you can use the Local Service. To do that, follow these steps:
- Repeat the previous steps, but instead of selecting the Local System Account, enter Local Services as the account name and clear the password fields. Click Apply and OK to save changes.
- After doing that, restart Peer Name Resolution Protocol service.
After the service restarts, check if the problem is resolved.
Solution 9 – Install the latest updates
In some cases Peer networking error 1068 can appear due to missing system updates. Sometimes there might be glitches on your system, and that can cause this issue to appear.
Installing updates is rather simple, and for the most part Windows 10 automatically installs the missing updates. However, you can always check for updates manually by doing the following:
If any updates are available, Windows 10 will download them in the background and install them as soon as you restart your PC. Once your system is up to date, check if the problem still appears.
Solution 10 – Make sure that all required services are running properly
Peer networking error 1068 can appear if the required services aren’t running, and in order to fix it, you need to enable those services. To do that, open Services window and enable the following services:
- Application Layer Gateway Service
- Network Connections
- Network Location Awareness (NLA)
- Plug and Play
- Remote Access Auto Connection Manager
- Remote Access Connection Manager
- Remote Procedure Call (RPC)
Keep in mind that you might not be able to enable all services that are on the list such as Remote Access Connection Manager. This service is dependent on Windows Event Log service, and if Windows Even Log service won’t start, you’ll need to change certain permissions by doing the following:
- Navigate to C:\Windows\System32\winevt directory.
- Locate the Logs directory, right-click it and choose Properties from the menu.
- Navigate to the Security tab and click the Edit button.
- Now click the Add button.
- In the Enter the object names to select, enter Local Service. Now click Check Names and OK.
- Now repeat steps 4-5 but instead of Local Service enter Network Service.
- Now Select Local Service, and check Full control in the Allow column. Do the same for Network Service. Now click Apply and OK to save changes.
After doing that, restart your PC. Once your PC restarts, go back to the Services window and start Windows Event Log along with other services that weren’t able to start before.
Once you enable all the required services, the issue should be resolved and everything will start working again.
Peer networking error 1068 can be problematic, but most users reported that they managed to fix it by deleting the idstore.sst file. If that solution doesn’t work for you feel free to try any other solution from this article.
Editor’s Note: This post was originally published in August 2016 and has been since completely revamped and updated for freshness, accuracy, and comprehensiveness.
- Fix: Network Protocol Missing in Windows 10
- Fix: ‘Windows Could not Automatically Detect Network’s Proxy Settings’
- How to Fix Windows 10 Network Adapter Problems
- Fix: Homegroup Cannot Be Set Up in Windows 10
- How to fix Ethernet problems in Windows 10
Drumming is a passion that many music lovers nurture, and physical drum machines have been sufficing the needs till now. But with the advancement of […]
Microsoft has recently released the first Beta preview of Microsoft Edge. Along with that, to ensure the security of their browser, they also announced the […]
Sometimes, while trying to connect with a 32-bit access database from Power BI-64bit Dekstop, you may encounter not registered error. The error can occur with […]