A DLL file doesn't normally open as an app when you double-click it. To see what's inside one in Windows 11, start with its Properties. Use a code-inspection tool only if you're looking for functions or .NET instructions inside the file.
The right tool depends on the question. A missing-DLL error needs an app repair, a downloaded plugin needs its host program, and a developer inspecting a library needs a viewer that understands that library's format.
In this guide
Choose what you need to see
For a file's publisher, version, or signature, use Windows' file information. For the exported functions in a native library, use DUMPBIN. For a trusted .NET assembly, use ILDASM, the .NET Framework disassembler.
These tools show different things. Exported functions are named entry points another program can call. A .NET assembly contains intermediate instructions and details about the code, which a compatible disassembler can display.

A text editor isn't a useful general DLL viewer. It may show fragments of readable text mixed with symbols because the file contains binary data. Saving changes from that editor can damage the library.
For trouble with an installed app, read the repair section before downloading a developer tool. Opening a library to inspect it doesn't install or repair the program that uses it.
Check the file's Properties first
Open File Explorer and locate the DLL. Right-click it and choose Properties. In Windows 11, use Show more options if the menu arrangement requires it, or press Alt + Enter with the file selected.
On General, check the filename, location and size. On Details, look for the file description, product name and version. Some libraries have little or no version information, so an empty field alone doesn't tell you something is wrong.
If a Digital Signatures tab is present, select a signature and open Details. This can show the signer and signature status. Not every DLL has an embedded signature that appears in that tab.
To check the signature without changing the file, open PowerShell and run this command with your file's actual path:
Get-AuthenticodeSignature -LiteralPath "C:\Example\library.dll" |
Format-List Status, StatusMessage, SignerCertificate
The signature command documentation explains that Windows can retrieve an embedded or catalog signature. NotSigned means no signature was found by that check; it isn't a malware verdict.
Keep unfamiliar files out of developer inspection tools until you know where they came from. I'd ask the sender which application produced the DLL before trying to make sense of an unexpected attachment.
Inspect native DLL exports with DUMPBIN
For a native Windows library, open a Visual Studio developer command prompt with the C++ build tools available. DUMPBIN is a developer tool, so a regular Windows installation may not be set up to run its command.
Run this command with the real path, keeping quotation marks around paths containing spaces:
dumpbin /exports "C:\Example\library.dll"
If the library has exported definitions, the command lists them. It can include names, ordinal numbers and addresses. It doesn't reconstruct the original C or C++ project, comments, or variable names.
Microsoft's DUMPBIN exports reference describes the export information the command displays. Use the list to check for a function that other programs should be able to call in this DLL.
If Windows reports that dumpbin isn't recognized, check that you're in the developer command prompt for an installation containing the C++ tools. Windows can't find the inspection tool; that tells you nothing about the DLL's contents.
If the command reads the library but a function you expect is missing, check the version and the supplier's documentation. Don't rename another DLL to match the expected filename. A matching name won't give it the functions the app needs.
View a trusted .NET assembly with ILDASM
ILDASM shows the intermediate instructions and information about the code in a managed .NET assembly. Use it only with trusted input, as the tool's own instructions require. It isn't the viewer for every file ending in .dll.
From a developer command prompt where ILDASM is available, run:
ildasm "C:\Example\library.dll"
The graphical viewer can display the assembly's structure. Expand the entries to inspect its types and methods. The text shows the code in an intermediate form. It isn't necessarily the original C# or Visual Basic source.
For text output in the command window, use:
ildasm "C:\Example\library.dll" /text
If ILDASM reports a missing or invalid common language runtime header, it can't read the file as a managed .NET assembly. A native DLL can produce that result without being damaged. If it's a native DLL, use the DUMPBIN steps instead.
If ildasm isn't recognized, check your developer installation and its documentation. Installing the regular .NET runtime doesn't necessarily give you this tool. Until the tool runs, that message tells you nothing about the DLL itself.

Use the host app for plugins and repair missing libraries
A DLL supplied as a plugin belongs in the program and location named by its maker. Open that host application and follow its plugin installation instructions. Double-clicking the DLL won't create a standalone version of the plugin.
If a program says a DLL is missing, repair or reinstall that program using its official installer. If it names a runtime package, use the package supplier's supported installation steps rather than a loose DLL download.
The MSVCP140.dll repair guide covers that specific Visual C++ runtime error. It explains why installing the right runtime is different from copying one file into Windows folders.
A file that exists but fails while the program starts needs another route. Use the DLL initialization failure checks when that is the actual message. Inspection alone won't repair the app's startup failure.
Avoid setting a permanent DLL file association or running random regsvr32 commands just to open the file. Registration is an installation step for components that support it. It isn't a way to view any DLL.
If the tool's results still don't answer your question, give the software developer the filename, version, full error, and what you're trying to find out. Ask which host or development tool the library requires.
The Short Version
Use Properties for details, DUMPBIN for native exports, and ILDASM for trusted managed assemblies. Install plugins through their host app. Repair missing-library errors with the app or runtime installer rather than launching the DLL.
Checked November 16, 2026.







