Using Classic Outlook on Windows for personal email, calendar, and contact management
Hey All,
To make matters just so much worse, here's a further update.
I ended up rebuilding my customers terminal server over a weekend and a week, this cost me a great deal of time, effort and money (in lost time + running two servers in coexistance while migrating batches of users)
This new server is running Windows 10 1903 Multi User Edition, it is a Windows Virtual Desktop host.
I thought I was out of the woods with this issue, a week and a half in and no reports of Outlook sticking to the foreground.
Great success... until....
The user has reported the issue persisting on this new server... less than a week and a half old, with minimal software installed.
I lost my s*** at Microsoft and got a new engineer assigned to my ticket, as my previous engineer was total garbage and we're going through the trouble shooting and log gathering process once more.
I am hopeful this time around, the engineer seems a lot better, and their recommended solution of rebuilding the affected device has yielded no results.
Here's some weird stuff I've noticed about this issue, which I'd like you to test:
If within Outlook I open up SOME application Windows, the issue will subside. I can replicate this with:
- Opening the options menu and immediately closing, issue resolves itself immediately.
- Opening the "save attachment menu" and immediately closing, the issue will resolve itself immediately.
If you can test, please let me know if you have the same behavior with the above, I suspect you will.
This really must be a programming error somewhere within Outlook, my theory is that when we open one of these two menu's it for some reason "reinitializes" or "recalculates" the Outlook window Focus, forcing it to unlock itself from the foreground.
What's weird is it's not all tpyes of windows, for example I tried with the address book and found that it did not resolve the issue.
Anyway, I will continue to work with Microsoft on this issue and I'll report back any findings we may have to hopefully save someone from being in this awful, awful position in the future.
Best of luck.
We have found that your work around does in fact fix the issue temporarily. The only thing is if you go back into the menu after it fixes the issue it then breaks it again. I've had about 4 users confirm that for me so far. We continue to engage Microsoft for this issue.