atl80.dll Is Missing: Fixes for Windows 11 and Windows 10

If atl80.dll is missing, Windows is usually unable to start an older program that depends on the Microsoft Visual C++ 2005 runtime. If atl80.dll was not found, could not be loaded, or triggered a side-by-side error, identify the affected program first and then install the matching runtime architecture.

Before changing anything, note:

• Which program, game, installer, or utility reports the error.
• Whether the error appears during Windows startup or only when launching one application.
• Whether the program is 32-bit or 64-bit.
• Whether the problem began after reinstalling software, cleaning the disk, restoring a backup, updating the program, or an antivirus scan.
• The complete error wording and any path shown for the DLL.

In most cases, the safest repair is installing or repairing the official Visual C++ 2005 SP1 Redistributable. Do not download a loose copy of atl80.dll from a random DLL website.

As an Amazon Associate I earn from qualifying purchases.

What is atl80.dll?

ATL80.dll is part of Microsoft’s Active Template Library runtime for Visual C++ 2005, also known as Visual C++ 8.0. Microsoft’s package file tables list ATL80.dll in the Visual C++ 2005 SP1 redistributable packages. Microsoft’s VC++ 2005 file table

It is a runtime component used by software compiled with that development environment. The application may expect Windows to find the file as a shared side-by-side assembly, or the application’s installer may deploy a private copy beside the program.

That means atl80.dll is not normally a standalone Windows system file. It also is not the same file as:

• atl.dll, which belongs to a different ATL runtime arrangement.
• atl90.dll, which is associated with Visual C++ 2008.
• mfc80.dll, another Visual C++ 2005 runtime component.
• msvcr80.dll, the Visual C++ 2005 C runtime component.
• A .NET Framework assembly.

These files can be installed together by the same older application, but they are separate components. Installing a different file with a similar name does not satisfy a program that specifically requires ATL80.dll.

Older desktop applications, games, installers, and utilities may depend on it. There is no universal list of affected programs. The executable named in the error is the best clue because it identifies which program is requesting the runtime.

Why is atl80.dll not in System32?

Many users expect every DLL to be directly under C:\Windows\System32. That is not how all Visual C++ runtime assemblies are deployed.

Microsoft documents that side-by-side assemblies can be searched for in the Windows component store and, where appropriate, in the application directory. Microsoft’s assembly search sequence

Depending on the installer and application, ATL80.dll may therefore be associated with:

• A WinSxS side-by-side assembly.
• A private application directory.
• A runtime package installed by the application’s setup program.
• A matching manifest that tells Windows which assembly identity to load.

Do not manually search for a copy and move it into System32 or SysWOW64. A DLL can require a manifest, dependent runtime files, catalog information, and the correct architecture. Copying only the named file can make the loader error harder to diagnose.

Fix 1: Install or repair Visual C++ 2005 SP1

This is the quickest and most likely fix when the error names ATL80.dll.

Microsoft’s current legacy Visual C++ redistributable guidance identifies Visual C++ 2005 as Visual C++ 8.0 and provides access to the older redistributable packages.

Choose x86 or x64

The package must match the application, not merely the version of Windows.

• A 32-bit application needs the x86 redistributable.
• A 64-bit application needs the x64 redistributable.
• A 32-bit application still needs x86 when it runs on 64-bit Windows.
• If you do not know the application architecture, install both x86 and x64.

A 32-bit process cannot load a 64-bit DLL, and a 64-bit process cannot load a 32-bit DLL. Microsoft explains this distinction in its 32-bit application guidance.

The Program Files (x86) folder is a useful clue that a program is 32-bit, but it is not absolute proof. The application’s documentation, installer, or vendor support information is more reliable.

Download the official package

Use Microsoft’s own download pages:

• Visual C++ 2005 SP1 ATL Security Update
• Visual C++ 2005 SP1 MFC Security Update

These pages provide official redistributable packages for the supported architectures. Microsoft’s file tables for the packages include ATL80.dll.

Do not assume that the newest Visual C++ package replaces Visual C++ 2005. The Visual C++ 2005, 2008, 2010, and later runtimes remain separate dependencies. The current v14 runtime is not automatically a replacement for the VC80 runtime required by an older application.

Install the runtime

1. Close the program reporting the error.
2. Download the x86 package from Microsoft.
3. Right-click the downloaded installer and select Run as administrator.
4. Accept the license terms.
5. If the installer offers Repair, select it.
6. If it is not installed, select the installation option.
7. Repeat the process with the x64 package if the computer is 64-bit or the application architecture is unknown.
8. Restart Windows.
9. Launch the affected application again.

If the installer says the runtime is already installed, use its Repair option rather than assuming the installation is healthy.

If both architectures are already listed in Windows, repair the entries rather than removing them. Older software may require more than one Visual C++ generation at the same time.

Check whether it worked

The repair worked if the affected program starts normally or if the original missing-file message disappears.

If the error changes to a side-by-side message, Error 1935, or “not designed to run on Windows,” the runtime may now be present but the application manifest, a dependent component, or an application-local copy may still be damaged. Continue with the next fixes.

Fix 2: Repair or reinstall the affected application

Installing the shared runtime does not restore a private copy that was removed from the application folder. It also does not repair a damaged manifest or incomplete program update.

Use Windows’ built-in repair option first.

Repair a Windows app

On Windows 11:

1. Open Start.
2. Select Settings.
3. Select Apps.
4. Select Installed apps.
5. Find the affected program.
6. Select the three-dot menu beside it.
7. Select Advanced options.
8. Select Repair.
9. Start the program again.

If Repair does not help, return to the same page and use Reset only if you understand that it may remove the application’s local settings or stored data.

Repair a traditional desktop program

1. Open Control Panel.
2. Select Programs.
3. Select Programs and Features.
4. Find the affected program.
5. Right-click it.
6. Select Repair or Change.
7. Follow the installer’s instructions.
8. Restart Windows if requested.

Microsoft documents these repair paths in its application repair instructions.

If no repair option exists, uninstall and reinstall the program from its original vendor, store, or game launcher. Save configuration files or game saves first if the application stores them inside its installation directory.

Reinstalling the specific program is especially important when:

• The error began immediately after an application update.
• The program was copied from another computer.
• The application folder was restored from a backup.
• The installer was interrupted.
• The error names a DLL path inside the program’s own folder.
• Other programs work normally.

A program-specific failure usually points to that program’s installation rather than to Windows as a whole.

Fix 3: Verify game files through the launcher

If a game reports ATL80.dll, verify its installed files before repeatedly reinstalling Windows components. Game launchers may include private runtime files or secondary installers that are not restored by a separate Visual C++ repair.

Steam

1. Open Steam.
2. Select Library.
3. Right-click the affected game.
4. Select Properties.
5. Select Installed Files.
6. Select Verify integrity of game files.
7. Wait for the process to finish.
8. Start the game again.

Steam notes that games may also include secondary installers for components such as Visual C++. Steam’s official troubleshooting guidance

Epic Games Launcher

1. Open the Epic Games Launcher.
2. Select Library.
3. Find the game.
4. Select the three dots beside the game.
5. Select Manage.
6. Select Verify.
7. Wait for verification to finish.
8. Launch the game again.

Epic documents this process in its official file verification instructions.

Launcher verification can restore files deliberately bundled with the game. It may not install the system-wide Visual C++ runtime, so install or repair the correct VC++ 2005 architecture if the error remains.

Fix 4: Check antivirus quarantine

A security scan can remove or quarantine a runtime file. This is more likely when the error began immediately after a scan and the application had worked before.

Check Windows Security before downloading anything.

1. Open Start.
2. Type Windows Security.
3. Open the application.
4. Select Virus & threat protection.
5. Select Protection history.
6. Review entries from the time the problem began.
7. Expand any entry associated with the affected application or runtime.
8. Note whether the file was quarantined, blocked, or removed.

Microsoft warns that restoring a genuinely malicious file can put the computer at risk. Use the application’s official installer or game launcher to restore the file whenever possible. Microsoft Protection History guidance

Only consider restoring a quarantined file when all of the following are true:

• The program came from a trusted official source.
• Protection History clearly identifies the affected file.
• The application vendor confirms the file is legitimate.
• The file’s digital signature and location are consistent with the original installation.

Do not disable antivirus protection permanently to make the error disappear. If the file is repeatedly quarantined after a clean reinstall, submit the detection to the security vendor or contact the application publisher.

Fix 5: Diagnose a side-by-side or manifest failure

Some errors mention ATL80.dll but are actually caused by a broken side-by-side assembly or manifest. Common wording includes:

• “The application has failed to start because its side-by-side configuration is incorrect.”
• “Error 1935.”
• “The application has failed to start because ATL80.dll was not found.”
• “ATL80.dll is either not designed to run on Windows or it contains an error.”
• “Runtime Error R6034.”

The exact message depends on the Windows version, application, manifest, and dependency that failed.

Use sxstrace

Windows includes sxstrace.exe for investigating side-by-side loader problems.

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Start tracing with:

sxstrace.exe Trace -logfile:C:\sxstrace.etl

1. Leave the window open.
2. Reproduce the atl80.dll failure.
3. Return to the Command Prompt.
4. Press Enter to stop tracing.
5. Parse the trace with:

sxstrace.exe Parse -logfile:C:\sxstrace.etl -outfile:C:\sxstrace.txt

1. Open C:\sxstrace.txt in Notepad.
2. Look for the missing assembly name, architecture, manifest, or dependent DLL.

The trace may show that the application is requesting the Microsoft.VC80.ATL assembly, that the wrong architecture was installed, or that a related runtime component cannot be found.

Repair the runtime and application again

If the trace identifies VC80 or Microsoft.VC80.ATL:

1. Repair the matching x86 or x64 Visual C++ 2005 package.
2. Repair the affected application.
3. Restart Windows.
4. Run the program again.
5. Repeat the trace only if the same error remains.

Do not delete folders from C:\Windows\WinSxS. WinSxS is managed by Windows servicing, and manually removing files can damage unrelated applications and future updates.

Fix 6: Repair Windows components with DISM and SFC

ATL80.dll is normally a Visual C++ runtime component rather than an ordinary Windows-core DLL. SFC is therefore not the best first step for a single application that reports this file.

Use DISM and SFC when:

• The Visual C++ installer will not run.
• Several unrelated Windows applications are failing.
• Windows servicing is reporting errors.
• Side-by-side failures affect multiple programs.
• Other protected Windows files are also missing or damaged.

Microsoft recommends running DISM before SFC. Microsoft’s DISM and SFC instructions

1. Open Start.
2. Type Command Prompt.
3. Right-click Command Prompt.
4. Select Run as administrator.
5. Run:

DISM.exe /Online /Cleanup-Image /RestoreHealth

1. Wait for the command to finish.
2. Restart Windows.
3. Open an elevated Command Prompt again.
4. Run:

sfc /scannow

1. Wait until verification reaches 100 percent.
2. Restart Windows.
3. Retry the Visual C++ repair and the affected application.

Do not close the window while either scan is running. A scan that reports no integrity violations has not repaired the application’s private runtime. A successful SFC result also does not prove that a third-party VC++ assembly or application manifest is correct.

When repeated DISM and SFC runs produce no change, stop rerunning them and return to the application installer, side-by-side trace, or security history.

If hunting through Windows servicing results and repeating SFC/DISM leaves you unsure what changed, Outbyte PC Repair can scan for issues and show what it found; repairs are completed with the full version, and it is not required when the affected program needs its own clean reinstall.

Fix 7: Check Windows Features only for a matching error

Windows Features do not normally install the Visual C++ 2005 ATL runtime. Do not enable random features simply because atl80.dll is missing.

To inspect the available features:

1. Press Win+R.
2. Enter:

optionalfeatures

1. Press Enter.
2. Review the list without changing unrelated options.
3. Close the window if the error specifically names ATL80.dll and does not mention .NET.

A .NET Framework error is different from a VC++ ATL error. If the application’s documentation explicitly requires a particular .NET feature, enable only that required feature and restart Windows. Enabling .NET will not replace ATL80.dll.

Fix 8: Do not register atl80.dll with regsvr32

regsvr32 is for registering certain self-registering COM and ActiveX DLLs. ATL80.dll is a runtime library, not normally the application’s COM server, and it should not be registered with:

regsvr32 atl80.dll

This command usually produces another error because the runtime does not expose the registration entry points that regsvr32 expects. Microsoft Q&A specifically addresses why ATL80.dll is not normally registered this way. Microsoft’s regsvr32 guidance for ATL80.dll

A separate application DLL built with ATL may require registration if the application vendor explicitly instructs you to do so. That is a different file and a different repair procedure.

For reference, when a vendor genuinely requires registration, the registration tool must match the DLL architecture:

%windir%\System32\regsvr32.exe "C:\path\to\64-bit-file.dll"

For a 32-bit DLL on 64-bit Windows:

%windir%\SysWOW64\regsvr32.exe "C:\path\to\32-bit-file.dll"

Do not use either command for ATL80.dll unless the software’s official support instructions specifically establish that an unusual private deployment requires it.

Fix 9: Reinstall a related driver only when the driver installer is failing

ATL80.dll is not a device driver. Updating a graphics, audio, chipset, printer, or network driver is unlikely to fix a normal application launch error that names this runtime.

Driver work is relevant when:

• The error appears inside a hardware vendor’s installer.
• The affected program is a driver control panel or configuration utility.
• Device Manager shows a separate hardware error.
• The vendor’s installer bundles an old Visual C++ runtime and is the only program that fails.

To reinstall a device driver through Windows:

1. Open Start.
2. Type Device Manager.
3. Open Device Manager.
4. Expand the category containing the device.
5. Right-click the device.
6. Select Uninstall device.
7. Confirm the removal if prompted.
8. Restart Windows.
9. Allow Windows to reinstall the device, or install the driver supplied by the hardware manufacturer.
10. Retry the affected installer or application.

Microsoft provides the same general process in its Device Manager driver instructions.

If identifying which of many drivers is stale is the problem, Outbyte Driver Updater can scan and show the driver issues; the actual driver installation is handled by the full version, and it is not required for a program-specific ATL80.dll repair.

Do not use driver reinstallation as a substitute for repairing the Visual C++ package when ordinary applications are affected.

Fix 10: Use System Restore when the timeline fits

System Restore can help when the error began immediately after a software installation, cleanup utility, driver change, or Windows configuration change and a suitable restore point exists.

1. Open Control Panel.
2. Select Recovery.
3. Select Open System Restore.
4. Choose a restore point created before the problem began.
5. Select Scan for affected programs if available.
6. Review the programs and drivers that will be changed.
7. Start the restore.
8. Let Windows restart and complete the process.

You can also press Win+R, enter:

rstrui.exe

and press Enter.

System Restore rolls back system files, settings, drivers, and installed programs while preserving personal files. Microsoft’s System Restore instructions

Use it when the timing is clear. It is not a substitute for reinstalling an application whose own files are missing, and it will not necessarily restore a runtime removed by a later installer.

Fix 11: Investigate malware or storage corruption

The filename alone does not prove malware. ATL80.dll is a legitimate Microsoft runtime component, but malware can replace, tamper with, or imitate legitimate DLLs.

Run a full scan in Windows Security if:

• The file appeared in an unexpected directory.
• The error is accompanied by suspicious pop-ups or unknown processes.
• Multiple files are disappearing.
• Protection History shows repeated detections.
• The program was obtained from an untrusted source.

If several programs begin failing, check more than one DLL. Storage errors, interrupted installations, and file-system corruption can damage multiple files.

Look in:

• Windows Security > Virus & threat protection > Protection history
• Event Viewer > Windows Logs > Application
• The application’s own log folder
• The drive’s health and error reports

Do not replace a suspicious DLL with a downloaded copy. Reinstall the application from its official source and scan the system.

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

What not to do

Do not download a loose DLL

Random DLL download sites can provide:

• Malware or tampered files.
• The wrong Visual C++ build.
• The wrong architecture.
• A file missing its manifest or dependencies.
• A version that belongs to another application.

Even a clean-looking copy may not fix the actual problem because the application could need the complete VC80 assembly, a matching manifest, or another runtime file.

Use Microsoft’s official Visual C++ package pages or the affected application’s original installer instead.

Do not copy the file into System32

Putting a 32-bit file in System32, or a 64-bit file in SysWOW64, does not make the loader accept it. The directory names are also counterintuitive on 64-bit Windows: System32 contains 64-bit system files, while SysWOW64 is used for 32-bit system components.

More importantly, the loader may be looking for a side-by-side assembly or application-local deployment. A manual copy can leave the actual manifest problem untouched.

Do not uninstall every old Visual C++ package

Older applications can depend on different runtime generations. Removing Visual C++ 2005 because it looks obsolete can break the program that needs ATL80.dll.

Keep required Visual C++ versions installed side by side unless the application vendor or Microsoft’s installer specifically instructs you to remove one.

Documented versions and architecture notes

Microsoft documents different ATL80.dll versions in different VC++ 2005 SP1 security packages. These are examples, not a complete inventory.

Package context	Documented file version	Architectures listed
VC++ 2005 SP1 ATL security update	8.0.50727.4053	x86, x64, and historically IA-64
VC++ 2005 SP1 MFC security update	8.0.50727.6195	x86, x64, and historically IA-64
Later Microsoft-serviced VC80 file	8.0.50727.6229	Depends on the package

File size also varies by architecture and package build. There is no single correct size that every ATL80.dll must have.

The important checks are whether the application’s required VC++ 2005 runtime is installed, whether the architecture matches, and whether the application’s manifest and private files are intact.

How to tell which cause applies

Symptom	Most useful next step
One older program fails immediately after a clean Windows installation	Install or repair VC++ 2005 x86, x64, or both
A game fails after an update	Verify files in Steam or Epic Games Launcher
The error names a path inside the application folder	Repair or reinstall that application
The error began after antivirus activity	Check Windows Security Protection History
“Side-by-side configuration is incorrect” appears	Repair the runtime and use sxstrace.exe
Error 1935 appears during installation	Repair VC++ components, the application, and investigate servicing
Several unrelated programs fail	Run DISM and SFC, then inspect Event Viewer and disk health
Only a hardware vendor’s installer fails	Repair the bundled runtime and investigate the vendor installer
regsvr32 is suggested by a random guide	Do not register ATL80.dll
The problem began immediately after a system change	Consider System Restore

Frequently asked questions

Is atl80.dll a Windows file?

It is a Microsoft runtime file, but it is not normally a core Windows component like the standard system ATL file. It belongs to the Visual C++ 2005 deployment system and may be installed through WinSxS or beside an application.

Which Visual C++ package installs atl80.dll?

The relevant family is Microsoft Visual C++ 2005 SP1, also called Visual C++ 8.0. Microsoft’s official security-update redistributable packages list ATL80.dll in their file tables.

Do I need Visual C++ 2005, 2008, or 2010?

For an error specifically naming ATL80.dll, start with Visual C++ 2005 SP1. Visual C++ 2008 and 2010 are different runtime generations and do not automatically replace VC80.

Do I need x86 or x64?

Use x86 for a 32-bit application and x64 for a 64-bit application. Many 64-bit Windows computers need both because they run older 32-bit software.

Can I install only the newest Visual C++ Redistributable?

Do not rely on the newest v14 redistributable to replace Visual C++ 2005. Older applications can require their original runtime generation, and the generations are designed to remain side by side.

Should I register atl80.dll?

No. ATL80.dll is normally a runtime library, not a self-registering application component. Do not run regsvr32 atl80.dll.

Is atl80.dll related to .NET?

No. It is part of the native Visual C++ 2005 ATL runtime. A program can require both .NET and Visual C++, but enabling a .NET Windows Feature does not install ATL80.dll.

Why did the error appear after disk cleanup?

A cleanup operation may have removed an application-private file or damaged an installation, but the filename alone does not prove that cleanup caused the problem. Repair the application, check antivirus history, and use System Restore only when the timeline supports it.

Can SFC repair atl80.dll?

SFC repairs protected Windows system files. It may help when Windows servicing is damaged, but it may not repair a third-party Visual C++ runtime assembly or a private application copy. Install or repair VC++ 2005 first for a single-program failure.

Should I restore the file from antivirus quarantine?

Only after confirming the program is trusted and Protection History clearly identifies the file. Reinstalling from the official application installer is safer than restoring an isolated DLL.

Why does the application still fail after installing VC++ 2005?

The program may use a private runtime copy, have a damaged manifest, require the other architecture, or depend on another missing component. Repair the application and use sxstrace.exe if the error is side-by-side related.

When should I contact the application vendor?

Contact the vendor when only one application fails after the correct runtime architectures have been repaired, the application has been reinstalled, and its launcher has verified the files. Provide the complete error, application version, executable path, architecture, installed VC++ entries, Event Viewer details, and parsed sxstrace output.

What evidence should I collect if every fix fails?

Record:

• The complete error text.
• The affected program and version.
• Whether it is 32-bit or 64-bit.
• The full path shown in the message.
• Installed Visual C++ 2005 entries and architectures.
• Windows Event Viewer application errors.
• The C:\sxstrace.txt output.
• Windows Security Protection History results.
• Whether other applications fail.
• Whether the problem occurs in a new Windows user account.

That information distinguishes a missing runtime from a private application failure, manifest mismatch, security quarantine, damaged Windows servicing, storage corruption, or a problem specific to the user profile.

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.