The most effective fix for this error involves manual registration via the Command Prompt. Because modern Windows security is much tighter than it was during the era of ActiveX, the process must be performed with administrative privileges. The first step is ensuring the file is placed in the correct system directory— C:\Windows\System32 for 32-bit systems or C:\Windows\SysWOW64 for 64-bit systems. Once the file is in place, the user must use the regsvr32 command. This utility tells the Windows Registry exactly how to interact with the component, effectively "plugging" the legacy code back into the modern operating system.
The most common "fix" is to re-register the file in the Windows Registry. This tells Windows exactly where the file is and how to use it. fast2001ocx fix