Tom, Tech Support wrote: ↑Mon Sep 07, 2020 11:58 amSorry, I did mean to post an update here some time ago but forgot. We got things working again with this customer, but quite honestly, it was such a convoluted and oddball case that we couldn't pin-point the exact cause or what fixed it specifically. If I recall correctly, I think a major contributor to the issue was that the customer's macro folders were pointing to a shared/mapped drive on the host machine (they were running iMacros inside of a Windows VM on a Mac). Once we changed the folders to be local on the guest machine, then we had a breakthrough.
OK, good-good, Thanks for sharing this Update @Tom...
I'm not completely-completely "convinced" about the "Correlation" indeed, but OK..., glad you managed to get it to work for this User...
>>>
I've "complained" btw in my "crude Style that @OP didn't like too much" on the super-irritating MS Site where you can't concentrate on the Content on any Page until you've found 3x the Word "Experience" and 1x the Word "Journey", grrr...! , about 'Regsvr32' that they could mention the Name of the "Offending" DLL in the Error Msg, + whether using the _x32 or _x64 Bit Version, + mentioning in plain Text what "return code 0x3" meant, + that dropping the _x64 Version in some "System32" Folder and its _x32 Version in some "...W64" Folder felt completely confusing and anti-logical to me...!