Start with these checks
Before changing Windows, write down:
- The exact program, game, launcher, or Python application showing the error.
- Whether the message appears at startup, during installation, or when importing a package.
- Whether the calling application is 64-bit.
- Whether the file is missing or exists beside the program’s executable.
- Whether the problem began after an update, antivirus quarantine, cleanup, migration, or CUDA removal.
cudart64_100.dll is an NVIDIA CUDA Runtime library for the CUDA 10.0 runtime family. The 64 indicates a 64-bit Windows library, while 100 identifies CUDA 10.0. It is not a normal Windows component, so repairing Windows alone usually will not restore it.
What cudart64_100.dll belongs to
This file can be installed in either of two ways:
- A CUDA-enabled application bundles the runtime beside its own executable.
- The NVIDIA CUDA Toolkit installs the runtime as part of its CUDA 10.0 components.
NVIDIA’s CUDA 10.0 Windows package identifies the runtime as cudart_10.0. A normal toolkit installation uses a path similar to:
C:Program FilesNVIDIA GPU Computing ToolkitCUDAv10.0
The file may instead be inside the application’s installation directory. That is common because software developers can redistribute the CUDA Runtime with their program. Different applications may therefore use different runtime builds, and a newer CUDA installation is not automatically a replacement for the CUDA 10.0 runtime expected by an older application.
The safest repair is usually to repair or reinstall the program that reports the error. If you installed or develop CUDA software directly, use NVIDIA’s official CUDA Toolkit 10.0 archive and its matching Windows installer rather than a generic DLL download.
#1 Best Overall
- AI Performance: 767 AI TOPS
- OC mode: 2632 MHz (OC mode)/ 2602 MHz (Default mode)
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- A 2.5-slot design maximizes compatibility and cooling efficiency for superior performance in small chassis
Fix 1: Repair or verify the affected application
This is the fastest and most likely solution when a game, creative application, scientific program, or launcher suddenly reports the missing file.
Windows Store or packaged application
- Open Settings.
- Select Apps.
- Select Installed apps.
- Find the affected application.
- Select the three-dot menu beside it.
- Choose Advanced options.
- Select Repair.
- Start the application again.
If Repair does not help, return to the same page and select Reset, if available. Reset can remove the application’s local data, so use it only after checking whether the program stores important settings or projects locally.
A successful repair lets the application start without the cudart64_100.dll message. If the error remains, uninstall the application from Settings > Apps > Installed apps, restart Windows, and install it again from the publisher’s official installer or the official launcher.
Traditional desktop application
- Press Windows key + R.
- Enter:
appwiz.cpl
- Press Enter.
- Select the affected program.
- Choose Repair, Change, or Modify if the installer provides one.
- Follow the repair wizard.
- Restart Windows and test the application.
For a game or launcher, open its settings and look for Verify files, Repair, or Scan and repair. This replaces files supplied by that application without mixing unrelated CUDA versions into Windows.
If verification reports damaged files but cannot repair them, uninstall the program, restart Windows, and reinstall it from its official source. Do not copy cudart64_100.dll into the game folder from a random website.
Fix 2: Restore the matching CUDA 10.0 runtime
Use this step when the application documentation specifically requires CUDA 10.0, when you installed CUDA software yourself, or when repairing the application does not include its runtime.
NVIDIA’s archived Windows package is CUDA Toolkit 10.0.130. Download the Windows installer from NVIDIA’s official CUDA 10.0 archive, not from a DLL-indexing site. The archive includes the network installer commonly named cuda_10.0.130_win10_network.exe.
Rank #2
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5070 Ti
- Integrated with 16GB GDDR7 256bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
During installation:
- Close the CUDA application and related development tools.
- Right-click the NVIDIA CUDA installer.
- Select Run as administrator.
- Allow the installer to check system compatibility.
- Choose the recommended installation mode unless your development setup requires custom components.
- Ensure the CUDA Runtime or toolkit components are selected.
- Complete the installation.
- Restart Windows.
- Start the affected program again.
This does not mean every CUDA application needs the complete toolkit. Many programs package only the runtime they require. Installing the toolkit is most appropriate when the application expects a system CUDA installation or when you develop CUDA software.
Do not assume CUDA 10.1, 10.2, or a current CUDA release supplies the exact runtime expected by a CUDA 10.0 application. CUDA Runtime libraries do not guarantee binary compatibility across runtime versions. Installing a newer release may leave the original error unchanged or create a version conflict.
Fix 3: Check whether antivirus removed the file
Windows Security or another antivirus product may quarantine a legitimate application file after an update or a change in detection rules. Do not restore a file automatically. First confirm that it belongs to a known application and came from a trusted installer.
- Open Windows Security from the Start menu.
- Select Virus & threat protection.
- Select Protection history.
- Review recent quarantined items.
- Open an entry related to the affected application.
- Check its path and detection details.
- If it is clearly part of a legitimate installation, follow the available Restore or Allow on device action.
- Reinstall the application instead if the source or file identity is uncertain.
- Start the program again.
If the file is restored but disappears again, do not repeatedly disable antivirus protection. Update the security product, obtain a clean installer from the application publisher, and contact that publisher if its signed files are being detected incorrectly.
Fix 4: Check the application architecture
A 64-bit application normally needs the 64-bit CUDA runtime represented by cudart64_100.dll. A 32-bit program cannot use that file simply because it has the same name pattern.
Recommended Free Tools
Check the program’s architecture where its publisher documents it. You can also inspect the executable with a trusted development or diagnostic tool. Do not rename another file, such as a different CUDA runtime generation, to make it appear to be cudart64_100.dll.
If the program is 32-bit, it may require a 32-bit CUDA runtime with a different filename. If it is 64-bit, it needs a compatible 64-bit runtime. Repairing the application is preferable because its installer knows which architecture and CUDA generation belong together.
Rank #3
- Powered by the NVIDIA Blackwell architecture and DLSS 4. System Requirements: Minimum 850W PSU with 16-pin 12V-2x6 (12VHPWR) connector required. Verify before purchasing.
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability. Compatibility: 348mm (13.7") length, 3.6 slots, 4.3 lbs. Confirm case clearance and slot spacing. GPU bracket included.
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.6-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
Fix 5: Check the NVIDIA driver separately
The CUDA Runtime DLL and the NVIDIA display driver are related but different components. Installing or updating a graphics driver is not guaranteed to restore cudart64_100.dll.
Check the installed driver:
- Right-click the Start button.
- Select Device Manager.
- Expand Display adapters.
- Double-click the NVIDIA adapter.
- Open the Driver tab.
- Note the driver provider, date, and version.
- Select Update Driver if you need to check Windows Update.
- For a clean or specific version, use the driver package supplied by NVIDIA for your GPU and Windows installation.
- Restart Windows and test the application.
CUDA 10.0.130 documentation lists Windows driver version 411.31 as a minimum for that toolkit. A later driver is generally intended to support applications built with older CUDA versions, but the application’s own requirements remain important.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11If Device Manager shows a warning icon, the adapter is disabled, or the driver is missing, repair the driver before troubleshooting the runtime further. If the adapter is working normally and only the DLL is missing, return to application repair or the matching CUDA installation.
Manually checking driver versions and repeating installs can involve hunting through hardware IDs and package variants. Outbyte Driver Updater offers a free scan that shows which drivers are outdated; the repair or driver installation is handled by the full version, and NVIDIA’s official driver package remains the appropriate source for this CUDA-related case.
Fix 6: Repair Visual C++ only when the message names it
The Microsoft Visual C++ Redistributable is not a replacement for cudart64_100.dll. Install or repair it only if the next error names a file such as:
VCRUNTIME140.dllMSVCP140.dll- Another
MSVCPorVCRUNTIMEfile
Use Settings > Apps > Installed apps, find the Microsoft Visual C++ Redistributable entry, select its menu, choose Modify, and then choose Repair if offered. If the application publisher specifies a particular redistributable, use Microsoft’s official package.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →A Visual C++ repair can fix a dependency needed by the application, but it will not create the NVIDIA CUDA Runtime DLL.
Fix 7: Run DISM and SFC for Windows corruption
Use these commands when Windows itself is behaving abnormally, protected system files are damaged, or several unrelated Windows components are failing. They normally do not replace an application-bundled CUDA file.
Rank #4
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5060
- Integrated with 8GB GDDR7 128bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
- Open Start.
- Type Command Prompt.
- Right-click Command Prompt.
- Select Run as administrator.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for it to finish.
- Then run:
sfc /scannow
- Restart Windows.
- Test the application.
A message stating that no integrity violations were found means protected Windows files passed the scan. It does not prove that the CUDA installation is complete. If either command reports repairs, restart and test again. If the DLL error remains, repair or reinstall the calling application.
Running repeated scans without knowing what changed is tedious, especially when the missing file belongs to a third-party program. Outbyte PC Repair offers a free scan that identifies reported system problems; repairs are performed by the full version, while reinstalling the affected application remains the definitive fix when its private CUDA runtime is missing.
Why regsvr32 is not a fix
Do not run this command against cudart64_100.dll:
regsvr32 cudart64_100.dll
regsvr32 is for DLLs that expose COM registration entry points such as DllRegisterServer. The CUDA Runtime is a normal runtime dependency, not normally a self-registering COM component. Registering it cannot install a missing runtime and may produce an entry-point error.
Likewise, do not copy the file into:
C:WindowsSystem32
C:WindowsSysWOW64
The correct location is normally the application directory or the CUDA toolkit’s own bin directory, as determined by the installer. A global copy can make one program load the wrong version and break another.
If the file exists but still will not load
“Specified module could not be found” does not always mean the named DLL is absent. Windows may be unable to load a dependency used by that DLL.
Check the following:
- Open the application’s installation folder.
- Confirm the file is beside the executable when the publisher documents local runtime deployment.
- Confirm the application and runtime architecture match.
- Repair the application rather than replacing only the DLL.
- Check whether the error names a Visual C++ runtime or another dependency.
- Confirm the NVIDIA driver is installed and the GPU appears normally in Device Manager.
- Avoid adding random CUDA folders to the global
PATH. - If the program is launched from Python, a launcher, or an IDE, test it through the supported environment rather than a different shell with a modified PATH.
If every repair fails, record the executable name, complete error text, application version, CUDA requirement, GPU model, driver version, and whether the DLL exists beside the executable. The application publisher is the authoritative source for a private, patched, or bundled runtime.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsWhy random DLL downloads are unsafe
Avoid downloading cudart64_100.dll from an arbitrary DLL website. The file may contain malware, belong to the wrong CUDA build, use the wrong architecture, or be incompatible with the application. Third-party listings also do not establish one universal file size, checksum, or version for every installation.
Use the application publisher’s installer or NVIDIA’s official CUDA Toolkit 10.0 archive. Restore an antivirus-quarantined file only after verifying its source and identity.
Best Value
- Powered by the NVIDIA Blackwell architecture and DLSS 4 OC mode: 2640MHz/Default mode: 2610MHz (Boost Clock)
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.125-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
Frequently asked questions
Is cudart64_100.dll a Windows file?
No. It is an NVIDIA CUDA Runtime library used by CUDA-enabled software. Windows does not normally provide it through System32, SysWOW64, Windows Update, SFC, or DISM.
Does installing NVIDIA graphics drivers fix it?
Not necessarily. The display driver supports communication with the GPU, while the CUDA Runtime DLL is supplied by the application or CUDA Toolkit. Repair the application first.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Do I need the full CUDA Toolkit?
Only if the application or development workflow requires a system CUDA installation. Many applications bundle their own runtime and do not need the complete toolkit.
Can CUDA 11 or another newer version replace CUDA 10.0?
Do not assume so. The application may require the CUDA 10.0 runtime specifically, and runtime compatibility is not guaranteed between generations.
Should I install both 32-bit and 64-bit versions?
No. Match the runtime to the calling application. cudart64_100.dll indicates a 64-bit runtime; installing unrelated architectures can add confusion without repairing the program.
What if the error appeared after a program update?
Run the program’s Verify, Repair, or Scan and repair function, then reinstall it if necessary. An incomplete update is a common reason for a bundled runtime to disappear.
Free tools Windows power users keep installed
One-click scans. No signup required.
Can System Restore help?
It can help after a confirmed recent system change, provided a suitable restore point exists. Open Settings > System > Recovery > Open System Restore, choose a restore point, and follow the wizard. Back up important data first, and prefer application repair when only one program is affected.
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.
