Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now

Power BI Desktop Refresh Issue

Power BI Desktop February 2026 — "Refresh All" Permanently Stuck on "Evaluating"

Issue Description:

After updating to the February 2026 release of Power BI Desktop, "Refresh All" hangs indefinitely on the "Evaluating" stage and never progresses. This affects multiple semantic models of varying sizes — not isolated to a single file or large model. Individual table refreshes complete without issue. The problem occurs only on "Refresh All"

Affected Versions:
- Version 2.151.1052.0 64-bit (February 2026) — issue present
- Version 2.151.1182.0 64-bit (February 2026 QFE) — issue still present

Working Version:
- Version 2.150.2102.0 64-bit (January 2026) — refresh completes normally

Environment:
- Data source: SQL Server (import mode)
- Multiple models affected, ranging from small to ~2.8 GB
- 64-bit Power BI Desktop
- Hardwired ethernet connection

Troubleshooting Steps Taken (none resolved the issue):
- Updated to the latest February 2026 QFE build (2.151.1182.0)
- Changed "Parallel loading of tables" from Default to "One (disable parallel loading)" under Current File > Data Load
- Individual table refreshes all complete successfully
- Reverted to January 2026 build (2.150.2102.0) — Refresh All works immediately, confirming this is a February 2026 regression

Expected Behavior:
"Refresh All" should evaluate and refresh all tables as it does in the January 2026 release.

Actual Behavior:
All tables remain in "Evaluating" status indefinitely. No error is thrown. The process must be force-cancelled. This behavior is consistent across multiple models of different sizes.

This is a clear regression introduced in the February 2026 release. Rolling back to January 2026 immediately resolves the issue. Please investigate and patch in a future QFE or the March 2026 release.

Status: New
Comments
chadmkelly
Regular Visitor
has this been resolved with the March 2026 release? @willdiles