Windows Error 0x8007007E Fix: "The Specified Module Could Not Be Found" in Updates, Printers and Apps

What error 0x8007007E actually means

Error 0x8007007E is not a random number. It is a Windows error code with a plain meaning hiding inside it. The last two hex digits, 7E, are the number 126. In Microsoft's documentation of system error codes, number 126 is named ERROR_MOD_NOT_FOUND and its message is "The specified module could not be found." The "80070" at the front just wraps that Win32 code in the longer format that Windows Update, installers and some apps display. We confirmed the 126 and 0x7E pairing on Microsoft's System Error Codes page (see Sources).

A "module" here is almost always a DLL file, a small shared library that a program loads while it starts or while it installs something. When Windows or an installer asks for a module and cannot find it, cannot reach it, or finds a copy it is not allowed to use, you get this error. That explains why the same code shows up in very different places: a failed Windows update, a printer or scanner that stops working after setup, a program that refuses to open, or a driver that will not install.

Notice what the message does not say. It does not say the file is corrupt, and it does not say your computer is infected. Most of the time the cause is boring: a missing runtime library, a half-installed update, a driver package that references a file that was never copied, or a security tool that quarantined a file that the next step needed. Boring causes mean boring fixes, and you can usually work through them in about 30 to 60 minutes.

Where you will see it, and why that matters

Before touching anything, write down exactly where the error appeared. The place tells you which fix to start with, and it saves you from running ten repairs when one would do.

The wording in the second row is the classic "rundll32" style popup. It looks alarming because it appears right after you sign in, but it usually just means Windows is trying to run a startup item whose file was deleted. That is a cleanup job, not an emergency.

The common causes, in plain language

1. A missing runtime library

Many Windows programs are built with Microsoft's C++ tools and depend on the Visual C++ Redistributable, a set of shared libraries. Microsoft's documentation explains that a redistributable at least as recent as the build tools used for the app must be installed, and that its architecture must match the app (an x64 package for a 64-bit app, an x86 package for a 32-bit app). If the library is missing or damaged, the app cannot load its modules and reports a missing module.

2. Damaged or incomplete Windows system files

Windows keeps its own files in a protected store. If a previous update was interrupted by a power cut, a forced shutdown or a full disk, a few files can end up half written. The next update or installer then trips on the same spot. Microsoft's built in tools for this are DISM and System File Checker, and we cover the exact commands below.

3. A driver package that does not match the hardware or the Windows build

Printer, scanner and some multifunction device installers copy a driver, then ask Windows to load a helper library. If the helper never arrived, or was built for a different driver model, the install ends with a module error. We see this most often right after a big Windows feature update, when an old vendor installer meets a newer Windows.

4. Security software getting in the way

Antivirus and endpoint tools sometimes quarantine a DLL that an installer unpacked a moment ago. The installer then cannot find it. This is more common with older or lesser known software, and with installers downloaded from unofficial sites. If the file was quarantined for a real reason, you want to know that, not just override it.

5. Leftovers from uninstalled or "cleaned" software

Uninstallers and registry "cleaners" regularly remove a file while a startup entry, scheduled task or service still points to it. Windows then looks for the file at every sign in and complains. This is the cause behind most of the startup popups.

6. The DLL exists, but Windows cannot find it where it looks

Windows searches for a DLL in a defined order: modules already loaded and known system DLLs, then the folder the application loaded from, then the system folders, then the current folder and finally the folders listed in the PATH setting. Microsoft documents this order in its DLL search order page. If the right file sits in a folder that is not on that list, the program reports it as not found even though you can see the file in Explorer. Dependencies matter too: Microsoft notes that if a DLL has its own dependencies, the system looks for those by module name only, so a missing second level file produces the same message as a missing first level file.

Before you start: five safe habits

• Restart first. A pending restart from an earlier update blocks the next one more often than people expect. Restart, wait for sign in to finish, and retry the action.
• Free some space. Microsoft's update troubleshooting page says Windows needs at least 16 GB free on 32-bit systems and 20 GB on 64-bit systems for updates. Low space produces half written files, which produces module errors.
• Note what changed. New printer, new antivirus, last night's update, a program you removed? The most recent change is the prime suspect.
• Do not download DLL files from the internet. "DLL download" sites are a well known way to get malware onto a machine, and a random copy of a system file may be the wrong version. Fix the cause (runtime, repair, driver) instead of dropping a loose file into System32.
• Keep your files safe. None of the steps below should remove personal files, but if the PC holds anything irreplaceable, copy it to an external drive or cloud folder first. It takes ten minutes and removes all the stress.

Fix 1: when it appears in Windows Update

This is the path Microsoft itself recommends for general update errors. On Windows 11, open Settings, then System, then Troubleshoot, then Other troubleshooters, and choose Run next to Windows Update. On Windows 10 the path is Settings, then Update and Security, then Troubleshoot, then Additional troubleshooters.

1. Run the Windows Update troubleshooter and apply anything it offers. Restart.
2. Check that the date, time and time zone are correct and set to automatic (Settings, Time and language, Date and time). A wrong clock breaks update checks.
3. Unplug external drives, docks and anything you do not need for the update to run.
4. Go to Settings, Windows Update, and select Check for updates again.

If the same code returns, move on to repairing the Windows component store (Fix 2). If the update is simply stuck at a percentage, our guide to Windows Update stuck or failing covers the stall patterns, and the article on errors 0x80070643, 0x80070005 and 0x800f0922 covers three neighbouring codes that often travel with it.

Fix 2: repair Windows files with DISM and SFC

This pair of commands is the most useful single repair for module and update errors, and it is the order Microsoft documents: DISM first, then SFC. Both need an elevated prompt.

1. Click Start, type cmd, right click Command Prompt and choose Run as administrator.
2. Type DISM.exe /Online /Cleanup-image /Restorehealth and press Enter. It can take several minutes and may appear to pause for a long time. Let it finish.
3. In the same window, type sfc /scannow and press Enter. Keep the window open until the scan reaches 100 percent.
4. Restart and retry whatever failed.

Read the SFC result message carefully. "Windows Resource Protection did not find any integrity violations" means system files are fine, and your cause is elsewhere (runtime, driver, startup entry). "Found corrupt files and successfully repaired them" means the repair worked and a restart is next. "Found corrupt files but was unable to fix some of them" means you need the log. Microsoft says the details are in %windir%\Logs\CBS\CBS.log, and that you can extract just the SFC lines with the following command, which writes a file named sfcdetails.txt to your Desktop:

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"

If "Could not perform the requested operation" appears, Microsoft suggests running the scan in Safe Mode. If Windows Update itself is broken and DISM cannot download repair files, Microsoft documents a form of the command that uses a repair source such as a mounted Windows image or a known good installation, with /Source and /LimitAccess. That variant is where a mistake can cause real trouble, so if you have not done it before, this is a good moment to ask for help.

Fix 3: clear the update download cache

Microsoft's update troubleshooting page lists this as a documented step. It is safe because Windows rebuilds the folder.

1. Press Windows key and R, type services.msc and press Enter.
2. Find Windows Update, right click and choose Stop.
3. Open File Explorer, go to C:\Windows\SoftwareDistribution and delete the contents of the folder (not the folder itself).
4. Back in Services, start Windows Update again, restart the PC and check for updates.

The first check after this takes longer than usual because Windows rebuilds its list. That is normal. Give it ten minutes before deciding nothing happened.

Fix 4: when a program or installer fails with the code

If the failure is in an app, the cause is usually a missing runtime or an app folder that was partly deleted. Work through these in order.

1. Repair the app. Settings, Apps, Installed apps (Apps and features on Windows 10), choose the app, then Modify or Advanced options and Repair if offered.
2. Reinstall it. Uninstall, restart, then install a fresh copy downloaded from the publisher's own site. Skip third party download portals.
3. Install the Visual C++ runtime. Microsoft's page lists permanent links for the latest supported Visual C++ v14 Redistributable: aka.ms/vc14/vc_redist.x64.exe and aka.ms/vc14/vc_redist.x86.exe. Microsoft says the v14 redistributable covers apps built with Visual Studio 2017 and later. It also adds that if you are trying to fix an app by updating the runtime, you should contact the app vendor for instructions, so if the app is paid or business software, check its support page first.
4. Install both flavours when unsure. On a 64-bit PC, 32-bit apps still need the x86 runtime, and 64-bit apps need the x64 runtime. Installing both is harmless.

Microsoft notes that redistributables for Visual Studio 2013 and older remain installed side by side, and are separate packages. A very old program may ask for one of those. Again, that is a vendor question, and the older packages are linked from the same Microsoft page, including the x86 and x64 2013 files.

Fix 5: the startup popup ("There was a problem starting ... .dll")

This version appears when you sign in. A startup item is asking for a file that no longer exists. Your job is to find the item and remove it, not to hunt for the file.

1. Note the exact file name in the popup. Write it down or take a photo.
2. Press Ctrl, Shift and Esc to open Task Manager, then open the Startup apps tab. Look for an entry that matches the file name or a program you remember uninstalling. Right click it and choose Disable.
3. Open Task Scheduler (search for it in Start). In Task Scheduler Library, look for tasks with the same name or publisher. Right click and Disable. Do not delete tasks you do not recognize until you know what they are.
4. If nothing in those two places matches, Microsoft's free Autoruns tool from Sysinternals lists every automatic start location in one window, including ones Task Manager does not show. Search the file name, and untick the entry. Untick, do not delete, so you can undo it.
5. Restart and confirm the popup is gone.

A word of caution. If the file name in the popup is random letters, or the popup showed up right after you opened an attachment or ran a "free" tool, treat it as a possible malware leftover rather than a simple orphan. Read the next section on when it is not an innocent error before you click anything else.

Fix 6: printer and scanner driver installs

When 0x8007007E appears during a printer or scanner install, or when the "scan to computer" feature stops working after an update, the pattern is nearly always the same: a driver package that is incomplete or too old for the current Windows build. Windows has also been moving printers toward newer driver models, so an old vendor package built around a legacy model can fail in ways that look like missing modules. Our article on printers that stop working on Windows 11 because of legacy v3 and v4 drivers explains that background without jargon.

1. Disconnect the printer (unplug USB, or remove it from the Wi-Fi setup screen).
2. Remove the device in Settings. Settings, Bluetooth and devices, Printers and scanners, select the device, Remove.
3. Remove the old vendor software from Settings, Apps, Installed apps. Remove every entry from that maker for that model (the full software suite, scan utility and any "driver" entry).
4. Restart. This releases files that were locked by the old software.
5. Install fresh from the maker's support page for your exact model and your Windows version. Choose the full driver package or the manufacturer's current setup tool. If a basic driver is offered, try it first, because it has fewer helper files that can go missing.
6. Or let Windows try it first. After the restart, reconnect the printer and see whether Windows installs it on its own. Many modern printers print fine this way, and you can add the manufacturer's scan tool afterward if you need scanning.

If the printer shows up but will not print, the cause may be the print queue service rather than the driver. See our print spooler error guide, and the broader printer not working fix. For help choosing and updating drivers safely in general, read how to update drivers.

Fix 7: security software and quarantined files

If the error began the moment you tried to install something, open your antivirus history (Windows Security, Virus and threat protection, Protection history). Look for an entry from the exact minute of the failure that quarantined or blocked a file related to the installer.

• If the quarantined file belongs to a vendor you trust and you downloaded the installer from the vendor's real site, restore the file, add a narrow exclusion for the install folder only if the vendor documents it, and retry.
• If the installer came from a forum, a "crack", a cleaner tool or any site you are not sure about, leave the file in quarantine and do not install. The antivirus is doing its job. Download the program from the official source instead.
• Never turn off protection entirely "just to install". If the vendor tells you to, call us or their support first.

When it is not an innocent error

Most 0x8007007E cases are harmless. A few are not, so know the warning signs.

• The file named in the popup is a random string of characters, or sits in an odd location such as a Temp folder or a folder named after a stranger.
• The popup started right after you ran a "free" download, a cracked program, a fake support call or a "fix your PC" tool.
• Browser settings changed on their own, or you see new toolbars, redirected searches or pop up ads.
• Windows Security reports threats that keep coming back after removal.

If two or more of those match, stop using the PC for banking or email, run a full scan with Windows Security (Virus and threat protection, Scan options, Full scan, and a Microsoft Defender Offline scan as a second pass), and read our guide to removing a virus from a computer. Change important passwords from a different, clean device. If you were on the phone with someone who asked for remote access, that is a different problem and you should call us right away.

Quick decision table: which fix for which symptom

When the basics fail: the stronger options

Clean boot to find a conflicting program

A clean boot starts Windows with only Microsoft services and no third party startup items. Press Windows key and R, type msconfig, open the Services tab, tick "Hide all Microsoft services", then Disable all. Then open Task Manager's Startup apps tab and disable everything. Restart, and test the install or update that failed. If it now works, turn items back on in small groups until the error returns. The last group contains the culprit. Remember to return Windows to normal startup afterwards.

Test with a new Windows user

Create a new local administrator account and try the failing action there. If it works, your original profile has a damaged setting or a user-level startup entry, which is much easier to fix than a damaged Windows. If it fails in both accounts, the problem is system wide, which points back to system files, drivers or the runtime.

In-place repair install

This reinstalls Windows over itself while keeping files and apps. On Windows 11 you download the official installation media from Microsoft's site and run setup from within Windows, choosing to keep personal files and apps. It is a heavy tool and takes one to two hours, but it replaces every system file with a good copy and often ends stubborn module and update errors that DISM and SFC could not. Back up first, and make sure the PC is on mains power. If you are unsure whether to keep apps and files, do not guess: pick the option that keeps both, or ask us.

What to avoid

• Registry cleaners. They are a frequent source of the very errors people use them to fix.
• Downloaded DLL files. A random copy can be the wrong version or carry malware.
• Resetting Windows first. A reset is a last resort, not step one.
• Running commands copied from a forum without reading them. Some "fixes" delete folders you need.

Three realistic scenarios (illustrative)

These are Realistic scenarios, not real customer cases. They show the usual shape of this error and how long a fix takes.

Scenario 1: the home office printer after a big update

A freelance designer in Laval installs a monthly Windows update on Thursday evening. On Friday the printer's scan software shows 0x8007007E and the "scan to PC" button does nothing, though printing still works. She removes only the scan utility, restarts, and installs the current version from the maker's support page. Total time: 25 minutes. She skips the temptation to reinstall Windows, because printing proved the system was healthy. Cost: nothing but her time.

Scenario 2: the small office PC that cannot finish updates

A bookkeeper's desktop in a three person office in Longueuil has failed the same update four times with 0x8007007E. The disk shows 11 GB free, below the 20 GB Microsoft lists for 64-bit systems. The office manager deletes old installers and a duplicated downloads folder to reach 38 GB free, runs the update troubleshooter, then DISM and SFC (SFC reports it repaired files), restarts and the update installs on the fifth try. Time: about 70 minutes, most of it waiting for DISM. The root cause was low space, which had damaged the update download.

Scenario 3: the startup popup that was not innocent

A retiree in Gatineau sees "There was a problem starting a file with a random name. The specified module could not be found." at every sign in. It began after installing a free "PC speed booster". Task Manager does not list the entry, and Autoruns shows a scheduled task pointing to a Temp folder. Windows Security's full scan then finds a threat. After removal and a password change from a phone, the popup stops. Time: about 2 hours. The lesson: an unexplained file name that appeared after a "free tool" is worth a proper scan.

Printable checklist

For the curious: why Windows says "module not found" when the file is there

People often say "but the DLL is right there in the folder." Both statements can be true. A module is not found when the loader cannot use it from where it looks. According to Microsoft's DLL search order documentation, an unpackaged desktop app that does not give a full path is searched in this sequence: DLL redirection, API sets, side-by-side manifest redirection, the list of already loaded modules, known DLLs, the folder the application loaded from, the system folder, the Windows folder, the current folder, then the PATH folders. Safe DLL search mode, enabled by default, keeps the current folder late in the list so that a stray file in a random folder is less likely to be picked up.

Three practical consequences follow. First, a file in Downloads or on the Desktop does nothing for an app, however identical the name. Second, a 32-bit app cannot use a 64-bit DLL, and the reverse, so the right file in the right folder can still fail. Microsoft has a separate error for that mismatch (ERROR_BAD_EXE_FORMAT, 193, "is not a valid Win32 application"). Third, one missing dependency deep in the chain gives the same top level message, which is why a program that "has all its files" can still report a missing module. This is also why reinstalling the whole program or the runtime is better than hunting for one file by hand.

There is also a security side. Microsoft's documentation warns that if an attacker controls one of the searched directories, they can place a malicious copy of a DLL there. That is one more reason never to scatter downloaded DLL files into program folders or System32.

Neighbouring error codes and where to go next

Several Windows codes travel with 0x8007007E in forum threads. They look similar but point to different causes, so do not mix up their fixes.

The meanings in this table for codes other than 0x8007007E are summaries of what our own guides cover. If your exact code differs, open the matching guide rather than applying this article's steps blindly.

What it costs: DIY versus paying a technician

The honest advice: try the free steps first. Fixes 1 to 7 solve most cases at no cost. A remote session makes sense when you have already tried DISM and SFC, when the PC is a work machine you cannot afford to experiment on, or when the signs point toward malware and you want a second pair of eyes.

How to stop it coming back

• Keep 20 GB or more free on the system drive, so updates never write into a full disk.
• Let updates finish. Do not hold the power button during "Working on updates". If a PC is slow to finish, leave it plugged in and wait.
• Uninstall properly. Use Settings, Apps, Installed apps rather than deleting folders by hand, then restart.
• Skip registry cleaners and "PC booster" tools. Windows manages itself well enough.
• Install drivers from the maker. And after big feature updates, check the maker's site for a newer driver before you reinstall an old CD or download.
• Keep Windows Security on. It is built in, current, and free.
• Back up. A recent backup turns any Windows problem, even a reinstall, into an inconvenience rather than a loss.

Official resources

• Microsoft: System Error Codes (0 to 499), where 126 (0x7E) is ERROR_MOD_NOT_FOUND
• Microsoft Support: Troubleshoot problems updating Windows
• Microsoft Support: Use the System File Checker tool
• Microsoft Learn: Latest supported Visual C++ Redistributable downloads
• Microsoft Learn: Dynamic-link library search order

When to call a pro

Stop and get help if any of these are true: DISM or SFC reports errors it cannot repair, the same code returns after every step above, the PC is a work machine with client data, you see signs of malware, you are about to do an in-place repair install and are unsure about the keep-files option, or you simply do not want to spend an evening on it. IT Cares has supported people remotely and on site in Quebec since 2014. We connect to your PC with you watching, find the real cause, fix it and explain what happened. Call 1 (888) 711-9428 or book a session below. Our customers rate us 4.9 stars across 78 Google reviews.

If you also need broader help, see our printer repair service in Montreal for on-site printer problems.

Frequently asked questions

Related guides

• DLL not found errors
• Windows error 0x80070005 (access denied)
• Windows error 0x80070057
• Windows error 0x80073712
• Windows error 0xC000007B
• Windows Update stuck or failing
• Printer not working fix
• How to update drivers

Sources and official references

Last verified: November 11, 2026

• Microsoft Learn: System Error Codes (0-499), ERROR_MOD_NOT_FOUND 126 (opened 2026-11-11)
• Microsoft Learn: MS-ERREF Win32 error codes (opened 2026-11-11)
• Microsoft Support: Troubleshoot problems updating Windows (opened 2026-11-11)
• Microsoft Support: Use the System File Checker tool (opened 2026-11-11)
• Microsoft Learn: Latest supported Visual C++ Redistributable downloads (opened 2026-11-11)
• Microsoft Learn: Dynamic-link library search order (opened 2026-11-11)