Any idea what that's for? It's classified as Important, but in my experience the driver related updates from MS almost always break stuff. I once had to regscan my Win98SE PC from some kind of CPU related update from them because it wouldn't even boot anymore.
I just set up a wireless router for use with this PC a few days ago (Cisco E3000), the wifi card is an Intel Wifi Link 5100 with the latest drivers from Intel.
-
FWIW, there was also once a time where autoexec.bat and config.sys ran the computer and device settings actually sat in at .inf file. WHQL rolled out roughly 6 or 7 years ago to prevent that kind of scenario to ensure that drivers MS rolls out at least provide a minimum of functionality and stability. The WHQL drivers are typically a middle ground somewhere between the component manufacturer's bleeding edge and the computer manufacturer's "known good" 2 year old versions. Holding a grudge over a bad driver from over a decade ago is absurd. -
It wasn't just one bad driver, it was every single time I downloaded a driver from Windows Update over the course of many years, including after WHQL was established. The CPU thing was just the most potentially severe one. If I hadn't known to run regscan.exe and rollback the PC I would've likely figured I needed to buy a new PC.
I'm still not sure why they think I'd need a separate driver from MS for features involved with Intel hardware interfacing with my Cisco router. Seems like all Windows would need is the driver for the wifi card.
Driver for "microsoft wireless router module" shows up in MS Update now
Discussion in 'Networking and Wireless' started by nemt, Oct 10, 2010.