Unable to install Microsoft Access Database Engine 2016 (ACE 16.0) – installer doesn’t launch I downloaded the official Microsoft Access Database Engine 2016 (ACE 16.0) installer (accessdatabaseengine_X64.exe) from the Microsoft Download Center. When I

Gudipati, Satya (BC Pension) 0 Reputation points
2025-11-05T18:10:14.84+00:00

I downloaded the official Microsoft Access Database Engine 2016 (ACE 16.0) installer

(accessdatabaseengine_X64.exe) from the Microsoft Download Center.

When I run the file—either by double-clicking it or from Command Prompt as Administrator

nothing happens. No installation window, progress bar, or error message appears.

I also tried running the command:

accessdatabaseengine_X64.exe /quiet /passive /norestart

and verified that no ACE component appears under “Programs and Features” afterward.

Troubleshooting already attempted:

  • Verified that Microsoft Office 365 (64-bit) is installed.
  • Uninstalled any older 32-bit Office / Access components.
  • Rebooted the system and retried the installation.
  • Tried running with the /passive /log switch to generate a log file.
  • Confirmed Windows Server 2019 (64-bit) as the operating environment.

Despite these steps, the installer still does not execute or complete.

I need assistance installing the 64-bit Microsoft Access Database Engine 2016 (ACE 16.0)

driver, which is required for SSIS Excel connections in our development environment.

Microsoft 365 and Office | Access | For home | Windows
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Tammy-Ng 5,510 Reputation points Microsoft External Staff Moderator
    2025-11-06T04:22:45.0733333+00:00

    Dear Gudipati, Satya (BC Pension)
    Welcome, and thank you for sharing your issue in the Q&A forum.

    Based on the information you provided, I understand you're experiencing issues installing the Microsoft Access Database Engine 2016 (ACE 16.0) 64-bit, even after following several troubleshooting steps. The installer does not respond no interface, progress bar, or error message appears.

    Although you have Office 64-bit installed, the ACE 64-bit installer may still be blocked if remnants of a previous 32-bit Office installation remain on the system.

    1. Check Registry for Bitness Conflicts
    • Open Registry Editor (regedit) and navigate to:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration

    • If the Platform value is set to x86, this indicates a 32-bit configuration.
    • You may need to either:
    • Change the value to x64, or fully uninstall Office and reinstall a clean 64-bit version.
    1. Run Installer with Logging

    Try running the installer with a log switch to capture installation details: accessdatabaseengine_X64.exe /log install.log

    Then check the install.log file in the current directory for any recorded errors.

    1. Alternative: Install the 32-bit Version

    Even with Office 64-bit, you can install the 32-bit ACE driver to avoid conflicts between Click-to-Run and MSI-based installations.

    • Download accessdatabaseengine.exe (32-bit version) from the Microsoft Download Center.
    • Run the installer from an elevated Command Prompt: accessdatabaseengine.exe /passiveor accessdatabaseengine.exe /quiet
    1. Configure SSIS to Use 32-bit Runtime

    If you're using SSIS in Visual Studio (SSDT):

    • Open your SSIS project properties.
    • Set Run64BitRuntime = False.

    This ensures SSIS uses the 32-bit driver during execution.

    If you try these steps and still encounter issues, feel free to share any error logs or screenshots. I’m always here and happy to assist further!


    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.


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.