binkw32.dll is missing or fails to load: what the file is and how to fix it
binkw32.dll is the 32-bit Bink Video library from RAD Game Tools, the part of a game that plays its intro movies, logos and cutscenes. Every game that uses Bink ships its own copy in its own folder, in the version it was built with. When a game says the file is missing or cannot be loaded, the fix is the game's own files, not a DLL from the internet and not a video codec pack.
Prefer to fix it yourself? The manual steps follow.
How to fix binkw32.dll errors
The file belongs to the game that shows the error. Windows does not include it and no runtime package installs it. If the game came from a store, let its launcher check the files: in Steam right-click the game, choose Properties, Installed Files, Verify integrity of game files; the EA app, Epic Games Launcher, GOG Galaxy and Ubisoft Connect have a Repair or Verify option in the game's menu. The launcher downloads the binkw32.dll that this game was made with. A game installed from a disc or an old installer gets the file back only through a reinstall from that same source, followed by the publisher's patches.
RAD Game Tools, the maker of Bink, says plainly that Bink DLLs are not replaceable: a different version copied into a game is likely to make it crash. Its RAD Video Tools download does not even contain the DLL, so installing it does nothing for a game. A copy from a DLL site or from another game is the wrong build in the same way.
Which games and programs ship binkw32.dll
RAD licenses Bink to game developers through the Bink SDK, and the developer puts binkw32.dll next to the game's .exe or in a subfolder the game loads it from. That is why there is no single binkw32.dll on a PC: there is one per game, each in its own version, and they cannot be swapped between games. These are the cases you will meet.
| Program | Made by | What to know |
|---|---|---|
| 32-bit PC games with Bink videos | RAD Game Tools (library), shipped by the game's developer | The game calls the file for every .bik movie it plays: publisher logos, the intro, cutscenes. Many of these games stop at start-up if the file is gone, before any menu appears. The copy sits in the game's own folder. |
| Older games sold again on Steam, GOG or other stores | The re-release publisher, with RAD's library inside | Store versions of older games keep the binkw32.dll of the original build or of the updated release. Verify or repair in the store's launcher restores exactly that copy. |
| Games installed from a disc or a boxed installer | The original publisher | No launcher can restore the file. Reinstall the game from the disc or installer, then install the publisher's official patches in their order, because a patch may replace binkw32.dll with the version the patched .exe expects. |
| Mods, widescreen fixes and ASI loaders | Their own authors | Some mods use binkw32.dll as a proxy: they rename the game's original file and put their own binkw32.dll in its place, which then loads the original. Removing such a mod without restoring the original is a common cause of the missing file error. |
| RAD Video Tools | RAD Game Tools | RAD's free tool for playing and converting Bink and Smacker videos. RAD states that it does not contain the Bink DLL a game uses, so installing it does not fix a game's binkw32.dll error. |
| 64-bit games that use Bink | Their own developers | A 64-bit game cannot load a 32-bit DLL, so it ships a separate 64-bit Bink library under another name. binkw32.dll is only for 32-bit games, and renaming files between the two never works. |
Step by step
- Start the game the way it was installed. Launch a store game from its launcher (Steam, EA app, Epic, GOG Galaxy, Ubisoft Connect) rather than from an old desktop shortcut, and a disc game from its Start menu entry. A shortcut that points to an old install folder or to another copy of the game can fail at the same point as a missing file.
- Look at your security software's protection history. In Windows Security open Virus and threat protection, Protection history; other security programs have a quarantine or a history list of their own. If binkw32.dll from the game's folder is listed, you know why it is gone. Do not restore it yet: the verify or reinstall in the next step brings back a clean copy anyway.
- Verify or repair the game files. Steam: right-click the game, Properties, Installed Files, Verify integrity of game files. EA app, Epic Games Launcher, GOG Galaxy and Ubisoft Connect: open the game's menu or settings and choose Repair or Verify. Wait until it finishes. The launcher replaces missing and changed files with the build that game ships, binkw32.dll included.
- If the file was removed again, deal with the detection. Only for a game you bought from a store or installed from its own disc: when the security program removes the copy a second time, check its digital signature or compare it with the file check on this page, restore it from quarantine, allow that file or the game's folder and report the false detection to the program's maker. Never allow a file that came with a cracked or repacked game.
- Remove mods that replaced the file. Mods and loaders that use binkw32.dll as a proxy rename the original and add their own file, often with a .asi file, a scripts folder or a .ini next to it. Remove the mod with its own uninstaller or by its instructions, then verify the game: the launcher puts the original back, but it may leave the extra files the mod added.
- Install the official patches of a disc game. If the error appeared after you installed or reinstalled an older game from a disc, install the publisher's patches in order. A patched .exe can expect a newer binkw32.dll than the one on the disc, and the patch brings the matching file. Get patches only from the publisher or the store, never from a DLL site.
- Reinstall the game. Uninstall it, check that its folder is gone (move your own save files first if the game keeps them there), and install it again from the same store or disc. A clean install also removes files that a verify leaves in place, such as a mod's proxy DLL.
What not to do
Do not download binkw32.dll from a DLL site.
RAD Game Tools states that Bink DLLs are not replaceable and that a different version copied into a game is likely to crash it. A downloaded file is also of unknown origin, and a DLL in a game folder runs with your rights every time the game starts.
Do not install the RAD Video Tools to fix a game.
It is a tool for viewing and converting Bink videos, and RAD says it does not contain the Bink DLL at all. It cannot put a binkw32.dll into your game folder, and leaving it installed does nothing for the error.
Do not copy the file from another game.
Both are RAD's library, but almost never the same version. A game asks binkw32.dll for the functions of the Bink version it was built with, and a copy from another game often lacks them, which gives the procedure entry point error or a crash when the first video plays.
Do not put binkw32.dll into System32 or SysWOW64.
The game looks in its own folder first, and a copy in the Windows folders fixes nothing. It stays behind, of unknown version, and any other program that uses Bink without its own copy might load it.
Do not restore a quarantined copy from a cracked or repacked game.
A binkw32.dll is a common place for cracks and mods to hook into a game, because the game loads it at start-up. In a download of that kind the detection may be right. Restoring it and switching protection off is how many infections from free game downloads start.
Check the copy on your PC
Choose the binkw32.dll from your game folder. Its checksum is calculated in your browser and compared with 43 copies of the file collected from PCs, all reporting RAD Game Tools, Inc.
The file stays on your computer. Nothing is uploaded: the checksum is computed locally.
Found a binkw32.dll next to a .asi file or a renamed copy of itself, in a game from a repack, or outside any game folder? Then the question is whether it is RAD's file at all, and that is a security question rather than a missing-file one. Is binkw32.dll RAD's file or a planted copy? On 2-Spyware
The error messages and what each one means
The wording points to the cause: a missing file, a file of the wrong version, a file that cannot be loaded, or a crash while a video plays. These are the texts Windows and games show, with the file name filled in.
The code execution cannot proceed because binkw32.dll was not found. Reinstalling the program may fix this problem.
Windows 10 and Windows 11 wording. The game's own copy is gone: deleted, quarantined, or removed with a mod. Check the protection history, then verify or repair the game, or reinstall a disc game.
The program can't start because binkw32.dll is missing from your computer. Try reinstalling the program to fix this problem.
The same situation in the older Windows wording. Same fix: let the launcher verify the files, or reinstall the game from its own source.
The procedure entry point _Bink... could not be located in the dynamic link library binkw32.dll.
A binkw32.dll was found, but it is not the version the game needs: the Bink function named in the message is missing from it. Typical after copying the file from another game or a DLL site, or after installing a patch without its files. Verify the game, or reinstall it and its patches in order.
binkw32.dll is either not designed to run on Windows or it contains an error.
Windows found the file but it is damaged, empty or not a valid library, often after an interrupted download, a failed patch or a disk error. Verify or reinstall the game; if several games show it, check the drive.
The application was unable to start correctly (0xc000007b).
Often a 32-bit and 64-bit mix-up: a 64-bit Bink library renamed to binkw32.dll, or a file copied into the wrong folder. Remove what you copied by hand and verify the game.
Error loading binkw32.dll. The specified module could not be found.
The game tried to load the file from its folder and nothing was there, or it was blocked. Same cause as the not found message: check the quarantine, then verify or reinstall the game.
Faulting module name: binkw32.dll
A line from the Application log in Event Viewer after a crash, usually when a video starts. Look at the Faulting module path of the same event: a path outside the game's folder or a file you added points to a mod or a copied DLL. Inside the game's folder, verify the game and install its official patches.
File facts
binkw32.dll is the 32-bit Windows library of Bink Video, the video codec RAD Game Tools makes for games; RAD's website carries the copyright of Epic Games, Inc.. A game uses the library to open its .bik video files and decode them frame by frame while it draws them on screen, with the sound. Because a game decides itself when to play a video, a game with a broken binkw32.dll can fail at start-up, at the first cutscene or not at all until a level with a movie loads. What the catalogue copies of the file report:
- Description in the file
- RAD Video Tools
- Company in the file
- RAD Game Tools, Inc.
The game loads binkw32.dll from its own folder, next to its .exe or in a subfolder it was built to use, and Windows looks there first. A genuine copy therefore lives inside a game's install folder and never in the Windows folders. It describes itself as Bink Video or RAD Video Tools from RAD Game Tools, Inc. (Properties, Details) and is small, about 160 KB to 340 KB across the copies listed below. Every copy in the catalogue is a 32-bit build, and versions run from the 1.0 releases to the 1.99 and 1.9.99 builds; neither the version nor the newest copy tells you which file your game needs. Only the game's own installer, patch or launcher has that answer.
Copies of binkw32.dll found on PCs
Public DLL catalogues have collected 43 copies of binkw32.dll uploaded from PCs, from version 1.6a to 1.9.99.0, all reporting RAD Game Tools, Inc. as the company. Each one came from some game's folder. The table lists them with their checksums, so you can tell whether your file is one of them.
None of them is the right file for your game unless it came from that same game. RAD states that Bink DLLs are not replaceable, and the newest copy here, 1.9.99.0, is not an upgrade for an older one. If your copy matches an entry, it is most likely a genuine RAD build; whether it fits the game only the game's own files can confirm.
| Version | Build | Size | MD5 | SHA-1 |
|---|---|---|---|---|
1.9.99.0 | 32-bit | 225 KB | 7c43791dffb9386af84d01a9828864b4 | d91548452c4d087be4b77e6975278ef93d237937 |
1.9.99.0 | 32-bit | 225 KB | a284545c089f1f20cf8c1e0e5bbdcf5d | e9a0551f5b4f53a80c64abec8818efd778da8ae0 |
1.9.99.0 | 32-bit | 225 KB | b30682d59444e618b0b26a315ea943a7 | 81346b1797074ad4fc37946897776277644a1fd4 |
1.9.99.0 | 32-bit | 225 KB | b3e3e380444c99f1010789482deea6bd | 0255816632bf06f786ddb64f58f093b7d7153ee6 |
1.9.99.0 | 32-bit | 225 KB | c3befc56ba8faa7d172270df7347d2f2 | 08b9a83704f142d401a5f44b241a2ef846bbc346 |
1.9.99.0 | 32-bit | 225 KB | c565487fe52464cc9a08159158657cad | edf23dcfeb86c282df4c304831d123e4aede7f8b |
1.9.99.0 | 32-bit | 225 KB | d9a4019d94e667f4a5aec93d56442a7e | 13692337eb69ef174b9f272dd100bbcfacd4ad7e |
1.9.99.0 | 32-bit | 225 KB | e665de4399e7392a78cf78d761052c9a | c74b3cd5677d84269933cb18e2c6cd2d7ad57535 |
1.9.18.0 | 32-bit | 174 KB | 309ec04c8e8ce771b0a79d501d17234e | 71f70825328206e8c12e15360035b3932d87ef35 |
1.9.18.0 | 32-bit | 174 KB | 4bbacd1b60bfaa0681fb8546496f7f4c | 8c9165f31ffd1538855e54c9e8e87daa166be2e8 |
1.9.18.0 | 32-bit | 174 KB | 8ebf14e7932485bb764937214ed81eed | c4652d4900fc43292b3e06053e10e5719c009789 |
1.9.18.0 | 32-bit | 174 KB | c077ac3fd828c8a4957836873073b65f | 1109971ec27e73e7c7e70e2b0d60dbdd06012aa2 |
1.9.14.0 | 32-bit | 174 KB | 25fa8ef5fcc6a90be7a290c09a506812 | d4c0516c173fc56cb5c288dab316e45ed8ea2ef8 |
1.9.12.0 | 32-bit | 174 KB | 61d1d5d60ffc1c5e2d84a6e934a45072 | 9c6b9e2cc93bc01bb9a2942c1ad198bbc8385e14 |
1.9.9.0 | 32-bit | 174 KB | c7bc266129eb690aa4eb344c92e8f7ff | 58b0b893bd8dcbde28af88e0ef987f175a517b96 |
1.9.9.0 | 32-bit | 174 KB | eb3f61f8c33706170a7d5cde641717ae | 864673fc5baeb04a02c9d86f35ce979ca0250e82 |
1.9.9.0 | 32-bit | 174 KB | f9e1dcd53aea742f42758011ff81a761 | a2705843e9a9889f6d86c9c67bd67aeea2819858 |
1.9.8.0 | 32-bit | 174 KB | 73caa2f66f2d8964403a87ac2359e263 | d807dee018cf742ba9596994fc02ea5cd7b36c08 |
1.9.1.0 | 32-bit | 174 KB | 8aae681be4095750a922dc958ee2b293 | e45e74b9c3671bc5ec7f17cdc1402dc78dcb8843 |
1.8.22.0 | 32-bit | 174 KB | 791dc1038f530239120aa22ccc8da14a | 50a365b9a556f7496fd38fa8383995dad80f880b |
1.8.12.0 | 32-bit | 195 KB | 6accc9b282ab720b49846131edf6832c | f5ec51a08245d4949a07dda9885f867cf9cee7fd |
1.8.12.0 | 32-bit | 195 KB | 8213ad6f2263af291ca4cf4e10c4c63c | 949b594f9249ae09a3732a7fe70d1a6ce1da6358 |
1.8.8.0 | 32-bit | 195 KB | 110aac6aeb281551bd0cca204515681d | 5e8786364d7dd9d6ffba1b8eb68f79a721802f08 |
1.8.8.0 | 32-bit | 195 KB | 17d83705502ce17f7608cb783f9347e3 | eff909818b60e25681f30584670efce95e548b74 |
1.0j | 32-bit | 256 KB | 69009fff6ddf9e4a788e539c5d62281a | ecac05558f1290e57a5a5b174f0b24fe2e8858f0 |
1.0a | 32-bit | 174 KB | 71f0294906ee3da26499b7fce1dff180 | 66d81feb880c218ba9ff2afda41747a794b30446 |
1.0q | 32-bit | 276 KB | e15b492959dfabc12aa4ca070b38f21a | 613f81f82e12131e86ae60dd318941f40db2200f |
1.99f | 32-bit | 205 KB | 6c16d545b0717830773fb1ba4a195778 | 4d205ef5ab7664f2e2b1de7b951824afa769ed61 |
1.99r | 32-bit | 225 KB | 7975407db3cf9876fa9292e01fa2e54c | 626e3be099d26740643ae7de53c35d7e24e47ab3 |
1.99m | 32-bit | 225 KB | b3a9cd183d5b6515f036e2454a5599be | 7d1e42d5c419dcbab8b26163e0f1d214b1c6ab1e |
1.9u | 32-bit | 184 KB | 7468ac27effceee900fe49c0b7d6129a | 8ccc2fec996bd81cf6f289e02ab7cb91d76df4c3 |
1.9r | 32-bit | 174 KB | a06839c06de2091e996e3e97a08680dc | d21aae55819bb6d8958f77edc9f0d2ab6e29c5b0 |
1.9p | 32-bit | 174 KB | 128b560ef70e8085c507368da6f26fe6 | 016558453bacdf92830eb8cb68b9fc11c29ac05c |
1.9n | 32-bit | 174 KB | 0d8168d5639b7e93cc3671384517ca93 | ca82bdbb9404f12c4f6d79079b51716d4a5e6a48 |
1.9i | 32-bit | 174 KB | c908384d1360b80f7aa0a5c7a2c08ac4 | 037eafaabc9258ad126e738d938cd5dfe998e792 |
1.9g | 32-bit | 164 KB | ca45a5705f452659ec14c4e3a2c5e5e0 | fadbddc0b19bdd5eafe171da6919ed19af963338 |
1.9a | 32-bit | 164 KB | 549c0b3a1bff0de86e16bea39b76a126 | cb6367428a4b2cd1c4c2d330ae870fb872fdbebc |
1.8x | 32-bit | 164 KB | aefcee5d1319929889267a470d261edc | 5fbb6886b1a7647a65da8c926f1a0d921bb9ccc3 |
1.8w | 32-bit | 164 KB | 9dc19dc76534614a62d746517e00776d | fa9608927ceb34a35c3b3c4ed95e747670a63bd4 |
1.8L | 32-bit | 195 KB | fcd554df06723953326dd0af5d430231 | c6ce07f9bb25f5bcee845222f11e83d34ec1c3ea |
1.8k | 32-bit | 195 KB | 3326ec37f845496cfb841602d93fcefc | 8c6b54168f1882323632f1d946417d2208dc8956 |
1.8i | 32-bit | 184 KB | 8264b55f8c6ebd2d83e6b9e52af83171 | ee336cf75c1b9ebce6a2bc8585e07e187320a0dd |
1.6a | 32-bit | 338 KB | 7b3abbe27f707d7a02d7044214a4b878 | 95b4132dec72b49e66ab9ff7a9508c8524b2995e |
Copies uploaded by users to a public DLL catalogue, read on 17 October 2026. 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 RAD's signature.
Questions people ask
Is binkw32.dll a virus?
RAD's binkw32.dll is a harmless video library that games ship in their own folders. Because a game loads it at start-up, cracks and mods sometimes put their own file under this name, and downloads of cracked games often carry real malware. A copy in a game you bought, in that game's folder, is normally RAD's. Read the security page linked above for a copy of unknown origin.
Will installing the RAD Video Tools fix binkw32.dll?
No. RAD Game Tools answers this in its own Bink FAQ: the RAD Video Tools do not contain the Bink DLL that games use, so installing them has no effect on a game. They are a tool for playing and converting Bink videos. The game's own files are the only source of the right binkw32.dll.
Can I download binkw32.dll and put it in the game folder?
You should not. RAD states that Bink DLLs are not replaceable and that a different version is likely to make the game crash. Each game needs the build it was made with, and a downloaded file is of unknown origin. Verify or repair the game in its launcher, or reinstall it, to get the matching copy.
Why does a game ask for binkw32.dll when it worked before?
Most often a security scan removed the file, a mod that replaced it was uninstalled without restoring the original, or a patch was interrupted. Check the protection history first, then think about mods and updates since the game last worked. A verify or a reinstall fixes all of these once the cause is clear.
Can I play the game without binkw32.dll?
Usually not. Many games load the library at start-up and stop if it is missing, even before the menu. Deleting or renaming video files does not help either, because the game still loads the DLL. Restore the file through the game's launcher or a reinstall instead.
What is the difference between binkw32.dll and the Bink video files?
binkw32.dll is the program code that plays the videos. The .bik files in the game's folders are the videos themselves. A missing .bik file usually causes a skipped or black cutscene, while a missing or wrong binkw32.dll stops the game or crashes it when a video starts. Both come back with a verify or a reinstall.
Does reinstalling DirectX or a codec pack help?
No. Bink is not a Windows codec and is not part of DirectX, a Visual C++ package or any codec pack. Those installers never place binkw32.dll in a game folder. Leave codec packs out of it and restore the file through the game itself.
Related guides
binkw32.dll is missing or fails to load: what the file is and how to fix it
Sources
- RAD Game Tools: Bink FAQ (Bink DLLs are not replaceable; the RAD Video Tools do not contain the DLL)
- Steam Support: Verify Integrity of Game Files
File data read on October 17, 2026.
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.
…