Wszystkie dyskusje > Fora Steam > Help and Tips > Szczegóły wątku
Ten wątek został zamknięty
"steamwebhelper.exe" not responding no matter what
Hi there,

a friend of mine has been having constant issues with "steamwebhelper.exe" not responding and so far nothing we came up with worked at all.

Here is a list of things we tried:

- Restarting Steam when it happens leads to the same issue
- Starting Steam with the "-no-browser" option
- Reinstalling steam (both to the default location and on a different harddrive)
- Restarting the webhelper with both GPU acceleration and sandboxing disabled
- Deleting "steamwebhelper.exe" and having Steam redownload it
- Clearing steam browser and download caches (both via menu and filesystem)
- Opting for STEAM Beta client
- Adding the "steamwebhelper.exe" and the whole steam folder to the Windows Defender Exceptions list
- Checked firewall settings for steam
- We replaced the RAM (16GB) as we thought it might have been the issue, which it wasnt

Some additional notes:
- There is no additional Antivirus on the system which is Windows 10 and up to date
- When starting the PC and waiting a while so all services come up the error occurs. Starting steam right after being on the desktop seems to work, but we could not identify any services that might cause the issue
- The issue has been going on for a while
- After the dialogue for the non responsive "steamwebhelper.exe" the main Steam window opens but browser and Friends list wont show up

We have been browsing the web up and down and saw a lot of these issues occur but so far no fix seems to remedy it.

So any input regarding this would be greatly appreciated.

Thanks a lot in advance!
< >
Wyświetlanie 91-105 z 110 komentarzy
Mr Sy Guy 1 października 2024 o 9:20 
I've tested a number of various launch options, as well as all the install recommendations, including a fresh windows install. DISM and SFC come back clean, and nothing has worked.
Still seeing 5 - 7 webhelper processes start and stop in a loop. This happened after updating to the latest graphics driver but was not remediated by rolling back.

What I find interesting in my case, is that AMD Adrenaline software experiences the same type of crash loop cycle when I try to open it. Even after a cloud reinstall of windows and fresh Steam and Adrenaline install these behaviors persist.

I've opened a support case and will follow up if we are able to identify anything useful.
iMageYou 1 października 2024 o 10:10 
Początkowo opublikowane przez Mr Sy Guy:
I've tested a number of various launch options, as well as all the install recommendations, including a fresh windows install. DISM and SFC come back clean, and nothing has worked.
Still seeing 5 - 7 webhelper processes start and stop in a loop. This happened after updating to the latest graphics driver but was not remediated by rolling back.

What I find interesting in my case, is that AMD Adrenaline software experiences the same type of crash loop cycle when I try to open it. Even after a cloud reinstall of windows and fresh Steam and Adrenaline install these behaviors persist.

I've opened a support case and will follow up if we are able to identify anything useful.


Are you on a gaming laptop with monitors hooked up? For a lot of us it takes unplugging the monitors. In my case I have to completely disconnect from my dock and use the laptop screen and it opens fine then I can connect it back
Mr Sy Guy 1 października 2024 o 10:28 
Początkowo opublikowane przez iMageYou:

Are you on a gaming laptop with monitors hooked up? For a lot of us it takes unplugging the monitors. In my case I have to completely disconnect from my dock and use the laptop screen and it opens fine then I can connect it back

Thanks for checking, no I am on a desktop setup, and even so I tried disconnecting any peripherals I didn't need removing keyboard and monitor once I was setup to click 'run as administrator' on the shortcut, seemed silly, but worth a try.

PC build, nothing is overclocked:
B550 Aorus Elite AX V2
Ryzen 5 5600x
AMD Radeon RX 6700XT (Latest driver version 32.0.11037.4004 - also tested with previous versions)
32 GB DDR4 CL16
Windows 10 Pro 64bit build 10.0.19045
Mizphit Reign 2 października 2024 o 6:13 
The fix for me. I went through all of the things said in this discussion and others. Nothing helped, uninstall, reinstall on new drive, in new folder. appdata, disconnect monitor, etc. I noticed my nvidia had an error when opening also, was thinking the shadowplay overlay might be messing with it.
I downloaded the latest drivers and nvidia experience and installed with fresh install. All works now.
Hope it helps someone get this fixed for them. Was infuriating when nothing worked as I seen everyone say "that worked for me" lol
Shadefang 3 października 2024 o 5:25 
Tossing this out in case it's useful to anyone: I had a similar problem and the solution was to disable my onboard graphics adapter (I use it alongside a card). Steam would get stuck in a loop of trying to load, popping up a window, then instantly closing it. Disabling the adapter lets it get through the initial launch, and then I'm able to turn it back on once steam's up and running.
mallyredd 9 października 2024 o 17:08 
Początkowo opublikowane przez Shadefang:
Tossing this out in case it's useful to anyone: I had a similar problem and the solution was to disable my onboard graphics adapter (I use it alongside a card). Steam would get stuck in a loop of trying to load, popping up a window, then instantly closing it. Disabling the adapter lets it get through the initial launch, and then I'm able to turn it back on once steam's up and running.
THIS WORKED TYSM
mdeka 12 października 2024 o 18:01 
In my case on my HP desktop, there is integrated graphic and additional AMD Radeon one...
OS is freshly installed Win10 Pro 22H2, two weeks ago...
I use two monitors; one connected on additional VGA card (primary) and another on integrated one...
Both monitors in moment I installed steam client app was connected via VGA cable, and app vas working...
In meantime I obtained one Display port cable and connected second monitor to integrated graphic with them...
Today I finally find some time to install some of my games, but steam client app looped in crush cycle with info that steamwebhelper.exe not responding...
I tried everything (reinstall steam app, delete recommended files or folders, make exceptions for AV scanning or firewall...) but nothing helps.
Then I see that someone has issue with docking station for laptop, and monitor cables, and tried to disconnect Display port before started steam app and damn thing started correctly!!!

This is solution in my case...
Ostatnio edytowany przez: mdeka; 12 października 2024 o 18:05
AllADream 18 października 2024 o 20:28 
Początkowo opublikowane przez MaxNoise:
does anyone else have any ideas on how to fix this issue. i've tried everything listed above here and everything i can read online. uninstalled and reinstalled steam so many times i lost count. i cannot get this to work. windows firewall disabled, i use avast and have totally disabled it and i still get the same looping behavior where the steam ad windows pop up for a second and then disappear. when i right click in the tray i get the standard error dialog " steamwebhelper, a critical Steam component, is not responding The Steam UI will not be usable" and the only option that works is Exit steam - none of the others do anything.

When i look at windows task manager i see "steam (32 bit)" running and then "steam client webhelper" quickly jumps in the mix like 7 times and disappears. about every 4 ot 5xs a steamerrreporter jumps in a sec too. this continues to do loop OVER AND OVER until i kill it.

So at this point the steam and all of my games are unplayable. i've been trying to resolve this for days and i'm at a dead end. is there anything else that someone has tried that has worked ??? at this point i'll literally try ANYTHING

I encountered this issue after Windows Update (WU) tried to update my Nvidia graphics drivers on its own while I had GTA Online loaded, leading to a BSOD. On reboot, the BSOD occurred a couple minutes after loading the desktop, while WU tried to install the driver update again. After a few rounds of this I killed WU and the driver update process in Task Manager before the BSOD occurred. That gave me an opportunity to manually update the GPU driver to the latest stable version 565.90 dated October 1, 2024. That cured the BSOD.

Unfortunately, the problems didn't end there. When I tried to load GTA again, I discovered Steam would not open. It was basically as MaxNoise described in the quote above.

No amount of uninstalling and reinstalling Steam, with full wipes of all Steam data (via both Windows and Revo Uninstaller), installing to a different directory, modifying launch arguments, turning on compatibility mode, etc. worked.

This is a desktop Windows 10 PC with no integrated GPU, connected to only one monitor, and with no third-party AV (Windows Defender only).  So none of the mentioned solutions relating to these scenarios apply.

I finally got things working by uninstalling the new GPU drivers (which brought back the BSOD), then installing the oldest available non-archived version from Nvidia (546.17) in Safe Mode. After that, I restored my backed-up Steam files and Steam launched, allowing me to log in and proceed as usual.

I saw someone mention in another discussion that Nvidia drivers newer than 551.xx or so may cause this issue.

So for anyone who has tried everything like I did, and has an Nvidia GPU, it might be worth downgrading GPU drivers. As of now I can confirm 546.17 works for me, but newer versions may work as well. I haven't tested.
Iceira 19 października 2024 o 3:22 
Początkowo opublikowane przez AllADream:
Początkowo opublikowane przez MaxNoise:
does anyone else have any ideas on how to fix this issue. i've tried everything listed above here and everything i can read online. uninstalled and reinstalled steam so many times i lost count. i cannot get this to work. windows firewall disabled, i use avast and have totally disabled it and i still get the same looping behavior where the steam ad windows pop up for a second and then disappear. when i right click in the tray i get the standard error dialog " steamwebhelper, a critical Steam component, is not responding The Steam UI will not be usable" and the only option that works is Exit steam - none of the others do anything.

When i look at windows task manager i see "steam (32 bit)" running and then "steam client webhelper" quickly jumps in the mix like 7 times and disappears. about every 4 ot 5xs a steamerrreporter jumps in a sec too. this continues to do loop OVER AND OVER until i kill it.

So at this point the steam and all of my games are unplayable. i've been trying to resolve this for days and i'm at a dead end. is there anything else that someone has tried that has worked ??? at this point i'll literally try ANYTHING

I encountered this issue after Windows Update (WU) tried to update my Nvidia graphics drivers on its own while I had GTA Online loaded, leading to a BSOD. On reboot, the BSOD occurred a couple minutes after loading the desktop, while WU tried to install the driver update again. After a few rounds of this I killed WU and the driver update process in Task Manager before the BSOD occurred. That gave me an opportunity to manually update the GPU driver to the latest stable version 565.90 dated October 1, 2024. That cured the BSOD.

Unfortunately, the problems didn't end there. When I tried to load GTA again, I discovered Steam would not open. It was basically as MaxNoise described in the quote above.

No amount of uninstalling and reinstalling Steam, with full wipes of all Steam data (via both Windows and Revo Uninstaller), installing to a different directory, modifying launch arguments, turning on compatibility mode, etc. worked.

This is a desktop Windows 10 PC with no integrated GPU, connected to only one monitor, and with no third-party AV (Windows Defender only).  So none of the mentioned solutions relating to these scenarios apply.

I finally got things working by uninstalling the new GPU drivers (which brought back the BSOD), then installing the oldest available non-archived version from Nvidia (546.17) in Safe Mode. After that, I restored my backed-up Steam files and Steam launched, allowing me to log in and proceed as usual.

I saw someone mention in another discussion that Nvidia drivers newer than 551.xx or so may cause this issue.

So for anyone who has tried everything like I did, and has an Nvidia GPU, it might be worth downgrading GPU drivers. As of now I can confirm 546.17 works for me, but newer versions may work as well. I haven't tested.

If you get BSOD, you have a pc that's not update, BIOS and chipset Driver is possible the issue, and you also confirm it with new Drivers that dont like old settings in your pc.

If you are AMD user in top of this say's it all.
its not any job here to tell you update your pc, thats is your job, ( old pc saying read the crappy manual pc once had or cd or digital DL )

Use older driver my butt, seem to be a frequent user problem here, Nvidia and AMD do make mistake sometimes that not same as you did not contact them with it,

GPU card support is not a steam issue or game devs issue.

To many steam user get away with alot of posting of crap here and they dont have own pc updated. ( be happy some one bother with it and tell you things the hard way. )

Sure it can happend some day a user is right, and yet you fail in understand ask your GPU card Support, it's here steam user fail in who has support.

Steam is not going to fix your GPU driver and BIOS and Chipset driver
ask yourself this do you think GPU card support is going to fix BIOS and chipset driver,
hell NO they focus on GPU card driver only, be luck if someone point it out and it will still be your problem to fix it.

BSOD my butt here.
we can also say maybe you have a defect pc gpu card , this is a user forum, have you any idea of rare that is, then you will see update pc is much easier to do task then swap hardware. then most user here dont have any spare part.

This is a user forum for steam users to steam users this is not support.
now go fix your pc or not, we cant force you to do anythinmg here. gl with that.
Ostatnio edytowany przez: Iceira; 19 października 2024 o 3:43
LordBeDe 19 października 2024 o 5:17 
Początkowo opublikowane przez AllADream:
I finally got things working by uninstalling the new GPU drivers (which brought back the BSOD), then installing the oldest available non-archived version from Nvidia (546.17) in Safe Mode. After that, I restored my backed-up Steam files and Steam launched, allowing me to log in and proceed as usual.

I had the same problem, BSOD after automatic driver update and Steam not starting after rollback. Clean installing 546.17 worked for me.

GTX 970 btw.
Ostatnio edytowany przez: LordBeDe; 19 października 2024 o 5:18
Iceira 19 października 2024 o 5:22 
Początkowo opublikowane przez LordBeDe:
Początkowo opublikowane przez AllADream:
I finally got things working by uninstalling the new GPU drivers (which brought back the BSOD), then installing the oldest available non-archived version from Nvidia (546.17) in Safe Mode. After that, I restored my backed-up Steam files and Steam launched, allowing me to log in and proceed as usual.

I had the same problem, BSOD after automatic driver update and Steam not starting after rollback. Clean installing 546.17 worked for me.

GTX 970 btw.

And again take it up with GPU card support,
steam and game dev's, is not going to fix your BSOD for you.
Ostatnio edytowany przez: Iceira; 19 października 2024 o 5:27
sayonara 6 stycznia o 17:08 
Początkowo opublikowane przez WinterSolstice:
Ready for the REAL FIX, OP?

Well here it is:

Go to this location below:

(drive letter where Steam is installed on):\Steam\userdata\(Corresponding Steam Account Number)\config\librarycache and delete achievement_progress.json

If this file is over say 400KB+ (mine was at 8999KB), this is your issue and delete it when Steam is not running.

If Steam Client in Task Manager is taking up 1.1GB+ of RAM, this is 100% the issue/fix.

When Steam starts it will make a new file. The file is simply recording achievements that have been completed and when a user has a lot of games, this file can add up a lot of useless information when it is bugged and not clearing itself out.

This file causes a few issues such as high RAM usage, library view stuttering, Steam Webhelper not running, Steam infinite restart loops, and Steam Library Home not loading/failing to start.

Take my advice, you will not regret it, capisce?

This is the working fix for me in 2025. Thank you King.

Still, it's a weird bug.
Mec 12 marca o 9:57 
I ♥♥♥♥♥♥♥ hate technology man. Everything worked fine, everything is updated etc etc, Then suddenly this ♥♥♥♥♥♥♥ webhelper just goes on strike and no fix can do anything to stop it's relentless quest in ♥♥♥♥♥♥♥ my day up
Mec 12 marca o 9:58 
Im going back to the ♥♥♥♥♥♥♥ stone age ♥♥♥♥ this ♥♥♥♥ im tired of trouble shooting i've been doing it for the most part of my ♥♥♥♥♥♥♥ life now
nesag 12 marca o 10:11 
Tried everything from this thread. Don't even have userdata folder. Nothing works.
Steam Support doesn't help. It has been a problem for several days now. I know how the guy above feels.
Ostatnio edytowany przez: nesag; 12 marca o 10:11
< >
Wyświetlanie 91-105 z 110 komentarzy
Na stronę: 1530 50

Wszystkie dyskusje > Fora Steam > Help and Tips > Szczegóły wątku
Data napisania: 21 marca 2024 o 2:17
Posty: 110