Latest version of Intel PROSet Wireless causes 100% CPU usage
, April 29th, 2007Last night I had the misfortune of updating to the latest version of the Intel PROSet Wireless application and device drivers (11.1.0.86). After updating the machine spins into a 100% CPU gobbling cycle by the ZCfgsvg.exe process. This is related to the Intel PROSet application. Killing the process moves the problem to the iFrmwork.exe process. After faffing around for 30 minutes trying to figure out what was poked I just uninstalled the whole damn thing.
The reason I upgraded was to try and resolve a very bizarre problem I’ve had for some time on my Windows laptop. Every so often the machine will throw a complete hissy fit with fonts not rendering making the machine unusable (even the Windows Start button text goes away). For some time I’ve had my suspicions that it was related to the Intel PROSet Wireless application somehow mangling something in the OS. It’s a pretty far fetched suspicion because no application should be able to prevent the OS from being able to render fonts onto the display. However, more often than not it all went pear shaped after an error box (with nothing in it) was popped up by the Intel PROSet Wireless application.
So, now I may not have the problem with fonts going away but I’m faced with using Windows wireless networking which I never got to really work satisfactorily in the past - why I moved to the native Intel application in the first place. Luckily I found another Windows download that helps resolve some of the problems I was initially having with the Windows wireless management - I’ll cover this in a later post.
October 18th, 2007 at 6:11 pm
Damn, I’m having exactly the same problems but with a slightly older version of Proset. Going to look for a solution elsewhere.
The comment above is spam btw.
November 7th, 2007 at 4:53 am
I ended up reinstalling Proset, including older versions a few times, with no luck. Then, at one point, after one of such reinstalls, my profiles disappeared. After that, everything is fine. I didn’t get to keep my profiles but there was something in them, apparently, that was messing everything up.
April 23rd, 2008 at 4:38 pm
I had The problem described above on a customers Laptop. I managed to fix the problem by enabling the proset wirless application to manage wireless networks and created a profile for the connection within that application. Once it was set up properly the cpu usage dropped from 75% + down to 7% used. Problem sorted.