shimgvw.dll Won’t Load: Repair Windows Imaging Safely

shimgvw.dll errors usually mean Windows cannot load an older imaging component, not that you need to download a replacement file. The safest repair is to identify what is calling shimgvw.dll, then repair Windows components before considering legacy registration or recovery.

You may see one of these messages:

• The program can't start because shimgvw.dll is missing from your computer.
• The system cannot find the file specified.
• LoadLibrary("shimgvw.dll") failed - The system cannot find the file specified.
• Error loading C:WINDOWSsystem32shimgvw.dll
• shimgvw.dll is either not designed to run on Windows or it contains an error.
• Missing entry: ImageView_Fullscreen
• Cannot register shimgvw.dll

Which fix applies to you

Use the symptom that most closely matches your situation:

As an Amazon Associate I earn from qualifying purchases.

• Windows or several programs report the error: repair Windows with DISM and SFC.
• The file exists in System32, but the error remains: check dependencies, architecture, and the program or command that called it.
• Only one old image viewer or application fails: repair or reinstall that application and its file association.
• The problem began after an update, driver installation, or application change: use System Restore after checking system files.
• Microsoft Defender quarantined the file: inspect Protection history before restoring anything.
• You are using a 64-bit system: distinguish native files in System32 from 32-bit files in SysWOW64.
• You are considering regsvr32: use it only for older Windows installations where legacy registration genuinely applies.
• You found a DLL download page: do not use it as the first repair. A copied file can be the wrong build, architecture, language, or dependency set.

What is shimgvw.dll

shimgvw.dll is a genuine Microsoft Windows system DLL. Its description is Windows Picture and Fax Viewer, the legacy image-viewing component associated with older Windows releases.

Microsoft documents Shimgvw.dll as implementing Windows image-viewer functionality, with Windows XP as the minimum supported client for the relevant API. It was used by Windows Picture and Fax Viewer and by later image-viewing, printing, and file-association operations. Microsoft also documents calls to the DLL through rundll32.exe, including the ImageView_PrintTo entry point.

The component is most strongly associated with Windows XP, Vista, and Windows 7, and it can also matter to older applications or legacy associations on some Windows 8, Windows 8.1, and Windows 10 installations. Do not assume that every Windows 10 or Windows 11 installation contains or uses it in the same way.

Typical locations are:

%SystemRoot%System32shimgvw.dll
%SystemRoot%SysWOW64shimgvw.dll

On 64-bit Windows, System32 normally contains native 64-bit system files, while SysWOW64 contains 32-bit system files. The names are confusing, but copying a file between these folders is not a safe repair.

The file is part of the Microsoft Windows operating system, not a Visual C++ runtime, DirectX package, or .NET component. Installing those redistributables is therefore not the correct first response.

Why the error can appear when the file exists

A visible shimgvw.dll does not prove that Windows can load it. Windows may fail before the DLL starts because:

• a dependency required by the DLL is missing or inaccessible;
• the calling program has the wrong architecture;
• the file belongs to another Windows build;
• the file is damaged despite having the correct name;
• a legacy file association points to an invalid entry point;
• antivirus software quarantined or modified a related file;
• the application is using an incorrect search path;
• the error is being raised by an old program that expects behavior no longer present on the current installation.

A documented Microsoft Q&A incident showed a shimgvw.dll load failure where the target file existed but a dependency, including gdiplus.dll, could not be resolved. That is why manually replacing the named DLL often does not solve the actual problem.

Fix 1: Install updates, then repair Windows

This is the correct first fix when the error affects Windows Explorer, thumbnails, several programs, or more than one image type.

Install pending Windows updates

1. Press Windows key + I to open Settings.
2. Select Windows Update.
3. On Windows 10, select Update & Security, then Windows Update.
4. Select Check for updates.
5. Install available quality, security, and servicing updates.
6. Restart the computer, even if Windows does not immediately require it.
7. Test the original action, such as opening an image or starting the affected program.

If the error remains, repair the component store and protected system files.

Run DISM

1. Select Start.
2. Type cmd.
3. Right-click Command Prompt and select Run as administrator.
4. Approve the User Account Control prompt.
5. Enter this command:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Press Enter.
2. Wait for the operation to finish. Do not close the window because the percentage may pause for some time.

DISM repairs the Windows component store that supplies replacement files to Windows servicing tools. A successful result normally reports that the restore operation completed successfully.

If DISM reports that it cannot find source files, confirm that the computer is connected to the internet, restart it, install pending updates, and run the command again. If it still fails, continue to SFC and then use Windows recovery options rather than downloading a replacement DLL.

Run System File Checker

After DISM finishes, use the same elevated Command Prompt and enter:

sfc /scannow

Press Enter and wait until verification reaches 100 percent.

The result will usually fall into one of these categories:

• Windows Resource Protection did not find any integrity violations: protected files are not visibly corrupted. Continue with dependency, association, and architecture checks.
• Windows Resource Protection found corrupt files and successfully repaired them: restart Windows and test the original operation.
• Windows Resource Protection found corrupt files but was unable to fix some of them: restart, run DISM again, and repeat SFC. If it still cannot repair the files, move to System Restore or Windows recovery.
• The scan cannot run: restart and try again from an elevated Command Prompt.

Outbyte PC Repair can show what changed when repeatedly hunting through Windows repairs is becoming difficult. Its free scan identifies reported problems, while repair actions are handled by the full version; it is optional, and DISM and SFC remain the normal Microsoft repair path.

Restart and verify the result

Restart after SFC completes. Then test the exact action that produced the error:

• open the same image file;
• open a folder that previously showed blank thumbnails;
• start the same legacy program;
• print or send the same image;
• repeat the command that reported the DLL failure.

If the error disappears, do not copy additional DLLs into Windows folders. The servicing tools repaired the protected component or a related dependency.

Fix 2: Identify the program that is calling the DLL

A DLL error is more useful when you know who requested the file.

Check the error window and shortcut

Look at the title bar, full message, and path shown in the error. If the message appears when starting one application, that application is the first suspect. If it appears when opening a folder, changing thumbnails, or using the context menu, Windows Explorer or a file association may be involved.

Also check the shortcut:

1. Right-click the affected shortcut.
2. Select Properties.
3. Review the Target field.
4. Note whether it launches a legacy image viewer, a script, or a command involving rundll32.exe.
5. Do not alter the target yet. Record it first.

A legacy viewer can be invoked with a command similar to:

rundll32.exe %SystemRoot%System32shimgvw.dll,ImageView_Fullscreen "C:Pathphoto.jpg"

This is an identification and legacy-use example, not a general repair command. Replace the sample path only when testing a known image and a known legacy association.

If only one third-party application calls this command, repair or reinstall that application. Do not assume the application supplies shimgvw.dll; it normally belongs to Windows.

Repair or reinstall the affected application

Use these steps when the error occurs only in one program:

1. Open Settings.
2. Select Apps.
3. Select Installed apps on Windows 11, or Apps & features on Windows 10.
4. Select the affected application.
5. Choose Advanced options if available.
6. Select Repair, then test the program.
7. If Repair is unavailable or unsuccessful, select Reset only if the application’s settings can be recreated.
8. If neither option exists, uninstall and reinstall the application using its legitimate installer or built-in recovery media.
9. Restart Windows and test again.

If the application has its own installer repair option, use that before uninstalling. If the program is very old, check whether it has a documented compatibility mode or a supported replacement viewer.

Fix 3: Repair the image file association

A damaged association can produce a shimgvw.dll error even when Windows files are healthy.

Choose a current image viewer

1. Right-click an affected image file.
2. Select Open with.
3. Select Choose another app.
4. Select an installed image viewer.
5. Enable Always use this app to open files if that is the intended behavior.
6. Select OK.
7. Repeat for other affected extensions, such as .jpg, .jpeg, .png, or .bmp, if necessary.

You can also change the default application centrally:

1. Open Settings.
2. Select Apps.
3. Select Default apps.
4. Search for the image extension or the viewer.
5. Assign the extension to an installed application.

If modern viewers work but an old shortcut still produces the error, the Windows component may be healthy and the old shortcut or association is the problem. Keep the modern association instead of forcing a legacy viewer to load.

Fix 4: Check dependencies and architecture

Use this step when the file is present but Windows still reports that it cannot load it.

Confirm the relevant paths

1. Press Windows key + E.
2. Enter %SystemRoot%System32 in the address bar.
3. Search for shimgvw.dll.
4. On 64-bit Windows, also check %SystemRoot%SysWOW64.
5. Right-click the file, select Properties, and review the Digital Signatures tab if present.
6. Check the Details tab for Microsoft information.

Do not treat a matching filename as proof that the file is correct. A file copied from another machine may have a different Windows build, architecture, language, servicing level, or dependency set.

Understand the 32-bit and 64-bit paths

• A native 64-bit caller normally uses the 64-bit Windows system copy.
• A 32-bit legacy application on 64-bit Windows may use the 32-bit system environment and the SysWOW64 copy.
• A 32-bit DLL cannot be made compatible with a 64-bit caller by renaming it.
• A 64-bit DLL cannot be made compatible with a 32-bit caller by copying it into another folder.

Do not manually move files between System32 and SysWOW64. Run DISM and SFC so Windows can restore the correct copy for the installation.

Check for a missing dependency

If the original application error names another DLL, investigate that file instead of replacing shimgvw.dll. You can also check:

1. Open Event Viewer by pressing Windows key + R, entering eventvwr.msc, and selecting OK.
2. Review Windows Logs → Application.
3. Look for an error at the time of the failed launch.
4. Record the application name, faulting module, and exception details.
5. Compare the event with the exact error message.

A trusted dependency-analysis utility can help an administrator identify unresolved imports, but it should be used for diagnosis, not to download individual DLLs. If the missing dependency is a protected Windows file, return to DISM and SFC.

Fix 5: Check Microsoft Defender Protection history

Security software can quarantine a system file or a related dependency. Do not restore a quarantined file simply because an error appeared.

1. Open Windows Security from the Start menu.
2. Select Virus & threat protection.
3. Select Protection history.
4. Review detections from the time the problem began.
5. Expand a relevant detection.
6. Confirm the affected path and file name.
7. If Microsoft Defender identifies a false positive and the file is genuinely Microsoft-signed, use the available Restore or Allow on device action.
8. If the detection concerns a modified, unsigned, or suspicious copy, leave it quarantined.
9. Run a full scan after addressing the detection.

If malware may have modified Windows files, restore the system through normal Windows servicing and perform a security scan. Restoring an unverified DLL can reintroduce the problem.

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

Fix 6: Update or reinstall a related driver only when evidence points there

A display, printer, or imaging driver can expose an image-viewing or printing failure, but a driver is not the usual cause of a missing Windows DLL. Use this path only when the error began immediately after a driver change or when Device Manager reports a related problem.

Check Device Manager

1. Right-click Start.
2. Select Device Manager.
3. Expand Display adapters, Printers, Imaging devices, and Cameras as relevant.
4. Look for a warning icon.
5. Right-click the affected device and select Properties.
6. Review the General tab for a device status message.
7. Open the Driver tab and record the provider and date.
8. Use Update Driver only with a driver from the computer or device manufacturer.
9. Restart Windows and retest the original operation.

If the issue began after a driver update, open the same Driver tab and select Roll Back Driver when available. If the device is no longer needed, uninstalling its driver should be done only when you have a supported replacement path.

Outbyte Driver Updater can reduce the work of hunting through dozens of driver versions by showing which drivers it identifies as stale; its free scan reports the findings, while installation is handled by the full version. Use it only as an optional convenience, and prefer the hardware manufacturer’s supported driver when reinstalling a specific device.

Do not use Windows Features as a DLL replacement

Windows Features can enable or disable supported Windows components, but there is no general feature switch that repairs every shimgvw.dll error. Do not enable random legacy components to make an error disappear.

If an old program requires a Windows feature that is clearly named in its documentation:

1. Open Settings.
2. Select Apps.
3. Select Optional features.
4. Review installed and available features.
5. Enable only the documented requirement.
6. Restart if Windows requests it.
7. Test the application again.

On some systems, the older component may not be available or supported. In that case, use the application’s supported viewer or replace the obsolete workflow.

Fix 7: Use regsvr32 only for applicable legacy systems

regsvr32 is not a universal missing-DLL repair tool. Most runtime DLLs should not be registered, and registration does not repair a missing dependency, damaged component store, wrong architecture, or invalid binary.

Older Windows releases treated shimgvw.dll registration differently. Microsoft documented unregistering and re-registering it as part of a security workaround for the WMF vulnerability:

regsvr32 /u %windir%system32shimgvw.dll
regsvr32 %windir%system32shimgvw.dll

This is mainly relevant to legacy Windows installations and should not be the default fix on Windows 10 or Windows 11. Unregistering the component disables Windows Picture and Fax Viewer functionality until it is registered again.

If you have a documented legacy requirement:

1. Open Command Prompt as administrator.
2. Run the unregister command.
3. Confirm the result.
4. Run the registration command.
5. Restart Windows.
6. Test the specific legacy viewer or association.

If either command reports an architecture or entry-point error, stop. Do not try random copies of regsvr32.exe or DLL files. Use the correct Windows architecture and return to DISM, SFC, application repair, or recovery.

Fix 8: Use System Restore after a recent change

System Restore is appropriate when the problem started after an update, driver installation, application installation, or configuration change.

1. Press Windows key + R.
2. Enter:

rstrui.exe

1. Select OK.
2. Select Next.
3. Choose a restore point created before the problem began.
4. Select Scan for affected programs if available.
5. Review the changes.
6. Select Next, then Finish.
7. Allow Windows to restart.
8. Test the original operation.

System Restore normally rolls back system files, registry settings, drivers, and installed programs without removing personal documents. It does not replace a full backup, and it may not be available if protection was disabled or no restore point exists.

Fix 9: Use Windows recovery when repair still fails

If DISM, SFC, dependency checks, application repair, and System Restore do not resolve the error, use Microsoft’s supported recovery options.

Before proceeding:

• back up personal files;
• record application installers and license information;
• confirm the exact Windows edition and architecture;
• disconnect unnecessary external devices;
• make sure you know the account credentials required after recovery.

Open Settings → System → Recovery on Windows 11, or Settings → Update & Security → Recovery on Windows 10. Review the available reset, recovery, or reinstall options and read whether personal files and applications will be removed.

An in-place repair or supported recovery operation is preferable to copying a DLL from another computer. A clean reinstall is a last resort when the Windows installation is broadly damaged, the component store cannot be repaired, and other recovery options are unsuitable.

Windows 2000 also requires a qualification: Windows Picture and Fax Viewer functionality was introduced with Windows XP, so instructions intended for XP and later do not automatically apply to Windows 2000.

Do not download shimgvw.dll manually

Avoid DLL download websites and random file-sharing sources. A manually downloaded file may contain malware, have the wrong Windows build, use the wrong architecture, lack a required dependency, or create side-by-side and signature problems. It may also hide the real cause, such as a damaged component store or broken file association.

Microsoft does not provide a current standalone shimgvw.dll redistributable download page. Use Windows Update, DISM, SFC, the original Windows installation or recovery media, and supported application installers instead.

Manual replacement should be considered only by an experienced administrator using a verified matching Windows installation source after normal servicing tools fail. Even then, servicing and recovery are safer than copying a file directly into System32.

Prevention and verification

After the repair:

1. Restart Windows once more.
2. Open the image or application that originally failed.
3. Test more than one image extension if thumbnails or associations were involved.
4. Test printing only if printing triggered the error.
5. Confirm that Windows Security no longer shows an unresolved quarantine.
6. Keep Windows updated.
7. Avoid registry cleaners and DLL “fixer” utilities that replace protected files.
8. Keep a restore point or system backup before major driver and application changes.
9. Record the exact application and command that produces any future error.

FAQ

Is shimgvw.dll safe?

It is a genuine Microsoft Windows system component named Windows Picture and Fax Viewer. Safety depends on the actual file and its location, signature, and Windows installation. A file with the correct name downloaded from an unknown source is not automatically safe.

Does Windows 11 always contain shimgvw.dll?

No. Do not assume that every Windows 11 installation contains or uses this legacy component. The error may come from an old application or association expecting a component that is not part of the current workflow.

Is shimgvw.dll still relevant on Windows 10?

It can be relevant to some older installations, applications, and associations, but usage varies by Windows build, architecture, and configuration. Repair the current Windows installation instead of assuming that a historical DLL version applies.

Should I register shimgvw.dll?

Usually not on a current Windows installation. regsvr32 has limited historical relevance for older Windows releases and does not repair dependencies or corrupted system files.

Why do thumbnails fail when image viewing also fails?

Thumbnails, image associations, and legacy viewer commands can share Windows imaging components. If Windows cannot load the component or a dependency, both thumbnail generation and opening an image may fail.

What if SFC reports no violations?

Check the calling application, file association, dependency errors, architecture, Defender Protection history, and recent system changes. A clean SFC result does not rule out an application-specific configuration problem.

Should I install Visual C++, DirectX, or .NET?

Not as a first fix. shimgvw.dll is a Windows component, not one of those redistributable runtimes. Use DISM and SFC, then investigate the specific program or dependency.

When should I reinstall Windows?

Use recovery or an in-place repair when Windows cannot restore its component store, SFC repeatedly cannot repair files, System Restore is unavailable or ineffective, and the error continues across relevant applications. Back up personal data first.