Hi. I have been having ongoing issues with Outlook for over 6 months, in which Outlook will become locked to the foreground. Outlook has no add-ins enabled, and has been repaired, reinstalled, updated and downgraded many times. The affected OS is a Windows Server 2016, functioning as a terminal server. The affected users have two screens, and occasionally when a window is dragged to the same screen area as Outlook, Outlook will remain the foreground focus and the application being dragged will be "under/behind" the Outlook window. This can also happen when the user is using a single screen. This is not application specific, and even happens with the Outlook "New Email" window if popped-out from the Outlook client. We have gathered numerous ETL logs and event logs and have come up with absolutely nothing. Previously, the only known way to resolve the matter was to close and re-open Outlook. However, strangely enough I have found that opening the options menu and closing it (Not changing any options, hitting either cancel or OK) will also resolve the issue. From the options menu, we have tried with the following settings both enabled and disabled, with no luck on any setting: Hardware Graphics Acceleration Live Preview Use Animations when expanding conversations and groups We have tested the Email auto-configuration XML, and the MS partner support rep I was working with has confirmed that it is all okay. I also provided him with screenshots of the connection status when Outlook is stuck, and we confirmed that all was OK there. Another potential solution that was tried was unlocking and locking the taskbar. Both when the issue occurs and pro-actively. We also recreated one of the users Outlook profile. This did not resolve the issue. The issue is confirmed to not follow the user to other devices. I'm sure there are more solutions that we have tried, that I have simply forgotten about during the length of this ticket. At long last, the technician had advised me that I need to rebuild the affected server. This is not an option for us, as the server is used literally every single day inclusive of weekends, and the customer is entirely dependent on the running of this server. I have now been advised by the technician to log a forum post here. Please let me know if any other information should be required, but I feel this is quite extensive. I do have recordings of the issue, and all ETL + Event logs.

Hey mate, definitely still happens in cached mode. On my WS2016 RDS server we were caching straight to the disk, issue still occured. In my new W10 Multi-User WVD environment we're caching with FSLogix and getting the same behaviour on both WVD hosts in the hostpool.

The problem only happens to us when we apply Office updates from last year around September. We removed them and it's OK now. Can'tr tell which one it is though. Everyone, we have to make direct noise at MS Support to get traction here. If you haven't already log a ticket with MS and cross-reference my ticket [Ticket #:18415639] and this forum post. At least we can make some ticket noise internally and see if they sort it out.

The problem only happens to us when we apply Office updates from last year around September. We removed them and it's OK now. Can'tr tell which one it is though. Everyone, we have to make direct noise at MS Support to get traction here. If you haven't already log a ticket with MS and cross-reference my ticket [Ticket #:18415639] and this forum post. At least we can make some ticket noise internally and see if they sort it out. Cross reference my ticket too: #15038381 Heh - your ticket is 18xxxxx mine is 15xxxxx so guessing mines ancient. Almost 2 years ive had this ticket open.

Looks like its a Windows component then than just doesn't like multi-user environments. It's a big deal for MS then if it's even affecting WVD with FSLogix!

Hello, Someone else has the issue without Chrome installed, so its not that. What version of Adobe Reader were you on, and what version did you move to? We are on 17.011.30150 Planned update, October 15, 2019 Exchange 2016 in Online Mode Thanks

Outlook "Stuck on top/Foreground". Issue is intermittent, and occurs usually after ~1 hour of use. Can be sooner

Anonymous

Hi.

I have been having ongoing issues with Outlook for over 6 months, in which Outlook will become locked to the foreground.

Outlook has no add-ins enabled, and has been repaired, reinstalled, updated and downgraded many times.

The affected OS is a Windows Server 2016, functioning as a terminal server.

The affected users have two screens, and occasionally when a window is dragged to the same screen area as Outlook, Outlook will remain the foreground focus and the application being dragged will be "under/behind" the Outlook window.

This can also happen when the user is using a single screen.

This is not application specific, and even happens with the Outlook "New Email" window if popped-out from the Outlook client.

We have gathered numerous ETL logs and event logs and have come up with absolutely nothing.

Previously, the only known way to resolve the matter was to close and re-open Outlook.

However, strangely enough I have found that opening the options menu and closing it (Not changing any options, hitting either cancel or OK) will also resolve the issue.

From the options menu, we have tried with the following settings both enabled and disabled, with no luck on any setting:

Hardware Graphics Acceleration
Live Preview
Use Animations when expanding conversations and groups

We have tested the Email auto-configuration XML, and the MS partner support rep I was working with has confirmed that it is all okay.

I also provided him with screenshots of the connection status when Outlook is stuck, and we confirmed that all was OK there.

Another potential solution that was tried was unlocking and locking the taskbar. Both when the issue occurs and pro-actively.

We also recreated one of the users Outlook profile. This did not resolve the issue.

The issue is confirmed to not follow the user to other devices.

I'm sure there are more solutions that we have tried, that I have simply forgotten about during the length of this ticket.

At long last, the technician had advised me that I need to rebuild the affected server. This is not an option for us, as the server is used literally every single day inclusive of weekends, and the customer is entirely dependent on the running of this server.

I have now been advised by the technician to log a forum post here.

Please let me know if any other information should be required, but I feel this is quite extensive.

I do have recordings of the issue, and all ETL + Event logs.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

211 answers

Anonymous

2020-02-28T09:10:40+00:00

Hey mate, definitely still happens in cached mode.

On my WS2016 RDS server we were caching straight to the disk, issue still occured.

In my new W10 Multi-User WVD environment we're caching with FSLogix and getting the same behaviour on both WVD hosts in the hostpool.
Was this answer helpful?

0 comments No comments
Anonymous

2020-02-28T09:11:47+00:00

The problem only happens to us when we apply Office updates from last year around September. We removed them and it's OK now. Can'tr tell which one it is though.

Everyone, we have to make direct noise at MS Support to get traction here. If you haven't already log a ticket with MS and cross-reference my ticket [Ticket #:18415639] and this forum post. At least we can make some ticket noise internally and see if they sort it out.
Was this answer helpful?

0 comments No comments
Anonymous

2020-02-28T09:15:52+00:00

The problem only happens to us when we apply Office updates from last year around September. We removed them and it's OK now. Can'tr tell which one it is though.

Everyone, we have to make direct noise at MS Support to get traction here. If you haven't already log a ticket with MS and cross-reference my ticket [Ticket #:18415639] and this forum post. At least we can make some ticket noise internally and see if they sort it out.

Cross reference my ticket too:

#15038381

Heh - your ticket is 18xxxxx mine is 15xxxxx so guessing mines ancient.

Almost 2 years ive had this ticket open.
Was this answer helpful?

0 comments No comments
Anonymous

2020-02-28T09:18:23+00:00

Looks like its a Windows component then than just doesn't like multi-user environments. It's a big deal for MS then if it's even affecting WVD with FSLogix!
Was this answer helpful?

0 comments No comments
Anonymous

2020-02-28T10:52:37+00:00

Hello,

Someone else has the issue without Chrome installed, so its not that.

What version of Adobe Reader were you on, and what version did you move to?

We are on 17.011.30150 Planned update, October 15, 2019

Exchange 2016 in Online Mode

Thanks
Was this answer helpful?

0 comments No comments