Article ID: 820252 - Last Review: November 16, 2007 - Revision: 6.3

A program window may not be visible if the program hangs in Windows XP or in Windows Server 2003

View products that this article applies to.
System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

On This Page

Expand all | Collapse all

SYMPTOMS

A program window may not be visible if the program stops responding (hangs). A program is considered to be hung if the program does not respond to window messages within several seconds, and a status of "Not Responding" appears in Windows Task Manager. In the problem state, the Win32 IsWindowVisible function does not return the WS_VISIBLE flag.

A Microsoft Visual Basic program may report the following error when the program tries to use the SetFocus method on a window:
Run-time error '5': Invalid procedure call or argument.
Back to the top

CAUSE

The Ghost Window feature creates ghost windows on behalf of a program when the program does not respond correctly to window messages within several seconds and is considered to be hung. The original program window's visibility state may not be restored before the program starts processing.
Back to the top

RESOLUTION

Windows Server 2003

Back to the top

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100  (http://support.microsoft.com/kb/889100/ ) How to obtain the latest service pack for Windows Server 2003
Back to the top

Windows XP

Back to the top

Service pack information

To resolve this problem, obtain the latest service pack for Windows XP. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
322389  (http://support.microsoft.com/kb/322389/ ) How to obtain the latest Windows XP service pack
Back to the top

Hotfix information

Prerequisites

To apply this hotfix, you must have Windows XP Service Pack 1 (SP1) installed on the computer.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
   Date         Time   Version        Size       File name
   --------------------------------------------------------
   09-May-2003  09:38  5.1.2600.1220    529,408  User32.dll
   09-May-2003  09:23  5.1.2600.1220  1,677,056  Win32k.sys

Back to the top

WORKAROUND

You can use the Application Compatibility Toolkit to create and install a custom Application Compatibility database to disable the Ghost Window feature for your program. To download the Application Compatibility Toolkit, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/aa286552.aspx (http://msdn2.microsoft.com/en-us/library/aa286552.aspx)
To create a custom Application Compatibility database:
  1. Install and run the Compatibility Administrator tool (add the /x switch to the command line for advanced features).
  2. Right-click Custom Database, and then click New.
  3. Right-click the new database, and then click Rename.
  4. Type noghost as the name of the database.
  5. Right-click New Database, click Create New, and then click Application Fix. Type the name of the program to be fixed.
  6. Type the name of the program manufacturer.
  7. Locate and then click the appropriate program (.exe) file.
  8. Click Next.
  9. In the Compatibility Modes window, click None, and then click Next.
  10. In the Compatibility Fixes list, click NoGhost.
  11. Click either Test Run or Finish. Clicking Test Run starts the program with the Application Compatibility setting. Clicking Finish adds the compatibility fix to your database.
  12. On the File menu, click Save to save the database. Or, copy the database to the C:\Windows\AppPatch folder.
  13. Right-click the database, and then click Install. Or, run the sdbinst c:\windows\apppatch\noghost.sdb -q command to install the database.
Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2. This problem was first corrected in Windows Server 2003 Service Pack 1.
Back to the top

MORE INFORMATION

The following information about the GetMessage function is documented for the Ghost Window feature in Windows XP. For more information, visit the following Microsoft Web site:
GetMessage function (http://msdn2.microsoft.com/en-us/library/ms644936.aspx)

If a top-level window stops responding to messages for more than several seconds, the system considers the window to be hung and replaces it with a ghost window that has the same z-order, location, size, and visual attributes. This allows the user to move it, resize it, or even close the application. However, these are the only actions available because the application is actually hung. When in the debugger mode, the system does not generate a ghost window.
Back to the top
APPLIES TO
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows XP Professional
  • Microsoft Windows XP Home Edition
  • Microsoft Visual Basic 6.0 Learning Edition
  • Microsoft Visual Basic 6.0 Professional Edition
  • Microsoft Visual Basic 6.0 Enterprise Edition
Back to the top
Keywords: 
kbhotfixserver kbqfe kbwinxpsp2fix kbwinxppresp2fix kbfix kbbug KB820252
Back to the top