Enabling WebView2 not working

[slu]

I'm trying to enable WebView2 feature on my Power BI desktop, but somehow it's not working no matter what I do.

Here's all I have done to enable the feature:

• installed Microsoft Edge WebView2 (v. 95.0.1020.30)
• installed newest release of Power BI desktop (October 2021, v. 2.98.1004.0, 64-bit)
• enabled "Power BI Desktop infrastructure update" from Preview Settings
• cleared all Power BI caches
• restarted Power BI desktop multiple times
• restarted my computer (Windows 10 20H2)

And still, my Power BI uses IE11 for web contents.

Should I update my Windows to version 21H1, or am I missing something else?

[amreagan]

One of our applications that depends on WebView2 broke with the 95.0.1020.30 update. At the moment it's not clear whether the developer's implementation of WebView2 is at fault or if there's a broader issue with the 9.0.1020.30 release. You may want to try an earlier release of WebView2 if possible to see if you encounter the issue. However, the update mechanism to maintain WebView2 appears that it's intended to be automatic and reverting to a previous version may be easier said than done.

[amreagan]

I know that this problem is unrelated to Power BI, but it does point out that there is some issue with the 9.0.1020.30 release of WebView2. I'm only posting this information due to the fact that I was unable to find any other official information about a problem with this release. 

from: https://status.templafy.com/Templafy Status

Update - Microsoft have confirmed the problem with the WebView2 component and they are working on providing a fix.

We will update this issue as soon as new information is available.
Oct 26, 08:12 CEST

Update - After investigating on user computers, we have reason to believe that the following issues are causing the Templafy Add-ins to not progress beyond the loading screen and Templafy Desktop to report an error at startup.

https://github.com/MicrosoftEdge/WebView2Feedback/issues/1870
https://github.com/MicrosoftEdge/WebView2Feedback/issues/1860

We have reached out to Microsoft to confirm the problem is indeed with WebView2 95.0.1020.30.
Our initial investigation has shown that downgrading WebView2 to version 94.x or below resolves the issues. We strongly recommend that customers who encounter this issue, downgrade the WebView2 component.

We will keep this issue open until a workaround has been provided.

[slu]

@amreagan thank you for the information! Even though it's unfortunate that the WebView2 95.0.1020.30 has some issues, it's good to know that my setup should be fine.

For me this problem isn't crucial (yet), so I think I'm just gonna wait for Microsoft's fix for the problem.

[Anonymous]

Hi @slu,

Can you please share a pbix or some dummy data that keep raw data structure with expected results? It should help us clarify your scenario and test to troubleshoot.

How to Get Your Question Answered Quickly 

Notice: please not attach any sensitive data in your sample. 

Regards,

Xiaoxin Sheng

[slu]

Hi @Anonymous ,

I don't actually have any dummy data, since I'm trying to get the data from web, and Google Sheets won't open if Power BI if using Internet Explorer.

For example, when I'm accessing https://www.whatismybrowser.com/, I'll get this view:

When I'm trying to connect to Google Sheets, instead of getting login options, I only get an announcement that I need to update my browser and I can't click on anything, the view is just frozen:

I know that I can use data from Google Sheets via publising the sheet to public internet, but I would like to use Power Bi with Edge since it would be more secure.

Thank you for your time!

[Anonymous]

HI @slu,

Have you installed the prerequisite and runtime of edge webview2? If not, I'd like to suggest you install these environment softwares first.

Microsoft Edge WebView2 and Microsoft 365 Apps - Deploy Office | Microsoft Docs

In addition, if you enable this feature and open data connector the webview panel, have you turned on the 'task manager' to confirm 'msedgewebview2.exe' has been running at the backend? 

If that is the case, it may mean the webview2 features did not directly replace the original webview client. It may add some edge features to the webview to improve the function/features usages. (they did not fully invoke edge browser so that can't be recognized by test tools)

Regards,

Xiaoxin Sheng