![]() ![]() and found that deleting the Experiment and ExperimentConfigs keys under HKCU\Software\Microsoft\Office\16.0\Common would immediately fix a "broken" profile on a machine that was rolled back to the March build of 2302. With this info, I started trying to drill down into the user-level side of things. (And new profiles created after the rollback would be fine, obviously). Deleting the profile and recreating it would make it work immediately, though. Similarly, rolling back from the April build of Verson 2302 to the March build would usually not fix the issue right away for an existing "broken" profile, but eventually attachments WOULD start working for that user. Once we discovered this, we were able reproduce the issue on demand on brand new bare-bones machines in order to definitively rule out any third party antivirus or other applications. However, we discovered that a brand new user profile on a machine that has the April build of Version 2302 would ALWAYS have the issue immediately. This made it tricky to troubleshoot at first. Sometimes it is immediate, but often it would take several minutes or hours (and an Outlook reload). I say "developed" because our experience has been, with an existing user/mail profile, it doesn't always start right after installing the update. We rolled out 0.20394 (April build of Version 2302) to a handful of machines previously on the March build of 2302 and they all developed this issue. None of these resolved the issue and Outlook crashes even when running in safe mode. Ensured office was up to date using the Click2Run.exe /update user command We have a few users that having Outlook crashing when either responding to e-mails that include attachments (tested with docx, xlsx, zip, pdf) or when composing a new message and either using the built-in Attach > Attach Files > Select file or dragging/dropping the file. Wondering if anyone else is seeing similar experiences with this. EDIT: I have been able to at least roll back office using the ODT method, it is documented here - Ĭonfirmed that rolling back to 2208 (15601.20538) and 2302 (16130.20306) resolves this issue.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |