Do not download a single DLL or paste it into System32. First decide whether only one app fails or several unrelated apps and Windows features fail. Repair or reinstall one affected app from its publisher; install a runtime only when that publisher names the package and architecture. Use DISM followed by SFC only for the Windows or multi-app branch.
1
Start here: record the app and DLL
Close the message, repeat the same action once, and write down the full DLL filename, affected app, and exact trigger. Check whether only that app fails or whether several unrelated apps or Windows features also fail. A DLL name alone does not prove which package or architecture is correct.
2
If it followed a download, scan the installer
Use this branch only when the error began after installing or extracting a new download. Right-click that installer or archive, choose Show more options > Scan with Microsoft Defender, and wait for the result. If Defender reports a threat, stop and obtain a clean installer from the original publisher.
3
If one app fails, repair or reinstall it
Open Settings > Apps > Installed apps. Select More (…) beside the app, open Advanced options, and choose Repair when offered. Otherwise use Control Panel > Programs > Programs and Features > Repair or Change. Retest the original action. If it still fails, preserve local data and license details, uninstall only that app, and reinstall it from Microsoft Store or its original publisher.
4
If the publisher names a dependency, install it
If the app publisher names Microsoft Visual C++, DirectX legacy components, or .NET, follow its required version and architecture and use Microsoft's official download. An x86 app can require the x86 Visual C++ package even on 64-bit Windows. For legacy D3DX, XInput, or XAudio files, use the publisher's prerequisite or Microsoft's DirectX End-User Runtime, never an individual DLL site.
5
If Windows or several apps fail, run DISM and SFC
Use this system branch only when the missing file belongs to Windows or several unrelated apps or Windows features fail. Install Windows updates and restart if requested. Search for Command Prompt, choose Run as administrator, approve the prompt, run DISM.exe /Online /Cleanup-image /Restorehealth, and wait for successful completion. Then run sfc /scannow and wait for 100%.
6
Repeat the original failing action
Reopen the same app and repeat the action recorded in Step 1. Stop when that action completes without the missing-DLL message. A Repair button, reinstall, or completed command is not proof by itself; the original action is the success test.
If it does not work
If the name begins with VCRUNTIME or MSVCP, use the app vendor's prerequisite instructions and match x86, x64, or ARM64; do not guess from the Windows architecture alone.
If the name begins with D3DX or identifies XINPUT1_3.dll or an XAudio component, use the app's prerequisite installer or Microsoft's legacy DirectX runtime, not a copied DLL.
If SFC reports no integrity violations and only one app fails, stop system repair and return to that app's dependency or reinstall path.
If SFC repairs files, restart and retest the exact app. If SFC cannot repair files, follow Microsoft's CBS-log or recovery guidance instead of manually copying a DLL.
If the same message returns immediately after an official reinstall, send the exact DLL name and app version to that publisher's support team.
ⓘ Sources and verification
Checked against official documentation on . Scope: Windows.
Follow the linked first-party guidance if labels differ after a platform update.
