Windows 10 and RB 02/18/2026 Update and bank feeds not working

[Charles Fleischmann]

I'm running QB Enterprise Solutions 24 on Windows 10 as my system will not support Windows 11. Ran "Bank Feeds" successfully  this morning and when I restarted my system this afternoon it installed "critical update" RB 02/18/2026. After this was complete, my non QB WebConnect bank feeds stopped working. The "Bank of America-New" splash screen would endlessly show the processing circle of dots for as long as I cared to wait. You have to close the window to get it to stop.

If you have a similar issue, the work around is to deactivate the Online services for that account and then log into the web site of the service, Bank of America in this case. Select the account in the web site you want and download the data using the "Web Connect for Qickbooks 2018 and above" for the file type. If you then open the downloaded file, it will ask you to associate the file with an account. Select the one you deactivated and it will import the data and report the success or failure of the import. Alternatively, you can go to the "File/Utilities/Import/Web Connect Files" menu option and import the file(s) that way.

I believe that this is a bug that is introduced by the update and it is not being handled. Support claims it is a security feature of the move to Windows 11. This "feature" should either be handled by version control within the update (i.e don't update a Windows 10 system) or by the code with a time out message or n.

[KenoLee_P]

Hi there, Charles. Appreciate you sharing the fix for the Bank Feeds issue after the RB 02/18/2026 update. Deactivating Online Services and manually importing the Web Connect file worked perfectly well.

This does appear to be a bug introduced with the update, and improved version control or handling for Windows 10 users would definitely enhance the experience. Rest assured that the QuickBooks Team is committed to addressing issues like this in future updates.

Thanks again for sharing your solution, it’s been incredibly helpful. If you have additional insights or questions, feel free to comment below.

[Charles Fleischmann]

KenoLee_P,

Thank you for the reply. I look forward to the bug fix which will restore the functionality the update broke.

One issue with the work around is that, at least initially, there are duplicate instances of the transactions that were previously uploaded. This requires research and deletion of the duplicates, not a practice supported by GLAPAR best practices.

Regards,

CF