I work on a set of applications where there is one main application that is\nthe owner window of the windows for the other applications. Everything works\nfine initially, however, an interesting bug occurs when: I minimize the main\napplication (which minimizes the owned window application also as expected),\nclose the main application (which closes the owned applications as expected),\nand restart the main application (which restarts the owned applications as\nexpected). At this point, the owned window becomes a topmost window and\ndoesn't minimize when the main window is minimizes. This becomes a problem\nbecause any of the popups displayed by the owner window (and all other\napplications that are not topmost) are hidden behind this topmost owned\nwindow. This state persists no matter how many times you open or close the\nmain application, which does close the owned window applications, too. If you\nrestart the machine the state of the windows returns to normal. Here's the\nreal kicker on this unusual behavior: the window states return to normal if\nany other application's window is restored from being minimized while the\nproblem application is not running.\n\nWhat does all this mean? This is most definitely a bug with Windows Vista\nand how it handles owner and owned window relationships. I had found another\nlocation on the MSDN where a Microsoft representative admitted that there was\nan issue with owner and owned windows with Alt-TAB on Vista. The really wierd\npart of all this is that it only occurs with on subsequent instantiations of\nthe application after the application was minimized.\n\nFinally, we're testing our software on 2 machines. A set of panasonic\ntoughbook CF-18's and Dell D620's. The toughbooks only meet minimimum\nrequirements because we put more memory in them. The Dell is "Window Vista\nCapable". The bug does NOT occur on the toughbooks and does occur on the Dell\nD620's. Even worse, the bug didn't occur with one of the three Dell D620's\nand build release 5728.