Fix Microsoft Access Crashes Involving mso.dll or OLEAUT32.dll
Question details
Identify and resolve random Microsoft Access crashes associated with mso.dll or OLEAUT32.dll.

- Product
- Microsoft Access
- Device & OS
- Windows; version not provided
- Scenario
- Access crashes while a user is working with a database, potentially after an Office update.
- Observed behavior
- Application Error 1000 reports exception code 0xc0000005 and may reference MSACCESS.EXE, mso.dll, or OLEAUT32.dll.
Note when the crash occurs and whether it affects one database or multiple databases. If Access opens, check File > Account > Product Information and record the Office version and update channel.
Run an Online Repair of Microsoft Office
Use Online Repair to address a potentially damaged Office installation, then check whether Access remains stable.
Close Access and any other open Office applications before starting the repair.
Open Windows Settings > Apps, then select Installed apps or Apps & features, depending on your Windows version.
Find Microsoft 365 or Microsoft Office, select Modify, and choose Online Repair > Repair. Follow the prompts; administrator permission and an internet connection may be required.
Reopen Access and the affected database, then repeat the actions that previously caused a crash.

Check the Office version and update channel
Use this check when crashes began after an Office update or occur on several computers.
Isolate the Windows profile or database environment
Test another Windows account and collect crash details if the issue continues after repair.
Use WPS Office for everyday documents and spreadsheets
WPS Office is a free, lightweight alternative for everyday office work, with a familiar interface and support for common Microsoft Office formats. It does not repair Microsoft Access or replace Access databases, but it can help you migrate document, spreadsheet, and presentation work.

Frequently Asked Questions
What does exception code 0xc0000005 mean in an Access crash?
It indicates an access violation, but it does not identify the root cause by itself. Check the Application Error event in Event Viewer > Windows Logs > Application and compare it with the Office version, user account, and database affected.
Does a crash involving mso.dll mean that the DLL should be replaced?
Not necessarily. The named module may be involved without being the underlying cause. Try Office Online Repair through Windows Settings > Apps before considering other troubleshooting.
How can I tell whether an Office update caused the crash?
Check Access > File > Account > Product Information for the version, build, and update channel. Compare them with Microsoft release notes and known issues, and ask IT whether other users on the same build are affected.
Why should I test Access under another Windows account?
If the same database works under another account, the original Windows profile or its settings may be involved. Use an account with permission to open both Access and the database.
Can WPS Office fix an Access database crash?
No. WPS Office does not repair Microsoft Access or replace Access databases. Use Office Repair and the Access troubleshooting steps above; WPS can be used separately for compatible documents, spreadsheets, and presentations.




