Microsoft Access often seems to freeze in one of a few places: the app itself, the file, a query, or the network. Check them in that order. Restarting Access only fixes hangs at the app layer.

Pick the wrong layer and you burn time. You can also push a weak database harder, and the same hang may return during edits, saves, or linked-table loads.

This guide shows how I sort out the layer quickly, which symptoms point to each cause, and the fixes that usually stop the freeze.

What Access freezing usually means

A freeze in Microsoft Access is often a hang rather than a crash. The window stops repainting, the title bar shows Not Responding, or a command never returns while the process stays open in Task Manager.

Freezing at startup

Startup hangs often point to add-ins, custom startup code, or a damaged app installation. If Access opens a blank file but not one specific database, the file is the better suspect.

Freezing when opening a form or report

That pattern usually points to a heavy form, a report with expensive queries, or load-time code. Subforms, unbound events, and images can stall the UI before the object finishes drawing.

Freezing during a query or save

Query stalls usually come from missing indexes, locks, or a slow linked table source. A save that never finishes can also point to file corruption or back-end network trouble.

Likely causes, ranked from most common to least

Most often, Access freezes because of a corrupt database file, add-ins or startup code, linked tables or network back ends, slow queries, heavy forms or reports, or a damaged Office installation. The best fix depends on which layer fails.

Symptom pattern Most likely layer First test
Freezes on one database only File Open a blank database
Freezes before any file opens App or add-in Start in Safe Mode
Freezes only on linked tables Network or back-end Open the source data directly
Freezes on one form or report Object design Open a different form or report
Freezes after an update App installation Repair Office

Have you backed up the file first?

Back up first because Compact and Repair, import-and-rebuild work, and some recovery steps can write to the database. If the file is already weak, a bad repair can make recovery harder.

What to copy before you start

Copy the .accdb or .mdb file, any back-end file, and any companion files used by the app. Keep the copy on local disk, and use a new filename so the original stays untouched.

  1. Close Access.
  2. Copy the database file to a new folder.
  3. Copy the back-end file if the front-end uses linked tables.
  4. Open the copy, not the original, for repair work.

When to stop and restore instead of repairing

Stop if the database will not open after a repair attempt, objects disappear, or corruption returns at once after the same action. At that point, restore the last known good backup and rebuild the changed objects into a clean file.

Is Access itself the problem?

If another database opens normally, the app is probably fine and the problem sits in one file. If Access hangs before any file opens, Safe Mode and add-in testing help separate app damage from database damage.

Open a second database or a blank file

Open a second database that is known good, or create a blank file with File > New > Blank database. If that opens normally, the freeze is probably tied to the original file or its linked data.

Start Access in Safe Mode

Close Access, press Windows + R, type msaccess /safe, and press Enter. That starts Access without many customizations and add-ins, so startup hangs are easier to trace.

Disable add-ins and test again

Go to File > Options > Add-ins. At the bottom, manage COM Add-ins and clear nonessential entries, then restart Access. I’ve seen add-ins freeze startup and clash with an Office update.

Does the database file need repair?

Does the database file need repair?

If only one database freezes, the file is a strong suspect. A corrupt Access database file often causes hangs during open, save, compact, or form load, and minor corruption sometimes clears after repair on a copy.

Run Compact and Repair on a backup copy

Open the copied file, then choose Database Tools > Compact and Repair Database. It is safest to run it on a backup copy first. If the repair completes and the file opens normally, test the failing action again.

  1. Close every open object in Access.
  2. Open the backup copy.
  3. Select Database Tools > Compact and Repair Database.
  4. Wait for the process to finish before opening forms or queries.

Watch for signs of deeper corruption

If Compact and Repair does not help, or if the same forms, queries, or tables still hang after repair, the file may need more than maintenance. Export or import objects into a new blank database instead of repeating the same repair cycle.

Import objects into a new database if repair fails

Create a new database, then import tables, queries, forms, reports, macros, and modules in stages. Test after each batch. If one object type triggers the freeze, that object is the one to rebuild.

Are linked tables or the network causing the hang?

Linked tables can make Access look frozen when the source system is slow, offline, or locked. The front-end waits on the back-end, so the UI can stop responding even when the local file is fine.

Test the back-end connection

Open the source data directly, then open the linked table again. If the source will not open cleanly, fix the back-end first. Also test the same action from another machine to separate local from network causes.

  1. Confirm the back-end file or database server is reachable.
  2. Open the linked table source directly.
  3. Retry the linked table in Access.
  4. Compare behavior on another user account or another PC.

Check whether the issue happens on one machine or for one user

If only one machine freezes, look at that workstation, its network path, and its Access installation. If only one user freezes, compare add-ins, trusted locations, and the user’s startup path. If every user freezes on one file, the back-end or file is the likely fault.

How do I stop Microsoft Access from freezing when I run a query?

Long-running query execution, missing indexes, and lock contention are common reasons Access appears frozen during a query. The app may still be working, but it is waiting on too much data or on another user’s lock.

Reduce the work the query has to do

Open the query in Design View and remove unneeded joins, sorts, and calculated fields. Filter early, return fewer rows, and add indexes on joined fields. If the query runs against a linked table, test it against a local copy first.

  1. Open the query in Design View.
  2. Check joins for fields that lack indexes.
  3. Remove broad filters and test smaller date ranges.
  4. Run the query again and note where it stalls.

Check for locking contention

If freezing happens during edits or saves, another user may already hold the lock. Split the front-end from the back-end, confirm each user has a separate front-end copy, and test the query when the other user is out of the file.

Why do forms and reports freeze Access?

Forms and reports freeze when they try to load too much at once. Heavy controls, subforms, repeated queries, and load-time event code can stall repainting and make the window seem dead even when the file itself is fine.

Open the object with fewer moving parts

Open the form or report in Design View and disable expensive controls one by one. Remove image controls, reduce subform count, and test whether the object opens when its data source is simplified.

  1. Open the object in Design View.
  2. Set the record source to a smaller query.
  3. Disable subforms and custom event code temporarily.
  4. Save, close, and reopen the object.

Look for load or repaint code

Check Form Load, Current, Open, and report event procedures. A long VBA routine, especially one that hits linked tables, can freeze the interface before the object fully opens.

When should you repair Office instead of the file?

Repair Office when Access freezes in more than one database, Safe Mode still hangs, or the problem began right after an update or Office upgrade. That points to the app installation rather than a single damaged file.

Use Quick Repair first

Go to Control Panel > Programs and Features, select Microsoft 365 or Microsoft Office, choose Change, then run Quick Repair. This is the least disruptive repair and often fixes damaged program files.

Use Online Repair if Quick Repair fails

If Quick Repair does not fix the freeze, run Online Repair from the same Change menu. It takes longer and reinstalls more of Office, so use it only after confirming the problem follows the app rather than one database.

Should I repair Microsoft Office or just the Access file?

Repair the Access file when one database freezes, but repair Office when every database has the same problem, Safe Mode still hangs, or the issue began after an update. The wrong repair wastes time and can hide the real fault.

Use this decision path

  1. Open a different database.
  2. If the new file works, repair the original file copy.
  3. If every file freezes, start Access in Safe Mode.
  4. If Safe Mode helps, disable add-ins.
  5. If Safe Mode does not help, run Office Quick Repair.
  6. If Quick Repair fails, run Office Online Repair.

How do I open Access safely if it keeps hanging on startup?

Use Safe Mode first, because it starts Access without many customizations and add-ins. If the file opens there, the startup hang is usually in the environment, not in the database itself.

Use a clean startup path

Press Windows + R, run msaccess /safe, and open a known-good file only after Access loads. If that works, disable add-ins and remove custom startup actions before trying the problem file again.

Try a new blank database

Create a blank database with File > New > Blank database. If a blank file opens but the problem file does not, focus on the file, its linked tables, and its objects rather than the app installation.

Frequently asked questions

Why does Microsoft Access keep freezing when I open my database?

The usual reason is a fault in the file layer, especially corruption, linked tables, or startup code in the database. Open a different file first. If that works, the original database needs repair, import into a new file, or a check of its linked back end.

How do I stop Microsoft Access from freezing when I run a query?

Open the query in Design View and cut its workload. Add indexes on joined fields, narrow the filter, and test the query against local data. If it only freezes with linked tables, the back-end or network path is the part to fix.

Does Access freeze because of a corrupt database file?

Yes. A corrupt file can hang on open, save, or object load. Copy the file first, then run Database Tools > Compact and Repair Database on the copy. If that fails, import the objects into a new blank database.

Will compact and repair fix Access freezing?

It can fix minor corruption and database bloat, but it will not repair every freeze. Run it on a backup copy, not the only original file. If the freeze comes from add-ins, network links, or Office damage, Compact and Repair will not solve it.

Can add-ins or linked tables make Access hang?

Yes. Add-ins can freeze startup, and linked tables can stall when the back end is offline, slow, or locked. Test by starting with msaccess /safe and by opening the source data directly. Those two checks separate app issues from network issues quickly.

Why does Access freeze after an update or Office upgrade?

That pattern points to the app installation or a changed add-in. Start in Safe Mode, then run Quick Repair from Control Panel > Programs and Features > Microsoft 365/Microsoft Office > Change. If the problem remains, use Online Repair.

Still not working?

Still not working?

If the freeze survives backup, Safe Mode, add-in removal, file repair, and Office repair, the next step is a clean rebuild: create a new database, import objects in small groups, and isolate the one object or linked source that triggers the hang.

Recovery order that avoids more corruption

  1. Back up the original file and its back end.
  2. Test a different database or blank file.
  3. Start Access in Safe Mode and disable add-ins.
  4. Run Compact and Repair on a copy.
  5. Check linked tables and the network back end.
  6. Repair Office if the problem follows the app.
  7. Restore from the last good backup if corruption returns.

Prevention

Keep a dated backup before major edits, and do maintenance on copies first. That habit makes recovery far easier when Microsoft Access keeps freezing again.