tj leigh found the root cause. Let me explain it.
1. Burn adds a RunOnce entry automatically every time it starts, and it removes it when it ends if no reboot has been requested by any of the packages. 2. The driver installation either uses an InstallFromHinfSection or calls DIF_INSTALLDEVICE, either directly or indirectly. 3. Windows processes all of the RunOnce entries before Burn has exited/removed its RunOnce entry. Tobias, please add this new information to the bug you opened (if you haven't already). The fix (in my mind) will require that the burn engine determines that this situation has happened and to mitigate it by recreating the RunOnce entry and exiting silently. I don’t see any workarounds. Blair From: Tobias Erichsen Sent: Wednesday, November 06, 2013 5:33 AM To: General discussion for Windows Installer XML toolset. Hi, thanks for that input as well. My driver's inf-file does not contain any RunOnce entries. So I assume that burn is doing that somewhere... Could Rob or Bob possibly chime in on this? I'd gladly do some more digging/debugging, but as I still do not fully understand the overall architecture on how burn & MSIs interact during the installation-process, I'd be glad to get some pointers on where to focus my search... Best regards, Tobias ________________________________________ Von: tj leigh [tjle...@outlook.com] Gesendet: Mittwoch, 6. November 2013 12:25 Bis: wix-users@lists.sourceforge.net Betreff: Re: [WiX-users] Burn installation with Aladdin eToken driver (msi) opens second burn's window. http://blogs.msdn.com/b/junfeng/archive/2006/09/19/761765.aspx says this: Be careful about RunOnce registry key: It may run before system restart. According to KB 281829, RunOnce registry key will run in the following cases: 1. At the end of installation through InstallFromHinfSection even in the cases where you must restart the computer. 2. After the default processing of DIF_INSTALLDEVICE even if you must restart the computer (with the exception of server-side processing). 3. After the system has been restarted. This means, RunOnce registry key entries may be executed immediately after a device driver installation, which may happen at any given time. --- Hi Blair, thanks for the input. I let the whole thing run while also using "Process Monitor" to log all processes being created and you were right: The last rtpMIDISetup.exe process (showing the erroneous dialog) is instantiated from runonce.exe, which itself is instantiated from MsiExec.exe... The whole chain goes like this: services.exe msiexec.exe /V msiexec.exe -Embedding F815A8F1DDE9C0C1DB2AB19224A4B71C M Global\MSI0000 runonce.exe -r rtpMIDISetup.exe /burn.log.append "C:\DOKUME~1\ADMINI~1\LOKALE~1\Temp\rtpMIDI_20131106100345.log" /burn.runonce I still don't know what actually causes this - it is definately not my WIX-code or CA installing the driver (at least not consciously). What do you mean by "reloading some profile"? Best regards, Tobias ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
