I think you are going to find that some file, probably a dll called
comctl32.dll ('common controls'), is damaged, or perhaps some lesser app you
installed has put one. There is a system file repair utility run with the
command 'sfc /scannow' that will repair comctl32.
Another possibility, of course is some conflict between a hardware drive
and a recent update. Much like early XP, nothing is impossible, but my
feeling is that there would be that a lot more reports of this evident here.
Chasing down a common control error is technical, and involves finding the
MUI file at fault. (conctl32.dll.mui) with tools from SystemInternals.com
--
Was this helpful? Then click the Ratings button. Voting helps the web
interface.
http://www.microsoft.com/wn3/locales....htm#RateAPost
Mark L. Ferguson
..
"Bill Martin" <> wrote in message
news:...
> On Sun, 10 Feb 2008 16:06:59 -0600, "Mark L. Ferguson"
> <> wrote:
>
>>Have you tried putting the focus in the window, and pressing Alt-F4?
> --------------
>
> Next time it happens I'll try that -- if I remember it. I've never
> heard of that technique.
>
> I can't really say that's an obvious way to get rid of a message
> window. If that's what Microsoft intends, they sure as heck should
> put that in the window as an additional message. They put all that
> energy into eye candy to slow down Vista, but overlook something as
> basic as closing a message window.
>
> Thanks.
>
> Bill