I would also enable MSI extra debug logging and evaluate the msi logs, typically in %temp%. My first guess, and it is only a guess (without specific data from the log) is that on a x64 system, if the msi CA tried to launch a 32 bit version of the api it would fail. But again this is only one possible guess. If the call to the Setupapi.dll failed due to bitness, I would not expect any entry in the setupapi.xxx.log, but you should see info in a verbose msi log.
On Win7, I assume that you looked at both the setupapi.app.log and the setupapi.dev.log (and not setupapi.log). I also assume that you enabled full verbose setupapi logging prior to running the setup, as the default logging often does not provide much information. For info see here <http://msdn.microsoft.com/en-us/library/windows/hardware/ff550808%28v=vs.85%29.aspx> . I would use the Wix DifxAppExtension, and avoid using a CA to call InstallHInfSection. In a Component element, which includes the File Element for the INF file, add the following (and adjust the parameters to your needs): <difx:Driver AddRemovePrograms="no" PlugAndPlayPrompt="no" /> -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Strange-behavior-of-SetupAPI-function-InstallHInfSection-tp7598825p7598828.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. vanity: www.gigenet.com _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
