Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now
Hello, may I ask a question?
Has anyone encountered issues with WebView2 crashing? I’m currently facing this problem when clicking Close & Apply and loading data.
So far, I’ve tried uninstalling and reinstalling Power BI, and also tried fixing it by unchecking “Enable load” for tables not used in visuals or relationships. I’ve also made some improvements to the Query Dependencies, but the issue still persists. (There are about 145 tables in the Query Editor.)
Does anyone have a permanent fix or any suggestions to resolve this? I can’t continue my work because of this. Thank you in advance.
Specs:
Task Manager Data while loading data.
Solved! Go to Solution.
Hi @GPS-DataAnalyst , Thank you for reaching out to the Microsoft Community Forum.
This points to a breakdown in how the Power BI interface renders large models, rather than a problem with your actual system resources. Even though your machine is powerful, the problem lies in the number of queries and the UI load they generate. Power BI uses WebView2 (based on Chromium) to render visuals and dialogs. When that rendering process exceeds what the sandboxed environment or Windows GDI can handle, it crashes. This isn’t about total RAM or CPU but about rendering limits and UI resource exhaustion.
Go to Power BI's options and disable hardware acceleration. This forces the app to use software rendering, which reduces strain on WebView2 and often stops these crashes. Next, update the WebView2 runtime using the official Evergreen installer from Microsoft’s Edge developer site, this replaces potentially buggy or outdated versions that ship with Power BI. Most importantly, consider breaking your PBIX file into smaller, domain-focused files. With this many queries, the model is simply too heavy for Power BI Desktop to handle reliably in one go. You can offload logic to dataflows or use shared datasets to keep everything manageable and still connected.
You don’t need to reinstall Power BI again. The crash isn’t unique to your setup, it’s a limitation of how Power BI Desktop handles large models with complex dependencies. The only reliable way forward is to reduce the rendering and query load inside the file.
If this helped solve the issue, please consider marking it “Accept as Solution” so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
Hi @GPS-DataAnalyst , Hope you are doing well. Kindly let us know if the issue has been resolved or if further assistance is needed. Your input could be helpful to others in the community.
Hi @GPS-DataAnalyst , I hope you're doing well! Just checking in to see if you had a chance to review the details shared earlier. If any of the information addressed your needs, feel free to mark it as "Accept as Solution" to help others in the community. Please let me know if you have any further questions!
Hi @GPS-DataAnalyst , I wanted to check with you and see if the provided information was useful. If any of it helped resolve your question, consider marking it as "Accept as Solution" to make it easier for others to find. Let me know if there's anything else I can assist with!
Hi @GPS-DataAnalyst , Thank you for reaching out to the Microsoft Community Forum.
This points to a breakdown in how the Power BI interface renders large models, rather than a problem with your actual system resources. Even though your machine is powerful, the problem lies in the number of queries and the UI load they generate. Power BI uses WebView2 (based on Chromium) to render visuals and dialogs. When that rendering process exceeds what the sandboxed environment or Windows GDI can handle, it crashes. This isn’t about total RAM or CPU but about rendering limits and UI resource exhaustion.
Go to Power BI's options and disable hardware acceleration. This forces the app to use software rendering, which reduces strain on WebView2 and often stops these crashes. Next, update the WebView2 runtime using the official Evergreen installer from Microsoft’s Edge developer site, this replaces potentially buggy or outdated versions that ship with Power BI. Most importantly, consider breaking your PBIX file into smaller, domain-focused files. With this many queries, the model is simply too heavy for Power BI Desktop to handle reliably in one go. You can offload logic to dataflows or use shared datasets to keep everything manageable and still connected.
You don’t need to reinstall Power BI again. The crash isn’t unique to your setup, it’s a limitation of how Power BI Desktop handles large models with complex dependencies. The only reliable way forward is to reduce the rendering and query load inside the file.
If this helped solve the issue, please consider marking it “Accept as Solution” so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.
I truly appreciate your advice. I’ll try following the methods you suggested and will come back to share the results with you.
You are invited to click the "Get in Touch" button and record your scenario in the dedicated thread.
Check out the November 2025 Power BI update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!