How to Fix Runtime Error 339?

Question

Issue: How to Fix Runtime Error 339?

Hello. I need help. I’ve received a runtime error message on multiple occasions. The warning says: “Runtime error 339: Component COMDLg32.ocx is not correctly registered or file is missing”. I’ve tried troubleshooting this issue, but nothing has worked. Could you help me to solve the issue?

Solved Answer

Runtime Error 339 is a common Windows OS error that can be also identified as a missing file error when OCX or DLL file needed to launch the application is missing or not registered on the PC. Such files went missing during the application installation, but the pop-up itself occurs when the system is not found during the launch of a program, so you need to repair the damaged file and fix the root of the issue.

This runtime error might occur for numerous reasons depending on each particular user and system.^[1] However, it is often related to the corrupted or missing .ocx files. They are legitimate files that could be found on the Windows operating system.

On average the system includes around 10,000 OCX files.^[2] These files are crucial program parts that are necessary for performing various functions or maintaining the program’s stability. Seeing runtime error 339 means that some of these files are corrupted, deleted or missing. The particular Runtime Error 339 is the issue associated with program launching problems. In some cases, this error shows up due to the issues with DLL files of the particular program. For instance, these files might be deleted or corrupted. What is more, the error might also be related to various problems with Windows Registry. Fortunately, usually, it’s not hard to fix Runtime Error 339. You need to fix the corrupted file that prevents a program from running properly.

The error message always includes the name of the file that needs to be fixed, for instance:

Runtime error 339: Component COMDLg32.ocx is not correctly registered or file is missing.

Thus, in this case, there’s a problem with the COMDLg32.ocx file. Sometimes this error is caused because of an incorrectly installed program. As we already mentioned, this warning message might show up when running programs. Hence, even if the installation of the application was smooth, this error might still occur. If the program has been installed not correctly, usually it’s enough to uninstall and reinstall it in order to fix runtime error 339. This Runtime Error 339 is indicating that DLL or OCX file is corrupted or missing.

How to fix Runtime Error 339

In order to get rid of Runtime Error 339, you need to fix the particular file that causes this problem. As we already mentioned, this filename is written in the pop-up error window. For solving this issue, you have three options. The first and simplest method requires uninstalling and installing again the program which uses you receive this error. Thus, you should try this method at first. If it doesn't work, then try the second and third methods listed below.

However, if none of these methods have worked or you have noticed that your computer operates oddly, check the system for the virus infection. Scan the computer with a reputable PC repair tool, such as Reimage. Sometimes malware^[3] uses names of the legitimate files or system processes to bypass computer security, so you should ensure that this is not the case before altering any settings.

Reinstall the program

If this error occurs when using a particular program, uninstall and then reinstall it again. One of the reasons why Runtime Error 339 occurs is an incorrect installation of the software.

Reregister the corrupted file

The error message you received includes the name of the corrupted file. If you received a message saying “Runtime error 339: Component COMDLg32.ocx is not correctly registered or file is missing”, you need reregister COMDLg32.ocx files. If you have issues with another .ocx file, instead of “COMDLg32.ocx” use your file name.

1. Go to the Command Prompt.
2. Select Run as administrator and type this command:

   regsvr32 comdlg32.ocx

3. Then, you are supposed to receive a message saying that you managed to reregister the corrupted .ocx file successfully. The message should look like “DllRegisterServer in comdlg32.ocx succeeded” or similarly.

Replace the missing or corrupted file

1. Go to Start and launch the Run window.
2. Type regsvr32 -ucomdlg32.ocx and click OK. The file is referenced from the error message, so it should change in a particular incident.
3. Search for that file in the general search on the system.
4. Click on the file and select Delete after right-click.
5. Now you need to download the new one from a credible source. Finding the file via Run window allows you to locate the particular corrupted file.

Execute commands in Command Prompt

If none of the above methods haven’t worked for you, try this method to fix Runtime Error 339:

1. Run the Command Prompt.
2. Choose Run as administrator.
3. Execute all of the following commands in the Command Prompt. Press enter after each typed command:
   regsvr32 \\Windows\\System32\\ comdlg32.ocx /u

   regsvr32 \\Windows\\System32\\ comdlg32.ocx

   NOTE. If you receive an error about another .ocx file, please replace “comdlg32.ocx” with your file name.

4. Exit Command Prompt. Now you should not receive error 339. Administrative rights needed to launch Command Prompt because this way you can make changes.

Repair your Errors automatically

ugetfix.com team is trying to do its best to help users find the best solutions for eliminating their errors. If you don't want to struggle with manual repair techniques, please use the automatic software. All recommended products have been tested and approved by our professionals. Tools that you can use to fix your error are listed bellow: