>>>Considerable effort was put into troubleshooting this issue on affected machines, without success.
>>>
>>>The final resolution was to replace Excel automation with the use of Greg Green's VFPx class: https://github.com/ggreen86/XLXS-Workbook-Class .
>>>
>>>My gut feel is the future will see increasing restrictions/lockdowns on inter-process communications, function calls, automation etc both by Windows and by security/AV programs. My recommendation would be to eliminate Excel automation where feasible and replace it with this class.
>>
>>For intermediate tasks there is the flip side of having a non-internet visible/connected VM running XP and COM-working older versions.
>>Middle finger to MS for a couple of years, until versionitis makes such an aproach more work than other ways circumventing new MS efforts.
>>I do remember periods where new versions enabled developers...
>
>...to do things automatically, pretty much as if they were done by a computer? Hell, no, it's not that kind of computer, it's not confined to some ADP (automatic data processing) lab where they wear white lab coats and carry bundles of zebra paper around. It's the click. If it's not clickable it's doomed. Forget code which accepts no clicks, it belongs into the kernel of them Windowses. Everything else must be visible, the more visible the better, the more interaction with the user the better, it needs to engage the user, amuse him, keep him occupied. You want to do things behind the scenes? Go work for Microsoft then, do telemetry and Windows updates.

I remember working with MS Multiplan on 6502 to hack together some "flexible bookkeeping" SW over a long weekend, having no knowledge of bookkeeping, its rules and abuses or controlling with and without hidden cash depots.
Definately rodent-free environment ;-)