A .dll (dynamic-link library) is a piece of a Windows program: code and resources that one or more programs load while they run. An .exe is a program itself. Neither can be opened like a document - running an unknown one is how computers get infected - but both carry information about themselves that can be read safely: a description, the company and product they belong to, their version, the processor they are built for, a digital signature saying who made them, and the other files they need.
This page reads all of that from the file, without running a line of it, and says in plain words what the file is. It also checks the digital signature against the file: if anything in it has changed since it was signed, by damage or tampering, the page says so. It shows the name in the signing certificate, but cannot confirm the certificate really belongs to that name - Windows does that, under Properties, then Digital Signatures.
- A program says a DLL is missing. Should I download it?
- No - not on its own, and not from "DLL download" websites, whose files are often the wrong version, outdated or infected. A missing DLL belongs to something: reinstall the program that shows the error, or install the package the DLL comes from, from its maker. Files named msvcp140.dll, vcruntime140.dll or mfc140u.dll come with the Microsoft Visual C++ Redistributable; d3dx9_43.dll and xinput1_3.dll with the DirectX End-User Runtime. Dropping a copy of the DLL here shows which program or package it belongs to.
- How can I tell if a DLL or EXE is safe?
- Start with who made it and whether it is signed. Programs from Adobe and other large companies are usually signed, and the page checks that the signature still matches the file; a signed file that has changed since it was signed is a warning sign. The page shows the name in the signing certificate, but anyone can make a certificate with any name, so to confirm who signed it, right-click the file and choose Properties, then Digital Signatures: Windows checks the certificate against the authorities it trusts. Many of Windows' own files carry no signature inside: Windows keeps their signatures in separate catalog files, which that Properties tab, or
Get-AuthenticodeSignature in PowerShell, can check. Being signed is not a guarantee on its own, and an unsigned file is not necessarily harmful - many small programs are unsigned - so for anything doubtful, also scan it with your antivirus before running it. - Is this DLL 32-bit or 64-bit?
- The page says, under its name: x86 for 32-bit, x64 for 64-bit Intel and AMD, or ARM64. A 64-bit program can only load 64-bit DLLs and a 32-bit one only 32-bit DLLs, which is behind many "not a valid Win32 application" and "bad image" errors: on 64-bit Windows, 32-bit DLLs belong in C:\Windows\SysWOW64 and 64-bit ones in C:\Windows\System32.
- Can it show the code inside, or edit it?
- No. A DLL's code is machine code, which needs a disassembler or, for .NET files, a decompiler such as ILSpy to read. This page shows everything the file says about itself, which answers what it is and who made it, and changes nothing.