Microsoft 365 Installation Problems

How to Keep Access Database Engine Installed with Microsoft 365 Apps

Algirdas JasaitisAlgirdas Jasaitis Nov 2, 2026 870 views

Question details

Users need to maintain the installation of the Microsoft Access Database Engine alongside Click-to-Run Microsoft 365 Apps without it being removed by automated deployment policies.

How to Keep Access Database Engine Installed with Microsoft 365 Apps
Product
Microsoft 365 Apps and Access Database Engine
Device & OS
not provided
Scenario
Deploying Microsoft 365 Apps via Intune where the configuration is set to automatically uninstall Windows Installer (MSI) based Office products.
Observed behavior
The MSI-based Access Database Engine 2010 or 2016 is unexpectedly uninstalled from the system during the Microsoft 365 Apps deployment process.
Before you start

Ensure you have administrative access to your Microsoft Intune admin center and the XML configuration file used for deploying Microsoft 365 Apps.

Solution 1Recommended

Modify the Deployment XML to Prevent MSI Removal

Adjust your Microsoft 365 Apps deployment configuration file to prevent Intune from automatically uninstalling the Access Database Engine.

By default, Intune deployments for Microsoft 365 Apps may include an XML command that removes older MSI-based Office applications to prevent conflicts. Editing this XML configuration ensures your database drivers remain intact.

1
Access the deployment configuration

Log in to the Microsoft Intune admin center and locate the XML configuration file used for your Microsoft 365 Apps deployment profile.

2
Locate the RemoveMSI element

Open the XML file in a text editor and search for the `<RemoveMSI>` element within the configuration structure.

3
Modify the removal rules

To keep all MSI products, remove the `<RemoveMSI>` tag entirely. Alternatively, configure the tag to exclude the specific product IDs associated with the Access Database Engine.

4
Save and deploy

Save the modified XML file, upload it back to your Intune configuration profile, and push the updated deployment to your targeted devices.

Modify the Deployment XML to Prevent MSI Removal
Compatibility Warning: Running MSI-based Access Database Engines alongside Click-to-Run Microsoft 365 Apps is generally not recommended by Microsoft due to overlapping components. Thoroughly test the configuration in a staging environment.
Free Microsoft Office alternative

Need a Lighter Office Suite? Try WPS Office

If managing complex Click-to-Run and MSI installation conflicts for Microsoft 365 is slowing down your IT deployment, consider WPS Office. It provides a lightweight, highly compatible, and easy-to-deploy alternative without the strict installation conflicts associated with different Office deployment engines.

  1. 1. Download the installer: Visit the official WPS Office website and click the free download button to get the unified installer.
  2. 2. Run the setup: Open the downloaded executable file and follow the simple on-screen instructions to install the suite without complex XML configurations.
  3. 3. Open your files: Launch WPS Office and immediately start working on your existing Word, Excel, and PowerPoint documents with full compatibility.
Seamless compatibility with Microsoft Office file formats (.docx, .xlsx, .pptx)Lightweight installation with a single unified packageNo complex MSI vs. Click-to-Run deployment conflictsFree to use with a familiar, user-friendly interface
microsoft office alternative - wps office

Frequently Asked Questions

Why does Microsoft 365 Apps deployment automatically remove the Access Database Engine?

Microsoft 365 Apps use the Click-to-Run installation technology. When deployed via Intune with the `<RemoveMSI>` flag enabled, the deployment script automatically uninstalls older Windows Installer (MSI) based Office products to prevent software conflicts, which includes the Access Database Engine 2010 and 2016.

Can I run MSI and Click-to-Run Office products on the same computer?

Generally, Microsoft does not support installing MSI and Click-to-Run products of the same version on the same computer due to shared registry keys and file paths. It is highly recommended to use the same installation technology for all Office-related components to ensure stability.

How do I fix the 'Operating System is not presently configured to run this application' error related to Access Database Engine?

This error typically occurs due to a conflict between MSI and Click-to-Run installations. You can resolve it by uninstalling the MSI-based Access Database Engine and installing a newer, Click-to-Run compatible version, or by running an online repair for your Microsoft 365 installation.