Regarding the Irregular Display of the Access Runtime Installer

test_account 0 Reputation points
2026-02-06T01:36:58.46+00:00

This question was created using DeepL Translation.

Description

We have a device running both Access Runtime 2013 (32-bit version) and Microsoft Office Home and Business 2019 (64-bit version).

On this device, when opening an Accde file in Access, approximately once every few months,

the Access Runtime installer appears.

I cannot determine when this occurs, making it difficult to find a solution.

I have confirmed via history that Windows Update was not performed on the day the installer appeared.

Has anyone encountered a similar phenomenon?

Also, does anyone know the cause and solution?

Below are the steps I have tried:

・Repairing the Runtime

・Troubleshooting MSACCESS.exe

Translated with DeepL.com (free version)

以下日本語原文です。

Access Runtime 2013(32bit版) とMicrosoft Office Home and Business 2019(64bit版)を併用している端末があるのですが

その端末でAccessのAccdeを開く際に、数か月に一回ぐらいの頻度で

Access Runtimeのインストーラが表示される状態があります。

発生しているタイミングがわからず対応策が探せない状態です。

対象のインストーラが表示された日にWindows Updateがされていないことは

履歴で確認しています。

似たような現象に遭遇した方はいらっしゃいますでしょうか。

また原因と解決策を知っている方はいらっしゃいますでしょうか。

以下こちらで試した内容です

・Runtimeの修復

・MSACCESS.exeのトラブルシューティング

Microsoft 365 and Office | Access | Other | Windows
0 comments

3 answers

Sort by: Oldest
Most helpful Newest Oldest

  1. AI answer

    2026-02-06T01:37:07.49+00:00

    The issue you are experiencing with the Access Runtime installer appearing intermittently when opening an Accde file may be related to the coexistence of the 32-bit Access Runtime 2013 and the 64-bit version of Microsoft Office Home and Business 2019 on the same device. This situation can lead to conflicts or registration issues, particularly if the versions are not aligned correctly.

    Here are some potential causes and solutions to consider:

    1. Version Conflict: Since you have both 32-bit and 64-bit versions installed, ensure that the applications are compatible. It is generally recommended to use the same bit version for all Office applications to avoid issues.
    2. Repair Installation: You mentioned that you have already attempted to repair the Runtime. If you haven't done so, consider repairing the Office installation as well to ensure that all components are functioning correctly.
    3. Registry Issues: The appearance of the installer could be due to missing or incorrect registry entries related to the Access Runtime. Check the registry keys associated with Access and ensure they point to the correct installation paths.
    4. Windows Installer Behavior: The Windows Installer may trigger when the version of Access being used is not the one registered. This can happen if the Access Runtime is not properly registered or if there are multiple versions installed.
    5. Updates and Compatibility: Although you confirmed that Windows Update was not performed, ensure that both Access Runtime and Office are up to date with the latest patches and updates, as these can resolve known issues.

    If the problem persists after trying these solutions, consider reaching out to Microsoft Support for more tailored assistance.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Michelle-N 20,735 Reputation points Microsoft External Staff Moderator
    2026-02-06T02:48:14.2+00:00

    Hi @test_account

    Thank you for reaching out to Microsoft Q&A.

    Based on the information you shared, I understand that on a device running Access Runtime 2013 (32-bit) alongside Microsoft Office Home and Business 2019 (64-bit), the Access Runtime installer unexpectedly appears when opening an .accde file. This occurs intermittently (once every few months), is difficult to reproduce, and does not appear to be triggered by Windows Update. You have already attempted repairing the Runtime and troubleshooting MSACCESS.exe without success.

    After researching this behavior, it appears that this is a conflict scenario when multiple Office installations with different bitness (32-bit and 64-bit) coexist on the same machine.

    Currently, Microsoft does not support side-by-side installation of Office products with different bitness. When this configuration exists:

    Each Office version writes and expects different registry keys and COM registrations. When an Access-based application is launched, Windows Installer may detect a mismatch

    This triggers a self-repair/reconfiguration process, which appears as the Access Runtime installer. Because registry usage depends on which Office component ran most recently, the issue can appear intermittently, making it hard to trace.

    This behavior has been widely reported as a registry and Windows Installer self-healing conflict, especially involving Access Runtime.

    To prevent this behavior long-term, consider the following:

    -Align the bitness: Use the same bitness for Office and Access Runtime (preferably 64-bit if Office is already 64-bit). This is the only fully supported and stable configuration.

    -Recompile the ACCDE to match target bitness

    When deploying a new Runtime, recompile the .accde using Access of the same bitness as the target machine (for example, compile with Access 64-bit if users run Office 64-bit). This avoids API / Declare issues and reduces re-registration conflicts.

    The Access community generally recommends releasing applications in the same bitness as the customer environment.

    I hope this explanation helps clarify both the cause and the resolution.

    If the answer is helpful, please click ""Accept Answer"" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    2 people found this answer helpful.
  3. George Hepworth 23,120 Reputation points Volunteer Moderator
    2026-02-07T13:05:13.86+00:00

    You should probably consider an alternative to installing both a runtime version and a full version of Access on a single computer. While it can be implemented, it does come with problems (as you've reported).

    One alternative is to create a Virtual Machine for the second installation, probably the runtime version.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.