Missing DLL errors

chrome_elf.dll

This file belongs to Supplied with Google Chrome. Install that package and the DLL arrives with it, in the right place and correctly registered.

If the file is already there and Windows still complains, read the message again: “entry point not found” is a different problem from a missing file, and installing the runtime again will not solve it.

And if the box says RUNDLL rather than naming a program, the fix runs the other way: something left an instruction behind pointing at a file that is meant to be gone, so restoring the file is the wrong move.

Do not download this DLL on its own

Searching for a missing DLL by name leads to sites that hand you that single file. It is one of the oldest and most effective malware delivery methods there is, and a system DLL from an unknown source is indistinguishable from a deliberately modified one. There is never a legitimate reason to obtain a runtime component that way.

The same goes for the tools that offer to do it for you: what a DLL repair tool can and cannot actually fix.

What it is

An early-loading Chrome component that sets up crash reporting and blocklists before the browser starts. It ships inside the Chrome installation folder.

Where you see it: Chrome refusing to start after a failed update, or after antivirus removed a file from the Chrome directory.

Reinstalling Chrome over the top restores it. If you want the full standalone installer rather than the web stub, it is listed on our Chrome page with its SHA-256.

Install Supplied with Google Chrome

The official package, with the download URL Microsoft declares and the SHA-256 of every installer so you can verify it before running.

After downloading you can check the file against our index to confirm it is the installer the publisher shipped.

More DLL errors we cover