physxcooking.dll Missing: Restore PhysX Files Safely on Windows

physxcooking.dll is a PhysX game-runtime file, not a Windows system file. The safest first fix is to verify or repair the affected game’s files through its launcher, because this DLL is commonly installed beside the game that needs it.

Do not download a loose copy from a random DLL website, place it in System32 or SysWOW64, or run regsvr32 against it. Those actions can install the wrong architecture or version and usually do not restore the other PhysX or Microsoft runtime files the game also needs.

As an Amazon Associate I earn from qualifying purchases.

Fix 1: Verify the affected game’s files

Time needed: 5 to 15 minutes, plus any download time.

This is the most likely solution when only one game reports physxcooking.dll as missing. The file may have been removed during a failed update, damaged on disk, deleted by a mod, or quarantined by antivirus software.

Game launchers normally compare installed files with their original package and download missing or damaged files into the correct folder.

Steam

1. Open Steam.
2. Select Library.
3. Right-click the affected game.
4. Select Properties.
5. Select Installed Files.
6. Select Verify integrity of game files.
7. Wait for the scan and replacement process to finish.
8. Start the game again.

Steam may report that some files were reacquired. That is expected when the missing DLL belongs to the game.

Epic Games Launcher

1. Open Epic Games Launcher.
2. Select Library.
3. Find the affected game.
4. Select the three dots beside the game.
5. Select Manage.
6. Select Verify.
7. Wait for the process to complete.
8. Launch the game again.

Other launchers usually provide a similarly named Verify, Repair, Scan, or Check files command. Look in the game’s menu rather than copying a file manually.

How to tell whether verification worked

The repair succeeded if:

• the game launches normally;
• the missing-file message no longer appears; or
• the launcher reports that files were repaired and the game starts afterward.

If verification completes but the same error returns immediately, continue with the antivirus check below. If verification repeatedly downloads the same file, the game folder may be damaged, locked, or being cleaned by security software.

Fix 2: Check antivirus quarantine

Time needed: 5 to 10 minutes.

Security software can remove a genuine game DLL after an update or after the file changes. Check quarantine before reinstalling several runtimes.

Windows Security

1. Open the Start menu.
2. Type Windows Security.
3. Open Windows Security.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review recent detections.
7. Look for an entry mentioning the game folder or physxcooking.dll.
8. Open the detection details.

Only restore the file if you recognize the game installation and trust its original source. Microsoft explains the available actions in Protection history.

After restoring a trusted file:

1. Run the game launcher’s file verification again.
2. Start the game.
3. Watch Protection history to see whether the file is quarantined again.

Do not restore a copy that came from a DLL download sites website. If the detection returns, do not repeatedly approve it. Run a full scan and investigate why the file is being detected. Microsoft provides additional scanning guidance through Microsoft Defender.

Avoid adding a broad exclusion for your entire Downloads folder or system drive. If an exclusion is eventually necessary for a trusted game, limit it to the game’s installation folder and only after the launcher has repaired the files.

Fix 3: Reinstall the game’s bundled PhysX files

Time needed: 15 minutes to several hours, depending on the game size and connection speed.

If verification does not help, reinstall the affected game from its official launcher or original installation media. This is the definitive repair when the file is part of the game’s private runtime.

Before reinstalling:

1. Confirm that saved games are synchronized or backed up.
2. Note any installation options or expansion content.
3. Remove unofficial DLL replacements or modified executable files.
4. Restart Windows.
5. Uninstall the game through its launcher or through Settings.
6. Restart Windows again if the uninstaller requests it.
7. Install the game again from its official source.
8. Launch it before reinstalling mods or patches.

Some older games include runtime installers in folders named:

• _CommonRedist
• Redist
• Support
• __Installer
• DirectX
• PhysX

Open the game’s installation folder and inspect those directories. Run only installers supplied with the original game. Do not replace a file with a higher-numbered version found elsewhere.

If the game still fails after a clean reinstall, the issue may involve a system-wide PhysX runtime, Visual C++ dependency, permissions, or an incompatible modification.

Fix 4: Install the official NVIDIA PhysX runtime

Time needed: 10 to 20 minutes.

Some games use PhysX files installed system-wide instead of carrying every required library in the game folder. For those games, install NVIDIA’s official PhysX System Software 9.21.0713 package.

Use NVIDIA’s official PhysX System Software download page, not a third-party DLL site. The package is intended for older PhysX applications and supports several PhysX SDK generations, including the 2.x range associated with many copies of physxcooking.dll.

After downloading the official installer:

1. Close the game and its launcher.
2. Right-click the PhysX installer.
3. Select Run as administrator.
4. Accept the license terms.
5. Choose the normal installation option unless the installer offers a repair option.
6. Let the installation finish.
7. Restart Windows.
8. Run the game’s file verification again.
9. Start the game.

Installing the system-wide runtime does not guarantee that a missing game-local physxcooking.dll will return. If the game was designed to ship its own copy beside the executable, repairing or reinstalling the game remains the correct fix.

When to use PhysX Legacy

Very old games may require NVIDIA PhysX Legacy System Software 9.13.0604. NVIDIA identifies this package for games using older PhysX SDK releases, including the 2.7.0-and-earlier range and 2.7.2.

Use the Legacy package when:

• the game’s installer specifically includes it;
• the game’s documentation identifies PhysX Legacy;
• the game is from an older release period and the standard runtime does not resolve the error; or
• the game’s bundled installer is clearly labeled as a legacy PhysX package.

Do not install Legacy as a universal replacement for the normal PhysX package. It may install alongside other versions, but it will not correct a missing or damaged game-local file by itself.

Fix 5: Install the Visual C++ runtime required by the game

Time needed: 10 to 20 minutes.

physxcooking.dll is not part of Microsoft Visual C++ Redistributable. However, the game may need both PhysX and an older Visual C++ runtime.

This matters when the error says:

• “The specified module could not be found.”
• “There was a problem starting physxcooking.dll.”
• “The code execution cannot proceed.”
• the file exists, but the game still refuses to start.

Windows can report a DLL as missing when a dependency used by that DLL is missing. Microsoft describes this dependency behavior in its documentation about DLL search order.

Check the game’s _CommonRedist, Redist, or __Installer folder first. If it includes a Visual C++ installer, use that installer.

If no installer is included, use Microsoft’s official packages:

• Visual C++ 2008 SP1 Redistributable
• Visual C++ 2010 SP1 Redistributable

Install the architecture that matches the game:

• A 32-bit game normally needs the x86 package.
• A 64-bit game needs the x64 package.
• A 32-bit game on 64-bit Windows still needs x86 Visual C++.

Microsoft explains this application-based architecture rule in its supported Visual C++ downloads.

Install both x86 and x64 packages only when the affected computer runs programs of both architectures or the game’s installer requests both. Restart Windows after installation and try the game again.

Do not assume that installing the newest Visual C++ package replaces every older runtime. Older applications can depend on specific runtime generations.

Fix 6: Install legacy DirectX components only when required

Time needed: 10 to 20 minutes.

DirectX is separate from PhysX. Installing DirectX will not normally restore physxcooking.dll, and PhysX will not restore missing legacy DirectX files.

Use Microsoft’s DirectX End-User Runtime when the game also reports files such as:

• d3dx9_*.dll
• xinput1_3.dll
• xaudio2_7.dll

To install it:

1. Download the DirectX End-User Runtime from Microsoft.
2. Run the installer.
3. Accept the license terms.
4. Choose a temporary extraction folder if requested.
5. Open that folder.
6. Run the included setup program.
7. Restart Windows.
8. Start the game again.

Do not install DirectX merely because the PhysX filename looks like a graphics component. Use it when the game identifies a missing DirectX dependency or includes the runtime in its original installer.

Fix 7: Confirm the game is using the correct architecture

Time needed: 10 minutes.

The bare filename physxcooking.dll is commonly associated with a 32-bit PhysX build. The known public versions are commonly reported as 32-bit files, including:

File	Reported architecture	Reported versions
physxcooking.dll	32-bit	2.8.4.6, 2.8.4.5, 2.8.4.4, 2.8.3.43

These version details identify files seen in circulation. They are not a universal list of the correct file for every game.

A 64-bit Windows installation can run a 32-bit game through Windows compatibility support. The game still needs its 32-bit DLLs and 32-bit dependencies.

Do not substitute:

• PhysXCooking64.dll for physxcooking.dll;
• PhysX3Cooking_x86.dll for a PhysX 2.x file;
• PhysX3Cooking_x64.dll for a 32-bit file; or
• a file from another game simply because the names look similar.

These names represent different architectures or PhysX generations. The game’s original installer is the authority.

If the error says “not designed to run on Windows”

This message usually points to one of these problems:

• the DLL is corrupted;
• the DLL has the wrong architecture;
• a companion dependency is mismatched;
• the file was copied from another PhysX release; or
• the installation was modified.

Do the following in order:

1. Delete unofficial replacement files from the game folder.
2. Run the launcher’s file verification.
3. Reinstall the game if verification does not replace the file.
4. Install the Visual C++ package included with the game.
5. Check whether antivirus software altered the file.
6. Restart Windows and test again.

If the error includes 0xc000007b, do not keep copying DLLs. That code commonly indicates a 32-bit and 64-bit component mismatch or corrupted dependency. Reinstall the game’s original redistributables and use the architecture required by the game.

Fix 8: Run the game with appropriate permissions

Time needed: 5 to 10 minutes.

A game installed in a protected folder, synchronized folder, or drive with restrictive permissions may fail to read its own runtime files.

First, launch the game normally. If it fails:

1. Open the game’s installation folder.
2. Find the game’s main .exe file.
3. Right-click it.
4. Select Properties.
5. Open the Compatibility tab.
6. Select Run this program as an administrator.
7. Select Apply.
8. Select OK.
9. Start the game.

If that works, the issue may involve permissions or a launcher that does not have access to the game directory. It is usually better to repair the folder permissions or move the game to a normal local library than to permanently run every program as administrator.

Also check:

• whether the game is installed on a disconnected external drive;
• whether cloud synchronization is locking or replacing files;
• whether the installation folder is read-only;
• whether the drive has enough free space; and
• whether the game was moved without using the launcher’s move function.

Do not manually change permissions on the entire system drive. Work only with the specific game folder.

Fix 9: Update or reinstall the graphics driver when PhysX itself is damaged

Time needed: 20 to 45 minutes.

A graphics driver repair is not the first step for one missing game-local DLL. Consider it when:

• several PhysX games fail;
• the NVIDIA PhysX installation is damaged;
• the problem began immediately after a driver update;
• the game fails after repairing its own files; or
• other graphics applications also report initialization errors.

Check the installed driver in Device Manager

1. Right-click the Start button.
2. Select Device Manager.
3. Expand Display adapters.
4. Double-click your graphics adapter.
5. Open the Driver tab.
6. Note the provider, date, and version.
7. Select Update Driver.
8. Select Search automatically for drivers.

If Windows reports that the best driver is already installed, check the graphics-card manufacturer’s official support page for a driver compatible with your model and Windows version.

Reinstall the driver

1. Close running applications.
2. Download the correct driver from the graphics-card manufacturer.
3. Run the installer.
4. Choose a clean or custom installation option if it is offered.
5. Include the PhysX component when the installer lists optional components.
6. Restart Windows.
7. Test the affected game.

Device Manager can also remove the current device:

1. Open Device Manager.
2. Expand Display adapters.
3. Right-click the graphics adapter.
4. Select Uninstall device.
5. Choose removal of the driver package only if you have already downloaded a replacement and understand the installer’s options.
6. Restart Windows.
7. Install the downloaded driver.

Do not remove the display adapter without having a recovery plan if the computer depends on a specialized driver. If every PhysX application fails, also reinstall the official PhysX System Software after the graphics driver installation.

Manually checking dozens of driver versions can be tedious, especially when it is unclear whether the driver or PhysX component changed. Outbyte Driver Updater can scan for outdated drivers and show what it found; the repair or driver installation is handled by the full version, and it is not required to repair a game-local DLL.

Fix 10: Repair Windows components with DISM and SFC

Time needed: 15 to 40 minutes.

SFC and DISM do not normally recreate a deleted physxcooking.dll, because that file belongs to a game rather than protected Windows system files. Use them when Windows itself is unstable, other protected files are failing, or the game reports broader component errors.

Microsoft recommends running DISM before SFC. Use an administrator Command Prompt.

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

DISM /Online /Cleanup-Image /RestoreHealth

1. Wait for it to complete.
2. Then run:

sfc /scannow

1. Wait until verification reaches 100 percent.
2. Restart Windows.
3. Run the game launcher’s file verification again.

Microsoft’s full instructions are in System File Checker guidance.

Possible results include:

• Windows Resource Protection did not find any integrity violations: protected Windows files appear intact.
• Windows Resource Protection found corrupt files and successfully repaired them: restart and test again.
• Windows Resource Protection found corrupt files but was unable to fix some of them: run DISM again, restart, and review Microsoft’s repair guidance.
• DISM reports that source files could not be found: confirm that Windows Update is working and try again.

Do not interpret a clean SFC result as proof that the game’s PhysX files are correct. Return to launcher verification or reinstall the game.

If you prefer a guided scan while working through repeated Windows repair commands, Outbyte PC Repair can show detected system issues; its repair function requires the full version, and reinstalling the affected game remains the definitive fix for a missing game-owned DLL.

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

Fix 11: Install Windows updates

Time needed: 10 to 30 minutes, plus restart time.

Install available Windows updates when the problem began after a system change or when multiple older applications are failing.

1. Open Settings.
2. Select Windows Update.
3. Select Check for updates.
4. Install available updates.
5. Restart Windows, even if the update screen does not require it.
6. Test the game.

Microsoft documents this process in Install Windows updates.

Windows Update will not normally supply a missing private game copy of physxcooking.dll. Its purpose here is to correct broader Windows compatibility or servicing problems.

Fix 12: Use System Restore after a recent system change

Time needed: 20 to 45 minutes.

Use System Restore only when the error began immediately after a driver installation, runtime change, Windows update, or other system modification and a suitable restore point exists.

1. Press Win+R.
2. Type:

rstrui.exe

1. Press Enter.
2. Select Next.
3. Choose a restore point created before the problem began.
4. Select Scan for affected programs if available.
5. Review the list.
6. Select Next.
7. Select Finish.
8. Let Windows restart and complete the restoration.

System Restore normally preserves personal files, but it can roll back drivers, settings, system files, and installed programs. Microsoft explains the process in System Restore.

After restoration, verify the game files again. If the game was installed or updated after the restore point, its launcher may need to repair the installation.

Why regsvr32 is normally wrong for this file

Time needed: 1 minute to avoid an unnecessary repair attempt.

Do not run:

regsvr32 physxcooking.dll

regsvr32 is intended for DLLs that provide a registration entry point such as DllRegisterServer. Microsoft documents that requirement in its regsvr32 documentation and DllRegisterServer documentation.

physxcooking.dll is a runtime library loaded by the game. It is not normally a COM or ActiveX registration component. Running regsvr32 commonly produces an error about a missing entry point or registration failure, without repairing the game.

If the file exists but Windows still says it is missing

A file can be visible in the game folder while Windows still reports:

The specified module could not be found.

That message can mean that a dependency of physxcooking.dll is missing. Check the game folder for companion files such as:

• PhysXCore.dll
• PhysXLoader.dll
• PhysXDevice.dll
• msvcr90.dll
• msvcp90.dll
• msvcr100.dll
• msvcp100.dll

The exact files vary by game. Do not download each missing name separately.

Use this order:

1. Run the launcher’s file verification.
2. Install the Visual C++ redistributable included with the game.
3. Install the official DirectX runtime only if the game identifies a legacy DirectX file.
4. Install the appropriate official NVIDIA PhysX package.
5. Check antivirus Protection history.
6. Inspect the game’s logs for a more specific module name.
7. Use a dependency-analysis tool if you are comfortable interpreting its results.

Microsoft provides general DLL troubleshooting guidance.

If the file exists in the wrong folder, that is also a problem. A game may search its own executable directory and selected runtime folders, not arbitrary locations elsewhere on the disk.

Why random DLL downloads are unsafe

A DLL download sites site may provide:

• the wrong PhysX generation;
• the wrong 32-bit or 64-bit architecture;
• a file with missing companion dependencies;
• a modified or malicious binary;
• a version that causes entry-point errors; or
• a file that works temporarily but breaks another game.

Microsoft also warns that unsafe DLL search paths can create version conflicts and DLL-preloading risks in its guidance on DLL security.

The safe sources are:

• the affected game’s official launcher verification;
• the game’s original installer;
• a redistributable installer bundled with the game;
• the official NVIDIA PhysX System Software package; and
• official Microsoft Visual C++ or DirectX installers when those dependencies are identified.

Manual copying is appropriate only when the source is one of those trusted installers, the file matches the game’s architecture and PhysX generation, and the game’s original layout confirms where it belongs.

What probably caused the error

The cause is easier to identify by looking at the scope of the failure.

What you observe	More likely cause	Best next step
Only one game fails	Missing or damaged game-local file	Verify or reinstall that game
Several PhysX games fail	Damaged system-wide PhysX installation or driver	Install official PhysX software and repair the driver
Error began after an update	Failed launcher update or changed dependency	Verify files, then reinstall bundled runtimes
File disappeared after a scan	Antivirus quarantine	Review Protection history and verify the game
File exists but loader still fails	Missing dependency or wrong architecture	Install matching runtables and inspect dependencies
Error includes 0xc000007b	Architecture mismatch or corruption	Restore original files and matching x86 or x64 runtimes
Error says “not designed to run on Windows”	Corruption, mismatch, or bad dependency	Reinstall from the official source
Mods or an unofficial patch were recently installed	Altered executable or incompatible file set	Disable modifications and verify files
Game was moved to another drive	Broken path, permissions, or incomplete move	Use the launcher’s move or repair function

Older games may carry private PhysX libraries beside their executable, while others depend on a system-wide installation. Different games can therefore need different PhysX files at the same time. Replacing one game’s copy with another game’s copy is not a reliable solution.

FAQ

What is physxcooking.dll?

It is a PhysX geometry-cooking runtime library. PhysX cooking converts collision geometry into a form that the game can load and use efficiently.

Is physxcooking.dll part of Windows?

No. It is game middleware distributed by the game or installed through a PhysX runtime package. It is not normally a protected Windows system file.

Is it part of Visual C++, DirectX, or .NET?

No. Visual C++, DirectX, .NET, and PhysX are separate components. A game may require more than one of them.

Which games use it?

Older PhysX-powered games may ship or request it. Reports have involved games including Dragon Age 2, Crazy Machines 2, and Mass Effect 3, but the exact PhysX build can differ between games.

Should I install PhysX System Software?

Install the official standard PhysX System Software when the game depends on a system-wide PhysX runtime or its bundled installer requests it. If the missing file belongs directly to one game, verify or reinstall that game first.

Do I need PhysX Legacy?

Only when the game requires the older PhysX SDK range or includes the Legacy installer. Legacy is not a universal replacement for a missing game-local DLL.

Why does a 64-bit Windows computer need a 32-bit DLL?

Because Windows architecture and application architecture are separate. A 32-bit game normally needs 32-bit PhysX and Visual C++ files even when Windows itself is 64-bit.

Can I use PhysXCooking64.dll instead?

No. It is a separate filename and architecture. It is not a substitute for physxcooking.dll.

Can I copy physxcooking.dll into System32?

No. The game normally expects its private copy in the game directory or an installer-managed runtime location. Copying it into a Windows folder can create version conflicts and security risks.

Why does the error remain after I put the file back?

The file may have a missing dependency, the wrong architecture, or a damaged companion PhysX library. Verify the complete game installation instead of replacing DLLs individually.

Do SFC and DISM restore this file?

Normally no. They repair protected Windows components. Use the game launcher or original installer to restore a game-local PhysX file.

When should I use Device Manager?

Use it when several games fail, the problem began after a graphics-driver change, or other graphics applications show errors. It is not usually necessary for one missing game DLL.

What is the final decision?

If one game fails, verify that game and reinstall its bundled runtimes. If several PhysX games fail, install the official PhysX System Software and repair the graphics driver. If the file exists but the loader still fails, investigate Visual C++, DirectX, architecture, antivirus quarantine, and dependent modules rather than downloading another copy.

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.