Article ID: 173500 - Last Review: May 9, 2003 - Revision: 1.0

Error Message: MSN Failed to Load Folcom.dll

This article was previously published under Q173500

SYMPTOMS

When you connect to MSN, The Microsoft Network, you may receive the following error message:
MSN failed to load Folcom.dll.
If you click Setup or Help, you may receive the following error message:
Msn.ini file badly formed. Please contact Product Support.

CAUSE

This issue can occur if the Wsock32.dll file is damaged or missing.

RESOLUTION

To resolve this issue, replace the Wsock32.dll file. To do so, use the following steps:

  1. Click Start, click Shut Down, click "Restart the computer in MS-DOS mode," and then click Yes.
  2. At the MS-DOS prompt, type the following command, and then press ENTER
    <drive>:
    where <drive> is the letter of the drive on which Windows is installed. For example, if Windows is installed on drive C, type the following:
    c:
  3. Type the following commands, pressing ENTER after each command:
    cd\windows\system

    ren wsock32.dll wsock32.old

    exit
  4. Extract a new copy of the Wsock32.dll file to the Windows\System folder. You can extract the Wsock32.dll file from the following locations:
    • The Win95_11.cab cabinet file on the Windows 95 CD-ROM
    • The Win95_12.cab cabinet file on the original Windows 95 DMF disks
    • The Win95_19.cab cabinet file on the original Windows 95 non-DMF disks
    • The Win95_18.cab cabinet file on the Windows 95 OEM Service Release 2 CD-ROM
    If you are using Microsoft Windows 98, you can extract the Wsock32.dll file from the following location:
    • The Precopy1.cab cabinet file on the Windows 98 CD-ROM.
    For information about how to use the Extract tool, please see the following article in the Microsoft Knowledge Base:
    129605  (http://support.microsoft.com/kb/129605/EN-US/ ) How to Extract Original Compressed Windows Files
  5. Restart your computer normally.

MORE INFORMATION

This issue may also occur if you run RegClean, version 3.0 or 4.0, on your computer, and then attempt to run Visual Basic for Applications code that uses Automation to control another program. The issue occurs because RegClean 3.0 or 4.0 removes the keys that are required to use Automation.

Keywords: 
kbenv kberrmsg kbfile kbprb KB173500

APPLIES TO

Note: This article is from Microsoft Knowledage Base


How we have helped PC users like you

In the News: Read More In ...

Related problems posted by other users

more...