myinfo.dll Missing: Trace and Repair Its Legacy IIS Owner

myinfo.dll is a legacy Microsoft Internet Information Server utility component, not a normal Windows runtime file. If Windows says myinfo.dll is missing or cannot be loaded, the correct repair is usually to restore the old IIS or Classic ASP application that requested it, not to copy a replacement DLL into a system folder.

What myinfo.dll is

Historically, myinfo.dll belonged to Microsoft Internet Information Server and exposed the COM/ASP component identified by the ProgID MSWC.MyInfo. A Classic ASP application could create that component from Global.asa:

<OBJECT RUNAT=Server SCOPE=Session ID=MyInfo PROGID="MSWC.MyInfo">
</OBJECT>

The component provided site-information properties, such as administrator or company details, and was historically used alongside myinfo.xml.

This makes myinfo.dll a server-side IIS and Classic ASP dependency. It is not:

• A Visual C++ Redistributable file
• A DirectX component
• A graphics-driver file
• A current Windows 10 or Windows 11 runtime
• A general-purpose DLL that belongs in every System32 folder

Microsoft documented the IIS utility components, including My Info, as optional historical components. They were not installed by default with IIS 6.0, although an upgrade from an earlier IIS installation could retain them. Microsoft referred administrators to the IIS 6.0 Resource Kit for copies of those components.

Quick identification table

Item	What is known
File	myinfo.dll
Internal description	IIS Executable
Historical product	Internet Information Server
Publisher	Microsoft Corporation
Main interface	MSWC.MyInfo
Typical caller	Legacy Classic ASP application
Common configuration location	Global.asa
Modern status	Obsolete and not normally included with current Windows
Architecture	Public metadata identifies a historical 32-bit build, but this is not a current Microsoft-supported download
Correct source	The original IIS application, historical installation media, approved Resource Kit, or the application vendor

The exact folder is installation-specific. Do not assume that every valid copy belongs in System32, SysWOW64, or inetsrv.

First determine which kind of error you have

There are two substantially different situations.

Case 1: IIS reports MSWC.MyInfo

Look for an ASP error mentioning any of the following:

• Global.asa
• ASP 0134
• Invalid MSWC.MyInfo ProgID
• An object tag with MSWC.MyInfo
• A website that fails while loading through IIS

This strongly indicates that a legacy Classic ASP site is trying to create the MyInfo COM component.

The problem may be that the component was never installed, was removed during an IIS upgrade, was incorrectly registered, or is incompatible with the application pool’s architecture.

Case 2: A desktop program or game reports that myinfo.dll is missing

If the message appears before a game or desktop application opens, and the computer does not host an IIS website, the program may have bundled or referenced an old IIS development component. It could also be an incomplete installation, a failed uninstall, or software that should not be requesting the file at all.

Do not assume that enabling IIS will fix this case. The original application’s installer or vendor is the proper owner.

Safe checks before repairing anything

Read the complete error message

Record:

1. The exact wording
2. The name of the program or website
3. Whether the message appears during Windows startup, application launch, or a web request
4. Whether it mentions Global.asa, MSWC.MyInfo, or ASP 0134
5. The path shown in the error, if one is provided

A message saying “the specified module could not be found” does not always mean that myinfo.dll itself is absent. Windows can display that wording when a dependency required by the DLL is missing.

Identify the process that is requesting the file

For a desktop application, check the title bar and the executable name in Task Manager:

1. Press Ctrl + Shift + Esc.
2. Select Details.
3. Find the program that produced the error.
4. Right-click it and choose Open file location.
5. Note the program’s installation folder and publisher.

For IIS, inspect the website’s files and configuration:

1. Open File Explorer.
2. Locate the website’s content folder.
3. Search for Global.asa.
4. Open a copy in Notepad.
5. Search for MSWC.MyInfo or myinfo.dll.

Do not edit the production file yet. The purpose is to identify the dependency.

Check whether antivirus quarantined it

A legitimate historical component can be removed by security software, but a restored file should come only from trusted installation media or a known-good application package.

In Windows Security:

1. Open Start.
2. Type Windows Security and open it.
3. Select Virus & threat protection.
4. Choose Protection history.
5. Review recent quarantined or blocked items.
6. Select an entry only if you can match it to the correct IIS installation or application.
7. Do not restore an unidentified DLL merely because its filename matches.

If security software detected the file as malicious or suspicious, leave it quarantined until its origin and authenticity are established.

Fix 1: Repair the original IIS application or installer

This is the safest fix when a desktop program is the caller.

1. Open Start > Settings > Apps > Installed apps.
2. Find the application associated with the error.
3. Select the three-dot menu beside it.
4. Choose Advanced options, if available.
5. Select Repair.
6. Restart Windows and test the application.

If there is no Repair option:

1. Open Control Panel.
2. Select Programs > Programs and Features.
3. Select the application.
4. Choose Change, Repair, or Modify.
5. Follow the installer prompts.
6. Restart the computer.

Some older programs include a launcher with Verify files, Repair installation, or Reinstall components. Use that facility before searching for an individual DLL.

If repair does not work, uninstall and reinstall the exact application using its original installer or the publisher’s official installer. Back up saved data and configuration files first. The application vendor must provide any compatible copy of a legacy component it bundled.

If no installed application explains the error, inspect Task Manager > Startup apps, scheduled tasks, and the program listed in the error. An obsolete startup entry may be calling a file left behind by an incomplete uninstall.

Fix 2: Install or repair the IIS and Classic ASP features

Use this path when the error comes from a website, Global.asa, or MSWC.MyInfo.

Classic ASP is an optional IIS feature. Enabling it allows IIS to process Classic ASP pages, but it does not automatically guarantee that the historical MyInfo utility component is present.

Enable Classic ASP through Windows Features

1. Press Windows + R.
2. Type optionalfeatures.
3. Press Enter.
4. Expand Internet Information Services.
5. Expand World Wide Web Services.
6. Expand Application Development Features.
7. Select ASP.
8. Also select ISAPI Extensions if it is not already enabled.
9. Select OK.
10. Allow Windows to apply the changes.
11. Restart the computer if prompted.

Microsoft identifies the feature as IIS-ASP. On supported systems, the equivalent feature can also be enabled through an elevated command prompt:

DISM /Online /Enable-Feature /FeatureName:IIS-ASP

The command may report that the feature is already enabled. That means Classic ASP is available, not that myinfo.dll has been restored.

Check the IIS application pool

A historical COM component may be 32-bit. On 64-bit Windows, the application pool’s bitness must match the component and the rest of the application.

1. Open Start.
2. Type IIS.
3. Open Internet Information Services (IIS) Manager.
4. In the left pane, select the computer.
5. Select Application Pools.
6. Right-click the pool used by the affected site.
7. Select Advanced Settings.
8. Find Enable 32-Bit Applications.
9. Set it to True only when the application and its legacy components require 32-bit execution.
10. Select OK.
11. Recycle the application pool.

Do not switch this setting blindly. A 32-bit component cannot be replaced with an arbitrary 64-bit DLL, and changing pool architecture can break other COM objects or application dependencies.

Test the website

After enabling the required features:

1. Open IIS Manager.
2. Select Sites.
3. Right-click the affected site.
4. Choose Manage Website > Restart.
5. Browse to the page that previously failed.

If the error still specifically names MSWC.MyInfo, IIS is processing ASP but the historical utility component is still missing, unregistered, or incompatible. Installing current IIS again is not proof that MyInfo is included.

Fix 3: Restore the historical component from the correct source

Microsoft’s IIS documentation states that the utility components were omitted by default from IIS 6.0 and points administrators toward the IIS 6.0 Resource Kit for copies. This is a historical recovery path, not a recommendation to download a DLL from an unverified catalog.

Use this order:

1. Locate the original server backup or installation media.
2. Check the application’s deployment documentation.
3. Contact the application developer or system integrator.
4. Use the historically appropriate IIS Resource Kit only when its compatibility and provenance are known.
5. Restore the complete component according to that installation’s instructions.
6. Test the site under the correct IIS application pool architecture.

Do not select a file based only on its name, size, or a search result. Public catalog metadata describes a historical 32-bit build, but there is no verified current Microsoft standalone download page for myinfo.dll. A filename match does not establish authenticity, compatibility, or a safe installation path.

The installation directory also depends on the IIS or Personal Web Server generation. Copying the file to a guessed folder can leave the application unable to find it, register the wrong COM class, or interfere with another installation.

Fix 4: Use regsvr32 only when the installation requires it

regsvr32 registers a DLL when that DLL exposes the appropriate registration entry points. It is not a universal missing-DLL repair command.

Use it only when:

• You have the correct legacy DLL from trusted installation media.
• The application’s documentation explicitly requires COM registration.
• You know whether the application is 32-bit or 64-bit.
• You are working from an administrator account.

Open Command Prompt as administrator:

1. Open Start.
2. Type cmd.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Change to the folder containing the verified DLL.
6. Run the registration command specified by the application’s documentation.

For a 32-bit DLL on 64-bit Windows, the 32-bit registration utility is normally located at:

%windir%SysWOW64regsvr32.exe

For a 64-bit DLL, the 64-bit utility is normally located at:

%windir%System32regsvr32.exe

The folder names are counterintuitive: SysWOW64 contains 32-bit system utilities, while System32 contains 64-bit utilities on 64-bit Windows.

A successful registration message means only that registration completed. It does not prove that the DLL is the correct version or that its dependencies are available. If regsvr32 reports that the entry point is missing, the DLL may not be self-registering, may be the wrong file, or may not be intended for that operating system. Stop there and follow the original application’s installation procedure.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Fix 5: Repair Windows components when corruption is suspected

SFC and DISM can repair protected Windows components. They will not recreate an optional historical IIS Resource Kit file that was never installed.

Use them when other Windows files are also damaged, Windows servicing has failed, or the error began after broader system corruption.

Run DISM

1. Open Start.
2. Type cmd.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Run:

DISM.exe /Online /Cleanup-image /Restorehealth

1. Wait for the operation to finish.
2. Restart Windows.

Run System File Checker

Open an elevated Command Prompt again and run:

sfc /scannow

Wait until verification reaches 100 percent, then restart the computer and test the affected application or website.

If SFC reports that it repaired files, test again. If it reports that it could not repair some files, review the result and repeat the IIS or application-specific checks above. Do not expect SFC or DISM to supply a missing legacy utility component.

Repeating these commands without identifying what changed rarely solves a file that belongs to an omitted application component. If you want help identifying damaged Windows components while avoiding repeated manual scans, Outbyte PC Repair can provide a scan showing what it finds; repairs are performed by the full version, and it is not a substitute for reinstalling the IIS application that owns myinfo.dll.

Fix 6: Check drivers only when the evidence points there

myinfo.dll is not a graphics or hardware driver file, so reinstalling drivers is not a normal fix. Consider drivers only if the same incident includes device failures, display problems, or another clearly identified driver error.

To check devices:

1. Right-click Start.
2. Select Device Manager.
3. Expand categories such as Display adapters, Network adapters, and Universal Serial Bus controllers.
4. Look for a yellow warning icon.
5. Right-click the affected device.
6. Select Update driver.
7. Choose Search automatically for drivers.
8. Restart Windows if a driver is installed.

For a clean reinstall:

1. In Device Manager, right-click the affected device.
2. Select Uninstall device.
3. Confirm only if you have a replacement driver available.
4. Restart Windows.
5. Install the driver from the computer or device manufacturer’s official support page.

Driver hunting can involve matching hardware IDs, Windows editions, and 32-bit or 64-bit packages. If you want an automated scan to identify stale drivers, Outbyte Driver Updater can show what it detects; driver installation is handled by the full version, and this will not repair a missing IIS component.

Fix 7: Use System Restore after a recent change

System Restore can help if myinfo.dll worked previously and disappeared after a software removal, update, or configuration change.

1. Open Start.
2. Type Create a restore point.
3. Open the matching result.
4. Select System Restore.
5. Choose a restore point created before the error began.
6. Select Next, then Finish.
7. Allow Windows to restart.

System Restore does not normally remove personal documents, but it can roll back applications, drivers, and system settings. If no suitable restore point exists, return to the application or IIS installation path.

Migrating away from MSWC.MyInfo

MyInfo is obsolete. Restoring it may be necessary to keep an old ASP site running, but it should not be the long-term design for a maintained application.

An administrator should:

1. Back up the site and database.
2. Search Global.asa and the site’s ASP files for MSWC.MyInfo.
3. List which properties the application reads.
4. Move fixed site details into application configuration or ordinary ASP code.
5. Remove the COM object declaration after replacement code is tested.
6. Test every page that uses the old properties.
7. Restrict or retire the legacy Classic ASP site when its business purpose ends.

Do not remove the declaration without replacing its values. The website may load while producing blank administrator details, broken contact information, or later runtime errors.

What not to do

Do not download a random DLL

Avoid DLL catalog pages, file mirrors, and search-result downloads. They may provide:

• Malware or modified binaries
• The wrong historical build
• A 32-bit file for a 64-bit process, or the reverse
• A DLL with missing dependencies
• A file that registers an unsafe or incorrect COM class

Even an authentic file copied to the wrong folder may not fix the application.

Do not copy it into a guessed system folder

There is no universal rule that myinfo.dll belongs in System32, SysWOW64, or inetsrv. The correct location depends on the historical installation and the application’s registration model.

Do not run regsvr32 on an unknown file

Registration changes the system’s COM information. It can create a new problem while leaving the original dependency unresolved.

Do not install unrelated runtimes

Visual C++ packages, DirectX, graphics drivers, and Windows Update are not file-specific fixes for myinfo.dll unless investigation shows that the message actually concerns another file.

FAQ

Is myinfo.dll a legitimate Microsoft file?

Historically, yes. It was associated with Microsoft’s IIS utility components and the MSWC.MyInfo Classic ASP component. That does not make every copy found online trustworthy.

Is myinfo.dll part of Windows 10 or Windows 11?

It should not be treated as a normal component of current Windows. It is a legacy IIS/Classic ASP dependency, and current IIS installation does not prove that the historical MyInfo utility is included.

Should I enable IIS and Classic ASP?

Enable IIS and Classic ASP when the error comes from an ASP website, Global.asa, or MSWC.MyInfo. Do not enable them merely because a desktop game displays a missing-DLL message.

Why does Global.asa report an invalid MSWC.MyInfo ProgID?

The ASP application is attempting to create the COM object, but IIS cannot resolve that ProgID. The component may be absent, incorrectly registered, removed during an upgrade, or incompatible with the application’s bitness.

Can SFC or DISM restore the file?

Only if it was a protected Windows component on that installation. They will not recreate an optional IIS Resource Kit component that was never installed.

Does a 32-bit copy work on 64-bit Windows?

It can work only when the application and IIS application pool are configured for compatible 32-bit execution and the COM registration uses the correct 32-bit registry view. A 64-bit copy is not an automatic replacement.

What if the message appears on a computer with no IIS?

Identify the calling executable. It may be old software with an incomplete installation, an abandoned startup entry, or a program that bundled a legacy server component. Repair or reinstall that application rather than enabling IIS or downloading the DLL.

When is Windows repair justified?

Use DISM, SFC, or System Restore when other Windows components are also failing or the problem follows broader system corruption or a recent system change. For a single missing legacy IIS component, restoring the owning application is the more direct solution.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.