Installer never quits (WM_QUIT isn't delivered) when run as service on Vista #4114

Closed
wixbot opened this Issue Sep 23, 2013 · 7 comments

Comments

Projects
None yet
2 participants
@wixbot
Collaborator

wixbot commented Sep 23, 2013

When Burn is finished, it sends a WM_QUIT message. When run as a service on Windows Vista, this message never gets delivered and the installer never quits. WixStdBA needs to be updated to avoid using window messages.

Originally opened by bcran

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Sep 26, 2013

Collaborator

Originally changed by robmen
Status changed from Open to Untriaged

Collaborator

wixbot commented Sep 26, 2013

Originally changed by robmen
Status changed from Open to Untriaged

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Sep 26, 2013

Collaborator

If we can get a fix before WiX beta, we'll consider it for v3.8. Ideally, something that didn't use that extra variable.

Originally posted by barnson

Collaborator

wixbot commented Sep 26, 2013

If we can get a fix before WiX beta, we'll consider it for v3.8. Ideally, something that didn't use that extra variable.

Originally posted by barnson

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Oct 24, 2013

Collaborator

Originally changed by barnson
Release changed from v3.8 to v3.x

Collaborator

wixbot commented Oct 24, 2013

Originally changed by barnson
Release changed from v3.8 to v3.x

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Jan 23, 2014

Collaborator

The problem is caused somehow by loading the theme - disabling theme loading causes PostQuitMessage to work.

Originally posted by bcran

Collaborator

wixbot commented Jan 23, 2014

The problem is caused somehow by loading the theme - disabling theme loading causes PostQuitMessage to work.

Originally posted by bcran

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Oct 2, 2014

Collaborator

Sean Hall discovered:

SHAutoComplete documentation says you need to wait for the control to be destroyed before calling CoUninitialize. Since the window gets the WM_DESTROY message before its child controls, the control is probably never being destroyed. If we wait for the WM_NCDESTROY message instead, the control will be destroyed when we call PostQuitMessage.

Now that we know the fix (which is trivial) what 3.x release should it be fixed in?

Originally posted by robmen
AssignedTo changed from bcran to robmen
Status changed from Open to Untriaged

Collaborator

wixbot commented Oct 2, 2014

Sean Hall discovered:

SHAutoComplete documentation says you need to wait for the control to be destroyed before calling CoUninitialize. Since the window gets the WM_DESTROY message before its child controls, the control is probably never being destroyed. If we wait for the WM_NCDESTROY message instead, the control will be destroyed when we call PostQuitMessage.

Now that we know the fix (which is trivial) what 3.x release should it be fixed in?

Originally posted by robmen
AssignedTo changed from bcran to robmen
Status changed from Open to Untriaged

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Oct 2, 2014

Collaborator

Release changed from v3.x to v3.9

Collaborator

wixbot commented Oct 2, 2014

Release changed from v3.x to v3.9

@wixbot

This comment has been minimized.

Show comment
Hide comment
@wixbot

wixbot Oct 17, 2014

Collaborator

This was fixed in WiX v3.9 RC4.

Originally posted by robmen
Resolution set to fixed
Status changed from Open to Resolved

Collaborator

wixbot commented Oct 17, 2014

This was fixed in WiX v3.9 RC4.

Originally posted by robmen
Resolution set to fixed
Status changed from Open to Resolved

@wixbot wixbot added bug burn labels Dec 20, 2015

@wixbot wixbot added this to the v3.9 milestone Dec 20, 2015

@wixbot wixbot closed this Dec 20, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment