winhttp.dll is missing or crashes a game: what the file is and how to fix it

winhttp.dll is Windows HTTP Services, the library Windows components and programs use to send web requests and to follow the system proxy settings. It is part of Windows itself, so there is nothing to install. When a game reports it missing or crashes in it, the cause is usually a winhttp.dll in the game folder: the BepInEx mod loader ships its start-up proxy under this name. A damaged Windows copy is the rare case.

Prefer to fix it yourself? The manual steps follow.

How to fix winhttp.dll errors

Open the folder of the game or program that fails, the one with its .exe file. A winhttp.dll there is not Windows' copy. In most cases it is the Doorstop proxy of BepInEx, a mod loader for Unity games, and you will see a BepInEx folder and a doorstop_config.ini next to it. The game loads that file instead of the genuine one in System32. Rename it to winhttp.dll.bak and start the game. If it now starts, the mod setup is the cause: install the BepInEx build that matches the game, or update the mods. If there is no copy in the game folder, read the crash in Event Viewer, then repair Windows: install the pending updates, and run sfc /scannow and DISM from an administrator Command Prompt.

No runtime package, DirectX, Visual C++ or .NET installer contains winhttp.dll, so installing one does not fix these errors. The file is part of Windows 10 and Windows 11 and is repaired and updated only by Windows itself.

The order of fixes for winhttp.dll errors: the BepInEx copy in the game folder first, then Event Viewer, Windows Update, sfc /scannow and DISM
Check the game folder first: a mod loader's winhttp.dll causes most of these errors, not Windows.

Step by step

  1. Look in the game or program folder. Right-click the shortcut and choose Open file location, or in a game launcher use the option to browse local files. A winhttp.dll next to the .exe, together with a BepInEx folder, or a doorstop_config.ini file, belongs to the BepInEx mod loader. A winhttp.dll there with none of these was put there by some other tool. Games do not need their own copy of this Windows file.
  2. Rename that copy and test. Rename it to winhttp.dll.bak rather than deleting it, so you can put it back. Start the game. If it runs, the copy was the cause and the game itself is fine. The mods simply do not load while the file is renamed.
  3. Match the mod loader to the game. BepInEx has separate builds for 64-bit and 32-bit games and for different operating systems. Start the game and look at it in Task Manager: (32 bit) after the process name means the game needs the x86 build, no such note means x64. A wrong build is the usual reason for error 0xc000007b or a game that closes at once after BepInEx is added.
  4. Update the loader and the mods after a game update. A game update can change what the loader and its plugins hook into. Download the current BepInEx release for the game and the current versions of the mods from their authors' pages. If one plugin breaks the game, the log files in the BepInEx folder usually name it.
  5. Verifying the game files will not remove the copy. The verify or repair option of a launcher checks the files the game shipped and replaces damaged ones. It usually leaves extra files alone, so winhttp.dll and the BepInEx folder stay after a verify. Remove or rename them yourself.
  6. Read the crash in Event Viewer. Press Win+R, type eventvwr.msc, open Windows Logs, Application and find the Error event from the time of the crash. Note the Faulting application name and the Faulting module path. A path in the game folder points to the copy there. A path in System32 or SysWOW64 points to the program that used the genuine file, which is usually the one to update or reinstall.
  7. Install Windows updates and restart. Open Settings, Windows Update, install everything that is offered and restart, even if Windows does not ask. Cumulative updates replace system files, winhttp.dll included, with the current build for your Windows release.
  8. Run System File Checker. Type cmd in the Start menu, right-click Command Prompt and choose Run as administrator. Run sfc /scannow and wait until it reaches 100%. It compares protected Windows files with the stored originals and repairs a damaged or replaced winhttp.dll in System32 or SysWOW64. Restart afterwards.
  9. If System File Checker cannot repair everything, run DISM. In the same administrator window run DISM /Online /Cleanup-Image /RestoreHealth. It repairs the store that System File Checker copies its originals from, using Windows Update. When it finishes, run sfc /scannow once more, then restart.
  10. Still failing: repair Windows in place. On Windows 11, Settings, System, Recovery offers Fix problems using Windows Update, which reinstalls the current version of Windows and keeps your files, apps and settings. On Windows 10 the same result comes from running Microsoft's installation media and choosing to keep personal files and apps.

Download the genuine winhttp.dll for your Windows version

Each file below is Microsoft's own winhttp.dll for one Windows release, fetched from Microsoft's own server and checked against Winbindex, the index of the files in Windows images and updates. Pick your Windows version (Settings, System, About shows it) and the build: 64-bit for System32, 32-bit for SysWOW64. The repair steps above are still the better fix, because Windows protects these folders and keeps its copy updated. Use a file here to compare it with a copy you have, or when System File Checker and DISM cannot repair the file.

Older Windows releases

A free uGetFix account is needed to download. Sign in, or create one in a minute, and you come straight back here.

What not to do

Do not put Windows' winhttp.dll into the game folder.

This is the most common wrong fix. A Windows copy next to the .exe adds nothing, because Windows already provides the one in System32, and if you overwrite the BepInEx file with it, the mods stop loading without any error. It also stays behind, out of date, when Windows updates its own.

Do not download winhttp.dll from a DLL collection site.

You cannot tell which Windows release, build or architecture the file comes from, or whether it was changed. winhttp.dll is one of the names used for side-loaded code, so an unknown copy is a real risk. Use the genuine files above, and the checker below for a file you already have.

Do not copy a file into System32 or SysWOW64 by hand.

These copies are protected Windows files owned by the system. Many Windows components send web requests through this library, so a hand-placed file of the wrong build can break more than one program, and the next update or System File Checker run may replace it anyway. Repair with sfc /scannow instead.

Do not restore a quarantined copy without knowing where it came from.

If Microsoft Defender removes a winhttp.dll from a game folder, find out which mod pack or tool installed it before you restore it. Loaders are often flagged because of how they work, but the same name can carry harmful code. The security page linked below explains how to tell them apart.

Do not reinstall Windows first.

A winhttp.dll error rarely means Windows is broken. The copy in the game folder, the program that crashes and the repair tools above cover almost every case, and none of them touches your files.

Check the copy on your PC

Choose the winhttp.dll you are unsure about, for example the one in a game folder. Its checksum is calculated in your browser and compared with 377 Microsoft builds of the file from Windows releases and updates.

or drop the file here

The file stays on your computer. Nothing is uploaded: the checksum is computed locally.

21 genuine programs have been documented loading a planted copy of winhttp.dll. Found a winhttp.dll you did not expect, in a game folder you never modded, in Downloads, Temp or AppData? The name is used by mod loaders, and by code that hides next to a legitimate program. That is a security question, not a missing-file one. Is the winhttp.dll you found genuine? On 2-Spyware

The error messages and what each one means

The wording tells you which problem you have. These are the texts Windows shows, as written, with the file name filled in.

The winhttp.dll error messages Windows shows, what each one means and the fix for each
Not designed to run, 0xc000007b and a missing entry point point to a copy in the game folder; the crash path tells you where to look.
The code execution cannot proceed because WINHTTP.dll was not found. Reinstalling the program may fix this problem.

The wording of Windows 10 and Windows 11. Windows did not find a usable copy for that program. Every Windows release ships the file, so this is unusual: look in the game folder for a broken copy or a winhttp.dll.bak left from a test, then install updates and run sfc /scannow and DISM.

The program can't start because WINHTTP.dll is missing from your computer. Try reinstalling the program to fix this problem.

The same situation in the older wording of Windows 7 and 8. Same fix.

WINHTTP.dll is either not designed to run on Windows or it contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.

A winhttp.dll was found but could not be loaded. Almost always this is a copy in the game folder: a mod loader of the wrong build, a damaged download, or a file blocked by security software. Rename the game folder copy and test again.

The application was unable to start correctly (0xc000007b). Click OK to close the application.

This one does not name a file, but right after adding BepInEx it usually means a 32-bit winhttp.dll in a 64-bit game folder, or the other way round. Install the build that matches the game.

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

Windows names a function in this message. The program asked the winhttp.dll it loaded for a function this copy does not provide. A proxy copy has to pass every call on to Windows' file, so an old or incomplete proxy in the program folder is the usual cause. Update it, or rename it to test.

Faulting module name: WINHTTP.dll

A line from the Application log in Event Viewer after a crash. Look at the Faulting module path line of the same event. A game folder path means the crash happened in the loader's copy: update BepInEx and the mods, or remove them. A System32 or SysWOW64 path usually means the program that sent the web request is at fault: update or reinstall it, then run sfc /scannow if several programs crash the same way.

File facts

winhttp.dll is Windows HTTP Services (WinHTTP), the HTTP client interface of Windows. Microsoft documents it for services and server applications that send requests to web servers, and many Windows programs use it in the background: HijackLibs lists 20 programs in System32 that load it, among them mstsc.exe, netsh.exe and the proxy script worker pacjsworker.exe. It also holds the WinHTTP proxy setting that netsh winhttp show proxy displays. What Windows reports for the genuine file:

Description in the file
Windows HTTP Services
Where the genuine winhttp.dll belongs
C:\Windows\System32C:\Windows\SysWOW64
Signed by
Microsoft Windows, with a Windows catalog signature: the file's Properties show no Digital Signatures tab, which is normal. Check it in PowerShell: Get-AuthenticodeSignature <path to the file> (Status: Valid).

On 64-bit Windows, System32 holds the 64-bit file and SysWOW64 the 32-bit one; the folder names are historical. winhttp.dll is not on the short list of libraries that Windows always takes from System32, so when a program starts, Windows looks for it in the program's own folder first. That is what the BepInEx Doorstop proxy relies on: a file with this name next to a game's .exe is loaded instead of the Windows copy and passes the real calls on to it. The genuine 64-bit file is about 1.2 MB: 1,253,704 bytes in Windows 11 24H2 and 25H2, 1,096,152 bytes in Windows 10 22H2. A loader's copy usually has another size and description and is not signed by Microsoft.

Where Windows looks for winhttp.dll: the game's own folder first, then System32 or SysWOW64
A winhttp.dll next to the .exe wins over the Windows copy, which is how BepInEx starts and why a broken setup stops the game.

winhttp.dll versions by Windows release

Every Windows release has its own build of winhttp.dll, updated together with Windows. Winbindex lists 360 distinct Microsoft builds; the table shows the newest one indexed for each release and the update that delivered it.

Windows releaseFile versionDelivered bySize, 64-bit
Windows 11 26H110.0.28000.2704KB5121000, August 11, 20261,216,360 bytes
Windows 11 25H210.0.26100.9549KB5127648, October 13, 20261,253,704 bytes
Windows 11 24H210.0.26100.9549KB5127648, October 13, 20261,253,704 bytes
Windows 11 23H210.0.22621.4830KB5093998, June 9, 20261,245,240 bytes
Windows 11 22H210.0.22621.4830KB5093998, June 9, 20261,245,240 bytes
Windows 11 21H210.0.22000.3079KB5044280, October 8, 20241,146,104 bytes
Windows 10 22H210.0.19041.7663KB5129236, September 14, 20261,096,152 bytes
Windows 10 21H210.0.19041.7663KB5129236, September 14, 20261,096,152 bytes
Windows 10 21H110.0.19041.7663KB5129236, September 14, 20261,096,152 bytes
Windows 10 20H210.0.19041.7663KB5129236, September 14, 20261,096,152 bytes
Windows 10 200410.0.19041.7663KB5129236, September 14, 20261,096,152 bytes
Windows 10 190910.0.18362.1645KB5013945, May 10, 20221,014,912 bytes

Older copies of winhttp.dll found on PCs

Public DLL catalogues have collected 17 copies of winhttp.dll uploaded from PCs, from version 5.1.2600.2180 to 10.0.18362.778. Many come from older Windows releases. The table lists each with its checksums, so you can tell which one you have.

None of these replaces the file your Windows ships: the newest build indexed for Windows is 10.0.28000.2704, and each release keeps its own. If the check on this page finds your file in this list, it is most likely an older Microsoft build that was copied somewhere by hand. Confirm the Microsoft signature, remove the copy from the game folder, and let Windows use its own.

VersionBuildSizeMD5SHA-1
10.0.18362.77864-bit963 KB47f6bdf5ea61507053ee2698116e74ca92a9a26403e51f2040b10308864f314a0e64126c
10.0.18362.44932-bit748 KB5b1e96994b045107b4b3d8832664e95df70f108a2cb7bb1a19aaecf26bd0b3b35d2952fa
10.0.18362.164-bit952 KBbfe8e078140a14fe3f2024bfc1b0e0756b1a5640c5685abd80fc396f21511724c5f538f5
10.0.14393.064-bit799 KBc9e7d91a044b77cbcb4121c06610a86c8750abfe31e900d801a4cb8010f18061cb07ed4e
10.0.14393.032-bit614 KB732ee912cc1237a25ca957a26942be6d44b27f4f2e766889c308522d3f3f26ad923a92ee
10.0.10586.42064-bit778 KBd4b30e23a3b373648f61290daf432cb2cc76b9b8725f0dc041cb2ceed75278c6810f2446
10.0.10586.42032-bit604 KB1e497317417c1c68b5453dd04721b16d7d94dda45563c3582e91137c9677eaa63d7970b2
6.3.9600.1638432-bit573 KB984b3226c7a4cfc9fe91d7baca133d8d529cbc43c2d02b45c27cf198f304fe7113bae3a8
6.2.9200.1645164-bit696 KB7911470b6018059a880469a63b65700affe2879a44cef3775917e56002e16c3e7e1f7b3c
6.2.9200.1645132-bit502 KB7a4797475abad6ecf1bcb08637922ecadf138014f35a848f9ec0b570dc08af5395a7aab1
6.1.7601.1751432-bit338 KBca9f7888b524d8100b977c81f44c3234cae5f489296f07aff1b6782c2ffe7d0b80d13a58
6.0.6001.1831564-bit430 KB3a46c22a9e080f05bed6eb4fd1f4f0b593b61e6a9968807202cf8a193b079c9f30522e68
6.0.6001.1831532-bit369 KBce412dee2b485c11ba1802a64473e9bae293d64d401fb2750ea38bce7eb41611414518f5
5.1.2600.551232-bit348 KB25907d78e0916bbcbce932a4722e4e16ef4b2519666e95f394a71c8cf4d1afbf9610c326
5.1.2600.218032-bit338 KBcf1dc29afe2eb0fd7a32ab3e362ba29d5022fe691b35b2e0cd2c2f2d0deeca404039e4f1
5.1.2600.218032-bit338 KBea82a55f22654fbedcbd82d2d4305b45785be814b44a4571b8d1509fc41d258770a3f46d
5.1.2600.218032-bit338 KBf035e416e607fae8fdab422be6550c8d5ded3125d7e1e14b7eacfacd337384fb6937277f

Copies uploaded by users to a public DLL catalogue. We list their checksums so you can identify a file; we do not offer them for download and we did not verify each one against Microsoft's signature.

Questions people ask

Is winhttp.dll a virus?

The copies in System32 and SysWOW64 are genuine Windows files and are harmless. A winhttp.dll in a game folder is not Windows' copy: most often it is the BepInEx loader you or a mod manager installed, but other code can use the same name. Check the file with the tool on this page and read the security page linked above.

Why is there a winhttp.dll in my game folder?

Because a mod loader put it there. BepInEx starts through a small proxy called Doorstop, and its documentation says that proxy is usually named winhttp.dll. Mod managers install it for you when you add BepInEx mods to a Unity game. Removing it disables the mods and leaves the game itself as it was.

Do I need to install anything to get winhttp.dll?

No. winhttp.dll is part of Windows 10 and Windows 11 and cannot be installed separately. No DirectX, Visual C++ or .NET package contains it. If Windows' own copy is damaged, System File Checker, DISM and Windows Update repair it.

Mods do not load, and the game starts without errors. Is winhttp.dll the problem?

Often, yes. If no BepInEx.cfg file appears in the BepInEx\config folder after the first start, the proxy or the loader did not run. Check that winhttp.dll is next to the game's .exe, not in a subfolder, and that the build matches the game. For some older Unity games the BepInEx documentation suggests renaming winhttp.dll to version.dll.

Can I delete winhttp.dll?

Not the copies in System32 or SysWOW64: Windows components and many programs send web requests through them, and Windows treats them as protected system files. A winhttp.dll in a game folder can be removed or renamed safely as far as Windows is concerned; only the mods stop loading.

Will System File Checker remove a winhttp.dll from a game folder?

No. System File Checker repairs protected Windows files in the Windows folders. It does not look inside program or game folders, so a loader's winhttp.dll there stays until you remove it.

Should I use the 32-bit or the 64-bit file?

For Windows itself you need both, and Windows already has both: the 64-bit file in System32 and the 32-bit file in SysWOW64. For a mod loader in a game folder, use the build that matches the game. A mismatch causes error 0xc000007b.

Related guides

Reference

winhttp.dll is missing or crashes a game: what the file is and how to fix it

Fix

How to fix Windows update stuck on "Working on updates"?

Fix

How to fix Valheim crashes and errors?

Fix

How to fix Windows update error 0x800706ba?

Sources

File data read on October 17, 2026.

About the authoruGetFix Editorial TeamEditorial team

The editors who write and check uGetFix guides and reference pages. File facts are read from Microsoft's own installers and documentation, and every page shows the date its data was read.

Questions and experiences

Ask about this page: members and our editors answer. Reading is open; writing needs a free account.

0 comments

…

4,323 members already hereThey read, write, comment and vote. 0 verified · 32 joined this year