Your organization has been distributing an Access database application for years. Users run it via Access Runtime — they don't have a full Office license, just the runtime that lets them open the .accdb file. Now you're rolling out Windows 11, and suddenly Access Runtime won't install. Or it installs but forms don't render. Or it installs fine but crashes on a specific form that's worked since 2014.
This is a common and frustrating situation. The short version: Access Runtime 2016 and older have real problems on Windows 11. Here's what works, what doesn't, and what your actual options are — including the ones nobody wants to admit exist.
| Access Runtime Version | Windows 11 Status | Notes |
|---|---|---|
| Microsoft 365 Runtime | Works | Continuously updated, best compatibility |
| Access Runtime 2021 | Works | Clean install, stable, recommended |
| Access Runtime 2019 | Works | Free download from Microsoft, installs cleanly |
| Access Runtime 2016 | Partial | Installation frequently fails; form rendering bugs on 24H2 |
| Access Runtime 2013 | Broken | Installer fails; unsupported by Microsoft |
| Access Runtime 2010 and earlier | Broken | Incompatible with Windows 11's security model |
Note: "Works" means installs cleanly and runs standard .accdb databases. Complex applications with ActiveX controls, 32-bit API calls in VBA, or legacy DAO/ADO patterns may have additional issues regardless of runtime version.
Access Runtime 2016 is where most organizations are stuck. It was solid on Windows 10 for years. On Windows 11 — especially the 24H2 update released in late 2024 — it has three categories of problems.
The most common errors during installation:
The root cause: Access Runtime 2016 uses the Click-to-Run installation engine, which has compatibility issues with Windows 11's updated virtualization and security stack. Microsoft's own support documentation acknowledges this without providing a clean fix for 2016.
Even when Access Runtime 2016 installs successfully, Windows 11 24H2 introduced rendering changes that cause:
These aren't fatal crashes — they're UI bugs that make the application look broken to end users even when the data layer is functioning correctly. For a database application used daily by non-technical staff, these visual bugs erode trust fast.
If your Access application uses VBA with 32-bit Windows API declarations, those will fail in 64-bit environments. This isn't new to Windows 11 — it's been a problem since Office 2010 added 64-bit support — but organizations that stayed on Windows 10 + Office 32-bit indefinitely are now hitting it for the first time.
See our guide on auditing Access VBA before migration for a complete list of the API patterns that need updating.
If you're committed to staying on Access Runtime 2016, here's the approach that has the highest success rate:
Microsoft offers both Click-to-Run and MSI versions of Access Runtime 2016. The Click-to-Run version is what most people download from the Office portal. The MSI version is on the Microsoft Download Center and installs differently — it's more compatible with Windows 11's security model.
Search for "Microsoft Access 2016 Runtime" on the Microsoft Download Center. Download the accessruntime_4288-1001_x64_en-us.exe or equivalent MSI package, not the streaming installer.
Windows 11's memory integrity feature (also called Hypervisor-Protected Code Integrity, HVCI) can block older Office installers from writing to protected memory regions. To disable it temporarily:
This is a security trade-off. Don't leave memory integrity disabled permanently.
If a previous Access Runtime installation failed partway through, it may have left registry entries and files that block new installations. Microsoft's Support and Recovery Assistant (SaRA) tool can clean up Office installation residue. Run it before attempting a fresh install.
If the Access Runtime 2016 workarounds sound like more trouble than they're worth, that's because they are. Access Runtime 2019 is a free download from Microsoft, installs cleanly on Windows 11 (including 24H2), and is backward compatible with .accdb databases created in Access 2016.
The migration path from Runtime 2016 to 2019:
Declare statements — 2019 is available in both 32-bit and 64-bit — the 64-bit version requires PtrSafe declarationsThe VBA compatibility requirement is the most common sticking point. Our VBA audit guide covers how to find and fix all 32-bit API declarations in your Access codebase.
LegacyLeaps scans your .mdb and .accdb files and generates a report of all VBA API calls, ActiveX controls, and linked tables before you touch anything.
Run the Free ScanMany organizations running Access Runtime have a database that started as a simple data entry tool and grew into the core of a business process — inventory management, job tracking, client records, scheduling. The application works. Everyone knows how it works. Nobody wants to touch it.
But Access Runtime compatibility will keep getting harder. Microsoft 365 no longer includes Access in all subscription tiers. Windows 11 security features will continue to tighten. And at some point, Access Runtime will reach end-of-life for supported Windows versions just as Office 2016 already has.
If you're already troubleshooting runtime installations, you're closer to that inflection point than you think.
The shortest-term solution. Buys 3–5 more years of compatibility. Still requires someone to maintain an Access application that may have limited institutional knowledge about how it was built.
If you're running on .mdb format, converting to .accdb first is a prerequisite for long-term compatibility. See our guide on converting .mdb to .accdb — it covers the format differences and what to test after conversion.
For organizations where the Access database is effectively the application — not just a data store — the long-term answer is moving to a web-based tool that doesn't require a runtime install on every user's machine.
This used to mean a major custom development project. AccessLeap is a new tool we're building that generates a modern web application directly from your Access database schema. It reads your forms, queries, and relationships and produces a working web app — without requiring your database to be uploaded to any cloud service. Your data stays local until you're ready to deploy.
If you're facing Access Runtime compatibility problems and the database is a business-critical application, this path eliminates the runtime problem entirely.
Before deciding which path to take, it helps to know exactly what's failing. Here's how to diagnose Access Runtime problems systematically:
Go to Event Viewer > Windows Logs > Application and filter for errors with Source = "MsiInstaller" or "Application Error". Installation failures almost always generate a detailed error here, even when the installer itself shows nothing useful.
Click-to-Run creates a setup log at %temp%\OfficeSetup.log. Open this in a text editor and search for "error" to find the specific failure point.
Before rolling out Access Runtime to 50 machines, test the full installation and application behavior on a clean Windows 11 VM — no previous Office installations, standard user account, no domain policies. This tells you whether the problem is the runtime itself or your environment.
Many Access applications use ActiveX controls for features that Access forms don't provide natively — calendar date pickers, progress bars, rich text editors, embedded charts. These controls are COM objects registered on the machine.
On Windows 11, many legacy ActiveX controls simply won't register. Microsoft has tightened the security requirements for COM object registration, and controls compiled for 32-bit Windows or built against old COM libraries won't work.
If your Access application uses ActiveX controls, test each one specifically on a Windows 11 machine. The ones that fail need to be replaced — either with native Access alternatives or with custom VBA code. Our guide on replacing ActiveX controls in Access covers the common substitutes.
It depends on the version. Access Runtime 2019 and 2021 install and run on Windows 11 without significant issues. Access Runtime 2016 has installation problems on Windows 11 24H2 and form rendering bugs. Access Runtime 2013 and earlier should be considered unsupported on Windows 11.
Access Runtime 2016 and earlier use a Click-to-Run installation engine that conflicts with Windows 11's security model. Common errors include error 1935, error 30015, and silent failures. The fix is usually to use the MSI-based installer or upgrade to Access Runtime 2019.
Sometimes, with workarounds. Use the MSI installer (not Click-to-Run), temporarily disable Windows 11's memory integrity during installation, and run as Administrator. Even when installed, Access Runtime 2016 has known form rendering bugs on Windows 11 24H2. Access Runtime 2019 is a cleaner upgrade path.
For maintaining existing .accdb databases: upgrade to Access Runtime 2019 (free from Microsoft). For organizations where the database IS the application: converting to a modern web app using AccessLeap eliminates the runtime dependency entirely — no desktop install required.
LegacyLeaps migrates .mdb databases to .accdb and audits your VBA for 64-bit compatibility. AccessLeap can turn your Access application into a modern web app that doesn't need a runtime at all. Run the free scan to see what you're working with.
Download Free ScannerPractical fixes for legacy Excel and Access problems. No spam.