100% Fixed - Steam Client Bootstrapper has stopped working

[cyber_flame]

OK. Finally fixed it. Now Store, achievements and game are working.

Just run command Prompt or Windows PowerShell as Administrator

Type this command

netsh winsock reset

once successfully done, exit command prompt and restart your computer.

Voilaaaaaaaaa.

In case if you still face error then go to steam folder. Rename Steam.exe as Steam.exe.abc or whatever you wish.

Now rename steam.exe.old to steam.exe

Run Steam Client and it will work.


I have Windows 10 Professional Edition x64 (Completely Updated)

[cyber_flame]

I finally fixed it. Please try at your side, if work for you, inform to others.

[fff]

ty for help. this works

[Sov]

This fix worked for me with regards to getting steam to start running.

I was originally having an issue as well where bootstrapper error was occuring while playing games or just surfing steam but have not experienced it again so far.

Thanks, man

[cyber_flame]

Glad that your problems solved.

[Lab Grade Aspartame]

Still not working here Windows 7 x64

[Eswyr]

Originally posted by Lab Grade Aspartame:

Still not working here Windows 7 x64

I remove the userdata folder and open again the applicattion and work for me. i'm not sure why happens, but it's the only way to open the library and run steam normally.

Edit: I have too Windows 7 x64.

[The Giving One]

Originally posted by Chris:

I remove the userdata folder and open again the applicattion and work for me. i'm not sure why happens, but it's the only way to open the library and run steam normally.

From what we have seen here, it is the config.vdf folder inside that userdata folder that causes this problem. You may want to restore the rest of the userdata folder as there are other files you may want to keep.

[Eswyr]

Originally posted by The Giving One:

Originally posted by Chris:

I remove the userdata folder and open again the applicattion and work for me. i'm not sure why happens, but it's the only way to open the library and run steam normally.

From what we have seen here, it is the config.vdf folder inside that userdata folder that causes this problem. You may want to restore the rest of the userdata folder as there are other files you may want to keep.

oooooh, i try that later if work. Thanks alot! I run anyways, but i only lost my photos.

[The Giving One]

Originally posted by Chris:

oooooh, i try that later if work. Thanks alot! I run anyways, but i only lost my photos.

Exactly, as the photos you mentiond here are in that folder also. Try to merge everything back from the old userdata folder later if you want to, but leave out the config.vdf folder and that "should" take care of this.

Thanks.

[Kennysbot]

Still not working.....QQ

[[Magog] Fyrebyrd]

Worked for me Thanks!!

[Fohom]

Finally a solution that works for me! Thanks!!! - on windows 7 x64

[Merchant of Menace]

Just wanted to confirm that netsh winsock reset followed by a restart worked for me - thank you!!

[BitumenBunyip]

Hi All - I had this problem 12 September 2017 with Bitdefender Total Security 2018, the cmd action did not work, nor did running steam as administrator. What I did was turned off Bitdefender FIREWALL and turned off Bitdefender Advanced Threat Defense. Then ran steam and it worked from here on. Remember to turn on your firewall and Advanced Threat Defense - all seems well now.

[GoFigYourself]

Originally posted by KrazManik:

Hi All - I had this problem 12 September 2017 with Bitdefender Total Security 2018, the cmd action did not work, nor did running steam as administrator. What I did was turned off Bitdefender FIREWALL and turned off Bitdefender Advanced Threat Defense. Then ran steam and it worked from here on. Remember to turn on your firewall and Advanced Threat Defense - all seems well now.

Had this exact same issue after updating Bitdefender to 2018. This worked. Thanks for posting this.