WM_WININICHANGE Message Causes a Deadlock in Multithreaded Visual Basic 6.0 Applications

This article was previously published under Q325568
This article has been archived. It is offered "as is" and will no longer be updated.
When a multithreaded application (for example, Microsoft Internet Information Server [IIS], Microsoft COM+, or the Visual Basic 6.0 ActiveX EXE server) hosts Visual Basic 6.0 components (such as ActiveX DLLs), the application may experience a deadlock in response to WM_WININICHANGE messages. One common scenario under which this message can be generated is a change in default printer settings.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Visual Studio 6.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   Date         Time    Version    Size     File Name      Platform   ----------------------------------------------------------------   26-Jun-2002  12:48  1.32 MB  Msvbvm60.dll   x86
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Article ID: 325568 - Last Review: 02/27/2014 21:14:02 - Revision: 4.2

Microsoft Visual Basic 6.0 Enterprise Edition, Microsoft Visual Basic 6.0 Professional Edition, Microsoft Visual Basic 6.0 Learning Edition

  • kbnosurvey kbarchive kbbug kbfix kbqfe KB325568