Excel Running Background Query Not Responding? Fix It

Errors & fixes · Updated November 21, 2026

If Excel says a background query is running and stops responding, first give the refresh a little time and check whether it is still making progress; large files and slow or unavailable data sources can take several minutes. If it appears stuck, try to cancel the refresh from Data > Queries & Connections, then refresh queries one at a time and disable background refresh for the affected connection if that option is available.

What the background query message means

A query retrieves or transforms data from another source, such as a workbook, database, text file, website, or organizational service. Excel can run some of this work in the background so you can continue using the workbook while the data is being refreshed. The message does not, by itself, prove that Excel has crashed. It can mean the query is still waiting for a response, processing a large result, or working through transformation steps.

There are two situations users often describe as Excel not responding. In one, Excel displays a status message but still accepts clicks and lets you switch worksheets. In the other, the whole application becomes unresponsive: the window may fade, show a Not Responding label in Windows, or stop reacting to keyboard input. A slow query can cause the second situation, especially when it consumes substantial memory or when Excel must wait for a source that does not respond promptly.

Background refresh is a way of scheduling the work, not a separate data source or a guarantee that the workbook remains usable. Turning it off can make Excel wait visibly for the refresh to finish, but it does not necessarily make the query itself faster. If the underlying source is unreachable or a transformation is inefficient, the query may still take a long time.

How Excel refreshes query data

In Microsoft 365 for Windows, Power Query is commonly used to connect to and transform data. Its results can be loaded to a worksheet table or the Data Model. A refresh re-runs the steps against the source, so Excel may need to reconnect, retrieve records, apply filters or calculations, and then update the destination. A query that loads a few hundred rows from a local file is a very different workload from one that reads millions of database rows across a slow network.

Workbooks can also contain older external-data connections, including connections made through database drivers or web and text imports. Those connections can have their own refresh properties. A workbook may contain several queries that depend on one another: refreshing a final report can require refreshing multiple upstream queries first. As a result, a single Refresh All command may do much more work than refreshing one visible table.

Excel may also be waiting on something outside the workbook. For example, a database might be busy, a VPN could have disconnected, a cloud service might require sign-in, or a file server could be slow. Excel cannot complete a request until the source or its driver responds. Repeatedly clicking Refresh All usually does not resolve that wait and may create additional work.

What to do before force-closing Excel

Start by deciding whether the application is working or truly stuck. If the workbook is responsive, save it before changing connections or query settings. Look at the status bar and the Queries & Connections pane for refresh activity, and consider whether the source is normally slow. On Windows, Task Manager can show whether Excel is using CPU, memory, or network activity. Activity is a clue, not proof: a process can be busy without making useful progress, while a query waiting on a server may show little activity.

Try these steps in order:

  1. Wait briefly if the refresh has just started, particularly for a large database query or a workbook with several dependent queries.
  2. If Excel still responds, open Data > Queries & Connections. Check which query is refreshing rather than starting another refresh.
  3. Use the available cancel option for the active query or connection. The exact options depend on the connection type and Excel version.
  4. If the workbook is responsive again, save it. Then refresh only the query you need, rather than using Refresh All.
  5. If the entire Excel window remains unresponsive for a prolonged period, avoid repeatedly clicking it. Allow a little time for recovery before using Task Manager to end the Excel process as a last resort.

Force-closing can lose changes made since the last save, and it may leave the workbook needing recovery. After reopening, check the Document Recovery pane if it appears, save a recovered copy, and do not immediately repeat the same Refresh All action. If the query repeatedly hangs at the same point, investigate its source and steps first.

Common reasons a query seems stuck

  • A slow or unavailable source: A network drive, VPN, database, website, or cloud service may be offline, overloaded, or responding slowly. Try opening the source separately or checking with the service owner.
  • Too much data: Importing an entire table when the report needs only a date range or a few columns can increase download time, memory use, and the amount Excel must process.
  • Expensive transformation steps: Merging large tables, sorting many rows, or applying operations that require the full dataset can take time. Some sources can process filters on their side; other transformations may require Excel to retrieve more data first.
  • Authentication or privacy prompts: Expired credentials, changed permissions, or privacy-level conflicts can interrupt a connection. Excel may need attention even if the prompt is not immediately obvious behind another window.
  • Driver or connection issues: Database connections rely on suitable providers or drivers. An outdated, missing, or incompatible provider can cause errors or delays that look like a query hang.
  • Several refreshes at once: Refresh All, automatic refresh on opening, or refresh settings on multiple connections can create competing demands on the same source and workbook.

One common misconception is that the phrase background query means the task is harmless to cancel or unrelated to the workbook’s visible data. A refresh may be updating a table used by formulas, PivotTables, charts, or other queries. Canceling generally stops the current refresh; it does not make incomplete results a reliable replacement for the last successful refresh. Check the loaded data and refresh status before relying on a report.

Disable background refresh for a connection

If Excel remains usable but the background behavior makes it difficult to tell when a query has finished, you can check whether the connection supports synchronous refresh. In Excel for Microsoft 365 on Windows, go to Data > Queries & Connections. In the pane, select the Connections tab if it is shown, right-click the relevant connection, and choose Properties. On the Usage tab, look for Enable background refresh and clear it, then confirm with OK. The wording and availability can vary by connection type; some Power Query connections do not expose the same setting.

With background refresh disabled, Excel generally waits for that connection’s refresh to finish before you continue working in the workbook. This can make progress easier to observe, but the interface may be unavailable for the duration. It is a troubleshooting choice, not a speed optimization. If the workbook’s source is slow, disabling background refresh can make Excel feel more blocked even when the refresh is proceeding normally.

To change a Power Query rather than a legacy connection, open Data > Queries & Connections, right-click the query, and choose Edit to inspect it in Power Query Editor. Check the query’s load and refresh options through the available query or connection properties. Do not assume every query has an Enable background refresh checkbox: the options shown depend on how the query is loaded and the connection involved. In Excel for Mac, connection-management options and feature availability can differ from Windows; if a particular property is absent, use the available query properties or test the refresh in the Windows desktop version.

Find the query or step causing the delay

Isolate the problem instead of changing many settings at once. In Data > Queries & Connections, refresh one query at a time and note which one takes unusually long. If a report query depends on other queries, identify those dependencies before concluding that the visible report alone is responsible. A query’s preview in Power Query Editor can help locate a slow step, but preview behavior is not always identical to loading the full result.

For a query that reads more data than needed, review whether you can filter rows early, remove unused columns, or limit the date range. For example, a monthly report may not need to import several years of transaction history if the source can return only the required period. Keep the result accurate: changing a filter can change totals, and removing a column may affect later calculations. If the source is a database, an administrator may be able to confirm whether the query is waiting on a lock or returning an unexpectedly large result.

Also check whether the workbook is set to refresh on open or at a recurring interval. In the connection properties, review the refresh controls available for that connection. Disable automatic refresh temporarily while diagnosing repeated hangs, but document the change so users know the report may no longer update automatically. If sign-in is the issue, refresh credentials through Excel’s data-source settings rather than repeatedly restarting the workbook.

Prevent the problem from returning

Make refreshes more predictable by reducing unnecessary work and keeping the source connection healthy. Avoid refreshing every connection when only one report needs updating. Where possible, narrow the data at the source, use stable network access, and ensure required database drivers and permissions are maintained. If a workbook is shared, tell other users which queries are safe to refresh and whether the workbook expects a VPN or a specific sign-in.

Keep a backup before changing query structure, especially in a workbook that supports operational or financial reporting. Test changes on a copy and compare important totals with a known-good result. If a query regularly takes longer than the time available, discuss source-side filtering, an extract schedule, or a more suitable reporting system with the data owner. Very large or frequently updated datasets may be better handled by a managed database or analytics service than by repeatedly loading all records into a worksheet.

For Excel for the web, connection and refresh capabilities are not identical to desktop Excel and depend on the data source and workbook configuration. If the browser version cannot manage the connection or provide the needed refresh controls, open the workbook in the desktop app and use its Data tab. Avoid editing the same workbook in multiple places while a refresh is in progress, because simultaneous changes can complicate which version of the data or workbook is current.

Frequently Asked Questions

How long should an Excel background query take?
There is no universal time limit. A small local file may refresh quickly, while a large database query or a slow network source can take much longer. Compare the duration with previous successful refreshes and check whether the source is active before deciding it is stuck.

Can I cancel a running query in Excel?
If Excel is responsive, open Data > Queries & Connections and look for a cancel option for the active refresh. Its location and availability depend on the connection. If the whole application is frozen, you may have to wait or end Excel through Task Manager, which can discard unsaved work.

Will turning off background refresh make Excel faster?
Not necessarily. It changes whether Excel waits for the refresh or lets it run in the background; it does not fix a slow source or reduce the query’s workload. It can make the wait more visible, but Excel may be unavailable until completion.

Why does Refresh All make Excel stop responding?
Refresh All can update multiple connections and dependent queries, so it may create a much larger workload than refreshing one table. Test connections individually, confirm that the source is reachable, and identify whether one query consistently causes the delay.

Is it safe to close Excel while a query is running?
Closing Excel can interrupt the refresh and lose unsaved workbook changes. Save first if possible, cancel the refresh through Excel when available, and force-close only when the application remains unresponsive and waiting is not helping.

Related

Try it: the Formula Explainer: paste any formula and see each function and reference in plain English.

More in Errors & fixes

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.