Windows 10: That's it Mircrosoft and all followers of damaging my computer with faulty updates

The latest feature update has broken my computer you bastards. Now I'm going to get the whole company fined for property damage and if anyone trys to reply to this message will be sued on the spot. And if you suspend me or do a profile ban then Microsoft will be a dead company as I will take it further.

:)

 

2017 windows 10 Creator update damaged Homegroup

Hello,
My name is Daniel and I am having issues with the HOMEGROUP ever since the big update that came at the end of spring for windows 10.

First, my system is as follows:
there are 4 computers:
3 windows 10, 64 bits computers Home Edition, hardwired to the modem directly.
1 laptop windows 10 Home edition, connected wirelessly.

The problem that I have is as follows:
I have been using "Homegroup" for the past 3 years or so, and it always worked very well.
But ever since the "Creator's update" released either in April or may 2017, the Homegroup feature is broken.

My main computer which was the one who started the "Homegroup" got updated first, and after that, no other computer sees the homegroup.

However, I need to explain the following:
My main computer, who started the homegroup, still sees the "old homegroup" as active, AKA Ghost homegroup.
I have tried to delete it by following the steps here
Fix issues with the homegroup in Windows 10

Solution 1 – Delete files from PeerNetworking folder

1. Go to c:\windows\serviceProfiles\LocalService\AppData\Roaming\PeerNetworking.
2. Delete idstore.sst and move on to Step 3. If deleting idstore.sst doesn’t work, go back to c:\windows\serviceProfiles\LocalService\AppData\Roaming\PeerNetworking and delete all files and folders in it and go back to Step 3.
3. Go to the Network Settings and Leave the Homegroup.
4. Repeat this for all the computers in your network.
5. Turn off your computers.
6. Turn on just one, and create a new Homegroup on it.
7. This Homegroup should be recognized on all of your computers now.

I have followed this step by step. But I cant get rid of the old "homegroup".
This started to happen only after I upgraded to the "Creators update" and all computers are up to date.

How can I get rid once and for all from this ghost homegroup.

I have the followed the above mentioned steps, in each of the computers in the network. This ghost homegroup still appears and I can't join it, or leave it.

 

Windows Updated(16299.309).KB4088776 Restart is required to complete.

Hi dalchina. Good news, I followed your suggestion and reinstalled the update and now it appears as "installed correctly" *Biggrin Maybe it was not necessary to run the Windows Update Troubleshooter or maybe if necessary. But using it I do not think it could have worsened something. The installation was very fast, unlike the first time it showed step 1 and step 2 completed.

Thanks for the suggestions and for the time to respond Best regards.


And thanks for the tip of that program, I'll have it on my list.

 

Should I update bios?

I would read the warranty before doing anything. If the manufacturer finds out you did something not on their approved list of steps,for example using a program they didn't list, or a bios, etc, they can treat your video card rma like you threw it against the wall , because if something goes wrong and you didn't follow their steps exactly ,it was damaged through human error and they're not likely going to be obligated to cover it warranty wise. I don't know for sure, I just advocate that you check first , and I also advocate that you verify that it's an actual update ,because very rarely do manufacturers release updates for gpu bios'. And they most certainly wont cover a GPU "update" if its a bios file written by some dude in the Ukraine, it has to be a set process, they have predetermined often.