`ws2_32.dll` Missing on Windows: Causes, Fixes, and Safe Repair

ws2_32.dll is a legitimate Microsoft Windows system library for Winsock 2, so a missing or not-found message does not mean you should download a replacement. When ws2_32.dll fails, identify whether one application or Windows itself is affected, then repair the layer that actually caused the error.

What this file actually does

ws2_32.dll implements the Windows Sockets 2, commonly called Winsock, API. Applications use this Windows programming interface to create network connections, resolve addresses, communicate with servers, and perform other network operations. Microsoft documents Ws2_32.dll alongside the Ws2_32.lib import library and the winsock2.h development header in its Winsock socket documentation.

As an Amazon Associate I earn from qualifying purchases.

It is part of Windows itself. It is not:

• A Visual C++ Redistributable file
• A DirectX runtime
• A .NET package
• A network adapter driver
• A normal COM or ActiveX component
• A separately installed application called “Windows Socket 2.0 32Bit DLL”

That last description is a database-style label sometimes attached to the file. The actual component identity is the Windows Sockets 2 system library.

Winsock also includes other components, including providers and layered service providers. Firewalls, VPN clients, security software, and network drivers can add or interact with those components. They are separate from ws2_32.dll. A damaged VPN provider may break networking while the DLL itself remains present and correctly signed.

Why there are two different Windows folders

On 64-bit Windows, the normal locations are:

%windir%\System32\ws2_32.dll
%windir%\SysWOW64\ws2_32.dll

Despite the confusing names, System32 normally contains native 64-bit system files on 64-bit Windows, while SysWOW64 contains 32-bit files. Windows uses WOW64 file-system redirection so 32-bit applications receive the appropriate system components. Microsoft explains this behavior in its File System Redirector documentation.

A 32-bit game or older desktop application can therefore need the 32-bit copy even when the computer has a 64-bit processor and a 64-bit edition of Windows. Do not copy the 64-bit file into an application folder to satisfy a 32-bit program.

On 32-bit Windows, the relevant system copy is normally under System32.

The file’s version, size, timestamp, and hash depend on the Windows build, architecture, servicing level, and sometimes the platform. There is no single universal ws2_32.dll size or version that every Windows installation should have.

Diagnose the message before repairing anything

The exact wording and the number of affected applications determine the safest repair.

Message or symptom	What it usually points toward	Start here
“The program can’t start because ws2_32.dll is missing from your computer”	A missing, quarantined, damaged, or incorrectly loaded DLL	Check the application, antivirus history, and Windows system files
“This application has failed to start because WS2_32.dll was not found”	The loader could not locate the required library	Check the expected Windows location and whether only one application fails
“The procedure entry point <function> could not be located”	An incompatible Windows version, wrong local DLL, or missing exported function	Check the exact function, application compatibility, and local DLL shadowing
“Bad Image” or “not designed to run on Windows”	Corruption, wrong architecture, or an incompatible binary	Repair the affected application or Windows component
The application launches but cannot connect	Winsock catalog, VPN, firewall, provider, driver, or network problem	Confirm that the DLL exists, then investigate Winsock and network components
Many unrelated applications fail	Windows component-store corruption, malware, storage trouble, or a broad system change	Update Windows, then run DISM followed by SFC

The question that matters most is whether the failure affects one program or many.

Also note:

• The executable named in the dialog may be more important than the DLL name.
• A 32-bit application can fail even on 64-bit Windows.
• An application can load a private DLL from its own folder before Windows searches the system directory.
• A file that exists can still be corrupt, the wrong architecture, unsigned, or the wrong version for the application.
• ws2_32.dll errors are different from errors naming VCRUNTIME, MSVCP, DirectX, or a specific .NET assembly.

Check the expected file and its signature

Before changing anything, inspect the Windows copies. Open Command Prompt and run:

dir "%windir%\System32\ws2_32.dll"
if exist "%windir%\SysWOW64\ws2_32.dll" dir "%windir%\SysWOW64\ws2_32.dll"

A normal result shows the file in the expected Windows directory. The command does not prove that the file is healthy, but it tells you whether it is present.

PowerShell can show the path, size, and file version:

Get-Item "$env:windir\System32\ws2_32.dll",
         "$env:windir\SysWOW64\ws2_32.dll" `
         -ErrorAction SilentlyContinue |
  Select-Object FullName, Length,
    @{Name="FileVersion";Expression={$_.VersionInfo.FileVersion}}

To inspect the embedded or catalog signature, open PowerShell and run:

Get-AuthenticodeSignature "$env:windir\System32\ws2_32.dll"

Microsoft documents this command in the Get-AuthenticodeSignature reference. Microsoft’s Sysinternals sigcheck can also display version, signing, certificate-chain, and hash information:

sigcheck -i -h "%windir%\System32\ws2_32.dll"

The official Sigcheck documentation explains the available checks.

Do not compare the displayed version or size with a file copied from another Windows computer and assume they must match. Servicing level and Windows build differences can make those values different.

Fix 1: Repair the affected application first

If only one game or program displays the error, repair that application before repairing Windows. A single damaged installation, stale private DLL, or missing application dependency is more likely than a complete Windows failure when every other program works.

Microsoft Store and packaged applications

1. Open Start.
2. Select Settings.
3. Open Apps.
4. Select Installed apps.
5. Find the affected application.
6. Select its three-dot menu.
7. Choose Advanced options.
8. Select Repair.
9. Start the application again.

Repair normally keeps the application’s data. If it does not solve the problem, return to the same screen and use Reset where appropriate. Reset can remove application data, so check whether the program stores local saves or configuration files before using it.

Microsoft documents these steps in its guide to repairing apps and programs in Windows.

Traditional desktop applications

For older desktop software:

1. Press Win+R.
2. Enter appwiz.cpl.
3. Press Enter.
4. Select the affected program.
5. Look for Repair, Change, or a similar maintenance option.
6. Follow the installer prompts.
7. Restart Windows if the installer requests it.

If the program has no repair option, uninstall it and reinstall it from the publisher’s official installer or the official game launcher.

Games and launchers

Use the launcher’s own file verification or repair function. The exact wording varies, but it is usually found by opening the game’s properties or management menu and choosing Verify, Repair, or Verify integrity of game files.

This is especially important if the error began after:

• A failed game update
• A forced shutdown
• Moving the game to another drive
• Removing a mod
• An antivirus detection
• A partial reinstall

Look for an application-local copy

Windows can search the application’s directory before the system directories. Microsoft describes this behavior in its DLL search-order documentation.

Check the folder containing the affected executable for an unexpected file named ws2_32.dll. A stale or damaged private copy can shadow the genuine Windows copy. Do not replace it with a downloaded DLL. Instead:

1. Close the application and its launcher.
2. Make a backup copy of the suspicious file if you need it for the publisher’s support team.
3. Scan the file with Windows Security.
4. Use the application’s repair or verification feature.
5. If necessary, reinstall the application from its official source.

If only one application fails and Windows repair reports no corruption, an application-local file or another missing dependency becomes more likely.

Fix 2: Install Windows updates, then run DISM and SFC

If multiple applications fail, Windows features are also malfunctioning, or the expected system copy is missing or corrupt, repair Windows itself.

Microsoft recommends running DISM before SFC because DISM repairs the Windows component source that SFC uses.

Install pending updates

1. Open Start.
2. Select Settings.
3. Open Windows Update.
4. Select Check for updates.
5. Install all available updates.
6. Restart the computer, even if Windows does not immediately require it.
7. Check for updates again after the restart.

Then open an elevated Command Prompt:

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Approve the User Account Control prompt.

Run DISM:

DISM.exe /Online /Cleanup-Image /RestoreHealth

Allow it to complete. It can pause at a percentage for some time. Do not close the window merely because the progress display appears unchanged.

When DISM finishes, run System File Checker:

sfc /scannow

Wait until SFC reports its final result, then restart Windows and test the affected application.

How to interpret SFC

• Windows Resource Protection did not find any integrity violations: Windows did not find corruption in the files it checked. Investigate the application, local DLL search order, compatibility, or another missing dependency.
• Windows Resource Protection found corrupt files and successfully repaired them: Restart and test again.
• Windows Resource Protection found corrupt files but was unable to fix some of them: Run DISM first if you did not already, restart, and run SFC again.
• SFC cannot complete: Try again from an administrator account, then consider Windows recovery or a repair reinstall.

Microsoft’s full System File Checker guidance includes repair-source instructions.

If Windows Update cannot provide the required repair files, Microsoft documents using a suitable installation or repair source:

DISM.exe /Online /Cleanup-Image /RestoreHealth ^
 /Source:C:\RepairSource\Windows /LimitAccess

Replace C:\RepairSource\Windows with an appropriate source that matches the installed Windows version and architecture. Do not use an arbitrary folder or another computer’s unrelated Windows directory.

When the manual DISM and SFC sequence becomes repetitive, Outbyte PC Repair can provide a free scan showing what it identifies; repairs are performed by the full version, so it remains optional and Microsoft’s built-in servicing tools are still the appropriate path for a Windows system DLL.

Fix 3: Check whether antivirus quarantined the file

If the problem started after a security alert, cleanup operation, or antivirus scan, check Protection History before attempting a replacement.

1. Open Start.
2. Type Windows Security.
3. Open the application.
4. Select Virus & threat protection.
5. Select Protection history.
6. Expand the relevant detection.
7. Read the exact path and detection details.

Microsoft says Protection History normally retains events for only two weeks. Its Protection History documentation also warns that restoring a genuinely malicious file can put the computer at risk.

Restore or allow the file only when all of these points are established:

• The path is the expected Windows system directory.
• The file is identified as a legitimate Microsoft system component.
• The detection details support a false positive rather than a real infection.
• The computer has been scanned and no broader compromise is indicated.

If a suspicious copy was found in a program folder, download folder, temporary directory, or unknown location, do not restore it blindly. Scan the computer and use the affected application’s official repair process.

For a legitimate system copy that disappeared from System32 or SysWOW64, DISM and SFC are safer than manually allowing an unknown file back into place.

Fix 4: Repair-install Windows 11 when system repair is not enough

On supported Windows 11 installations, Microsoft provides a repair reinstall through Windows Update. It reinstalls the current Windows version, repairs system files and components, and preserves apps, files, and settings.

1. Open Start.
2. Select Settings.
3. Open System.
4. Select Recovery.
5. Find Fix problems using Windows Update.
6. Select Reinstall now.
7. Keep the computer connected to power and the internet.
8. Follow the prompts and restart when Windows requests it.

The feature is described in Microsoft’s guide to reinstalling the current version of Windows.

If the option is not available, continue with DISM and SFC, use System Restore if an appropriate restore point exists, or follow Microsoft’s Windows recovery options. Do not download ws2_32.dll from an unofficial source as a substitute for repairing Windows.

Fix 5: Use System Restore after a recent system change

System Restore is useful when the error began immediately after a driver installation, application installation, update, cleanup tool, or other system change.

1. Press Win+R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point created before the error began.
4. Select Scan for affected programs if available.
5. Review the programs and drivers that will be changed.
6. Select Next, then Finish.
7. Allow Windows to restart.

System Restore changes system files, settings, and installed programs while leaving personal files untouched. Microsoft explains the process in its System Restore documentation.

Restore points may be unavailable or disabled. If there is no suitable point, return to DISM and SFC or use Windows recovery.

Fix 6: Handle entry-point errors separately

An entry-point error is not the same as a missing DLL error. For example:

The procedure entry point inet_pton could not be located
in the dynamic link library WS2_32.dll

This means Windows loaded a DLL but could not find the function that the application requested.

Possible causes include:

• The application requires a function unavailable on the installed Windows version.
• A wrong or obsolete ws2_32.dll is being loaded from the application directory.
• The system copy is damaged.
• The application is incompatible with the operating system.
• The application update expects a newer Windows API.

Microsoft documents the operating-system requirements for InetPton. The exact function named in your message matters.

Use this order:

1. Write down the exact function name in the error.
2. Check the application’s minimum Windows requirement.
3. Update the application from its official source.
4. Check for an application-local ws2_32.dll.
5. Run DISM and SFC if the Windows copy may be damaged.
6. Use a compatible version of the application if the current one requires a newer operating system.
7. Contact the application publisher if the software still expects an unavailable API.

Do not solve an entry-point error by downloading a random DLL with the same filename. A file can have the right name and still export the wrong functions or be built for the wrong architecture.

Fix 7: Reset Winsock only when applications launch but networking fails

netsh winsock reset is not a replacement command for a missing or corrupt ws2_32.dll. It is appropriate when applications open normally but network connections are broken and the DLL exists in the expected Windows directory.

Before resetting Winsock, close applications that use the network. Then:

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

netsh winsock reset

1. Restart Windows.
2. Test the affected application.

This resets custom Winsock catalog entries and layered-service-provider configuration. Microsoft documents the command in its netsh winsock reference.

A reset can affect VPN clients, firewalls, filtering software, and other networking programs that install custom providers. If the problem returns, repair or reinstall the affected VPN, firewall, or security software rather than repeatedly resetting Winsock.

Use this fix for a connectivity problem, not for a launch dialog saying that ws2_32.dll is missing.

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

Fix 8: Investigate drivers only when the symptom is actually a driver problem

A network driver is separate from ws2_32.dll. Reinstalling a driver will not normally restore a missing Windows API library.

Investigate the driver layer when you see symptoms such as:

• The network adapter is missing.
• Device Manager reports an adapter error.
• Windows cannot see the Wi-Fi or Ethernet device.
• The computer has no network connection even though applications launch.
• A VPN or security filter driver is malfunctioning.

To inspect the adapter:

1. Right-click Start.
2. Select Device Manager.
3. Expand Network adapters.
4. Look for a warning icon.
5. Right-click the affected adapter.
6. Select Properties and read the device status.
7. Use Update driver to let Windows search for a driver.
8. If the device remains faulty, use the computer or adapter manufacturer’s official Windows driver package.
9. Restart Windows and test the connection.

Do not uninstall a working adapter without first confirming that you have a suitable replacement driver or a reliable way to restore connectivity.

When checking several devices manually becomes difficult, Outbyte Driver Updater can perform a free scan to show which drivers it identifies; installing drivers requires the full version, and a driver update is relevant only when Device Manager or the network hardware points to that layer.

Fix 9: Do not install Visual C++, DirectX, or .NET just because the error mentions a DLL

The word .dll does not identify which runtime is missing.

The Microsoft Visual C++ Redistributable supplies libraries such as VCRUNTIME and MSVCP. It does not supply ws2_32.dll. If an application specifically reports a Visual C++ runtime DLL, use the appropriate package and architecture from Microsoft’s Visual C++ Redistributable downloads.

The official DirectX End-User Runtime supplies legacy components such as D3DX, XAudio 2.7, XInput 1.3, and XACT. It does not replace the Windows Winsock DLL. Microsoft provides it through the DirectX End-User Runtime page.

Install a runtime only when:

• The error names a DLL belonging to that runtime.
• The application publisher explicitly requires it.
• The official Microsoft installer matches the application’s architecture and requirements.

Older programs may legitimately need multiple Visual C++ versions side by side. That is separate from a ws2_32.dll failure.

Fix 10: Do not enable random Windows Features

Windows Features are not a general-purpose DLL repair tool. Do not enable or disable features at random because an application reports ws2_32.dll.

You can inspect them through:

1. Open Start.
2. Type Windows Features.
3. Select Turn Windows features on or off.
4. Review the list.
5. Change a feature only when the application’s documentation specifically requires it.
6. Select OK and restart if Windows requests it.

A Windows Feature may be relevant to a separate application requirement, but it does not provide a normal standalone download or repair path for ws2_32.dll.

Why regsvr32 does not repair ws2_32.dll

Do not run:

regsvr32 ws2_32.dll

regsvr32 is intended for DLLs that implement COM or OLE self-registration through functions such as DllRegisterServer and DllUnregisterServer. Microsoft describes those requirements in its Regsvr32 support article.

ws2_32.dll is a Windows API library, not a normal self-registering COM server. Running regsvr32 against it will not restore the file or repair Winsock. It may instead produce a misleading message that the DllRegisterServer entry point was not found.

Why downloading ws2_32.dll separately is unsafe

A random DLL download cannot guarantee:

• The correct Windows build
• The correct x86, x64, or ARM architecture
• A valid Microsoft signature
• Correct dependencies
• Compatibility with the application
• That the file has not been modified

It can also hide the real cause, such as a damaged component store, application-local DLL shadowing, malware quarantine, or a broken installation.

A system DLL should normally be restored through:

• Windows Update
• DISM and SFC
• Windows recovery
• A supported Windows repair reinstall
• The affected application’s official repair or installer when the problem is local to that application

Do not place an x64 file in an application directory for a 32-bit program. Do not replace a protected Windows file by hand as a first-line fix. Microsoft documents advanced manual replacement from a matching known-good Windows installation as a last-resort recovery technique, but the source must match the Windows build and architecture. Most users should use Windows servicing or recovery instead.

If the problem still exists

Work through this checklist:

1. Copy the exact error text, including the executable name and any named function.
2. Establish whether one application or many applications fail.
3. Check whether the application is 32-bit or 64-bit.
4. Inspect %windir%\System32\ws2_32.dll.
5. Inspect %windir%\SysWOW64\ws2_32.dll when present.
6. Look for an unexpected ws2_32.dll beside the affected executable.
7. Check Windows Security Protection History.
8. Inspect the Microsoft signature and file metadata.
9. Install pending Windows updates.
10. Run DISM, then SFC.
11. Repair or reinstall the affected application.
12. Use netsh winsock reset only when applications launch and the remaining problem is network connectivity.
13. Check Device Manager only when the symptom points to a network adapter or driver.
14. Use System Restore or Windows repair reinstall if the failure began after a system change or Windows servicing cannot repair it.

If SFC reports no violations and only one program fails, focus on that program’s files, compatibility, search path, and other dependencies. If multiple programs fail and repairs do not remain effective, investigate storage health, malware, System Restore, and Windows recovery.

FAQ

Is ws2_32.dll a legitimate Windows file?

Yes. It is the Windows Sockets 2 system library used by applications for network communication. The legitimate system copies normally reside in the Windows system directories.

Should I download ws2_32.dll from a DLL website?

No. Use Windows Update, DISM, SFC, Windows recovery, or the affected application’s official installer. Unofficial downloads may have the wrong architecture, build, signature, or dependencies.

Is ws2_32.dll part of Visual C++?

No. Visual C++ Redistributables provide libraries such as VCRUNTIME and MSVCP. They do not replace the Windows Winsock DLL.

Is ws2_32.dll part of DirectX?

No. DirectX runtimes provide DirectX-related libraries. They do not repair ws2_32.dll.

Should I use regsvr32?

No. ws2_32.dll is not a normal self-registering COM DLL, so regsvr32 will not repair it.

Why does the file appear in both System32 and SysWOW64?

On 64-bit Windows, the two directories normally contain the native 64-bit and 32-bit system copies respectively. Windows uses file-system redirection so applications receive the appropriate architecture.

What if the file exists but Windows still reports an error?

The application may be loading a different local copy, the file may be corrupt, the application may require an unavailable entry point, or another dependency may be missing. Check the exact error and the application directory before replacing anything.

Does reinstalling the network driver fix this error?

Not normally. A network driver is separate from ws2_32.dll. Reinstall the driver only when Device Manager or the network hardware shows a driver problem.

What if only one game reports the error?

Repair or verify the game files first, then reinstall it from its official launcher if necessary. A private copy in the game folder may be shadowing the Windows system copy.

What if every application reports the error?

Treat it as a Windows integrity, malware, storage, or broad system-change problem. Install updates, run DISM followed by SFC, review Protection History, and use Windows recovery if required.

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.