

- #NEW INSTALL OF OUTLOOK 2016 WILL NOT OPEN UPGRADE#
- #NEW INSTALL OF OUTLOOK 2016 WILL NOT OPEN WINDOWS 10#
- #NEW INSTALL OF OUTLOOK 2016 WILL NOT OPEN SOFTWARE#
#NEW INSTALL OF OUTLOOK 2016 WILL NOT OPEN WINDOWS 10#
Other users also report the same issue even after configuring a new computer with Windows 10 and Office 2016 specifications.

The above incident presented a general outline of the OST file-related issue which seems to have affected a large number of users after they’d upgraded to Microsoft Office 2016 on Office 365.

Next, the user uninstalled and reinstalled the entire instance of Office 365, but the OST file still couldn’t be opened even after reinstalling the application. ThisĪctivity should have established the connection between the server and the email client, but the matter got worsened, with Outlook displaying the following error message: Outlook profile and created a new one to troubleshoot the problem. Immediately after the upgrade, the user was unable to sync Outlook with Exchange ActiveSync server, and the result was that Outlook failed to perform its intended functions such as to send or receive emails, calendars or updates. Instance of this error faced by an Office user.

I know I am not alone, especially in this quickly changing cloud centric world we live in.Upgrades for Outlook to fix the bugs and enhance/add the features and functions.However, the upgraded versions should be installed properly, else these may result in errors, as in this case of an error spelled out as “OST File won’t open in Outlook 2016”. I hope this gets the appropriate attention.
#NEW INSTALL OF OUTLOOK 2016 WILL NOT OPEN UPGRADE#
Is it an update? Is it a protocol? Should we upgrade our infrastructure to something more modern? I don’t know… Mainly because Microsoft will not give us any kind of clarification as to what is causing this problem, beyond the general issue stated in the Microsoft 365 Admin Center.Īgain, thank you so much for posting here. It would be so nice to know a little more detail as to what is causing problems like this. Not to give you the laundry list of problems, but communication is a really big problem for Microsoft when we are banging our heads on our desks trying to troubleshoot issues like this. There have been a few issues recently caused by Microsoft “updates” that make it hard for people who don’t have access to M365.įor instance, just a few weeks ago, and also something that just recently read its head again, a search issue in Microsoft outlook was seemingly caused by something Microsoft implemented that made it impossible for people to connect using “old authentication“, but people who did not have access to Microsoft 365 would have never received information from Microsoft regarding this issue. I would sincerely appreciate for you to professionally suggest to your powers at be that they come up with a more public method of communicating to professionals like us who might not have access to the M365 Admin Center. I can’t thank you enough for posting here, in public.
