This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
While using the Outlook App on Windows 10, Creating a new event in Calendar, and ONLY when selecting Invite Attendees button, Outlook will open a tab in my browser that does nothing but have the outlook logo.
Using Classic Outlook on Windows for personal email, calendar, and contact management
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.
Same with us. Folks who had this issue previously and the regkey modified are running into this issue again.
changes in the registry is not working anymore.
$RegistryPath = 'HKCU:\Software\Microsoft\Office\16.0\Outlook\Options\Calendar'
$Name = 'ShowLegacyRoomFinder'
$Value = '1'
I am expereincing the same problem working on my home PC running Microsoft Office app to open Outlook. It opens a browser tab in Edge every couple minutes and doesn't matter if I'm using email or calendar functions. Annoying bug.
I've been thinking this throughout the whole thread. In our case, the 3 users that are dealing with this don't even really use Outlook (other than email) and they certainly didn't do any calendar appointments or event creations. They're just not "computer users". They still have all of their reminders written on post-it notes. I have no idea what triggered this in our environment.
I had the same issue. Enabling OWA within office 365 made the problem go away, but that wasn't acceptable. I worked with Microsoft regarding this issue, but they didn't have any idea as to what was causing the problem. I ended up deleting the user's computer profile. After having the user log into the computer again to recreate the profile the problem went away.