Hello,

After a recent a system restore my homegroup stoped working. I saw that there was a problem with the Network list because I was connected to my wi-fi network but Network & Sharing showed no cennections. I was able to solve that problem by repairing the permissions on HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\ and its subkeys, but sadly that didn't solve the homegoup problem.

Than I exited my homegroup and tried to create a new one and than came the network must be private error.

my nework is private according to N&S Center and the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles->category is set to 1 which should be the value for private network

Than I tried everyting I can think of, but still no luck.

So far I tried this:

• Run the inbuilt homegroup "problem solver" (this says the problem is I'm not joined to any homegroup)
• Updated system image with DISM.exe /Online /Cleanup-image /Restorehealth and than run sfc /scannow
• Uninstalled AV and disabled Windows firewall
• Tried reseting registry permissions with SubinACL
• Deleted all files in C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\PeerNetworking
• Deleted all files in C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys
• Added LOCAL SERVICE to permissions on C:\ProgramData\Microsoft\Crypto\RSA
• Deleted current wi-fi connection and after reboot I re-connected and of course I allowed finding devices and PCs
• Uninstalled WMP and than re-installed it
• Created a new local admin user
• Set connection type to private in Local Security Policy

The funny thing is that Event Viewer only recorded an error for media sharring. First WMPNetworkSvc couldn't refresh registry with errror code 0x80070005 and after I re-installed WMP than with this A new media server was not initialized because RegisterRunningDevice() service detected an error 0x80070005. So looking at this error code obviously there are still some permission problems but I couldn't find where.

I was looking at the svchost.exe in procmon and I saw that it says "invalid parameter" for idstore.sst and idstore.sst.new and it says "name collision" for Crypto, Crypto\RSA and Crypto\RSA\MachineKeys when trying to create homegroup, which could be a problem or not, I'm not that pro to determine.

Is there anything I can do to make my homegroup work again?

And please don't say reinstalling/repair installing/refresh installing Windows because currently I don't have time fo it. It would take at least 24to48 hours to reinstall and properly configure all my softwares.

• Edited by PisziBP Friday, May 15, 2015 1:19 AM

Hi,

How about your problem now? Is there any Access Denied information in ProcMon? Is there any

error message with Home Group?