Has anyone else had problems with helpsrv.exe taking over their PC since the Tuesday MS security update?
Since I patched Tuesday, helpsrv.exe is starting up all by itself and using 100% of my CPU. The machine is frozen for several minutes until it stops.
I've seen the MS problem report links and blogs on it and according to MS the latest SP fixes it. The problem has been documented for at least 8 months but is new to my computer. I first noticed it when I came back after an hour of inactivity.
There was a hotfix issued last fall but it's on the "call and pay" service only.
It took 5 minutes for help service to stop thrashing and release the CPU.
-HD activity was high,
-CPU usage was at 100%.
-There was no internet activity.
-No other computers on the LAN were powered.
-I have a hardwire only network.
-My PC has all of the latest updates to AV (AVG), windows (XP Pro) and spyware (adaware and spybot) installed.
-Full scans were run on the PC with no hits.
-No new software installed since the problem surfaced.
For now I have switched help service to manual from automatic which was one of the suggestions in the blog. I'll update if that solves it.
Since I patched Tuesday, helpsrv.exe is starting up all by itself and using 100% of my CPU. The machine is frozen for several minutes until it stops.
I've seen the MS problem report links and blogs on it and according to MS the latest SP fixes it. The problem has been documented for at least 8 months but is new to my computer. I first noticed it when I came back after an hour of inactivity.
There was a hotfix issued last fall but it's on the "call and pay" service only.
It took 5 minutes for help service to stop thrashing and release the CPU.
-HD activity was high,
-CPU usage was at 100%.
-There was no internet activity.
-No other computers on the LAN were powered.
-I have a hardwire only network.
-My PC has all of the latest updates to AV (AVG), windows (XP Pro) and spyware (adaware and spybot) installed.
-Full scans were run on the PC with no hits.
-No new software installed since the problem surfaced.
For now I have switched help service to manual from automatic which was one of the suggestions in the blog. I'll update if that solves it.