I Should Know Better, and RTFM More Carefullyįlying through the release notes will occasionally - as was the case for me and Build 20231– cause a person (me, in this case) to fall victim to a known and documented gotcha. I guess that means I need a second helping of crow for not realizing the false alarm had an equally false cause. That small oversight corrected, I determined that as the Release Notes say “Office should still be there and working fine.” Indeed, once I actually had the software installed, that’s just how things turned out. Interestingly, it turns out that the default UWP app Microsoft Office Click-to-Run is enough to trigger the false alarm.Īfter a long series of troubleshooting steps, I got Office 365 installed on that PC (a Lenovo X380 Yoga laptop) when it had actually never been fully instantiated there. Go figure!īut upon further investigation, I realized that I didn’t actually have MS Office installed on one of the two test machines that threw the Compatibility Assistant error. Though MS does say that this is a false alarm, things get more interesting when the Office Click-to-Run app is its cause.
