ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Outlook 2016 profile corruption

    Scheduled Pinned Locked Moved IT Discussion
    2 Posts 2 Posters 610 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      frodooftheshire
      last edited by frodooftheshire

      Hi guys,

      So one of my customers running Outlook 2016 connecting to Office 365 on a Windows 10 laptop has had reoccurring issues with profile corruption - apparently after doing some digging it's related to an autodiscover.xml file being modified with incorrect data from a some source which nobody has been able to identify (at least from what I've read). Ultimately this corrupt xml file leads to Outlook not opening.

      Many seem to be having the issue:

      https://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-mso_win10/outlook-2016-frequent-ost-corruption/591feedb-13c2-4389-826c-d7d28abbfd3a

      https://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-mso_winother/outlook-2016-corrupted-profiles-becoming-way-too/81fa4c8a-5957-4e68-bbcd-65663bb76907

      https://answers.microsoft.com/en-us/msoffice/forum/msoffice_outlook-mso_winother/office-2016-major-issues-with-outlook-not-opening/31178871-75b9-416a-9cb9-e506bc9f8680

      https://www.youtube.com/watch?v=UrZrySKbUTY - lots of people in the comments

      When I first saw the issue I just figured "no big deal, profile corruption occurs from time to time," but when it happened the second and third time I knew something weird was up. What was also weird - the first time I created a new profile it went without issue for a few months, but the second time just a day. Apparently the issue is only effecting laptops and has something to do with going from one network to another.

      From what I've read it isn't effecting Outlook 2013, so I rolled the customer back today. I just wanted to see if anybody has come across the issue, and if you have, how did you fix it?

      1 Reply Last reply Reply Quote 2
      • MattSpellerM
        MattSpeller
        last edited by

        Just finishing our exchange 16 upgrade so.... not yet. But I will keep in touch.

        1 Reply Last reply Reply Quote 0
        • 1 / 1
        • First post
          Last post