How to Fix Microsoft Access Crashing on Windows 11 in Parallels
Question details
The user needs to resolve an issue where Microsoft Access silently closes when trying to open any database file within a virtualized Windows environment on a Mac.
- Product
- Microsoft Access
- Device & OS
- Windows 11 via Parallels (M1 MacBook Pro)
- Scenario
- Opening new or existing database files in Microsoft Access on an ARM-based Windows 11 virtual machine.
- Observed behavior
- Microsoft Access instantly crashes and closes without displaying any error codes or warning dialogues.
Before attempting to update or reinstall your software, restart your Parallels virtual machine to ensure no lingering background processes are interfering with Microsoft Office.
Update Windows 11 and Microsoft Access Builds
Installing the latest updates for both the Windows 11 ARM build and Microsoft Office resolves known compatibility and architecture translation bugs that cause the crash.
Early builds of Windows 11 on ARM and Microsoft Office 365/2021 had significant compatibility issues on M1 MacBooks. Updating Access to version 2112 (build 14827.20158) or newer, alongside the latest Windows 11 build, patches the specific fault causing silent crashes.
Open the Windows Start Menu, go to Settings > Windows Update, and click 'Check for updates'. Download and install all available system updates, then restart your virtual machine.
Since Access crashes upon opening, launch a different Microsoft Office program such as Microsoft Word or Excel inside your Windows 11 environment.
Click on 'File' in the top-left corner, select 'Account' (or 'Office Account'), click the 'Update Options' button, and choose 'Update Now'. Allow the process to complete and restart Access.
Completely Reinstall Microsoft Office Using the Support Tool
If standard updates fail, using Microsoft's official uninstallation tool removes corrupted registry keys and leftover files that a standard uninstallation leaves behind.
Diagnose the Crash Using Event Viewer
Use the built-in Windows Event Viewer to identify the exact module or DLL file causing the silent crash if updates do not fix the issue.
Try WPS Office for Stable and Native Productivity on Mac
While Microsoft Access is strictly for databases and requires virtualization on macOS, struggling with a buggy Windows VM can hinder your overall productivity. For your everyday document, spreadsheet, and presentation needs, switch to WPS Office. It runs natively on your M1 MacBook, eliminating the need for Parallels and bypassing Windows 11 ARM crashes entirely.
- 1. Download the Mac version: Visit the WPS website and download the native macOS installer.
- 2. Install the software: Open the downloaded file and drag the WPS Office icon into your Applications folder.
- 3. Open your Office files: Launch WPS Office and directly open your existing .docx, .xlsx, and .pptx files with zero formatting loss.
Frequently Asked Questions
Why does Microsoft Access crash without showing any error message?
Silent crashes in Microsoft Access, especially on virtual machines, usually happen when there is a fundamental architecture conflict—such as x64 emulation failing on an ARM-based processor. The application abruptly terminates before it can even generate a user-facing error dialogue.
Does WPS Office include a database alternative to Microsoft Access?
No, WPS Office is optimized for standard productivity tasks and includes a Word processor (Writer), Spreadsheets, Presentations, and a PDF editor. It does not include a relational database management system like Microsoft Access.
Can I run Microsoft Access directly on my M1 Mac without Parallels?
No. Microsoft has never released a macOS version of Microsoft Access. It remains a Windows-exclusive application, meaning you must use Parallels, VMware Fusion, or a cloud-based PC to run it on a Mac.
How do I check my current Microsoft Access version if the app keeps crashing?
Since the Office suite shares the same underlying build version, you can open another application like Microsoft Word or Excel. Go to File > Account, and look under the 'About' section to see the version and build number currently installed on your system.
