“The program can’t start because igdi.dll is missing from your computer.” Other messages include “igdi.dll was not found,” “igdi.dll could not be loaded,” and “There was a problem starting igdi.dll.” The file is normally an InstallShield runtime component, not a Windows system DLL, so the safest fix is to repair or reinstall the program whose installer needs it.
Which fix applies to you
Use the first description that matches what you see:
As an Amazon Associate I earn from qualifying purchases.
- The error appears while installing a program: obtain a complete installer from the software publisher, copy it locally, and run
setup.exeagain. - The error appears when launching an installed program: use that program’s repair option or reinstall it from its original installer.
- The file was quarantined: check your security product’s quarantine and Protection History before reinstalling.
- Only one old application is affected: keep the repair limited to that application. Do not copy
igdi.dllintoSystem32orSysWOW64. - Several programs show missing-DLL errors: check for disk problems, malware, or broader Windows corruption.
- The error mentions a separate Microsoft runtime DLL: repair that runtime independently. Visual C++, DirectX, and .NET do not normally provide
igdi.dll. - A real hardware driver also fails: troubleshoot that driver separately.
igdi.dllitself is not a graphics, audio, chipset, or printer driver.
What is igdi.dll
igdi.dll is identified as the InstallShield “IGdi DLL,” a component used by older InstallShield installation engines. Historical InstallShield runtime files are commonly found in paths resembling:
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteC:Program Files (x86)Common FilesInstallShieldProfessionalRunTime<version>Intel32IGdi.dll
The Intel32 part indicates a 32-bit runtime. A 32-bit installer can require a 32-bit DLL even when it is running on 64-bit Windows.
#1 Best Overall
- 1.1 GHz (boost up to 2.4GHz) Intel Celeron N5030 Quad-Core
The exact version, size, path, and surrounding files depend on the InstallShield generation bundled with the affected product. Several InstallShield runtime directories can legitimately coexist because unrelated applications may include different engine versions.
Is igdi.dll part of Windows
No. It should not normally be present as a protected Windows file in either of these folders:
C:WindowsSystem32
C:WindowsSysWOW64
System32 is also used for 64-bit system components on 64-bit Windows, while SysWOW64 contains many 32-bit Windows components. Neither folder is an appropriate destination for manually copying an InstallShield DLL.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Older file metadata may identify InstallShield Software Corporation or Macrovision. InstallShield is now associated with Revenera, but the publisher field on an old DLL does not by itself identify the application that installed it.
Fix 1: Repair or reinstall the affected application
This is the most likely solution when igdi.dll appears during program startup or setup.
If the program is already installed
- Press Windows key + R.
- Type:
text
appwiz.cpl
- Press Enter.
- Select the application that fails.
- Look for Repair, Change, or Modify.
- Follow the repair wizard.
- Restart Windows.
- Try opening the program again.
Not every application provides a repair button. If there is no repair option, uninstall the affected program, restart Windows, and reinstall it from its original vendor-supplied installer.
Before uninstalling, back up saved data, profiles, game saves, templates, and license information if the program stores them in its installation directory.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →If the error appears during setup
The setup package may be incomplete, damaged, or missing companion InstallShield files.
- Delete the incomplete installer copy.
- Obtain the installer again from the software publisher or from genuine installation media.
- Save the installer to a local folder such as:
text
C:InstallersProgramName
- If the download is an archive, extract the entire archive to that folder.
- Do not run an MSI copied out of an InstallShield package if the original package also contains
setup.exeand other setup files. - Right-click
setup.exeand select Run as administrator. - Complete the installation.
- Restart Windows and test the program.
A successful repair restores the application’s own InstallShield runtime in the location expected by that product. It does not necessarily create a single global copy of igdi.dll.
If you use a game launcher
Open the launcher and look for an option named Verify files, Repair, Scan and repair, or similar. The exact wording varies by launcher.
This is preferable to downloading an individual DLL because the launcher can restore the complete set of files and preserve the correct versions for that game.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallFix 2: Check antivirus quarantine
Security software can quarantine an old installer component, especially when the application is legacy or the installer uses outdated packaging.
Windows Security
- Open Start and search for Windows Security.
- Select Virus & threat protection.
- Select Protection history.
- Review recent actions involving
igdi.dll, the affected application, or its installer. - Expand the relevant entry and review its location and detection details.
Do not restore the file merely because its name matches the error. Restore it only when all of the following are true:
Rank #2
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
- The file belongs to an application you trust.
- The installer came from the software publisher or genuine media.
- The file path matches that application’s installation or setup folder.
- A complete scan does not identify the installer as malicious.
After verifying the source, repair or reinstall the application rather than relying on a quarantined file alone. Do not create a broad antivirus exclusion for the Windows directory or for every installer.
If malware or tampering is suspected, run a full Microsoft Defender scan and reinstall the affected program from trusted media.
Recommended Free Tools
Fix 3: Use a complete installer source
An old setup package can fail when files were lost during a transfer, extracted incorrectly, or removed from a network share.
Try these steps:
- Copy the complete installation media to a local drive.
- Confirm that the folder contains
setup.exeand the other files supplied with the installer. - Avoid launching setup directly from an unreliable network or removable drive.
- Temporarily close other installation programs.
- Right-click
setup.exe, select Properties, and check whether Windows shows an Unblock option on the General tab. - Select Unblock, if present, then select Apply.
- Right-click
setup.exeand select Run as administrator. - Run the installation again.
If the installer asks for another disc, folder, or source path, provide the complete original media. An MSI extracted by itself may not contain the InstallShield runtime files that the original setup process expects.
If the setup reports another missing InstallShield file after igdi.dll, assume that the package or cached installation source is incomplete. Replace the entire installer source rather than replacing DLLs one at a time.
Fix 4: Confirm that the application is compatible with Windows
A missing DLL can be a symptom of an obsolete setup engine rather than the only problem.
Try the built-in compatibility troubleshooter:
- Right-click the application’s shortcut or installer.
- Select Properties.
- Open the Compatibility tab.
- Select Run compatibility troubleshooter.
- Follow the recommendations.
- Test the program.
- If it works, return to the same tab and select Run this program as an administrator only if the application genuinely requires it.
You can also select a previous Windows compatibility mode manually, but change one setting at a time and test after each change.
If the publisher supplies a newer installer, use that version instead of forcing an old InstallShield package to run. Keep the old installer only when it is the necessary source for a legacy application.
Fix 5: Do not install Visual C++, DirectX, or .NET as a guess
igdi.dll is associated with InstallShield, not with the Microsoft Visual C++ runtime, DirectX, or the .NET runtime.
Installing one of those packages will usually not restore this file. Use them only when the actual error names a component from that runtime.
For example, if the application separately reports a missing Microsoft Visual C++ DLL, use Microsoft’s latest supported Visual C++ Redistributable downloads. A 32-bit application normally needs the x86 package even on 64-bit Windows.
If the error names a legacy DirectX component, use Microsoft’s DirectX End-User Runtime Web Installer. That package supplies certain legacy DirectX components, not InstallShield’s igdi.dll.
Do not install multiple runtime packages simply because a DLL error appeared. Match the package to the component named in the error.
Rank #3
- 14" diagonal, 1366x768 resolution, HD BrightView LED, Glossy NON-TOUCH Display
Fix 6: Repair Windows components only when Windows itself is damaged
System File Checker and DISM repair protected Windows components. They are unlikely to restore a third-party InstallShield DLL, but they are reasonable when Windows shows additional corruption symptoms, failed updates, damaged system tools, or multiple unrelated system errors.
Run DISM and SFC
- Open Start.
- Search for Command Prompt.
- Right-click it and select Run as administrator.
- Run this command:
text
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for it to finish.
- Run:
text
sfc /scannow
- Wait until verification reaches 100 percent.
- Restart Windows.
- Retry the affected application.
Run the commands separately. If SFC reports that it could not repair some files, restart and run the scan again. If Windows remains unstable, use Microsoft’s System File Checker guidance.
Outbyte PC Repair can reduce the guesswork when you are repeatedly hunting through Windows corruption symptoms and cannot tell what changed; its free scan identifies issues, while repair features are provided by the full version. It is optional, and reinstalling the application remains the definitive fix when that application owns igdi.dll.
Do not conclude that SFC succeeded merely because it completed. The meaningful test is whether Windows problems improved and whether the affected application now launches. SFC does not prove that an InstallShield DLL was restored.
Free tools Windows power users keep installed
One-click scans. No signup required.
Fix 7: Treat driver errors separately
Despite occasional file catalogs classifying igdi.dll under a broad “driver” category, this file is not a hardware driver. It is an InstallShield installation component. Device Manager will not normally restore it.
If the same computer also has a genuine graphics, audio, chipset, printer, or other device problem, repair that driver separately:
- Right-click Start.
- Select Device Manager.
- Expand the relevant category.
- Right-click the affected device.
- Select Properties.
- Open the Driver tab.
- Note the provider, date, and version.
- Use Update Driver or obtain the driver from the hardware manufacturer.
- If the problem began after an update, select Roll Back Driver when available.
- Restart Windows and test the hardware.
Do not uninstall a working device driver merely because an application reports igdi.dll.
Outbyte Driver Updater can help identify stale hardware drivers when you are manually checking many devices; its free scan shows what it finds, while driver installation is handled by the full version. It is not a substitute for repairing the application that supplied igdi.dll.
Why you should not copy a downloaded DLL
Avoid standalone DLL download pages and random file mirrors. A manually downloaded igdi.dll can have the wrong:
- InstallShield generation
- 32-bit or 64-bit architecture
- dependent files
- expected installation path
- digital signature or provenance
It may also contain malware or simply leave the damaged installer configuration unchanged.
Do not copy the file into:
C:WindowsSystem32
C:WindowsSysWOW64
Do not copy a file from one application’s InstallShield runtime folder into another application’s folder unless the application’s own installer places it there. Different programs may require different InstallShield engine generations.
The safe source is the original application installer, the software publisher’s download, genuine installation media, or the application’s built-in repair system.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Is regsvr32 required
Normally, no.
regsvr32 is used for DLLs that expose a self-registration entry, commonly COM or ActiveX components. There is no established reason to register igdi.dll as a standard repair step, and running a command such as this is not a substitute for repairing the owning application:
regsvr32 igdi.dll
If the command reports that an entry point was not found, that does not mean Windows needs another copy of the file. It usually means the DLL is not a self-registering COM component.
Rank #4
- 【Efficient Performance】 Powered by Intel Core i3 processor (2 cores, 4 threads, up to 3.4GHz) with 12GB RAM and 256GB SSD. Handles multitasking, office software, online classes, and HD video streaming smoothly. Integrated Intel UHD Graphics 620
- Backlit Keyboard & Complete Package】Comes with a cool backlit keyboard. Comes with awebcam, dual stereo speakers (8Ω/1.0W each), DC charger, and user manual – ready for late-night studying, online classes, video conferencing, and daily productivity
- 【Vibrant Display】 15.6-inch Full HD (1920x1080) anti-glare screen with 16:9 aspect ratio delivers crisp images and vivid colors – perfect for studying, watching lectures, or entertainment. Thin-bezel design maximizes viewing area
- 【Fast Connectivity & Expansion】 Equipped with WiFi 6 (802.11ax) and Bluetooth 5.2 for stable, high-speed wireless. Features 3 x USB 3.0, HDMI 2.1, Type-C (supports PD3.0 fast charging), and a TF card slot expandable up to 2TB – easily connect external monitors, mice, drives, or expand storage for all your files
- 【Long Battery Life & Portable】 Built-in 11.55V 5000mAh/57.75Wh high-capacity battery delivers approximately 7 hours of mixed-use battery life – enough for a full day of classes and assignments. Lightweight at just 1.63kg (3.6 lbs) and 19.5mm thin, plus a compact packing size – easily slips into a backpack for campus, library, or coffee shop
Check for disk corruption or malware
If files disappear repeatedly, the application installation becomes damaged again, or unrelated files are corrupted, investigate the storage and security environment.
- Back up important documents and application data.
- Review Windows Security Protection History.
- Run a full Microsoft Defender scan.
- Check the drive for errors using the drive manufacturer’s diagnostic utility or Windows’ drive error-checking tools.
- Reinstall the affected application after the storage problem is addressed.
System Restore may help only if the application and file worked at a known restore point. It is not a guaranteed replacement for reinstalling the application.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →How to identify the owning application
The filename alone does not identify which program needs it. Check:
- The complete path shown in the error
- The executable named in the dialog
- The folder opened immediately before the error
- Settings > Apps > Installed apps
- Control Panel > Programs and Features
- The application’s original setup media
- Recent antivirus quarantine entries
- Event Viewer > Windows Logs > Application
Record the full path, failing executable, Windows version, application version, and any related event details. These clues identify the owning product more reliably than igdi.dll alone.
FAQ
Is igdi.dll a Windows 11 or Windows 10 system file?
No. It is associated with an InstallShield runtime bundled with an application or installer. Windows 10 and Windows 11 can run into the error when using older software, but Windows does not normally provide the file as a core system component.
Can 64-bit Windows use igdi.dll?
Yes. Historical InstallShield copies are 32-bit, and a 32-bit installer can require them on 64-bit Windows. Restore the copy through the affected application’s installer rather than choosing a DLL based only on the Windows architecture.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhich application installed igdi.dll?
InstallShield is used by many unrelated software publishers. Identify the program from the error path, failing executable, installation folder, or setup media. The DLL name alone is not enough.
Will reinstalling the application always fix the error?
It is the most reliable repair, but it will fail if the installer is incomplete, the application is incompatible, antivirus blocks the file, or the disk is damaged. Use a complete installer and check those conditions if reinstalling does not work.
Should I run regsvr32?
Not as a normal fix. igdi.dll is not established as a COM or ActiveX server that requires registration.
Should I run SFC?
Run SFC when Windows itself shows corruption symptoms, not as the primary way to restore igdi.dll. SFC repairs protected Windows files and normally does not replace third-party InstallShield components.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteWhat if the error returns after reinstalling?
Check antivirus quarantine, obtain a different complete installer source, test the disk, and confirm that you are not copying a runtime from another InstallShield generation. If another InstallShield file is then missing, the installer package is probably damaged.
What is the final safe fix?
Identify the affected application, obtain its genuine complete installer, and use repair or reinstall. Keep the repair scoped to that application and never replace the file globally in the Windows system directories.
Quick Recap
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.
