Homegroup PC suddenly disappeared - sort of....

Hi, I'm at a bit of a loss. One of the PC's on our homegroup is today suddenly unreachable from the others. The error code is 0x80070035 "The network path was not found".


We have two desktop PC's both running the same version of Windows 7 Professional SP1, I'll call them PC1 and PC2. I also have an old laptop running Vista and a wireless printer. PC1 and the laptop can see each other but neither can see PC2. PC2, however can see both PC1 and the laptop. All can access the printer. The homegroup name of PC2 doesn't seem to have changed.



I've tried running both the network and homegroup troubleshooters on both PC's but have been unable to establish the cause or fix it.


On PC2, as suggested by the troubleshooter, I tried leaving the homegroup and then rejoining it but became a bit confused because, after it gave me the password for the homegroup, instead of me having to add any devices it reported it was already in the homegroup.


I've also tried powering off both PC's then rebooting but that hasn't helped. I can't think where to go from here so any suggestions would be really welcome.

Hi iko22, thanks for your reply.


Funnily enough after I'd posted my query I did think of doing a System Restore but your reply came in before I could prise my wife off the computer.


I have now completed the System Restore and this has fixed the problem. It looks like the last Windows rollup updates that I installed on 19th must have been responsible. One of them was for the .NET framework so I reckon that's the chief suspect.


I have Windows Update set to notify me of updates which I install manually so I can keep track of situations like this. It's one of the reasons I'm very reluctant to go to W10 which I have heard stories about automatic updates breaking users machines.


Thanks again.

Both are now working but mine (PC1) has been downloading but failing to install the monthly rollup for several months now and I just can't face the hassle of trying a system repair in an attempt to fix it. The last time I tried the update readiness tool it screwed something in the system and I had to use System Restore to get it working again. There's obviously something wrong somewhere in my system but as it's otherwise working ok I don't want to fiddle with it.


The wife's (PC2) has been installing the updates with no problem until now but it looks as if I'll have to reject the .NET update at least. I'll probably try installing the ordinary rollup again to see if that causes any problems but I'm resigned to the fact they'll now both be nagging me about updates.

I haven't investigated how to do that yet but it would be useful. I could, of course, set Windows Update to never check but I suspect it'll then keep nagging me about that.


I haven't run CHKDSK or sfc in the very recent past but I did use them to try to resolve the issue with Update and nothing was found so I'm afraid I've just given up on it. I will give them another go, though, just in case.

Many thanks for that. I've used it on my desktop (PC1) and bookmarked it for future reference.


I've now run CHKDSK and sfc on PC1 and nothing was found.

I decided to try to pin down what was the cause of the problem by installing the updates to PC2 one at a time. It turns out it was actually the Security Monthly Quality Rollup that was responsible. The .NET rollup installed without causing any problems.


I've now hidden the offending update on PC2.