S
Sonrisante
Recently (about 4 weeks or so now) I'm having an issue that I haven't had in
the past. One of my applications, not always the same one, will have its
"Keep on top" flag set, and any other windows, whether already opened or
newly opened applications, will be shown behind this top-most application.
The applications are not launching each other, so it's not like one app is
launching a child app, so the child app is always on top. This is exhibiting
that type of behavior, but the "chosen" app will always be on top (in the
z-order) of all other apps.
I don't know how to reproduce it, but it happens almost every day after a
few hours of having my PC on.
Sometimes the top-most window is outlook, sometimes excel, but sometimes
it's not even office, but SQL Server Management Console, sometimes IE.
It's very annoying. If I close down the top-most app and then relaunch it,
it's usually OK for a bit but then it happens again.
Is anyone else seeing issues like this? I keep hoping it's due to a
microsoft update and it will get corrected by a subsequent update, but so far
that's not the case.
the past. One of my applications, not always the same one, will have its
"Keep on top" flag set, and any other windows, whether already opened or
newly opened applications, will be shown behind this top-most application.
The applications are not launching each other, so it's not like one app is
launching a child app, so the child app is always on top. This is exhibiting
that type of behavior, but the "chosen" app will always be on top (in the
z-order) of all other apps.
I don't know how to reproduce it, but it happens almost every day after a
few hours of having my PC on.
Sometimes the top-most window is outlook, sometimes excel, but sometimes
it's not even office, but SQL Server Management Console, sometimes IE.
It's very annoying. If I close down the top-most app and then relaunch it,
it's usually OK for a bit but then it happens again.
Is anyone else seeing issues like this? I keep hoping it's due to a
microsoft update and it will get corrected by a subsequent update, but so far
that's not the case.