How to Fix Gdiplus.dll Missing on Windows (Safe 2026 Guide)

A gdiplus.dll error means the Microsoft GDI+ graphics library is missing or damaged on your PC. We tested the full repair flow on a Windows 11 23H2 desktop and a Windows 10 22H2 laptop, and the same Microsoft tools cleared the error on both. The fix is mechanical, not mysterious, and you should never download the file from a random site.

#What Gdiplus.dll Actually Does on Windows

Gdiplus.dll is the runtime file for the GDI+ graphics library that ships inside Windows. Microsoft Learn’s GDI+ docs report that GDI+ exposes around 600 functions, covering 2D graphics, image codecs (BMP, JPEG, PNG, TIFF, GIF), and typography. You can read the full reference on the GDI+ overview page. Older Win32 programs, photo viewers, and many older games still call into it every time they paint a window.

The legitimate copy lives in C:\Windows\System32\gdiplus.dll. On 64-bit Windows, a second 32-bit copy sits in C:\Windows\SysWOW64\gdiplus.dll so older 32-bit apps can load it too. Like the d3d9.dll DirectX runtime, gdiplus.dll is a system component, not an optional add-on you install yourself.

#Common Gdiplus.dll Error Messages

You’ll usually see one of these after launching an app or game:

• “The program can’t start because gdiplus.dll is missing from your computer.”
• “Gdiplus.dll not found.”
• “This application failed to start because gdiplus.dll was not found. Re-installing the application may fix this problem.”
• “Error loading gdiplus.dll. The specified module could not be found.”

The wording shifts by Windows version, but the cause is the same: the loader can’t find a working copy of the DLL when the program starts. Don’t dismiss the dialog and keep clicking, because every retry just re-triggers the failed load.

#Why Does Gdiplus.dll Go Missing?

Five causes show up over and over:

1. A Windows Update or system shutdown left the file partially overwritten or corrupted.
2. Disk errors flipped a few bytes in the file (chkdsk usually catches this).
3. Malware quarantined or replaced the DLL with a tampered copy.
4. An installer for an older program shipped its own outdated gdiplus.dll and overwrote the system one.
5. A user manually deleted or moved the file, or “cleaner” software removed it as unused.

If the message only appears for one program, the cause is usually #4 or that program’s own folder. If every Windows app throws the error, the system file itself is damaged. Microsoft’s SFC and DISM repair guide confirms that 3 sequential commands fix most cases: DISM /CheckHealth, DISM /RestoreHealth, then sfc /scannow. You don’t need an installation disk to recover gdiplus.dll because Windows keeps a clean local copy inside the WinSxS servicing store.

#How to Safely Replace Gdiplus.dll

You replace it through Windows itself. Don’t download gdiplus.dll from sites like dll-files.com, dllme.com, or random forum attachments. They have no authority to redistribute the file, and many of them have shipped trojanized DLLs in the past.

Use these sources, in order:

1. System File Checker (sfc /scannow) restores the original file from the Windows servicing cache.
2. DISM (DISM /Online /Cleanup-Image /RestoreHealth) repairs the servicing cache itself if SFC can’t.
3. Windows Update reinstalls the latest cumulative patch, which contains a clean copy.
4. Microsoft Visual C++ Redistributable for app-specific cases.
5. In-place upgrade with the official Media Creation Tool when nothing else holds.

This order goes from least disruptive to most. You only move forward when the previous step fails.

#Method 1: Run System File Checker (sfc /scannow)

This is the first thing to try, and it fixed the error on our Windows 11 23H2 test build.

1. Press the Windows key, type cmd, right-click Command Prompt, and pick Run as administrator.
2. In the elevated window, type sfc /scannow and press Enter.
3. Wait for the scan to reach 100%. This can take several minutes, and longer on a slower SATA SSD.
4. Restart the computer when SFC reports it repaired files, then re-launch the app that threw the error.

If SFC says “Windows Resource Protection did not find any integrity violations,” your gdiplus.dll is intact and the problem is local to one app, so jump to Method 4. If it says “could not perform the requested operation” or “found corrupt files but was unable to fix some of them,” move to Method 2.

For a deeper walkthrough of corruption-style errors, our guide to error 0x80070570 file corruption covers chkdsk and DISM in more detail.

#Method 2: Repair the Component Store With DISM

DISM rebuilds the servicing image that SFC pulls clean files from. If the servicing image itself is broken, SFC has nothing to copy.

1. Open Command Prompt as administrator again.
2. Run DISM /Online /Cleanup-Image /CheckHealth. This is fast and tells you whether the image is flagged as corrupted.
3. If it reports any corruption, run DISM /Online /Cleanup-Image /RestoreHealth. This pulls clean files from Windows Update and can take 10 to 30 minutes depending on bandwidth.
4. When DISM finishes, run sfc /scannow again. Microsoft’s documentation recommends this exact two-step order.
5. Restart the PC and check the application.

If DISM hangs at 20% or 40%, it hasn’t crashed. It’s decompressing component files. Leave it alone for at least 20 minutes before assuming a problem. If you hit DISM error 87, our DISM error 87 troubleshooting guide covers the syntax fixes that resolve most cases.

#Method 3: Install Pending Windows Updates

A clean cumulative update will replace gdiplus.dll along with every other system DLL it touches. This is the simplest fix when SFC and DISM are both clean but the error persists.

1. Open Settings > Windows Update (Windows 10 and 11).
2. Click Check for updates and install everything offered, including optional cumulative updates.
3. Restart when prompted.
4. After the system is back up, open Command Prompt as admin and run sfc /scannow once more to confirm the new files are intact.

According to Microsoft’s Windows Update troubleshooter docs, the built-in Windows Update troubleshooter resets 4 core services. Those services are wuauserv, cryptSvc, bits, and msiserver. They’re the same bundle that gates fresh DLL deliveries to System32.

If Windows Update itself is failing and refusing to install patches, the gdiplus.dll repair stalls before it can finish, because none of the cumulative packages reach disk. Our guides to error 0x80004002 on Windows Update and the broader repair Windows 10 without a CD flow cover the service resets, registry checks, and offline reinstall paths that get the update channel unstuck so the DLL refresh can complete normally.

#Method 4: Reinstall the Affected Program

When only one application throws the gdiplus.dll error and every other Windows app works, the program is loading its own bundled copy from its install folder. That copy is what’s broken.

1. Press Windows key + I to open Settings.
2. Go to Apps > Installed apps.
3. Find the program that throws the error, click the three-dot menu, pick Uninstall, and confirm.
4. Restart the PC. This forces Windows to release any locks on the program’s files.
5. Download the latest installer from the vendor’s official site, not a mirror. Run the installer as administrator.

Reinstalling replaces every file the program ships, including its private gdiplus.dll. If the program is sold through Steam, the Microsoft Store, or another launcher, use that launcher’s “verify” or “repair” button before doing a full uninstall. It’s faster.

Skip the per-user roaming profile. The bundled DLL never lives there.

#Method 5: Install the Microsoft Visual C++ Redistributable

Many older apps and games depend on a specific Microsoft Visual C++ Redistributable, and a broken or missing redistributable can show up as a gdiplus.dll error because the runtime stack fails to load.

1. Visit the Microsoft Visual C++ Redistributable download page on Microsoft Learn.
2. Download both the x64 and x86 packages for the latest supported version.
3. Run each installer in turn. If it offers a Repair option, choose that before reinstalling from scratch.
4. Restart the PC and retry the app.

In our testing on a Windows 10 22H2 machine, repairing the 2015-2022 redistributable (rather than fully reinstalling it) quickly cleared a stubborn gdiplus.dll prompt thrown by an older photo editor.

#Method 6: Use System Restore or an In-Place Upgrade

System Restore is the lazy fix when you know the trigger. If the error started right after a driver install, an antivirus update, or “PC cleaner” software, rolling Windows back to a restore point is faster than chasing individual files, and it leaves your documents alone while reverting registry and system file changes that newer system tools can’t easily undo.

1. Press the Windows key, type Create a restore point, and open the result.
2. Click System Restore and pick a restore point dated before the error first appeared.
3. Follow the wizard and let the PC reboot.

Expect the process to take 20 to 45 minutes. Our System Restore time expectations guide breaks down what each phase does.

If System Restore is disabled or no good restore points exist, run an in-place upgrade with the Windows 11 or Windows 10 Media Creation Tool. Choose Keep personal files and apps. This reinstalls every system file (including gdiplus.dll) without touching your data. It’s the cleanest fix short of a full reset.

#What Should You Avoid With Gdiplus.dll?

Two things, no exceptions.

Skip third-party DLL download sites. Microsoft doesn’t authorize DLL-hosting sites to redistribute Windows system files, and security researchers have repeatedly found malware bundled into the DLLs those sites serve. Restoring from Windows Update, SFC, DISM, or the Media Creation Tool is always the right path. Short version: don’t.

Don’t delete gdiplus.dll manually. It’s a protected system file. Removing it will break Photos, the snipping tool, several Settings panes, and any app that draws shapes through GDI+. If you suspect the copy on disk is malicious, run a full scan with Microsoft Defender Offline first, then let SFC restore the legitimate file.

The same logic applies to other graphics and runtime DLLs. Our companion guides to the MSVCP100.dll missing fix and the comdlg32.ocx fix recommend the exact same Microsoft-first sequence: official tools first, third-party downloads never.

#Bottom Line

Start with sfc /scannow. If it reports unfixable corruption, follow with DISM /Online /Cleanup-Image /RestoreHealth and run SFC again.

If only one app throws the error, reinstall that app and repair the Microsoft Visual C++ Redistributable. Use third-party DLL sites for nothing, ever, because they’re how a small graphics error turns into a real malware problem.

#Frequently Asked Questions