ActiveX component can't create object with reg-free com until after restart

1
votes

When I install a new version of the application that is using an ActiveX library through Reg-free com (using a manifest file) I get "ActiveX component can't create object" error. However, when I restart the machine and run the application again, the error is gone. No other applications are using the com dll.

Any idea what is causing this? Is there another way to successfully distribute this application without having to restart the machine?

1
comvb6activexregfreecom
Those symptoms make no sense, but we don't have enough information. Check to see what has ended up in the VirtualStore parts of both the filesystem and the registry following reboot. I suspect you are making quite a mess on "victim" systems. – Bob77
When I've written isolated COM solutions, all that is necessary is to do an xcopy of my directory tree to some directory on the target machine and it works. – Joseph Willcoxson

1 Answers

0
votes

This be a case where the EXE timestamp needs to be updated so that Windows recognizes the manifest. The manifest might be copied in after the EXE by the installer.

Perhaps on reboot, the 'cache' of the manifest gets invalidated which is why it then works correctly thence.

See additional: here and here.