RunOnce is triggered during installation on Windows7 x86 systems.

[wixbot]

Hi folks,

we had a serious problem with our x86 installer on Windows 7 systems (x64 was ok).
We were facing the problem, that a 2nd installer dialog appeared during installation.
This was caused by the following code seqment in file _src/burn/engine/registration.cpp_:

---

LPCWSTR sczResumeKey = REGISTRY_RUN_ONCE_KEY;

OS_VERSION osv = OS_VERSION_UNKNOWN;

DWORD dwServicePack = 0;


// On Windows XP and Server 2003, write the resume information to the Run key

// instead of RunOnce. That avoids the problem that driver installation might

// trigger RunOnce commands to be executed before the reboot.

OsGetVersion(&osv, &dwServicePack);

if (osv < OS_VERSION_VISTA)

{

      sczResumeKey = REGISTRY_RUN_KEY;

}

---

To get rid of this problem, we deleted the code above, and substituded it by the line shown below:

---

LPCWSTR sczResumeKey = REGISTRY_RUN_KEY;

---

Could you please verify this issue, and implement it in the next Release if it's ok!?

Many thanks and best regards,

Marco

Originally opened by marco

[wixbot]

We haven't seen this behavior past Windows XP. Are you installing a driver? Please gather all the logs that come during a run where you get the second window.

Release changed from v3.9 to v3.x

[wixbot]

Yes, there's a filter driver included in the bundle. And the described behaviour (2nd window) is comming from this filter driver! How can I share my logfiles??

Originally posted by marco

[wixbot]

Post them to sharing sites like pastebin, SkyDrive, or Google Drive and paste the links as a comment here.

[wixbot]

I've put all logs in the linked zip file. For the filter driver we use Setupapi. Therefore also a log file is included.

https://drive.google.com/drive/folders/0B36Ns5Ap9mBkT05SSEprQWhoaWs

Originally posted by marco

[wixbot]

Nobody's been able to access your logs on Google Drive. Can you try again and make sure the link is public?

[wixbot]

Now it's public!!

https://drive.google.com/open?id=0B36Ns5Ap9mBkQmt5MG82cHFWTEk

Originally posted by marco

[wixbot]

AssignedTo set to bobarnson

[wixbot]

I looked at the logs but there isn't enough data to figure out what's going on. Is there another bundle log (e.g., DEWETRON_TRION_Applications_*.log) around the same time (if another bundle kicked off)? Can you share your bundle? If not, can you capture a Process Monitor log filtered to the name of the bundle (DEWETRON-TRION-Applications-x86.exe)?

Originally posted by barnson

[wixbot]

Please let us know if you're able to help with additional data.

[wixbot]

Please let us know if you're able to help with additional data.

Resolution set to moredata
Status changed from Untriaged to Resolved

[wixbot]

AssignedTo changed from bobarnson to