Excel Error Codes

Fix Run-Time Error 80131700 Class Not Registered in Excel

Rana GarciaRana Garcia Oct 9, 2026 870 views

Question details

The user needs to resolve an automation run-time error indicating a class is not registered when using a specific VBA extension in Excel.

How to Fix Run-Time Error 80131700 (Class Not Registered) in Excel
Product
Microsoft Excel
Device & OS
not provided
Scenario
Using the Coral Point Count extension after installing Microsoft 365 and uninstalling an older version of Microsoft Office.
Observed behavior
Excel throws run-time error -2146232576 (80131700) with a 'Class not registered' message, preventing the extension from functioning.
Before you start

Ensure you have administrative privileges on your computer, as troubleshooting COM class registry issues or repairing Office installations requires admin access.

Solution 1Recommended

Consult VBA Specialists on Stack Overflow

Because this error involves complex third-party VBA extensions and specific system registry changes, getting expert advice is recommended over drastic measures like reformatting your computer.

Third-party add-ins like Coral Point Count rely on specific libraries that may break during Office migrations. Engaging with a developer community can provide a targeted fix for the exact extension.

1
Visit Stack Overflow

Open your web browser and navigate to the Stack Overflow community forum.

2
Detail your system environment

Create a new post detailing the error code (-2146232576 / 80131700), the exact extension (Coral Point Count), and the fact that you recently upgraded to Microsoft 365 while removing an older Office version.

3
Tag your question correctly

Apply the tags [vba] and [excel] to your post to ensure it reaches VBA programming specialists who are familiar with automation and COM registry errors.

Consult VBA Specialists on Stack Overflow
Avoid Extreme Measures: Do not reformat your operating system as a first troubleshooting step. This is a localized registry/software conflict, not a critical operating system failure.
Free Microsoft Office alternative

Switch to WPS Office for a Stable Spreadsheet Experience

Microsoft Office upgrades and messy uninstalls can corrupt system registries, leading to frustrating automation errors like 80131700. If you need a reliable alternative that avoids complex legacy registry conflicts, try WPS Office. It provides excellent compatibility with Excel formats in a lightweight, stable package.

  1. 1. Download WPS Office: Visit the official WPS Office website and download the free installer.
  2. 2. Install the software: Run the lightweight installer to quickly set up WPS Office on your computer without interfering with existing registry keys.
  3. 3. Open your spreadsheets: Launch WPS Spreadsheets and open your existing Excel workbooks to continue your work without interruption.
Highly compatible with Microsoft Excel (.xlsx, .xls, .csv) formats.Lightweight installation that avoids heavy system registry bloat.Free to use with a familiar, easy-to-navigate user interface.Seamless migration of your existing data and workbooks without registry errors.
microsoft office alternative - wps office

Frequently Asked Questions

What does Run-Time Error 80131700 mean in Excel?

This is an automation error indicating that a required COM class or DLL is "not registered" in the Windows Registry. It frequently happens when an older version of Office is uninstalled, breaking the registry links that third-party VBA extensions rely on.

Should I format my computer to fix the VBA Class Not Registered error?

No, reformatting your computer should not be your first step. This issue is typically resolved by repairing your Office installation, manually re-registering the specific extension DLLs, or seeking targeted help on developer forums.

Why did this error occur right after installing Microsoft 365?

When you install Microsoft 365 and simultaneously remove an older version of Excel, the uninstaller for the older version may accidentally wipe out shared registry keys that your third-party extensions still need to function properly.

Could switching from a 32-bit to a 64-bit Office version cause this?

Yes. Many older VBA extensions were explicitly designed for 32-bit versions of Excel. If you upgraded to the 64-bit version of Microsoft 365, the older 32-bit extension classes cannot be registered or loaded, triggering the automation error.