What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
python36.dll is a genuine Python 3.6 runtime DLL, but it is not a Windows system file. If python36.dll is missing or cannot load, repair the program that requested it rather than downloading a replacement and copying it into System32.
The safest order is to identify the calling application, repair or reinstall that application, then check its architecture and Microsoft Visual C++ runtime. These steps cover Windows 11 and Windows 10.
As an Amazon Associate I earn from qualifying purchases.
What python36.dll is
python36.dll belongs to CPython 3.6 for Windows. It may be installed with a normal Python installation, embedded inside a Python-based application, or bundled with software built using PyInstaller.
The name identifies the Python version:
python36.dllbelongs to Python 3.6.- Python 3.8 uses
python38.dll. - Python 3.9 uses
python39.dll.
Installing the newest Python release does not automatically repair an application that specifically requests python36.dll.
#1 Best Overall
The file may appear beside python.exe and pythonw.exe, inside an application’s installation folder, or in a PyInstaller temporary extraction directory. It normally does not belong in C:WindowsSystem32 or C:WindowsSysWOW64.
Python 3.6.8 was the final bugfix release for the Python 3.6 branch, which is now end-of-life. Use it only when an older application requires it, and prefer updating that application to a supported release if the vendor provides one.
Fix 1: Identify the program requesting the DLL
Time needed: 2 to 5 minutes
Do not begin by searching for python36.dll on the internet. First record the complete error and the path shown in it.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallLook for clues in:
- The title bar of the error.
- The executable path shown in the message.
- The program that you launched immediately beforehand.
- A game launcher, installer, utility, or startup notification.
- Windows Security protection history.
- A recent update, cleanup, profile migration, or change of installation folder.
If the error appears during startup, identify the program that Windows is trying to launch:
- Press
Ctrl+Shift+Escto open Task Manager. - Select Startup apps.
- Look for an entry associated with the error.
- Right-click it and choose Open file location, when available.
- Note the application name and folder.
You can also inspect Settings > Apps > Installed apps and search for recently installed or recently changed software. If the error appears only when opening a game or utility, that program is usually the owner of the missing DLL.
A program may request Python even when Python is not visible in the Start menu. Many applications include their own private Python runtime, and PyInstaller packages can contain Python files without installing Python system-wide.
Fix 2: Repair or reinstall the owning application
Time needed: 5 to 20 minutes
This is the most likely fix when the error belongs to a bundled application, game, installer, or Python-based utility.
First close the affected program. Then:
- Open Settings.
- Select Apps > Installed apps.
- Find the program named in the error.
- Select the three-dot menu beside it.
- Choose Advanced options, if available.
- Select Repair and wait for Windows to finish.
- Start the program again.
If there is no Repair option, use the application’s own installer or launcher. For a game, open its launcher and use Verify, Repair, or Verify integrity of game files before reinstalling the entire game.
If repair does not work:
- Back up any application-specific data.
- Uninstall the affected program from Settings > Apps > Installed apps.
- Restart Windows.
- Download the installer from the application’s official vendor.
- Install it into its normal location.
- Start it before restoring custom files or plugins.
Do not copy only an executable from another computer. An application may require its DLL, standard library, configuration files, and additional runtime dependencies together.
Fix 3: Restore a normal Python 3.6 installation
Time needed: 10 to 20 minutes
Use this step only when the error is associated with Python itself, a script launcher, or a program that documents Python 3.6 as a requirement.
Download Python 3.6.8 only from the official Python release page. Choose the installer architecture required by the calling application:
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Use x86 for a 32-bit application.
- Use x86-64 for a 64-bit application.
A 64-bit version of Windows can run 32-bit applications, so 64-bit Windows does not mean that every application needs 64-bit Python.
During installation:
- Right-click the official installer and select Run as administrator.
- Select Repair if the installer offers it.
- Otherwise remove the damaged Python 3.6 installation from Settings > Apps > Installed apps.
- Run the installer again.
- Enable the option to add Python to
PATHonly if the application or your command-line workflow requires it. - Finish the installation and restart the affected program.
Open Command Prompt and check which Python Windows finds:
where python
python --version
A working Python 3.6 installation should report a 3.6 version. If where python points to a deleted folder, an old launcher, or a different Python installation, repair the application’s configuration or reinstall the required version.
Do not rename python39.dll, python38.dll, or another runtime to python36.dll. Different Python ABI versions are not interchangeable.
Recommended Free Tools
Fix 4: Install the correct Microsoft Visual C++ runtime
Time needed: 5 to 10 minutes
An error stating that Python DLL loading failed, or that “the specified module could not be found,” does not always mean that python36.dll itself is absent. Windows may be unable to load a dependency required by that DLL.
Python’s embedded distribution does not include the Microsoft C runtime. The application installer is normally responsible for providing it, but a failed installation or cleanup can remove it.
Use Microsoft’s official Visual C++ Redistributable page and install the architecture matching the application:
- Install the x86 redistributable for a 32-bit application.
- Install the x64 redistributable for a 64-bit application.
On 64-bit Windows, a 32-bit application still needs the x86 runtime.
After installation:
- Restart Windows.
- Start the affected application.
- If it still fails, use the owning application’s Repair option or reinstall it.
The Visual C++ runtime is not a universal fix. If the application’s private copy of python36.dll was deleted, only repairing or reinstalling that application will restore the correct file.
Fix 5: Check PyInstaller and bundled applications
Time needed: 5 to 15 minutes
PyInstaller applications often carry their own Python DLL. A one-folder build may require python36.dll and other files beside the executable. A one-file build may extract its contents into a temporary folder whose name begins with _MEI.
If the error comes from a PyInstaller application:
- Return the executable to the complete folder supplied by the developer.
- Do not run only the EXE after moving it away from its supporting files.
- Delete an incomplete copy and extract or reinstall the complete package.
- Check Windows Security protection history for a quarantined file.
- Start the application again.
If you are the developer, rebuild the application with the correct architecture and distribute the complete output directory for an onedir build. For a one-file build, check temporary extraction permissions and whether security software is blocking the extracted runtime.
A PyInstaller error can say LoadLibrary: The specified module could not be found even when the named DLL is present. That message can describe a missing dependency, an architecture mismatch, or a blocked extraction.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteFix 6: Check architecture and application paths
Time needed: 5 to 10 minutes
A 32-bit executable cannot load a 64-bit python36.dll, and a 64-bit executable cannot load a 32-bit copy.
Check the application’s documentation or installer for x86 and x64 requirements. If the program is older, it may require 32-bit Python even on a 64-bit Windows installation.
Also check whether the application was moved:
- Right-click the program shortcut.
- Select Properties.
- Review the Target path.
- Confirm that the target folder still exists.
- Use Open File Location if available.
- Restore the program to its original folder or reinstall it.
PATH affects command-line discovery, but many applications load private DLLs from their own directory. Adding a random folder to PATH will not reliably repair a broken application.
If an old startup entry points to a deleted Python program, inspect Settings > Apps > Startup and Task Scheduler. Remove or repair the obsolete application rather than placing a DLL in a system folder.
Fix 7: Check antivirus quarantine
Time needed: 5 to 10 minutes
Security software can quarantine a bundled runtime after an update or a false positive.
- Open Windows Security.
- Select Virus & threat protection.
- Choose Protection history.
- Look for the affected application’s folder or
python36.dll. - Confirm the file belongs to a trusted installer before taking action.
Restore a quarantined file only when you can verify the application’s source and installation path. If there is any doubt, do not restore it. Reinstall the application from its official vendor instead, then run a security scan.
Do not permanently disable antivirus protection to make the program start.
Fix 8: Update Windows and relevant drivers
Time needed: 10 to 30 minutes
Drivers do not normally provide python36.dll, but updating Windows and relevant device drivers can help when the failure began after a system change or when the application also reports graphics, audio, or hardware initialization errors.
For Windows updates:
- Open Settings > Windows Update.
- Select Check for updates.
- Install available updates.
- Restart the computer.
For a device driver:
- Right-click Start and open Device Manager.
- Expand the relevant category, such as Display adapters.
- Right-click the device.
- Select Update driver.
- Choose Search automatically for drivers.
- Restart Windows if a driver was installed.
Outbyte Driver Updater can scan for outdated drivers when manually checking hardware categories is time-consuming; its free scan identifies what needs attention, while driver installation is handled by the full version. It is optional, and reinstalling the application remains the definitive fix when that application owns python36.dll.
Fix 9: Repair Windows components with DISM and SFC
Time needed: 15 to 30 minutes
Because python36.dll is not a Windows component, system repair is less likely to solve an application-specific installation problem. Use it after repairing the application and checking its dependencies.
- Open Start.
- Type
Command Prompt. - Right-click Command Prompt.
- Select Run as administrator.
- Run this command first:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for it to complete.
- Then run:
sfc /scannow
- Restart Windows and test the application.
Microsoft recommends running DISM before SFC. If either command reports that it could not complete, install pending Windows updates and repeat the repair once. Do not use SFC or DISM to justify downloading a replacement DLL from an untrusted source.
Outbyte PC Repair can reduce the manual work of hunting through repair results and repeating DISM or SFC without knowing what changed; its free scan shows detected issues, while repair is handled by the full version. It is optional and does not replace reinstalling the specific application that owns the DLL.
Free tools Windows power users keep installed
One-click scans. No signup required.
What not to do
Do not download python36.dll from a random DLL website
A downloaded file may contain malware, the wrong Python patch build, the wrong architecture, or incompatible dependencies. It may also leave the original application damaged.
Use the official application installer, the official Python 3.6.8 installer when Python itself is required, and Microsoft’s official Visual C++ Redistributable downloads.
Do not copy it into System32 or SysWOW64
The DLL normally belongs beside the application or Python executable that loads it. Global copying can create version conflicts and exposes Windows to unsafe DLL-loading behavior.
Do not use regsvr32
regsvr32 is intended for DLLs that expose registration entry points such as DllRegisterServer, commonly used by COM or ActiveX components. python36.dll is a Python runtime DLL, not normally a self-registering component. Registering it is not a repair.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Likely causes and the correct fix
| Cause | Correct response |
|---|---|
| The application’s private DLL was deleted | Repair or reinstall that application |
| Python 3.6 was removed or damaged | Install the required official Python 3.6.8 architecture |
| A dependency is missing | Install the matching Visual C++ Redistributable |
| x86 and x64 files are mixed | Reinstall the architecture required by the application |
| A PyInstaller folder is incomplete | Restore the complete folder or rebuild the package |
| Antivirus quarantined the file | Verify the source, then restore or reinstall |
| The executable was moved | Return it to its original folder or reinstall |
| Windows components are damaged | Run DISM, then SFC |
FAQ
Is python36.dll safe?
It is a legitimate CPython 3.6 runtime file when it comes from Python or a trusted application installer. A copy found in an unexpected folder should be scanned and verified rather than trusted automatically.
Does Windows include python36.dll?
No. Windows does not normally supply this Python runtime DLL, and Windows Update does not install the Python interpreter itself.
Why does an app request it when Python is not installed?
The application may bundle Python internally. Packaged programs, installers, games, and PyInstaller applications can request the DLL without showing Python as a separate installed program.
Will installing the latest Python fix the error?
Not necessarily. An application linked specifically to Python 3.6 requires python36.dll, not a newer versioned DLL.
Should I use System Restore?
Use System Restore only if the failure began after a known change and application repair, dependency repair, and reinstalling did not work.
What should I provide when asking for further help?
Record the exact error, full path shown, application name, Windows version, application architecture, and the change that occurred immediately before the failure. Also state whether repair, reinstalling, the matching Visual C++ runtime, antivirus review, and DISM/SFC changed the result.
Quick Recap
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.
