On Thu, Mar 22, 2018 at 10:53 AM, Tracy Pearson tracy@powerchurch.com wrote:
I have some client workstation that refuse to register an ActiveX control I use in my VFP app. Even manually typing the RegSvr32 command. The message that appears states it registered successfully. However, the Registry is never updated.
What ideas can I use to track down this problem?
You could tell us which OS the workstations had, 32-bit or 64-bit.
You could tell us which ActiveX control it is, which version, age, etc.
You could tell us what you know about the workstation, make, model, color, etc. If more than one, anything in common, well, besides color...
You could tell us whether these machines are brand new or are old boxes upgraded from Windows 8.
You could tell us if they were up-to-date on patches.
You mention turning off anti-malware, good, that's often an issue.
Were there any messages in the event log?
I guess these days we can assume much of this stuff, but you know what happens when you ASSuME.
My wild-guess-out-of-the-blue is... something-something-missing-old-VC++-runtime-no-longer-included-in-Windows-10...
https://stackoverflow.com/questions/27290154/regsvr32-query-the-module-xxxxx...
https://www.wintertree-software.com/support/wspell/registrationfailure.html
http://www.itninja.com/question/sapgui-7-10-sp-16-some-dll-ocx-files-fail-to...
Guess #2, if this is only one workstation: Registry is corrupt
Guess #3, some sort of anti-malware protection that prevents Registry entries, like a corporate Policy setting, as many malwares wedge themselves in there good.
Guess #4, the malware's already on the machine, and IT is preventing Registry entries!
That's it, time for more coffee. Happy Friday!