Dataflows Direct Query isn't working anymore since 144

[VDubois]

Hi,

The version 144 introduced a bug while refreshing a dataset getitng data from Dataflows Gen 1:

Could not load file or assembly 'System.IdentityModel.Tokens.Jwt, Version=8.1.2

I installed the latest version 2.146.1026.0 that is supposed to fix this issue:

Changelog => 

• Fixed DirectQuery failures for Gen1 Dataflows with Enhanced compute.

Still the same bug.... 

Could someone help or give a workaround?

Thanks !

[Nabha-Ahmed]

Hi @VDubois ,

This issue is known with recent Desktop versions. A couple of workarounds you can try:

1. Update to the very latest Power BI Desktop (September 2025 or newer) – sometimes the Store/MSI builds lag in fixes.

2. Clear the cache (File → Options → Data Load → Clear cache) and restart.

3. If still failing, roll back to version 2.143 (June 2025) which doesn’t have the bug. You can download older builds here: Previous releases of Power BI Desktop.

4. For Dataflows Gen1, consider testing Dataflows Gen2 if possible — this avoids many of the Gen1 limitations.

Docs: Troubleshoot connecting to Power BI dataflows

If this helps, please mark it as a solution ✅
— Nabha Ahmed (connect with me on https://www.linkedin.com/in/nabha-ahmed-166491221?utm_source=share&utm_campaign=share_via&utm_conten... ------

https://medium.com/@nnooonani2015/my-journey-with-microsoft-fabric-why-i-recommend-joining-this-comm...)

[v-menakakota]

Hi @VDubois 

Thanks for reaching out to the Microsoft fabric community forum. 

I would also take a moment to thank @Shahid12523  , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference. 

The suggested workaround is uninstalling, rebooting, clearing cached credentials, and reinstalling the latest Power BI Desktop.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.   

Best Regards, 
Community Support Team.

[VDubois]

Thanks for your help.

I have tried your workaround but the problem still persists.

I hope Microsoft will quickly find a solution.

[v-menakakota]

Hi @VDubois   ,

Since the issue still persists, this appears to be the known bug introduced in v144 affecting DirectQuery with Gen1 Dataflows.

At this point, the best approach is to temporarily switch to Import mode until Microsoft provides a permanent fix.

Best Regards, 
Community Support Team

[v-menakakota]

Hi @VDubois  ,

Can you please confirm whether the issue is sorted or not.

Thank you.

[VDubois]

Unfortunately the issue is not solved. Since switching to import mode is an irreversible action, we can't do that on our datasets....

[v-menakakota]

Hi @VDubois ,

Thank you for the update. Since switching to Import mode is not an option for your datasets and the issue still persists, I’d suggest opening a support ticket with Microsoft. This will allow the engineering team to directly investigate your specific scenario and provide guidance.

Please refer below link on how to raise a contact support or support ticket. 
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn 

Best Regards,
The community Support Team.

[VDubois]

Yes already done 2 weeks ago....

That 's why I have written on this forum, I am sorry to say the support is not very helpful. In one day you gave more help than the support.

[v-menakakota]

Hi @VDubois ,

Thank you for the update, Can you please share the Support ticket Number.

Regards,
Community Support Team.

[VDubois]

TrackingID#2508131420000976

Thanks

[v-menakakota]

Hi @VDubois ,

Can you please check support team has shared some mitigation steps, confirm whether they are working or not.

Thank you.

[VDubois]

Hi v-menakakota,

I confirm it is not working.

We found a way two weeks ago by copying old dll from previous versions. But, this is not a desirable solution as we have over 100 laptops. Moreover, with each new update it would have to be done again.

[VDubois]

Hi,

Some news about this issue.

We installed the latest version that is supposed to fix this bug.

We no longer have problem with refresh.

But now the visuals (table, graph) are all in error, the same error as before....

I had previously removed all permissions and completely uninstalled the previous version.

[v-menakakota]

Hi @VDubois ,

Even though refresh now works, the visuals (tables, graphs) can’t render since the app can’t find the right DLL version.

1.Make sure only version 6.16.0.0 of the DLL is installed. Remove any older copies left behind in system folders or the Power BI installation folder.

2.If all visuals are broken, completely uninstall Power BI Desktop and then install it fresh.

3.If you’re using custom visuals or connectors, update them so they point to version 6.16.0.0. In .NET projects, update the NuGet package.

4.Delete Power BI Desktop cache folders and reinstall the latest version to make sure no old files are being used.

Best Regards, 
Community Support Team  

[VDubois]

Thanks for the answer but it doesn't change anything.

Microsoft is looking for a solution....

[v-menakakota]

Hi @VDubois ,

Thank you for the update. Since you are already in contact with the Microsoft Support team, they are actively investigating the issue and will resolve it soon. We appreciate your patience.

[Shahid12523]

Power BI Desktop v144+ introduced a bug with Dataflows Gen1 DirectQuery (System.IdentityModel.Tokens.Jwt error).

Even in the latest v2.146.1026.0, many still face it.
Workaround:

Uninstall → reboot → clear Power BI credentials → reinstall latest → run as Administrator.

If still failing, use Import mode until Microsoft fully fixes it.

[Royel]

Hi @VDubois lets try some approach and see it work or not 

1. Uninstall your current Power BI Desktop version.
2. Restart your omputer. 
3. Clear any cached credentials:
   - Windows Credential Manager → Remove all Power BI related entries from Windows Credentials
4. Reinstall same Power BI Desktop (You have the latest version)
5. Run Power BI Desktop as an Administrator (Solved 95% of JWT authentication issues)
6. Check dataflow connection if failed 
7. Try to switch Import Mode 

Find this helpful? ✔ Give a Kudo • Mark as Solution – help others too!