cab.dll Missing: Repair the App That Owns It on Windows

cab.dll is usually a legacy 7-Zip archive plugin, not a Windows system file. The safest fix is to identify the application requesting it and repair or reinstall that application from its official installer instead of downloading a replacement DLL.

What this file actually does

The file description associated with cab.dll is Cab Plugin for 7-Zip. Historical 7-Zip installations stored format plugins in a Formats folder, commonly as:

As an Amazon Associate I earn from qualifying purchases.

C:Program Files7-ZipFormatscab.dll

A 32-bit installation may instead be under:

C:Program Files (x86)7-ZipFormatscab.dll

The plugin allows 7-Zip-based software to work with Microsoft Cabinet archives, whose files normally use the .cab extension.

This does not mean every cab.dll error comes from the current standalone 7-Zip application. Older installers, deployment utilities, archive programs, developer tools, games, and other applications sometimes bundled their own private 7-Zip components. In that situation, reinstalling standalone 7-Zip may have no effect because the broken copy belongs to another program.

Modern 7-Zip versions generally use the unified 7z.dll library for archive-format support, including CAB support. The official 7-Zip download page offers separate Windows packages for x86, x64, and ARM64 systems, but it does not present cab.dll as a current standalone runtime download.

cab.dll is also not the same file as these Windows components:

• Cabinet.dll: Windows’ Cabinet API library for creating and extracting CAB files.
• cabview.dll: an older Windows shell-related CAB viewing component.
• 7z.dll: the modern 7-Zip library that handles most archive formats.

Do not rename or substitute one of these files for another.

Common causes and the correct response

What you see	Most likely cause	Correct first response
Error appears when launching an old archive tool	Incomplete or damaged installation	Repair or reinstall that archive tool
Error names an installer or deployment utility	The utility bundled an old 7-Zip plugin	Reinstall the utility, not Windows
Error began after an antivirus detection	cab.dll was quarantined or deleted	Check Protection History and verify the file’s origin
Reinstalling 7-Zip changes nothing	Another program owns the failing copy	Find the requesting executable and repair that program
“Specified module could not be found” appears	The DLL or one of its dependencies is missing	Check the exact folder and reinstall the owning application
A 32-bit program fails on 64-bit Windows	Wrong application architecture or plugin	Install the matching x86 or x64 application build
Error names a Microsoft runtime DLL too	A separate runtime may be damaged	Repair the specifically named runtime
Error follows a Windows component problem	System files may be corrupted	Use DISM, then System File Checker

Fix 1: Identify the program that is requesting cab.dll

Before changing Windows files, find the application that actually loads cab.dll.

Check the error window

Read the title bar and the first line of the message. Windows may identify the executable, for example:

oldsetup.exe - System Error
archive-tool.exe - System Error
game-launcher.exe - System Error

That executable name is more useful than the DLL name alone.

Also check when the message appears:

• Immediately after opening a particular program: that program is the likely owner.
• During installation: the installer or setup package is likely incomplete.
• When launching a shortcut: inspect the shortcut’s target.
• At every Windows startup: an obsolete startup entry may be calling a removed application.

Inspect the shortcut

1. Right-click the shortcut that produces the error.
2. Select Properties.
3. Open the Shortcut tab.
4. Read the Target field and Start in field.
5. Note the executable’s full path.
6. Select Cancel without changing the shortcut.

The folder containing that executable is the first place to check for a private Formatscab.dll folder.

Check installed applications

1. Press Windows key + I.
2. Select Apps.
3. Select Installed apps.
4. Search for 7-Zip, an archive utility, an installer builder, deployment software, or the application named in the error.
5. Select the three dots beside the application.
6. Choose Advanced options if available.
7. Look for Repair.

If the program has no Repair button, use its official installer to reinstall it.

Search without downloading anything

You can search your installed application folders safely:

1. Open File Explorer.
2. Select This PC.
3. In the search box, enter:

cab.dll

1. Wait for the search to complete.
2. Record every result’s full path.

A path inside an application’s folder is important. A result under an old backup, temporary directory, or unknown download folder should not be copied into the application.

If the file exists, do not assume it is usable. Check its exact location, file properties, digital signature when available, and the executable that is attempting to load it.

Fix 2: Repair or reinstall the owning application

This is the most likely working fix for a genuine cab.dll error.

Use Windows’ built-in repair option

1. Press Windows key + I.
2. Select Apps.
3. Select Installed apps.
4. Find the program that produces the error.
5. Select the three dots beside it.
6. Select Advanced options.
7. Select Repair.
8. Start the application again.

If the error is gone, the application’s files were restored without removing its settings.

If Repair is unavailable or fails:

1. Return to the application’s entry in Installed apps.
2. Select the three dots.
3. Choose Uninstall.
4. Restart Windows.
5. Download the installer from the application developer’s official website.
6. Install the same program again.
7. Restart Windows and test it.

Do not install a random DLL separately. A proper installer restores the plugin, its related files, the correct folder structure, and any dependencies required by the application.

Repair standalone 7-Zip

If the error appears when opening 7-Zip itself:

1. Uninstall the existing 7-Zip installation from Settings > Apps > Installed apps.
2. Restart Windows.
3. Download the current installer from the official 7-Zip website.
4. Choose the package matching the application and Windows architecture.
5. Right-click the installer and select Run as administrator.
6. Complete the installation.
7. Open 7-Zip and test a CAB archive.

Current 7-Zip may not recreate a historical Formatscab.dll file because its archive support is generally consolidated into 7z.dll. That is normal. The application requesting the old plugin may itself need to be reinstalled instead.

Repair an application that bundles 7-Zip

Some software includes its own private 7-Zip files. Standalone 7-Zip cannot repair those copies.

For that application:

1. Close the application.
2. Open Settings > Apps > Installed apps.
3. Locate the application.
4. Use Advanced options > Repair, if present.
5. If no repair option exists, uninstall the application.
6. Restart Windows.
7. Reinstall it from the developer’s official installer or the software’s official launcher.
8. If it is a game, use the launcher’s Verify, Scan, or Repair files function before reinstalling the entire game.

Do not overwrite the application’s private plugin with a cab.dll copied from another installation. Even files with identical names can differ in architecture, dependencies, or expected location.

Fix 3: Check Windows Security quarantine

If the problem started immediately after a security scan, Windows Security may have quarantined or removed the file.

1. Open the Start menu.
2. Type Windows Security.
3. Open it.
4. Select Virus & threat protection.
5. Select Protection history.
6. Look for a detection involving cab.dll or the application that owns it.
7. Expand the detection to view its path and threat details.

Only restore a quarantined file if all of these are true:

• The file was inside software you intentionally installed.
• The software came from its legitimate developer or official distribution channel.
• The path matches the application’s installation directory.
• The detection is understood and has been verified as a false positive.

Do not disable antivirus protection to force an unknown DLL to load. If the application is legitimate, reinstalling it from its official installer is safer than manually restoring an uncertain file.

If Windows Security identifies the file as malicious, leave it quarantined and remove the application that installed it. A missing-file message is preferable to allowing an untrusted DLL to run.

Fix 4: Install the correct application architecture

Architecture mismatches can prevent a program from loading its plugin.

A 32-bit application normally needs its compatible 32-bit components. A 64-bit application cannot generally load a 32-bit DLL, and a 32-bit application cannot use a 64-bit DLL as a substitute.

To check Windows’ architecture:

1. Press Windows key + I.
2. Select System.
3. Select About.
4. Read System type.

To check an installed program:

1. Open Settings > Apps > Installed apps.
2. Select the program’s options or open its installation folder.
3. Check the application documentation or installer choices for x86, x64, or ARM64 support.

Install the architecture supplied by the application developer. Do not mix a 32-bit plugin from Program Files (x86) with a 64-bit program in Program Files.

If the software is old and offers only a 32-bit build, install that build and allow it to use its own files. Running a 32-bit application on 64-bit Windows is supported, but its DLLs must still match the application.

Fix 5: Repair Windows components only when Windows itself is involved

SFC and DISM are useful for damaged Windows components, but they do not normally recreate a third-party 7-Zip plugin in an application folder.

Use them when you also see broader Windows problems, such as damaged built-in applications, update failures, unexplained system errors, or problems involving Cabinet.dll.

Run DISM first

1. Open the Start menu.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Select Yes at the User Account Control prompt.
6. Run:

DISM /Online /Cleanup-Image /RestoreHealth

1. Wait for the operation to finish.
2. Restart Windows.

DISM may take time and can appear to pause. Do not close the window while it is working.

Run System File Checker

After restarting:

1. Open Command Prompt as administrator again.
2. Run:

sfc /scannow

1. Wait until verification reaches 100 percent.
2. Restart Windows.
3. Test the application again.

If SFC reports that it repaired files, retry the original program. If it reports that it could not repair everything, run DISM again, restart, and repeat SFC once.

If you prefer an automated way to inspect repair issues rather than hunting through Windows components and repeating DISM and SFC without knowing what changed, Outbyte PC Repair can scan and show what it finds; repair actions are handled by the full version. It is optional, and reinstalling the application that owns cab.dll remains the definitive fix for this file.

Fix 6: Repair only the runtime named by the error

Visual C++, DirectX, and .NET are not general fixes for a missing 7-Zip cab.dll.

Use these repairs only when the actual error also names a related runtime file or the application’s official support instructions identify that runtime.

Visual C++ Redistributable

If the error names a file such as a Visual C++ runtime DLL:

1. Open Microsoft’s official Visual C++ Redistributable downloads page.
2. Download the architecture required by the application.
3. Install the x86 package for a 32-bit application.
4. Install the x64 package for a 64-bit application.
5. On ARM64 Windows, use the ARM64 package when appropriate.
6. Restart Windows.
7. Test the application.

A 64-bit Windows installation may need both x86 and x64 redistributables because it can run applications of both architectures.

DirectX

Older games may require optional legacy DirectX components. Install Microsoft’s DirectX End-User Runtime only when the game or its error specifically identifies a DirectX component. It does not replace cab.dll.

.NET

If the message names a .NET component or the application reports a .NET startup error:

1. Open Settings.
2. Select Apps.
3. Select Installed apps.
4. Search for the affected .NET runtime or framework.
5. Use its available repair or uninstall option.
6. Reinstall the required version from Microsoft’s official source.
7. Restart Windows.

Do not install these runtimes merely because cab.dll is missing.

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

Fix 7: Update drivers only when the failure began after a driver change

A display, storage, or chipset driver does not normally provide cab.dll. Driver repair is relevant only if the application started failing after a driver installation, Windows upgrade, or hardware change.

To roll back a recently changed driver:

1. Right-click the Start button.
2. Select Device Manager.
3. Expand the category for the affected hardware.
4. Right-click the device.
5. Select Properties.
6. Open the Driver tab.
7. Select Roll Back Driver if available.
8. Restart Windows and test the application.

To update through Windows:

1. Open Device Manager.
2. Expand the relevant device category.
3. Right-click the device.
4. Select Update driver.
5. Select Search automatically for drivers.
6. Restart Windows if prompted.

If you are manually checking many device models and cannot tell which driver changed, Outbyte Driver Updater can scan and identify outdated drivers; the free scan shows what it finds, while installation is handled by the full version. This is optional and is not a substitute for reinstalling the application that owns cab.dll.

Why regsvr32 is usually wrong

Do not run:

regsvr32 cab.dll

A normal 7-Zip archive-format plugin is not a self-registering ActiveX or OLE component. regsvr32 expects the DLL to provide a registration entry point such as DllRegisterServer. Without that entry point, Windows may report that the module loaded but the entry point was not found.

Registration also cannot restore a missing file, repair a damaged application installation, or supply a missing dependency. Restore the complete application package instead.

Do not copy cab.dll into System32

There is no reliable evidence that this 7-Zip plugin belongs in:

C:WindowsSystem32

or:

C:WindowsSysWOW64

Windows searches application-specific locations according to its DLL search rules. A plugin normally belongs beside the application that loads it, often in an application-specific Formats directory.

Copying a DLL into a system directory can cause:

• Architecture mismatches.
• Conflicting versions.
• DLL preloading risks.
• A different application loading the wrong file.
• A misleading error that returns after the next update.

Never download cab.dll from a random DLL archive. The file may contain malware, may be the wrong architecture, may be incompatible with the requesting application, or may leave the real broken installation untouched. Use the official installer for the application or the official 7-Zip installer when 7-Zip itself is the owner.

If reinstalling does not fix the error

Work through these checks in order.

Confirm the exact path

A computer can contain several copies of old 7-Zip components. Use the error’s executable path, shortcut target, and File Explorer search results to determine which copy is involved.

Check permissions

1. Right-click the application’s main executable.
2. Select Properties.
3. Open the Security tab.
4. Confirm that your account has permission to read and execute the file.
5. Open the Compatibility tab.
6. Try Run this program as an administrator only as a test.

If administrator mode fixes the problem, repair the application’s permissions or installation rather than leaving every launch elevated.

Look for a dependency error

“ The specified module could not be found ” can mean that cab.dll is present but one of its dependencies is missing. Reinstalling the complete owning application is the safest way to restore those dependencies.

Check Event Viewer

1. Right-click Start.
2. Select Event Viewer.
3. Expand Windows Logs.
4. Select Application.
5. Look for an error at the time of the failed launch.
6. Record the application name, faulting module, and error code.

Give those details to the application developer if the official reinstall still fails.

Consider System Restore

If the error began after a recent installation, update, or configuration change and no installer is available:

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

rstrui.exe

1. Press Enter.
2. Select an appropriate restore point.
3. Review the affected programs.
4. Complete the restore.

System Restore can revert system configuration and installed programs without changing personal files, but it is not a replacement for obtaining a clean installer.

FAQ

Is cab.dll a Windows system file?

No. The file is associated with a historical 7-Zip format plugin. Windows has a separate Cabinet.dll, which is not a replacement for cab.dll.

Does Windows 11 or Windows 10 need cab.dll?

Not normally. Windows can work with its own Cabinet components without this 7-Zip plugin. A program that requests cab.dll usually has an application-specific dependency.

Should I download cab.dll separately?

No. Obtain the complete application installer from the developer’s official source. A standalone DLL may be malicious, incompatible, or unable to fix missing dependencies.

Does installing the newest 7-Zip always fix the error?

No. An old application may contain its own copy of the plugin, and modern 7-Zip generally uses 7z.dll for archive support. Repair the program named in the error.

Can I register cab.dll with regsvr32?

No, not as a normal repair. Archive-format plugins are not generally self-registering Windows components.

Should SFC or DISM restore cab.dll?

Usually not. They repair Windows component files, not third-party files stored in an application’s installation directory.

Is cab.dll 32-bit or 64-bit?

Do not rely on unverified online file records for its bitness. Install the version supplied with the application and match the application’s x86, x64, or ARM64 architecture.

What if the file is present but the error remains?

The file may be in the wrong folder, may have a missing dependency, may be blocked by security software, or may not match the application architecture. Reinstall the owning application and inspect its exact executable and plugin path.

What is the final safe repair?

Identify the requesting executable, remove or repair the application that owns it, and reinstall that program from its official source. Keep cab.dll inside the application’s folder and do not place it in System32 or SysWOW64.

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.