How to Fix Runtime Error 339: MSCOMM32.ocx

Written by james stone
  • Share
  • Tweet
  • Share
  • Pin
  • Email
How to Fix Runtime Error 339: MSCOMM32.ocx
(Jupiterimages/ Images)

The run-time error 339: MSCOMM32.OCX appears when the DLL file is either invalid, corrupt, missing or not correctly registered. The following error messages may appear during Windows start-up, shutdown or when running an installed application: "DLL Not Found" or "Bad Image." Solving the problem requires the user to download the MSCOMM32.OCX file from a trusted source and copy that file back in the Windows System 32 folder (the main folder created during the operating systems installation). The user will then have to register the DLL again to correct all Windows errors.

Skill level:


  1. 1

    Download the "MSCOMM32 zip file" (see Resources) and extract by right-clicking on the file and click "Extract All" from the drop-down menu.

  2. 2

    Click "Start" and then type "windows/system32/" in the search box. Double-click the "System 32" folder to open the folders location.

  3. 3

    Open the extracted folder and drag and drop the "MSCOMM32.OCX" file over to the System 32 folder. Alternatively right-click the "MSCOMM32.OCX" and click "Copy" and then right-click anywhere in the System 32 folder and select "Paste" to make a copy of the DLL.

  1. 1

    Click "Start" and type "Run" in the search box. Click the "Run" shortcut application. The Run box displays on the screen.

  2. 2

    Type "cmd" to open the Command Prompt window. Type "regsvr32.MSCOMM32.OCX" in the command prompt utility to register the DLL file.

  3. 3

    Type "Exit" in the Command Prompt to close the application. Close the Run box.

Tips and warnings

  • Adding the wrong items to the registry may corrupt the installed version of Windows.

Don't Miss

  • All types
  • Articles
  • Slideshows
  • Videos
  • Most relevant
  • Most popular
  • Most recent

No articles available

No slideshows available

No videos available

By using the site, you consent to the use of cookies. For more information, please see our Cookie policy.