Error 339 "File is not correctly registered" During Install

John Logue Updated by John Logue

If the file failing to self-register is MFC40.DLL:

You may safely ignore the error. Windows includes this file; it does not need to be installed by CFS.

If the file failing to self-register is TX4OLE.OCX:

There is a newer version of the file in the CFS program folder (TT2010, PR2009, etc.) which can be copied to the System32 folder. It will be necessary to uninstall the program before trying to install it again. The program should then install without the error.

If the file failing to self-register is DAO350.DLL:

This may indicate that the module MSVCRT40.DLL in Windows\System32 has been damaged. Do a file search for MSVCRT40. If you find the file, try to rename it to MSVCRT40.XXX. Repeat the search. Expect to find that Windows Protection has placed a new copy of MSVCRT40.DLL into the System32 folder. Install again to see whether this resolved the problem.

Otherwise, you must manually register the file, as follows:

  1. Hold down the Windows key (located in the bottom left corner of the keyboard, between Ctrl and Alt) and tap the 'R' key to open the RUN box.
  2. In the RUN box, type the REGSVR32 command followed by the name of the file which failed to to register (e.g., "REGSVR32  VBPRNDLG.DLL." (Case doesn't matter; upper case is used here for readability.)

Possible results:

  1. If the result is "Windows cannot find...," you probably misspelled REGSVR32.
  2. If the result includes the sentence, "The specified module could not be found," you may have misspelled the name of the file you are trying to register. Either that or the installation may have failed in such a way that the file did not get copied to the system library.
  3. If the result includes error code 0x80020009, the problem could be permission settings in the registry for that particular file. A frequent cause of this problem is that the workstation was previously used by someone else to install software, and some items in the registry are secured so that only when that person is logged on can those entries be modified. A qualified computer technician can use REGEDT32 to correct the security settings on those registry entries.
WARNING: Only a qualified person should do this. An unqualified person could effectively destroy the computer.
  1. If the result includes error code 0X80040200, there may be a permissions problem which can be resolved by running the installer as administrator. Right click on the installer file and left click on "Run as administrator." You will need to know the password for the administrator account.
  2. If, instead of an error code, REGSVR32 terminates in a program crash (Error performing inpage operation), try asking Windows to fix it, as follows:
    1. Find the file in the \Windows\SYSTEM32 (or WINNT\SYSTEM32) folder.
    2. Rename the file. (The preferred rename is to change the extension from OCX to OCY or DLL to DLM.)
    3. This may result in Windows installing a new image of the file into the ...\System32 folder. Use File Find to determine that a new image has been stored there.
    4. Try the REGSVR32 command again to see whether it reports success or failure. If Windows Protection feature does not provide a new copy, then rerun the installation so that our installer can provide a new copy.

How did we do?

Error 12031 when Downloading

Error 339: CSCMD32.OCX etc failed to self-register

Contact