Cato2
July 22nd, 2009, 11:35 AM
I recently installed ESET NOD32 Antivirus 4.0 on a friend's PC using Windows XP SP3. Downloaded on Sun 19th July (didn't note exact version, sorry).
Since then I have found that installing a new USB mouse (Logitech LX6) caused the New Hardware Wizard to pop up, but the detection failed to install any driver - it didn't show the exact name of the mouse, only "USB RECEIVER". I also found that a new PATA hard disk, which didn't require any new drivers, caused the New Hardware Wizard to pop up, and this too didn't install any drivers - the disk works fine and is now the only disk in use.
The Logitech LX6 mouse worked fine without any drivers in another PC (XP SP2, not running ESET and I can't install it there). So I know the mouse hardware is OK, and no new drivers are needed anyway.
You're probably thinking "nothing to do with ESET", but someone in this thread (http://forum.notebookreview.com/showthread.php?t=377822) seems to have had a similar problem, so I'm wondering if there is anything in this. Clearly can't be a common problem or there would be more hits on Google.
I tried reverting to XP SP2 but that seemed to make things worse if anything.
I will try installing ESET 3.0 and see if that helps. Since 4.0 added support for auto-scanning external drives and was released only a few months ago, perhaps it's plausible that 4.0 has a bug that interferes with hardware detection in some cases.
I have been using ESET 2.7 for some years on another PC, so I hope there's a solution for this.
Since then I have found that installing a new USB mouse (Logitech LX6) caused the New Hardware Wizard to pop up, but the detection failed to install any driver - it didn't show the exact name of the mouse, only "USB RECEIVER". I also found that a new PATA hard disk, which didn't require any new drivers, caused the New Hardware Wizard to pop up, and this too didn't install any drivers - the disk works fine and is now the only disk in use.
The Logitech LX6 mouse worked fine without any drivers in another PC (XP SP2, not running ESET and I can't install it there). So I know the mouse hardware is OK, and no new drivers are needed anyway.
You're probably thinking "nothing to do with ESET", but someone in this thread (http://forum.notebookreview.com/showthread.php?t=377822) seems to have had a similar problem, so I'm wondering if there is anything in this. Clearly can't be a common problem or there would be more hits on Google.
I tried reverting to XP SP2 but that seemed to make things worse if anything.
I will try installing ESET 3.0 and see if that helps. Since 4.0 added support for auto-scanning external drives and was released only a few months ago, perhaps it's plausible that 4.0 has a bug that interferes with hardware detection in some cases.
I have been using ESET 2.7 for some years on another PC, so I hope there's a solution for this.