Some Microsoft Access users reported an issue in July 2026 with SQL Server Migration Assistant (SSMA) for Access. Users running the 32-bit version of Microsoft Access experienced problems where the SSMA x86 installation appeared to launch a 64-bit process, resulting in a COM registration error.
Since the original report, Microsoft has released newer versions of SSMA for Access. Below are the details of the reported issue, along with the latest release information as of November 2026.

What Happens?
Users running the 32-bit version of Microsoft Access reported that after installing the affected SSMA for Access (x86) release, Windows launched the application as a 64-bit process instead.
When this happened, SSMA could fail to start and display the following error:
Retrieving the COM class factory for component with CLSID
{CD7791B9-43FD-42C5-AE42-8DD2811F0419} failed due to the following error:
80040154 Class not registered (0x80040154 (REGDB_E_CLASSNOTREG)).

Who Is Affected?
The issue was originally reported by users who were:
- Running 32-bit Microsoft Access
- Installing the affected release of SQL Server Migration Assistant (SSMA) for Access
- Experiencing the 0x80040154 (REGDB_E_CLASSNOTREG) error when launching SSMA
Current Status – November 2026 Update
Microsoft has since published newer versions of SQL Server Migration Assistant for Access.
As of November 2026, Microsoft lists SSMA for Access version 10.6, with both 32-bit (x86) and 64-bit installers available.
According to Microsoft’s official release notes, version 10.6 includes security, compliance, user experience, and accessibility fixes. However, the release notes do not specifically confirm whether the COM registration issue described in this article has been resolved.
Users experiencing this error should review the latest available version and test it in their environment before making changes to production systems.
For the latest information, refer to Microsoft’s official resources:
Workaround for the Originally Reported Issue
For users affected by the July 2026 issue, the original recommendations were:
- Continue using a previously installed version of SSMA if it is working correctly.
- Avoid upgrading production environments until the newer version has been tested.
These recommendations applied to the originally reported issue. If you are still experiencing the same error, check the latest SSMA release and verify compatibility with your Microsoft Access environment.
We will continue to monitor Microsoft’s release information and update this article when additional details about this specific issue become available.
Leave A Comment