Why does Outlook launch IE in the background?

Anonymous
2017-05-09T14:01:44+00:00

Hello,

We are using Office 365 ProPlus on Windows 10 Pro.  Opening Outlook (16.0.7927.1020) will launch two background processes of IE (iexplore.exe).  Why does Outlook open IE?  

This behavior does not happen in earlier versions of Office 365 ProPlus, such as 16.0.6001.1041.  It appears that an update for Office 365 ProPlus is causing Outlook to open IE in the background.

Thank you,

Evan

Outlook | Windows | Classic Outlook for Windows | For home

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 No comments

68 answers

Sort by: Most helpful
  1. Anonymous
    2018-10-17T18:51:17+00:00

    The UI here shouldn't be dependent on the version of Windows. Can you post a screenshot? (Be sure to blur out any personal info)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-10-17T17:56:52+00:00

    It's not there in Windows 10.  There is no "Office Updates" button, only "Insider", "About", and What's new".

    On Windows 7, I do have an "Office Updates" button in addition to those three.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-10-17T17:44:28+00:00

    How do I check for and get updates.  On Windows 10, I don't have "check for updates" or "enable updates" in any of my Office 365 products.

    In any Office app, File/Office Account, then see Office Updates/Update Options in the right hand column.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-10-17T17:34:10+00:00

    How do I check for and get updates.  On Windows 10, I don't have "check for updates" or "enable updates" in any of my Office 365 products.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-10-17T15:55:18+00:00

    We just checked in a fix to build 16.0.11005.37379, so any Insider Fast build higher than that should have the fix.

    I just checked on the integration status. Integration happened in build 16.0.11012.10000. So that's the build to really watch for.

    Was this answer helpful?

    0 comments No comments