We are installing the 3.3.1 update to Pro and are running into this error after install when opening office products. Anyone else running into this? A full Office repair fixes it, but we are installing on 300+ machines!
Any resolution?
We've definitely been seeing odd/buggy Office behavior, with Pro 3.1/3.2/3.3 installed.
Signed in members can post, follow updates, and more. New here? Register a free account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.