Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsapc60.dll is missing because an older Windows application cannot find its Microsoft Application Programmability Components installation. The safest fix is to identify that parent application and repair or reinstall its original VBA component rather than downloading apc60.dll from a random DLL website.
Quick identification
| Item | Verified information |
|---|---|
| File | apc60.dll |
| Description | Application Programmability Components |
| Publisher | Microsoft Corporation |
| Role | Legacy COM/object-library component used by applications that embedded VBA 6.0 |
| Windows status | Not a normal Windows system DLL |
| Typical architecture | Historical Win32, 32-bit component |
| Correct owner | The older application that installed VBA/APC |
Applications such as older Visio, CAD, design, and office-related programs could include VBA. The filename alone cannot identify which program is requesting it.
What the apc60.dll error means
You may see messages such as:
- “This application failed to start because apc60.dll was not found.”
- “The file apc60.dll is missing or corrupted.”
- “Error loading apc60.dll.”
- “The procedure entry point could not be located.”
- “The application cannot start because apc60.dll is missing from your computer.”
These messages usually mean that the host program’s VBA installation is incomplete, damaged, or incompatible with the program version.
Microsoft Application Programmability Components, or APC, was part of the technology used by software vendors embedding Visual Basic for Applications 6.0 into their own Windows programs. It is not the same thing as Visual C++ Redistributable, DirectX, or modern .NET.
Recommended Free Tools
#1 Best Overall
It is also not a standard Windows 10 or Windows 11 system file. Windows Update will not normally install a standalone copy of it.
Fix 1: Identify the application that needs apc60.dll
Start with the exact program named in the error dialog. If the message appears while launching a shortcut, its name is usually the affected application.
If the dialog does not identify the program, work backward from the recent change that preceded the error:
- Think about which older program stopped working.
- Check whether the problem began after uninstalling or repairing Office, Visio, a CAD program, or a design application.
- Check whether an old application was upgraded, moved to another drive, or restored from a backup.
- Open Settings and select Apps.
- Select Installed apps in Windows 11, or Apps & features in Windows 10.
- Search for recently changed legacy applications.
- Also check Control Panel → Programs → Programs and Features for older software that may not appear clearly in Settings.
Do not assume that the application is Microsoft Office merely because the missing component was developed by Microsoft. The embedded VBA component may belong to a completely different vendor’s application.
Check the shortcut target
If you start the program from a shortcut:
- Right-click the shortcut.
- Select Properties.
- On the Shortcut tab, read the Target field.
- Note the executable name and installation folder.
- Use that program’s repair or reinstall option.
If the shortcut points to a file that no longer exists, the application may have been partially removed. Reinstalling the parent application is more useful than replacing the DLL.
Fix 2: Repair the application
Repair the program that displays the error before trying Windows-wide repairs.
Repair from Windows Settings
- Press Windows + I.
- Select Apps.
- Select Installed apps.
- Find the affected application.
- Select the three-dot menu beside it.
- Choose Advanced options, if available.
- Select Repair.
- Start the application again after the repair completes.
Some older desktop applications do not provide a Repair button in Settings. Use Control Panel instead.
Repair from Control Panel
- Press Windows + R.
- Enter
appwiz.cpl. - Press Enter.
- Find the affected application.
- Right-click it.
- Choose Change, Repair, or Modify, depending on the installer.
- Select the VBA, macros, developer tools, or shared components option if the installer presents one.
- Allow the repair to finish.
- Restart Windows.
- Test the original application.
The exact feature name differs between products. A historical installer may expose the component as VBA 6.0, VBA support, macros, developer components, or a shared Microsoft VBA feature.
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 →If the installer asks for installation media, provide the original disc, mounted installation image, or approved network installation source. Do not replace that source with a downloaded DLL.
Fix 3: Reinstall the original VBA component
If repairing the application does not work, uninstall and reinstall the affected application from its original installation source.
Rank #2
Before removing it, make sure you have:
- The original installer or installation media
- The product’s license or activation information
- Any required service packs supplied by the software vendor
- Backups of the application’s documents, templates, and custom macros
During setup, choose a custom installation if available. Look for options related to:
- VBA
- Macros
- Developer tools
- Shared components
- Application programmability
- Microsoft Office or VBA integration
Some historical installers used a package named vba6.msi. Treat that name as a clue when searching your original media or an existing installer cache, not as a recommendation to download it from an archive. No current official Microsoft standalone download for apc60.dll or vba6.msi has been verified.
After reinstalling:
- Restart Windows.
- Launch the affected program directly.
- Open a normal document or project.
- Test the feature that previously failed.
- Confirm that the error does not return after another restart.
Fix 4: Check the expected installation folders
Do not use the presence of a file as proof that it is safe or compatible, but checking the application’s folders can reveal an incomplete installation.
Look in the application’s own installation directory first. Historical VBA 6 installations may also have used a path resembling:
C:Program FilesCommon FilesMicrosoft SharedVBAVBA6
On a 64-bit version of Windows, an older 32-bit program may instead use:
C:Program Files (x86)Common FilesMicrosoft SharedVBAVBA6
The exact folder depends on the installer. A missing apc60.dll is not the only possible problem. The application may also require another VBA file, such as vbai60.dll, or a dependency that Windows reports indirectly as a missing module.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →If the file exists but the program still fails:
- Right-click the file.
- Select Properties.
- Check the Digital Signatures tab if present.
- Check the file’s location.
- Compare that location with the application’s original installation structure.
- Do not move the file to another folder.
A file in an unrelated download folder is not a valid repair.
Fix 5: Check whether antivirus quarantined the file
Security software can quarantine an old DLL if its behavior or age triggers a detection. Restore it only when you can confirm that it came from the original application installer.
Windows Security steps
- Open Start.
- Type Windows Security.
- Open the application.
- Select Virus & threat protection.
- Select Protection history.
- Review recent detections.
- Expand any entry associated with the affected application or
apc60.dll. - Confirm the original file path and detection details.
- Do not restore the file if it came from an unknown download source.
- If the file came from trusted original installation media, scan the installer and the restored file before launching the application.
Microsoft warns that restoring a quarantined file can cause Defender to detect it again. Do not create a permanent exclusion simply to suppress the warning. If the file is repeatedly quarantined, contact the original application vendor and obtain a clean installer or updated compatibility guidance.
Fix 6: Check 32-bit and version compatibility
apc60.dll belongs to the VBA 6.0 generation. It should not be replaced with similarly named files such as apc62.dll, apc63.dll, or apc71.dll. Those names represent different component generations and are not interchangeable.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11A 32-bit application can run on 64-bit Windows, but it still needs the compatible 32-bit VBA component. Installing a newer 64-bit Office or VBA release does not automatically repair an old 32-bit application.
Use the installation location as a clue
These locations are clues, not absolute proof:
C:Program Files (x86)commonly contains 32-bit applications.C:Program Filescommonly contains 64-bit applications.- An application’s custom installer may use either location.
Inspect a file’s architecture with PowerShell
If you have a trusted copy of the application executable or DLL, you can inspect its PE architecture.
- Hold Shift and right-click the application’s folder.
- Select Open in Terminal or Open PowerShell window here.
- Run this script after replacing the path:
$path = "C:PathToapc60.dll"
$bytes = [System.IO.File]::ReadAllBytes($path)
$peOffset = [BitConverter]::ToInt32($bytes, 0x3C)
$machine = [BitConverter]::ToUInt16($bytes, $peOffset + 4)
switch ($machine) {
0x014c { "x86 / 32-bit" }
0x8664 { "x64 / 64-bit" }
0xAA64 { "ARM64" }
default { "Unknown architecture: 0x{0:X}" -f $machine }
}
Run the same check against the parent application’s .exe file. If the application is 32-bit, obtain its matching component from that application’s installer. Do not mix files from different VBA generations or different products.
Fix 7: Use the application’s Verify or Repair Files feature
Some software uses its own launcher rather than a normal Windows installer.
Open the application’s launcher and look for options named:
- Verify files
- Repair installation
- Scan and repair
- Check installation
- Modify installation
Run that process while connected to the internet if the product requires online files. If the launcher reports that the component is unavailable, reinstall the application from its official installer or contact its vendor.
This is especially useful when the application was moved between drives or restored from a backup, because the launcher may know which files and dependencies belong to that specific release.
Fix 8: Repair Windows components only when Windows damage is also suspected
Because apc60.dll is normally an application-installed file, System File Checker will not usually recreate it. However, run Windows servicing commands if you also see damaged Windows features, failed updates, or unrelated protected-system-file errors.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Microsoft recommends DISM before SFC.
- Open Start.
- Type
cmd. - Right-click Command Prompt.
- Select Run as administrator.
- Run:
DISM.exe /Online /Cleanup-Image /RestoreHealth
- Wait for it to finish.
- Then run:
sfc /scannow
- Restart Windows.
- Test the affected application again.
If DISM or SFC reports that it could not repair files, copy the exact result and return to repairing the parent application. Do not interpret a successful SFC scan as proof that apc60.dll has been restored.
Repeatedly hunting through Windows repairs can be tedious when the real problem is an incomplete third-party installation. Outbyte PC Repair can scan for issues and show what needs attention; its repair action is available with the full version, but reinstalling the application that owns apc60.dll remains the definitive fix.
Fix 9: Review recent driver or system changes
A graphics or device driver is not normally the source of apc60.dll, but an old application may stop launching after a system change, hardware replacement, or driver installation.
Rank #4
Use Device Manager to check for obvious device problems:
- Right-click Start.
- Select Device Manager.
- Expand categories with a warning icon.
- Right-click the affected device.
- Select Properties.
- Read the message on the General tab.
- Open the Driver tab.
- Use Roll Back Driver only if the problem began immediately after that driver update.
- Otherwise select Update Driver and use the approved Windows or hardware-vendor source.
- Restart Windows and test the application.
Do not remove random devices or install a driver merely because it appears old. Driver repair is relevant only when the application failure coincides with a device or system change.
Manually identifying the correct driver across several hardware vendors can involve comparing device IDs and package versions. Outbyte Driver Updater can scan and identify driver issues, with driver installation available through the full version; it is not a substitute for reinstalling the legacy application that supplied apc60.dll.
Fix 10: Use System Restore after a known system change
System Restore can help when the error began immediately after an update, driver installation, application removal, or other major change and a suitable restore point exists.
- Press Windows + R.
- Enter:
rstrui.exe
- Press Enter.
- Select Next.
- Choose a restore point dated before the error began.
- Select Scan for affected programs if available.
- Review the changes.
- Select Next, then Finish.
- Allow Windows to restart.
System Restore does not replace personal documents, but it can remove applications, drivers, or updates installed after the selected restore point. If the error remains, repair or reinstall the affected application.
What not to do
Do not download apc60.dll from a random DLL website
An arbitrary copy may have:
- The wrong architecture
- A different build
- Missing dependencies
- Incorrect file permissions
- Malware or tampering
- No connection to the application that needs it
Copying a DLL into System32 can also create conflicts between unrelated applications. The safe source is the original application installer, original installation media, or an approved repair package supplied by the software vendor.
Do not copy a similarly named DLL
apc60.dll is not interchangeable with another APC or VBA generation. Renaming a different file does not make it compatible.
Do not begin with regsvr32
A runtime or object-library DLL may not expose the DllRegisterServer entry point required by regsvr32. If you run the command against a non-self-registering DLL, Windows may report that the entry point was not found. That does not prove the file is corrupt.
Use regsvr32 only when the application’s official installer or vendor instructions specifically require registration. If explicitly instructed, use the full path supplied by that installer, for example:
Free tools Windows power users keep installed
One-click scans. No signup required.
regsvr32 "C:PathSuppliedByTheApplicationapc60.dll"
Do not register a downloaded copy, and do not use registration as a replacement for reinstalling the complete VBA feature.
Do not expect Visual C++, DirectX, or .NET to fix it
Those redistributables provide different runtimes. Installing them may be appropriate for another error, but they do not normally supply the legacy VBA/APC component represented by apc60.dll.
Frequently asked questions
Is apc60.dll part of Windows?
No. It is a legacy Microsoft application component normally installed with a program that embedded VBA 6.0.
Which application needs apc60.dll?
The filename alone cannot identify the parent application. Check the error dialog, shortcut target, recent installation changes, and installed legacy software.
Free tools Windows power users keep installed
One-click scans. No signup required.
Can I put apc60.dll in System32?
No. That is usually unsafe and often ineffective. Repair the application that originally installed the file.
Will SFC restore apc60.dll?
Usually not. SFC repairs protected Windows components, while apc60.dll is normally supplied by a third-party application installation.
What if the error says a module could not be found even though apc60.dll exists?
A dependency may be missing, or the file may be the wrong architecture or VBA generation. Repair the complete VBA installation instead of copying individual DLLs.
What if the installer asks for vbai60.dll too?
That indicates an incomplete VBA 6.0 installation. Restore the complete VBA feature from the original application installer rather than adding one file at a time.
Recommended Free Tools
Should I install a newer version of VBA?
Not automatically. The affected application may require the VBA 6.0 generation and its specific supporting files. Use the version supplied or supported by the application vendor.
What if the original installer is unavailable?
Search for the original installation media, an authorized installer cache, a company software archive, or the application vendor’s support channel. If the program is business-critical, preserve its documents and configuration before attempting removal.
When should I contact the vendor?
Contact the vendor when repair and reinstall fail, the installer requests an unavailable package, the file is repeatedly quarantined, or the application produces an entry-point error after a verified installation. Provide the exact error text, application version information, Windows version, and installation history.
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.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →
