How to fix Entry Point Not Found error in Windows?

Entry Point Not Found means a program asked a DLL for a function by name, and the copy of the DLL that Windows loaded does not have it. The DLL is usually there, but it is the wrong version. Read the program and the DLL named in the window first: they tell you which fix to start with.

Facts checked on 16 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What the Entry Point Not Found error means

A DLL (dynamic link library) is a file of ready-made functions that programs share. Windows itself has thousands of them, and most programs bring their own. Each function has a name, its entry point. When a program starts, Windows loads the DLLs it needs and looks up every function the program asks for.

How the window reads (the names change with the program)

Program.exe - Entry Point Not Found
The procedure entry point FunctionName could not be located in the dynamic link library
C:\Program Files\Program\Library.dll

• The title names the program that failed, for example Zoom.exe, httpd.exe, svchost.exe or Setup.exe.
• The function name after "entry point" is the piece of code the program wanted, for example DecodePointer or a long C++ name full of @ and ? signs.
• The last line names the DLL, often with its full path. This is the copy Windows actually loaded, and the path is the most useful clue on the page.
• The meaning: the DLL was found, but this copy does not contain that function. It is older, newer or from a different product than the program expects.

What causes the Entry Point Not Found error, from most to least common

Most often, a program update stopped half way and left new program files next to old DLLs, or the other way round. Less often, a shared runtime such as Visual C++ is older than the program needs, or another program put its own copy of the DLL in a folder Windows searches first. Rarely, Windows system files are damaged or Windows is too old for the program.

• Typical DLLs readers see. msvcrt.dll, api-ms-win-core-libraryloader-l1-1-1.dll, SQLite.dll, libcrypto and libssl files, and the Visual C++ files above. Programs that showed it include iTunes, Photoshop, Trillian, Zoom and games such as Grand Theft Auto V.
• Why it started after an update. A new version of the program or a new Windows update changed one side of the pair. The other side stayed old.
• It is rarely a virus. A DLL from a known program in its own folder is normal. A DLL with a system name, such as kernel32.dll, sitting outside C:\Windows deserves a scan: How to scan for malware with Microsoft Defender

How to fix the Entry Point Not Found error in Windows

Read the DLL name and path in the window, then start with the fix in your row of the table. Fixes 1 to 4 deal with the program and the DLL it loads, and work for most readers. Fixes 5 to 8 repair Windows itself, for when the DLL is a Windows file.

Fix 1. Update or reinstall the program named in the window title

10 minutesLow riskOne program fails, the DLL sits in that program's folder, or the error started right after the program updated itself.

Most programs ship their own DLLs. When an update is interrupted, the new program file ends up next to an old DLL that lacks the new function. A clean install of the current version puts matching files back together.

1. Note the program name from the title of the window, for example Zoom.exe.
2. Check whether the program has a newer version on its maker's website. If it has, download it there.
3. Uninstall the program in Settings > Apps > Installed apps on Windows 11, or Settings > Apps > Apps & features on Windows 10.
4. Restart the PC, so that no old DLL stays loaded in memory.
5. Install the version you downloaded and start the program again.

All the ways to remove a program, including one that is not in the list: Uninstall a program or app in Windows

Fix 2. Repair or reset the app in Settings

5 minutesLow riskThe app comes from the Microsoft Store or is a built-in Windows app, so Settings shows Advanced options for it.

For Store apps Windows keeps a clean copy of the package. Repair checks and replaces the app's files, which brings back a matching set of DLLs. Reset also clears the app's data, so try Repair first.

1. Open Installed apps. Select Start > Settings > Apps > Installed apps.
2. Open the app's advanced options. Find the app in the list, select the three dots next to it and select Advanced options. Some apps do not have this option: for those, see the section about desktop programs below.

   

3. Repair first. On the page that opens, select Repair if it is there. The app's data stays. Open the app and check whether it works.

   

4. Reset if Repair did not help. Select Reset. This deletes the app's data on this PC, including sign-in details and settings. Open the app and set it up again.

These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to repair or reset an app in Windows

Fix 3. Install the latest Microsoft Visual C++ Redistributable, x86 and x64

5 minutesLow riskThe DLL is vcruntime140.dll, vcruntime140_1.dll, msvcp140.dll, ucrtbase.dll, concrt140.dll or an api-ms-win-crt file.

These DLLs belong to the Microsoft C and C++ runtime. Microsoft says the Redistributable on the PC must be at least as recent as the build tools the program was made with. A program built with newer tools asks for functions an older runtime does not have, which is exactly this error.

1. Open Microsoft's page Microsoft Visual C++ Redistributable latest supported downloads on learn.microsoft.com.
2. Download vc_redist.x64.exe and vc_redist.x86.exe. On an ARM64 PC, the x64 package also contains the ARM64 files.
3. Run each file. If it offers Repair, select Repair; otherwise select Install.
4. Restart the PC and start the program again.

The full repair, including .NET: How to repair Microsoft Visual C++ Redistributable and .NET Framework. A closer look at one of these files: the vcruntime140_1.dll guide.

Fix 4. Find and move aside a stray copy of the DLL

15 minutesRead the warningThe path in the window points to another program's folder, or the program brings an old copy of a Windows or Visual C++ DLL, or the program is a developer tool such as Apache httpd.exe.

Windows takes the first copy it finds in its search order: the program's folder, System32, the Windows folder, the current folder, then every folder in PATH. An old copy left by another program or an installer wins over the right one. Moving it aside lets Windows find the correct file.

1. Write down the DLL name and the full path from the window.
2. Press Win + R, type cmd and press Enter.
3. Type this command with your DLL name and press Enter. It lists every copy in the current folder and in the PATH folders.

   where Library.dll

4. Compare the list with the path in the window. A copy in the folder of another program, or in a folder such as C:\Tools or an old PHP or Python folder, is the suspect.
5. If the window named a copy inside the failing program's folder, and the same DLL also exists in C:\Windows\System32, that program copy is the suspect.
6. Close all programs, open the suspect's folder in File Explorer and rename the file, for example from Library.dll to Library.dll.old.
7. Start the failing program again.

Fix 5. Update Windows when the program needs a newer Windows function

30 to 120 minutesLow riskThe DLL is KERNEL32.dll, USER32.dll or another System32 file, and the PC runs Windows 7, 8.1 or an old Windows 10 build.

Programs keep using new Windows functions. On an older Windows the function was never there, so no repair can add it. Microsoft notes that the latest Visual C++ runtime supports only Windows 10 and 11 and Windows Server 2016 and later, so new programs often stop working on older systems.

1. Press Win + R, type winver and press Enter. Note the Windows version and build.
2. Open Settings > Windows Update on Windows 11, or Settings > Update & Security > Windows Update on Windows 10, and select Check for updates.
3. Install every update, restart, and check again until nothing is left.
4. On Windows 10, install the feature update to version 22H2 or move to Windows 11 when it is offered.
5. Start the program again.

• Windows 10 support ended on 14 October 2025. Windows 10 22H2 still runs most programs, but new versions may require Windows 11.
• Windows 7 and 8.1 get no updates. If the program's current version needs a newer Windows, install an older version the maker still lists for your system, or upgrade Windows.
• When updates keep failing: Run the Windows Update troubleshooter

Fix 6. Repair Windows system files with DISM and SFC

20 to 30 minutesNo riskThe DLL is in C:\Windows\System32 or SysWOW64 on current Windows, many programs fail at once, or svchost.exe is in the title.

When a Windows DLL is damaged or replaced by a wrong version, every program that uses it can fail. DISM repairs the store of Windows components, and SFC then replaces damaged system files from that store with the correct version.

1. Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.

   

2. Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

   

3. Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.

   sfc /scannow

   

4. Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

   

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

Fix 7. Undo a recent change with System Restore

20 minutesRead the warningThe error started after a specific day: a Windows update, a driver, a new program or a cleaner tool.

System Restore takes Windows files, drivers, programs and settings back to a restore point, without touching your documents and photos. If a recent install replaced a DLL, going back to a point before it brings the old copy back.

1. Open System Restore. Press Windows+R, type the command below and press Enter. You can also open Control Panel > Recovery > Open System Restore. If a first page opens, select Next.

   rstrui.exe

2. Choose a restore point. Select a restore point from a time before the problem started. The Description often names the event, such as a driver or app install. If the one you need is missing, select Show more restore points (shown only when there are more).

   

3. See what will change. Select Scan for affected programs. The upper list shows programs and drivers that will be removed; the lower list shows those that might come back and may need to be reinstalled. Select Close.

   

4. Start the restore. Select Next, check the summary and select Finish. Windows restarts and applies the restore point. Do not turn the PC off.
5. Check the result. After sign-in Windows reports whether the restore succeeded. Check whether the problem is gone.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Undo recent changes with System Restore

Fix 8. Reinstall Windows in place and keep your files and apps

1 to 2 hoursRead the warningFixes 5 to 7 did not help, many programs show the error, or Windows Setup itself shows Setup.exe - Entry Point Not Found.

An in-place reinstall writes a fresh copy of every Windows file over the old one and keeps your files, apps and most settings. It replaces any damaged or wrong system DLL that SFC could not fix. Starting setup from fresh media also avoids a broken setup file.

1. Open Recovery in Settings. Open Settings > System > Recovery. Next to Fix problems using Windows Update, select Reinstall now. This keeps your apps, files and settings.

   

2. Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
3. Wait and restart. Windows Update downloads and installs a repair copy of your current Windows version. Keep the PC plugged in and online, and restart it when asked.
4. If that did not help: Reset PC. Back in Settings > System > Recovery, next to Reset this PC, select Reset PC. This keeps your personal files but removes installed apps and settings.
5. Choose Keep my files. Select Keep my files. Do not select Remove everything.

   

6. Choose where Windows comes from. Select Cloud download to download a fresh copy of Windows, or Local reinstall to use the files already on the PC (faster, but may not include the latest updates).
7. Reset. Review the summary and select Reset. The PC restarts several times.

These steps were written for Windows 11 22H2 and later. The full page with the other versions and what each result means: Reinstall Windows without losing files

If the Entry Point Not Found error is still there

Collect the facts that decide the next step. Most cases that survive the fixes above are a second copy of the DLL that nobody has found yet, or a program version that needs a newer Windows.

1. Take a photo of the window with the function name and the DLL path visible.
2. Run winver and note the Windows version and build.
3. Note the program's version, from its About page or from Installed apps.
4. Open Event Viewer > Windows Logs > Application and look for an Application Error from the same minute. It names the faulting module, which is often the same DLL.
5. Send these four things to the program's support. They know which DLL version their program needs.

How to keep the Entry Point Not Found error from coming back

The error comes back whenever two halves of a program get out of step. Let updates finish, and keep DLLs where their installers put them.

Frequently asked questions

What does "The procedure entry point could not be located in the dynamic link library" mean?

It means the program asked a DLL for a function by name, and the copy of that DLL Windows loaded does not contain it. The word after "entry point" is the function, and the last line names the DLL. The file is there, but it is a different version from the one the program was built with. That is why reinstalling the program, updating the Visual C++ runtime or removing a stray copy of the DLL usually fixes it, while downloading the DLL from a website usually does not.

Is Entry Point Not Found the same as a missing DLL error?

No. When a DLL is missing, Windows says that the code execution cannot proceed because the file was not found. Entry Point Not Found means the file was found, but it is the wrong version. The fixes overlap, since both are often solved by reinstalling the program or the Visual C++ Redistributable. But for Entry Point Not Found the path in the window matters more, because it shows which copy Windows took. Missing DLL guides on this site, such as the one for xlive.dll, cover the other case.

How do I fix Zoom.exe Entry Point Not Found?

Zoom brings its own DLLs in its program folder, so the usual cause is an interrupted Zoom update that left old and new files together. Uninstall Zoom in Installed apps, restart the PC, download the current installer from Zoom's own website and install it again, as in Fix 1. If the window names a Visual C++ DLL, install the latest Redistributable first (Fix 3). On Windows 7 or an old Windows 10 build, the current Zoom may need a newer Windows; we could not confirm which versions Zoom still supports there.

What about httpd.exe Entry Point Not Found in Apache?

Apache's httpd.exe and its modules load many DLLs, such as the OpenSSL libraries. When PHP, another web stack or an old Apache left different versions of the same files in a folder Windows searches, httpd.exe can pick the wrong one. Run where with the DLL name from the window, as in Fix 4, and look for copies outside the Apache bin folder. Also make sure Apache, PHP and the Visual C++ runtime are all builds for the same architecture, x64 or x86, as their makers state.

Why does svchost.exe show Entry Point Not Found?

svchost.exe is the Windows process that runs services, so this window means a Windows system DLL does not match the rest of Windows. It points to damaged system files or a broken update, not to a single program. Run DISM and SFC (Fix 6) first. If the error started after an update or an install, use System Restore (Fix 7). An svchost.exe outside C:\Windows\System32 or C:\Windows\SysWOW64 is not the Windows file, so scan the PC with Microsoft Defender in that case.

Should I download the DLL from a DLL website?

No. A DLL site cannot know which version your program needs, and the wrong version causes exactly this error. Such files can also be old, changed or carry malware. Placing a downloaded file in System32 can break other programs too. Get DLLs only from the installer of the program they belong to, from the Microsoft Visual C++ Redistributable, or from Windows itself through SFC, DISM or an update.

Does re-registering the DLL with regsvr32 fix it?

No. regsvr32 only registers COM components, by calling a function called DllRegisterServer inside the DLL. It does not change which functions the DLL contains, so it cannot add a missing entry point. Many DLLs are not COM components at all, and regsvr32 then shows its own message that the entry point DllRegisterServer was not found. That message is a different problem, explained in our ExplorerFrame.dll guide. The old version of this page suggested regsvr32, which was wrong.

Can I fix Entry Point Not Found on Windows 7?

Often only partly. Windows 7 left support on 14 January 2020, and Microsoft's latest Visual C++ runtime supports only Windows 10 and 11. Many current programs therefore ask for functions Windows 7 does not have, and the window then names KERNEL32.dll or another system DLL. Reinstalling or repairing cannot add them. Use an older version of the program that its maker still lists for Windows 7, or move to a supported Windows. For program files that are only damaged, Fixes 1 and 3 still work on Windows 7.

The message is in another language. Is it the same error?

Yes. Windows translates the title and the sentence into the language of the PC, so readers in Arabic who search حل مشكلة entry point not found, which means a solution to the problem, see the same window. The program name, the function name and the DLL path are never translated. Read those three, compare them with the table of causes on this page and follow the same fixes.