The symptoms that you have shared, (installs on a clean system, but when the "old" driver is present, the "new" driver is added to the driver store, but the class installer is not invoked by the PNP manager) are commonly due to the fact that the "new" driver has a lower driver rank than the "old" driver. When verbose setupAPI logging is configured there will be verbose information on driver ranking in either the setupapi.app.log or the setupapi.dev.log (on Vista or later).
The MSI log that was posted indicates that the Difx 'legacy' flag was set (but ignored - if you can believe that). A USB driver is always PNP (so far as I am aware). Certainly setting the 'legacy' flag, indicating a non-PNP driver, would make the driver rank very low. Also if the "old" driver is WHQL signed then it will always out rank a legacy driver or a driver which is not WHQL signed (even if test signed). Aside from the Difx 'legacy' flag issue. the fact that the driver was added to the driver store indicates that Wix/MSI and DifxApp did it's job and that the issue is at the PNP Manager/Class installer level. The setupapi log is the best way to track down driver design/driver signing issues so far as I am aware. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Driver-Issue-tp7595156p7595181.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
