PowerToys
PowerToys copied to clipboard
Fancy Zones - Blank Teams and Outlook windows.
Microsoft PowerToys version
0.64.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
Let Microsoft Teams flash up alerts and notifications. Leave Outlook windows open and switch between zones.
✔️ Expected Behavior
I should be able to read the Notifcations from Teams, and Outlook should have fully populated windows.
❌ Actual Behavior
Teasm shows a solid purple notification window. To close it, I hit ALT+TAB and close it in the pop up windows. Outlook does the same thing but has a partial fram.
Other Software
Microsoft Outlook (Microsoft Enterprise Office 16.0.14931.20764) Microsoft Teams 1.5.00.28567
Does it happen only with FancyZones running? /needinfo
Yes....
Confirmed, I am experiencing the same behavior. Extra Outlook windows are popping open on the new virtual desktop every time I switch to a new virtual desktop. Disabling FancyZones fixes it, and re-enabling FancyZones immediately starts it again on the current virtual desktop.
I have been having this same issue with the blank purple Teams notification getting stuck on the screen that @ChadThomsen shared. I've been having this issue for several months across multiple versions of PowerToys, but only recently realized that it is caused by FancyZones. However, unlike the actual behavior listed above, I cannot alt-tab to the window and close it. I must quit the Teams application and re-launch it which is very annoying.
@mltytskr what I meant is if you press and hold "Alt" button down and then click the tab button you will get the window showing all open apps. Do not let go of the "alt" button, and then mouse over the app or window you want to close, and you should see a X the upper right-hand corner of that window. Click the X and it will close that Window, and then you can release the "alt" button. Hope that helps.
Yes, I completely understand what you're saying. However, when I do that, the Microsoft Teams Notification window that is in your screenshot is not listed. The Teams app is, but not the notification window. So the only way I can get rid of it is to quit Teams and relaunch. I could probably tolerate the bug if I could close the notification like your screenshot shows. I will try again the next time it happens; thanks for the suggestion!
I am experiencing the exact same thing. My main repro case is when I switch monitor resolutions, which, for me, happens when I am working from home and then switch to working in the office, or vice-versa, and connect to the same computer. My home and office monitors have different sizes/resolutions. I leave my computer physically at the office with Fancy Zones installed and I have two different layouts for when I am working locally (office) or remotely (home). I then select the layout which matches my local monitor when I connect to the computer at the office.
I am currently running v0.64.0, but this has been happening since I started using Fancy Zones, which was probably 5-6 months ago.
It feels like what happens is that Teams and Outlook have non-visible windows created or cached internally for some reason and, normally, they aren't visible. But when Fancy Zones is activated or has to refresh zones (because of the layout changing), it then finds these windows in the apps it is trying to reposition the windows of, and mistakenly thinks those are visible windows that needs re-sizing or re-positioning. So it does that and, as a side-effect, they get activated or become visible.
I can make this happen at will. If Outlook is open and FancyZones is enabled, switching desktops will cause a blank Outlook appointment details window to open for the last appointment I worked on. If I turn off FZ and close the extraneous window, when I turn FZ on again, it reappears.
https://user-images.githubusercontent.com/27776818/203372089-6aeb679c-3ad6-4cc6-820e-dd7629b04c7f.mp4
/dup of https://github.com/microsoft/PowerToys/issues/19440
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!