comdlg32.dll Missing: Trace the Windows Repair Path Safely

Start with this diagnostic checklist

comdlg32.dll is a Windows system library, and errors involving it usually mean Windows or an application cannot load the Common Dialog Box Library. Before changing anything, note:

• Which program shows the error
• Whether one program fails or several Windows applications fail
• Whether the problem began after an update, crash, cleanup utility, antivirus action, application installation, or disk problem
• Whether the message says comdlg32.dll or COMDLG32.OCX
• Whether Windows is 64-bit and the affected application is 32-bit
• Whether the application launcher offers Repair, Verify files, or Scan and repair

The safest repair is not downloading a replacement DLL. Install pending Windows updates, then run DISM followed by System File Checker. This restores Windows component files from trusted servicing sources.

As an Amazon Associate I earn from qualifying purchases.

What comdlg32.dll does

comdlg32.dll is part of Microsoft Windows, not a Visual C++ Redistributable, DirectX package, .NET runtime, game, or ordinary third-party application. Microsoft describes it as part of the Windows Dynamic-Link Library system and the Common Dialog Box Library.

Applications use its Windows APIs for standard tasks such as:

• Opening a file
• Saving a file
• Selecting a printer
• Choosing a font or color
• Displaying common Windows dialog boxes

For example, Microsoft documents the GetOpenFileName API as requiring Comdlg32.dll. If this system component is missing, corrupted, the wrong architecture, or blocked by another failure, an application may stop during startup.

The file is supplied with the Microsoft Windows operating system and is published by Microsoft Corporation. Its internal description may appear as DLL-fil med vanliga dialogrutor on some systems.

Where Windows stores the file

On 64-bit Windows, the normal locations are:

C:WindowsSystem32comdlg32.dll
C:WindowsSysWOW64comdlg32.dll

The names are counterintuitive:

• System32 normally contains the native 64-bit system DLLs on 64-bit Windows.
• SysWOW64 normally contains the 32-bit system DLLs used by 32-bit applications.
• Windows uses WOW64 file-system redirection so 32-bit programs access the correct system components.

Do not copy the file from one folder to the other. A 32-bit program does not need a 64-bit DLL simply because Windows is 64-bit, and placing an incompatible file beside an application can create a different loading error.

Exact versions and file sizes vary with the Windows release, architecture, servicing level, build, and sometimes language packaging. Historical examples include Windows versions using 64-bit builds in the 10.0 and 6.x families, but those values are not universal requirements for current Windows installations. A matching name and approximate size do not prove that a replacement is correct.

What the error message means

Common messages include:

• “This application failed to start because comdlg32.dll was not found.”
• “The code execution cannot proceed because comdlg32.dll was not found.”
• “Cannot find COMDLG32.dll.”
• “comdlg32.dll is missing from your computer.”
• “The application or DLL is not a valid Windows image.”
• “The application or DLL is not designed to run on Windows.”

A “not found” or “missing” message usually means the loader could not locate or access the required file. It can result from Windows component corruption, deletion, quarantine, an application-specific loading problem, or an architecture mismatch.

A “not a valid Windows image” or “not designed to run on Windows” message can indicate corruption, an incompatible architecture, a damaged dependency, or a problem with another file. It is not proof that comdlg32.dll alone is corrupt.

If the message names COMDLG32.OCX, stop following the DLL repair steps and read the OCX section below. These are different files.

Fix 1: Install Windows updates and restart

Pending servicing updates can repair or replace Windows components. They can also provide the source files DISM needs.

Windows 11

1. Open Start.
2. Select Settings.
3. Choose Windows Update.
4. Select Check for updates.
5. Install all available updates.
6. Restart when Windows requests it.
7. Test the program again.

Windows 10

1. Open Start.
2. Select Settings.
3. Choose Update & Security.
4. Open Windows Update.
5. Select Check for updates.
6. Install the available updates.
7. Restart the computer.
8. Test the affected application.

If Windows Update fails, record the error and continue with DISM. Do not download comdlg32.dll from a search result as a workaround.

Fix 2: Run DISM, then System File Checker

This is the primary repair sequence for a genuinely missing or damaged Windows copy of comdlg32.dll. Microsoft recommends running DISM first because it repairs the component store that System File Checker uses as a repair source.

Open an elevated Command Prompt

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

Run this command exactly:

DISM.exe /Online /Cleanup-image /Restorehealth

Press Enter and allow it to finish. The scan may remain at one percentage for a while. Do not close the window just because progress appears slow.

When DISM completes successfully, run:

sfc /scannow

Wait until verification reaches 100 percent. Then restart Windows and test the application.

How to interpret SFC

SFC may report that:

• It found no integrity violations
• It found corrupt files and repaired them
• It found corrupt files but could not repair some of them

If SFC repaired files, restart and test again. If it found no violations but the application still fails, the problem may belong to the application, a dependency, the user profile, or COMDLG32.OCX rather than the Windows copy of comdlg32.dll.

If SFC cannot repair everything, run DISM again after checking that Windows Update works. Microsoft’s repair guidance also explains how to review the CBS log and use a matching Windows installation source when Windows Update cannot provide the required files. The source must correspond appropriately to the installed Windows edition and build.

Repeating SFC without checking what it reported rarely adds useful information. Outbyte PC Repair can reduce the manual work by showing what its free scan finds, while repair actions are performed by the full version. It is optional, and Microsoft’s DISM and SFC tools remain the authoritative first repair path.

Fix 3: Decide whether Windows or one application is broken

The number of affected programs is an important clue.

If many programs fail

If several unrelated applications cannot open files, save files, print, or start, suspect Windows component damage. This is especially likely if File Explorer dialogs also malfunction or the problem began after:

• A failed Windows update
• An unexpected shutdown or crash
• A disk problem
• A cleanup utility
• Malware removal
• A broader group of missing DLL errors

Complete the Windows Update, DISM, and SFC steps above. Also back up important files if you suspect storage failure.

If many unrelated DLLs are missing, do not replace them one at a time. That pattern points more toward component-store damage, disk failure, malware, or an incomplete Windows installation.

If only one program fails

A single failing application usually deserves application-level troubleshooting before replacing Windows files.

1. Open Settings.
2. Select Apps.
3. Open Installed apps on Windows 11, or Apps & features on Windows 10.
4. Select the affected program.
5. Choose Advanced options if available.
6. Try Repair.
7. If Repair does not help, use Reset only if you understand that it may remove the program’s local settings.
8. Otherwise uninstall and reinstall the application from its original publisher or installation media.

For games, open the launcher and use its file-repair function. In Epic Games Launcher, the documented path is Library, select the three dots beside the game, choose Manage, and select Verify.

If the application has its own Repair, Verify files, or Scan and repair option, use that before copying any DLL. A damaged installation may be missing several files even when the error names only comdlg32.dll.

Fix 4: Check Windows Security quarantine

Antivirus software can quarantine a file after detecting a threat or during malware remediation. Quarantine is possible, but it should not be assumed without checking Protection History.

Review Protection History

1. Open Start.
2. Type Windows Security.
3. Open the app.
4. Select Virus & threat protection.
5. Choose Protection history.
6. Review recent detections involving the affected application or Windows system files.

Do not restore a file merely because its name is comdlg32.dll. First check:

• The detection name
• The file path
• Whether the file is digitally signed by Microsoft
• Whether the detection is associated with a trusted Windows location
• Whether the application itself may have been compromised

If the detection is unclear, leave the item quarantined and run a full scan. Restoring a genuinely malicious file can expose the system again. After any confirmed malware incident, change important passwords from a trusted device and continue with Windows repair only after the system has been scanned.

Fix 5: Check whether the error is really COMDLG32.OCX

comdlg32.dll and COMDLG32.OCX are unrelated files with similar names.

COMDLG32.OCX is an old 32-bit Visual Basic 6 ActiveX control distributed with applications or the VB6 runtime extended files. Legacy software may show messages such as:

• “Component COMDLG32.OCX or one of its dependencies not correctly registered”
• Runtime error 339
• “Component not correctly registered”

If the error names COMDLG32.OCX:

1. Confirm the exact filename in the error.
2. Use the affected application’s Repair option if available.
3. Reinstall the application from its original vendor.
4. Obtain the supported VB6 runtime extended files through the application vendor’s supported installation method.
5. Contact the application vendor if its installer does not register the control correctly.

Do not substitute comdlg32.dll for COMDLG32.OCX. Do not copy an OCX from an unrelated computer merely because the filenames look similar.

COMCTL32.OCX is another different legacy control. Treat it as a separate application dependency.

Fix 6: Check 32-bit and 64-bit compatibility

A 32-bit application on 64-bit Windows normally uses the 32-bit system components through SysWOW64. A native 64-bit application uses the 64-bit components through System32.

A mismatch can occur when:

• An old 32-bit program expects a 32-bit component
• A manually copied DLL has the wrong architecture
• An installer placed a private DLL beside the program
• A damaged application dependency is being reported as a Windows DLL failure

Do not copy a 64-bit comdlg32.dll into a 32-bit program folder. Do not copy a downloaded DLL into System32 or SysWOW64. Windows servicing should restore its own copies.

To identify the application’s architecture, check the publisher’s documentation or installation details. Many older applications are 32-bit even when running on 64-bit Windows.

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

Fix 7: Do not register comdlg32.dll with regsvr32

regsvr32 is not a general-purpose DLL repair command. It applies to DLL or OCX files that expose registration entry points such as DllRegisterServer.

comdlg32.dll is a normal Windows API library loaded through its exported functions. It is not repaired by registration. Running:

regsvr32 comdlg32.dll

may produce an error such as “DllRegisterServer was not found.” That result does not mean the file needs a different registration command.

Registration may be relevant to an old OCX such as COMDLG32.OCX, but only when the application vendor’s installation instructions require it and the correct 32-bit registration environment is used. Do not apply OCX instructions to the Windows DLL.

Fix 8: Investigate a recent system change

If the error began immediately after an update, driver installation, cleanup operation, or other system change, System Restore may be appropriate.

Use System Restore

1. Open Start.
2. Type Create a restore point.
3. Open the matching Control Panel result.
4. Select System Restore.
5. Choose a restore point dated before the error began.
6. Select Next.
7. Review the affected programs and drivers.
8. Select Finish and allow Windows to restart.

System Restore rolls back system files, registry settings, drivers, and installed programs. It does not normally remove personal documents, but review the affected-program list before continuing.

If the issue started after a driver update, first use the hardware or application publisher’s supported rollback option. Device Manager can also show recent driver details:

1. Right-click Start.
2. Select Device Manager.
3. Expand the relevant device category.
4. Right-click the device and select Properties.
5. Open the Driver tab.
6. Use Roll Back Driver if Windows offers it.

A driver is not a normal cause of a missing comdlg32.dll, so update drivers only when the timing and symptoms point to a driver or device problem. Avoid installing unrelated driver packages just because a DLL error appeared.

When manually checking a long list of device manufacturers and driver versions is the problem, Outbyte Driver Updater can show what its free scan identifies, while driver installation is handled by the full version. It is optional, and the device manufacturer or Windows Update remains the preferred source when a specific driver is known to be involved.

Fix 9: Check the user profile and application logs

If the program works in another Windows account, the original profile may have damaged settings or permissions.

Create a temporary local Windows user and test the application there. This is a diagnostic comparison, not proof that comdlg32.dll is missing.

Also check:

• The application’s own crash log
• Event Viewer under Windows application error entries
• The application’s dependency or startup diagnostics
• Whether the program uses a private DLL beside its executable

If only one profile fails, repair or recreate the application’s settings rather than replacing a system DLL.

Fix 10: Escalate when DISM and SFC cannot repair Windows

If Windows Update, DISM, and SFC do not resolve a system-wide problem, use the least destructive recovery option that fits the evidence.

Possible escalation paths include:

1. Review SFC and DISM results for the specific failure.
2. Retry repair using a matching Windows installation source when supported.
3. Use System Restore if a suitable restore point exists.
4. Perform an in-place Windows repair installation.
5. Back up personal files and use Windows recovery or Reset if repair installation is unavailable.

Windows 11 recovery options may include reinstalling the current Windows version while preserving apps, documents, and settings where that feature is available. Read the choices carefully before confirming.

If the computer has disk errors, repeated crashes, many unrelated missing files, or signs of malware, address that underlying problem first. Replacing one DLL will not repair failing storage or a damaged Windows installation.

Why random DLL downloads are unsafe

Do not download comdlg32.dll from a random DLL website and place it into System32, SysWOW64, or an application folder.

A loose DLL download may have:

• The wrong architecture
• The wrong Windows build
• The wrong language or servicing level
• A modified or malicious payload
• A broken digital signature
• Dependencies that are also missing

It may also conceal the real cause, such as application corruption, quarantine, or component-store damage. Microsoft does not provide a normal standalone “latest comdlg32.dll” download for end users. Windows Update, DISM, SFC, application repair, and Windows recovery are the authoritative repair paths.

Microsoft documents manual replacement only as an advanced fallback using a known-good copy from the same Windows version. That is not the normal solution for a consumer system and should not be replaced with an anonymous internet download.

Frequently asked questions

Is comdlg32.dll part of Visual C++?

No. It is a Windows Common Dialog Box Library component. Reinstalling Visual C++, DirectX, or .NET is not a logical first fix unless the error names a different dependency.

Should I download comdlg32.dll?

No. Use Windows Update, DISM, and SFC. A download site cannot establish that a file matches your Windows build or is malware-free.

Why is the file in System32 on 64-bit Windows?

Despite its name, System32 normally contains native 64-bit system files on 64-bit Windows. The 32-bit system files are normally under SysWOW64.

Can I fix it with regsvr32?

Usually not. comdlg32.dll is not repaired by registration. regsvr32 is relevant only to components that expose registration behavior, such as some legacy OCX files.

Why does only one program show the error?

The program may have a damaged installation, a private dependency, an incompatible add-on, or a launcher file problem. Repair, verify, or reinstall that program before modifying Windows.

What if the error says COMDLG32.OCX?

That is a different 32-bit Visual Basic 6 component. Repair or reinstall the original legacy application and follow its supported runtime instructions. Do not substitute comdlg32.dll.

What if SFC says it found no problems?

The Windows copy may be intact. Check the application installation, exact error filename, 32-bit compatibility, antivirus history, event logs, and whether the issue occurs in another user account.

When should I use System Restore?

Use it when a suitable restore point predates the failure and the problem followed a known system change. Review which applications and drivers will be affected before confirming.

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.