bcrypt.dll Load Errors: Restore the Right Windows Component

The program can't start because bcrypt.dll is missing from your computer.

When bcrypt.dll is missing, not found, corrupt, or unable to load, the correct repair depends on which copy Windows or the application is trying to use. bcrypt.dll is a genuine Microsoft Windows system component, so downloading a replacement from a random DLL website is not a safe first step.

As an Amazon Associate I earn from qualifying purchases.

Which fix applies to you

Use the branch that matches the evidence on your computer.

1. Several unrelated programs fail, or the file is missing from the Windows directory: install Windows updates, then run DISM followed by SFC.

   #1 Best Overall

   Sale

   

   Microsoft Windows 11 (USB)

   • Less chaos, more calm. The refreshed design of Windows 11 enables you to do what you want effortlessly.
   • Biometric logins. Encrypted authentication. And, of course, advanced antivirus defenses. Everything you need, plus more, to protect you against the latest cyberthreats.
   • Make the most of your screen space with snap layouts, desktops, and seamless redocking.
   • Widgets makes staying up-to-date with the content you love and the news you care about, simple.
   • Stay in touch with friends and family with Microsoft Teams, which can be seamlessly integrated into your taskbar. (1)

   $124.97

   Buy on Amazon

2. Only one application or game fails, and the error names its installation folder: repair, reinstall, or verify that application.

3. The problem began immediately after an antivirus detection: inspect Protection History before restoring anything.

4. The error says “procedure entry point” or “not designed to run on Windows”: investigate a version or architecture mismatch and look for an application-local copy.

   ×

   Recommended Free Tools

   Windows Errors? Fix Them Before They Spread

   Fix My PC Now →Free scan · no reinstall

   Crashes, No Sound, or Screen Glitches?

   Find the Right Drivers →Free scan · under a minute

   PC Slower Than It Used to Be?

   Run a Free PC Scan →Free scan · Windows 10 & 11
   Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

5. The file appears in a crash log, but no startup dialog says it is missing: do not assume bcrypt.dll caused the crash. Check the application, mod, driver, or dependency identified elsewhere in the report.

6. Windows Update and DISM cannot repair several system files: use System Restore, Windows 11’s recovery reinstall, or an in-place Windows repair installation.

The first check is the path. Record the exact error text and every path shown in the dialog. A path such as C:\Windows\System32\bcrypt.dll points toward Windows. A path beside a game or application executable points toward that application’s private files.

What bcrypt.dll is

bcrypt.dll is part of the Microsoft Windows Operating System. Its internal description is Windows Cryptographic Primitives Library (Wow64), and it acts as the user-mode router for Windows Cryptography API: Next Generation, also called CNG.

Programs use CNG for operations such as:

• Hashing
• Encryption and decryption
• Key generation and key management
• Random-number generation
• Other cryptographic primitives

Microsoft documents the CNG primitive APIs under bcrypt.h and identifies Bcrypt.dll as the user-mode implementation used by applications calling APIs such as BCryptOpenAlgorithmProvider. Windows components, browsers, installers, security software, productivity programs, games, and game launchers can all depend on this functionality.

It is not the same file as:

• bcryptprimitives.dll
• ncrypt.dll
• cryptbase.dll
• Visual C++ runtime files
• DirectX runtime files
• .NET runtime files

It also does not come from Visual C++, DirectX, or .NET. Those packages can repair different missing dependencies, but they are not the normal source of Windows’ bcrypt.dll.

Where bcrypt.dll should be located

On 64-bit Windows, the normal locations are:

%windir%\System32\bcrypt.dll

for the native 64-bit copy, and:

%windir%\SysWOW64\bcrypt.dll

for the 32-bit copy used by 32-bit applications.

The directory names are confusing. On 64-bit Windows, System32 contains 64-bit system files, while SysWOW64 contains 32-bit system files. This behavior is part of Windows’ File System Redirector.

A 32-bit Windows installation has only the applicable 32-bit system directory. Do not conclude that a file is missing merely because it is not present in both locations.

To inspect the files, open Command Prompt and run:

dir "%windir%\System32\bcrypt.dll"
dir "%windir%\SysWOW64\bcrypt.dll"

The second command may report that the path does not exist on 32-bit Windows.

You can inspect version and signature information in PowerShell:

Get-Item "$env:windir\System32\bcrypt.dll" |
  Select-Object FullName, Length, LastWriteTime, VersionInfo

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

A normal Windows copy should be located in the Windows system directory and normally have a valid Microsoft signature. A file beside an application executable is a separate case. It may be an intentional private copy, an outdated copy, an incompatible copy, or a malicious replacement.

There is no single universal current version number or file size for every installation. The version depends on the Windows release, architecture, servicing level, and cumulative updates. Historical versions such as 10.0.19041.1 and 10.0.14393.0 describe particular Windows builds, not a download target.

Recognize the type of error

The wording varies by Windows version and by the program displaying the message. Common errors include:

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

This application has failed to start because bcrypt.dll was not found.
Re-installing the application may fix this problem.

The code execution cannot proceed because bcrypt.dll was not found.
Reinstalling the program may fix this problem.

There was a problem starting bcrypt.dll.
The specified module could not be found.

bcrypt.dll is either not designed to run on Windows or it contains an error.
Try installing the program again using the original installation media.

You may also see:

The procedure entry point <function> could not be located
in the dynamic link library ...\bcrypt.dll

or:

The application failed to initialize properly (0xc0000142).

“The specified module could not be found” does not always mean that the named file itself is absent. Windows may have found bcrypt.dll but failed to load one of its dependencies. Windows resolves dependent DLLs according to its DLL search order.

Before repairing anything, record:

• The full error text
• The full path shown in the error
• The affected program or game
• Your Windows version and build from winver
• Whether every program fails or only one
• Whether the issue started after Windows Update, an application update, a mod installation, antivirus action, disk trouble, or malware removal
• Whether the message names bcrypt.dll, bcryptprimitives.dll, another DLL, or a procedure entry point

Fix 1: Install Windows updates

A missing or damaged Windows component should first be repaired through Windows servicing.

Windows 11

1. Open Start.
2. Select Settings.
3. Select Windows Update.
4. Select Check for updates.
5. Install all available updates.
6. Restart the computer.
7. Return to Settings > Windows Update and check again.

Windows 10

1. Open Start.
2. Select Settings.
3. Select Update & Security.
4. Select Windows Update.
5. Select Check for updates.
6. Install the available updates.
7. Restart the computer.
8. Check for updates once more.

Microsoft’s Windows Update instructions cover the normal update process.

After restarting, launch the affected application again. If the program starts, the file was probably restored or the component mismatch was corrected by servicing.

If Windows Update fails repeatedly, or several protected Windows DLLs are missing, continue with DISM and SFC rather than searching for an individual copy of bcrypt.dll.

Fix 2: Repair Windows with DISM and SFC

For a genuinely missing or damaged Windows copy, run DISM first and SFC second. Microsoft explains that DISM repairs the component store used as a source by SFC, while SFC checks and replaces protected Windows system files. The official procedure is documented in Repair missing or corrupted system files.

Run DISM

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

DISM.exe /Online /Cleanup-Image /RestoreHealth

DISM can take time, and the progress percentage may appear to pause. Wait for the command to finish and report whether the restore operation completed successfully.

Run SFC

In the same elevated Command Prompt, run:

sfc /scannow

Wait until verification reaches 100 percent. Do not close the window while SFC is checking protected files.

Restart Windows after both commands complete, then test the affected application.

Interpret the SFC result

• “Windows Resource Protection did not find any integrity violations.” Windows did not detect corruption in the protected files it checked. If only one application fails, repair that application next.
• “Windows Resource Protection found corrupt files and successfully repaired them.” Restart Windows and test the program again.
• “Windows Resource Protection found corrupt files but was unable to fix some of them.” DISM may need a matching repair source, or Windows may need a repair installation.

If DISM cannot obtain repair files through Windows Update, Microsoft documents using a matching Windows installation source:

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

Replace C:\RepairSource\Windows with the actual path to a repair source that matches the installed Windows edition and build. Do not use an arbitrary folder from another computer.

If you want help identifying which Windows components are damaged instead of repeating SFC and DISM without knowing what changed, Outbyte PC Repair provides a free scan showing what is wrong; repair is performed by the full version, and it remains optional because DISM and SFC are Microsoft’s built-in repair path.

Fix 3: Repair or reinstall the affected application

If only one program fails and the Windows copies of bcrypt.dll exist, the application is the more likely owner of the problem.

This is especially likely when:

• The error names a path under the application directory.
• The program was recently updated or patched.
• A mod loader was installed or removed.
• The program was partially uninstalled.
• The application ships a private DLL beside its executable.

Repair a Windows application on Windows 11

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

Launch the application after the repair. If the error remains and the application provides Reset, use it only after considering what settings or locally stored data may be removed.

For a traditional desktop program:

1. Open Control Panel.
2. Select Programs.
3. Select Programs and Features.
4. Select the affected program.
5. Choose Repair, Change, or the vendor’s repair option if available.
6. Complete the wizard and restart if requested.

On Windows 10, the available path depends on the application type. Check Settings > Apps > Apps & features, select the application, and use Advanced options or Modify when provided.

If no repair option exists, uninstall the application, restart Windows, and install it again from the application publisher’s official installer. Back up saves, profiles, configuration files, or license information first when the program stores them locally.

Do not copy the Windows System32 version into the application folder. An application-local DLL can require a particular build or set of exports that does not match the system copy.

Fix 4: Verify game files through the launcher

For a game, use the launcher’s official verification or repair feature before changing Windows files.

For Epic Games Launcher:

1. Open the launcher.
2. Open Library.
3. Select the three dots beside the game.
4. Select Manage.
5. Select Verify.
6. Wait for the scan and replacement process to finish.
7. Launch the game again.

Verification compares installed files with the expected installation and replaces files that differ. It should not affect saved data.

Other launchers use names such as Repair, Validate, Scan and repair, or Verify integrity. Use the option provided by the launcher that installed the game.

If the game uses mods, temporarily disable or remove the mod loader and test the unmodified installation. A mod or compatibility layer may place a private bcrypt.dll beside the game executable. If that private copy is damaged, the game’s official repair process is the correct source.

When the game still fails after verification, check the exact path in the error. A path under the Windows directory points toward Windows repair. A path under the game directory points toward the game installation or its mod system.

Fix 5: Check antivirus quarantine safely

Windows Security may quarantine a file after a scan or application installation. Do not automatically restore bcrypt.dll, particularly when the detected file is inside a game, mod, crack, or unofficial software directory.

To inspect Defender’s records:

1. Open Start.
2. Type Windows Security.
3. Open the app.
4. Select Virus & threat protection.
5. Select Protection history.
6. Open the detection involving bcrypt.dll.
7. Record the original path, detection name, and action taken.

Microsoft documents Protection History and its Restore and Allow on device actions.

Before allowing or restoring a file, establish:

• Whether it came from %windir%\System32 or %windir%\SysWOW64
• Whether it came from an application or mod directory
• Whether it has a valid Microsoft or application-publisher signature
• Whether the detection reappears after restart
• Whether other suspicious files were detected at the same time

For a missing Windows system copy, repair Windows with Windows Update, DISM, and SFC. Do not download an unrelated replacement.

If malware is plausible, run an offline scan:

1. Open Windows Security.
2. Select Virus & threat protection.
3. Select Scan options.
4. Select Microsoft Defender Offline scan.
5. Select Scan now.
6. Save open work before Windows restarts.

Microsoft describes this process in its Microsoft Defender Offline guidance.

Fix 6: Check architecture and Windows-version mismatches

A bcrypt.dll error can result from loading the wrong architecture or a DLL from the wrong Windows generation.

On 64-bit Windows:

• 64-bit applications normally use the 64-bit copy in System32.
• 32-bit applications normally use the 32-bit copy in SysWOW64.
• Windows’ WOW64 redirection normally selects the correct system file for a 32-bit process.

Do not copy the 64-bit System32 file into a 32-bit application directory.

Procedure entry point errors

An error such as:

The procedure entry point <function> could not be located
in the dynamic link library ...\bcrypt.dll

usually indicates that the application loaded a DLL that does not export the function it expects. Common causes include:

• An outdated application-local DLL
• A program that requires a newer Windows build
• An x86 and x64 mismatch
• A damaged or partially updated application
• An unsupported Windows version

Check the full path named in the error and repair the owning application. If the program requires a newer Windows API, copying a newer DLL into an older operating system will not add the complete underlying implementation.

Microsoft documents the relevant CNG API as beginning with Windows Vista in the BCryptOpenAlgorithmProvider requirements. Modern software may require a newer supported Windows release even if the filename is present.

Fix 7: Update drivers only when the evidence points there

A crash log that lists bcrypt.dll proves that the module was loaded. It does not prove that the DLL caused the crash.

Consider a driver repair only when:

• The error identifies a driver file.
• The issue started immediately after a driver update.
• Device Manager reports a device error.
• The application publisher specifically links the failure to a driver.
• Graphics, storage, or security software is involved in the same failure.

To check Device Manager:

1. Right-click Start.
2. Select Device Manager.
3. Expand the category related to the suspected device.
4. Right-click the device.
5. Select Properties.
6. Check the General tab for a device status error.
7. Open the Driver tab and note the provider, date, and version.
8. Use Update Driver only when an update is appropriate.
9. Restart Windows and retest the program.

For a display, storage, or security device, use the hardware manufacturer’s official driver source when Windows does not provide a suitable update. If the problem began after an update, the Roll Back Driver option may be more appropriate than installing a newer package.

If you are tired of hunting through hardware categories and guessing which of several drivers is stale, Outbyte Driver Updater can provide a free scan showing the driver issues; installing the drivers is handled by the full version, and it is not required when the evidence points to Windows or the application instead.

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

Fix 8: Use System Restore after a recent change

System Restore can help when the failure began after a driver, update, cleanup utility, application, or system modification.

1. Press Win + R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point dated before the bcrypt.dll failure began.
4. Select Scan for affected programs if available.
5. Review the changes.
6. Select Next, then Finish.
7. Allow Windows to restart.

Microsoft’s System Restore documentation explains that the process rolls back system files, registry settings, drivers, updates, and installed programs without normally removing personal files.

Test the application after Windows starts. If System Restore does not resolve the error, continue with the repair installation options below.

Fix 9: Repair reinstall Windows

Use a repair reinstall when:

• DISM and SFC cannot repair the component store.
• Several protected DLLs are damaged.
• Windows Update fails repeatedly.
• System Restore is unavailable or ineffective.
• The problem affects multiple unrelated programs.

Windows 11 recovery reinstall

On supported Windows 11 systems:

1. Open Start.
2. Select Settings.
3. Select System.
4. Select Recovery.
5. Find Fix problems using Windows Update.
6. Select Reinstall now.
7. Follow the prompts.
8. Restart Windows and test the affected program.

Microsoft says this process reinstalls the current Windows version while repairing system files and components and preserving apps, files, and settings. See Reinstall the current Windows version.

If that option is unavailable, use official Windows installation media and select the option to keep personal files and applications. Read every screen carefully. An incorrect installation choice can remove programs or data. Microsoft documents the process in Reinstall Windows with installation media.

Why common DLL fixes do not apply

Do not download bcrypt.dll

Random DLL download sites can provide:

• The wrong Windows build
• The wrong architecture
• A file with missing exports
• A file with incompatible dependencies
• A tampered or malicious file
• A copy that hides the original component-store problem

A correctly named DLL is not necessarily a correct Windows component. Use Windows Update, DISM, SFC, System Restore, official Windows installation media, or the affected application’s official installer.

Do not copy it into System32 or SysWOW64

Overwriting a protected Windows file can create a second problem involving ownership, servicing, signature validation, or mismatched dependencies. Never replace a Windows system DLL with a file taken from another computer.

Do not run regsvr32 for bcrypt.dll

regsvr32 is used for DLL components that expose registration entry points such as DllRegisterServer, as described in Microsoft’s regsvr32 documentation and DllRegisterServer documentation.

bcrypt.dll is a CNG API library, not a COM or ActiveX component that users should register. Running:

regsvr32 "%windir%\System32\bcrypt.dll"

typically produces an error saying that DllRegisterServer was not found. That result is expected and does not repair the file.

Do not enable random Windows Features

Windows Features are not a general DLL repair tool. Do not enable or disable features merely because an application mentions bcrypt.dll.

If the same error sequence names a .NET Framework component, inspect:

1. Press Win + R.
2. Type:

optionalfeatures

1. Press Enter.
2. Review Windows Features only for the specifically required .NET or legacy component.
3. Apply the requested feature change.
4. Restart Windows.

A .NET feature may address a separate .NET dependency, but it does not supply the normal Windows bcrypt.dll.

Likewise, installing Visual C++ Redistributable, DirectX, or .NET is appropriate only when the error names a dependency from that package. Microsoft’s Visual C++ packages include files such as vc_redist.x86.exe, vc_redist.x64.exe, and vc_redist.arm64.exe; DirectX’s legacy web installer is dxwebsetup.exe; and .NET has separate Runtime and Desktop Runtime packages. None is the normal source of Windows’ bcrypt.dll.

Prevention and final verification

After repairing the system or application:

1. Restart Windows.
2. Launch the affected program.
3. Test another program that uses normal Windows services.
4. Recheck the original error path.
5. Confirm that the correct system copy still exists.
6. If antivirus quarantined a file, review Protection History again.
7. Re-enable mods one at a time if the problem involved a game.
8. Keep Windows and the application updated through their official update mechanisms.
9. Avoid DLL download archives and unofficial replacement files.
10. Keep backups before using cleanup tools, system repair, or application resets.

If only one program still fails while Windows itself is healthy, focus on that program’s installer, launcher verification, mods, and application-local DLLs. If multiple unrelated programs fail, return to Windows Update, DISM, SFC, malware scanning, and repair installation.

FAQ

Is bcrypt.dll a virus?

No. The genuine file is a Microsoft Windows system component used by CNG cryptographic APIs. A copy with the same name in an unexpected application or download directory can still be unsafe, so verify its path and digital signature.

Should I download bcrypt.dll from the internet?

No. Do not use a random DLL archive or copy the file from another computer. Repair the Windows component through Windows Update, DISM, SFC, System Restore, or official Windows installation media. If the file belongs beside a game or application, use that program’s official repair or verification process.

What is the difference between bcrypt.dll and bcryptprimitives.dll?

They are different Windows components. bcrypt.dll routes user-mode CNG cryptographic primitive calls, while bcryptprimitives.dll is a separate file. Repair the file named in the error rather than substituting one for the other.

Why does bcrypt.dll exist in both System32 and SysWOW64?

On 64-bit Windows, System32 normally contains the 64-bit copy and SysWOW64 normally contains the 32-bit copy used by 32-bit applications. This naming is counterintuitive but expected.

What if the file exists but the application still says it is missing?

Check the path in the error. The application may be loading a private copy beside its executable, or a dependency of bcrypt.dll may be missing. Repair the application and verify its files before changing Windows.

Can Visual C++, DirectX, or .NET fix this error?

Not normally. Those packages provide separate runtimes. Install them only when the error identifies a dependency from that package. They are not the standard repair source for Windows’ bcrypt.dll.

Why did SFC find no problem?

SFC checks protected Windows files. If the affected program is loading an application-local copy, SFC can correctly report no Windows integrity violation. Check the full path and repair the application.

Does a crash report naming bcrypt.dll prove that the file is broken?

No. It proves that the module was loaded or appeared in the crash path. The actual cause may be an application bug, mod, driver, or another dependency.

Does Windows XP support modern bcrypt.dll applications?

Microsoft documents the relevant CNG API beginning with Windows Vista. Copying a newer DLL into Windows XP cannot add the complete operating-system implementation required by a modern application. Use a compatible application version or upgrade Windows.

Is Windows 10 still receiving normal support?

Microsoft states that Windows 10 support ended on October 14, 2025. Systems that cannot receive current servicing may require an upgrade or supported repair path rather than an individual DLL download. See Microsoft’s Windows 10 support notification.

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.