After updating the driver for a 3COM card to use the Strobe Data DEQNA driver, the Properties page for all network cards in the system becomes unavailable.
This failure is caused by a bug in the Microsoft Windows operating system. The problem will be fixed in the next service pack released by Microsoft.
To workaround this bug, first use the device manager to uninstall the DEQNA network card and reboot. Fix the properties for the other network cards and then update the driver to use the Strobe Data DEQNA driver again.
The following email was sent by Microsoft after Strobe Data opened a problem report.
From: R... R... [mailto:r...@microsoft.com]
Sent: Wednesday, 31 August 2005 10:18 AM
To: support@strobedata.com
Subject: RE: E-mail for Case SRS05081.......
Here is what is happening ...
When a net-class device is updated with a non-net-class INF, the network class engine does not run. So, the network class engine never has a chance to clean up the binding information etc. Next time, when you select properties of any other NIC, network class installer instructs the binding engine to load all the information (or all the NICs). While, loading the bindings, the binding engine encounters some irregularities/unexpected bindings, and stats to complain.
Side-effects range from disabling the property page to errors like : "can not display properties for an adapter that does not exist".
If you uninstall the device and then install with the wdm-driver (non-net-class), it shall be trouble free.
How do you want to proceed from here ? I will definitely file a bug for this. If you want a hot fix, you should provide us with a very strong business justification. From my personal experience, it is highly un-probable to get a hot fix for this [please not that I do not intend to discourage you] -- Otherwise, the bug will be fixed in the next service pack.
Thanks,
R.... R...
R....@microsoft.com