Andy's VMware vSphere tip#9: Use Templates. It surprises us, that many organisations waste time, cranking the handle, installing operating systems manually, by connecting an ISO, and doing next, next, next, reboot finish!
Let vCenter Server do the heavy lifting for you, and spend some development time, creating Golden Masters for Windows 2012 R2, Windows 2016, Ubuntu 16.x etc - keep them patched and updated, create Many OS Customisations, and then when you get a service Request for a VM - sit back and Deploy from Template, which then Auto Renames the VM, Auto Joins domain, and is ready for hand over to the next team!
and you can sit back and take the pressure off.
If you have a SAN with VAAI enabled, deployment of templates will be very quick. (another TIP, do not have templates and VMs on the same datastore, create a datastore for storage of templates and datastore for isos).
It appears that a security update for the CVE-2019-1402 vulnerability in each version of Microsoft Office causes this error. Here is the list of Office security updates that you can uninstall.
Office 2010: Description of the security update for Office 2010: November 12, 2019 (KB4484127)
Office 2013: Description of the security update for Office 2013: November 12, 2019 (KB4484119)
Office 2016: Description of the security update for Office 2016: November 12, 2019 (KB4484113)