Forum Discussion
Double-clicking Outlook system tray icons no longer restores the app since Moment 2 update
frederick_hope Thank you - yep, confirmed, I don't have the option, could be IT haven't rolled out the latest Office update to us yet, or have disabled that functionality with a policy.
On a related note, have you seen Snipping Tool display similar behavior? When I take a rectangular snip, it always used to put the resultant snip as the active window, ready for editing/saving etc. Now however, the icon on the taskbar just flashes, (just like Outlook does when you double-click the system tray) and you have to then click on the taskbar icon to see your resultant snip. More clicks....
Wasn't sure if the two are linked, but reading the reviews here, it seems the latest update to the Snipping Tool broke things, so may just be a coincidence! (https://apps.microsoft.com/store/detail/snipping-tool/9MZ95KL8MR0L?hl=en-us&gl=us)
mattmcspirit no mate hadn't noticed that although I don't use the snipping tool. I always just used Print Screen or Alt + Print Screen then manual crop in mspaint. I just gave the tool a try though and I am experiencing the same behaviour you describe. After selecting the area, it does not come to the forefront.
Speaking of mspaint, it had a particularly egregious bug after this update where when closing an unsaved document, the dialog box that prompts you to save / discard the document would simply not appear, but the main application window was "stuck" as if it was waiting for you to action said prompt. I thought initially that the dialog was hiding on another monitor somewhere or off screen but apparently not as I saw online that other people had reported the issue too. I normally put up with Windows updates but I think I'm starting to get into my "grumpy old man" stage of life.
- mattmcspiritMar 29, 2023Copper ContributorI'm already at that stage of life 🙂 I just downloaded Sniptool from the store, and that seems to work well, and very configurable. And for editing, Paint.net for the win! 🙂
Hopefully a future build fixes this stuff!