Internal Browser Errors

Galen Gautreaux

The Quicken internal browser routinely fails me, which impacts so many areas of Quicken (Planning, Transaction Attachments, etc.). I have tried the usual fixes, including the Mondo upgrade, File Validate, Super File Validate, completely reinstalling Quicken. This happened on my Windows 10 machine, and the recently upgraded Windows 11 machine.

It surprises me occasionally by working flawlessly, but if I attach a document to a transaction, it breaks it again. An example is below, trying to view an attached document.

And trying to Explore What Ifs in Lifetime Planner…

Chris_QPW

The typical workaround for this is:

Close Quicken.

Delete this folder: C:\ProgramData\Quicken\Cache

Start Quicken and test.

Quicken Jasmine

https://community.quicken.com/discussion/comment/20471304#Comment_20471304

Hello @Galen Gautreaux,

Please let us know if this works for you!

Thanks!

Galen Gautreaux

Close Quicken, then delete this folder: C:\ProgramData\Quicken\Cache doesn't work either. I had already tried this, but failed to mention it in my original post. I've tried it again with fingers crossed this time, and it continues to fail.

Here's another tip… If I close Quicken, and relaunch it, the Lifetime Planner's Explore What If's works on the first attempt, but fails in all subsequent attempts. I think all of these problems are related.

Quicken Jasmine

Hello @Galen Gautreaux,

Would you mind providing me with the exact steps you take to receieve this error? This is so that I may attempt to replicate this issue within my own Quicken.

Thanks!

Galen Gautreaux

This is an intermittent problem, and ironically it it's working right now. But, I think my next Transaction Attachment will break it for use of the internal browser. Is there a log or Windows Event or file that can display information about internal browser failures?

Quicken Jasmine

Hello @Galen Gautreaux,

Thank you for coming back to update us. The next time this issue occurs, you can navigate to Help > Report a Problem and that will send over your logs files which could include internal error information.

Please let us know when it happens again!

Galen Gautreaux

So, when comparing the working version of C:\ProgramData\Quicken\Cache\Alert\CfgTpltCache.dat with the non-working CfgTpltCache.dat, I see the following differences related to specific alerts.

So apparently alert entries are inserted somehow by Quicken, but I suspect that they are breaking my internal browser. Since I don't use the alerts, I disabled all alerts, and now I cannot make Quicken's internal browser fail - it seems to have fixed my problems. Time will tell.

Galen Gautreaux

My internal browser is still working without a single instance of a problem since turning off all alerts. I suspect that the HTML inserted into CfgTpltCache.dat was malformed. I am confused why deleting the c:\ProgramData\Quicken\cache directory didn't fix my problem, but then again, I do not know what/when triggers the inserted HTML, so perhaps my CfgTpltCache.dat file was immediately getting corrupted. Regardless, Quicken needs to fix this.

Galen Gautreaux

As a test, I reenabled an alert (Common tax dates reminders), and my internal browser is broken again.

There are no differences between a working CfgTpltCache.dat file and the current (broken) file, so the problem is not based on CfgTpltCache.dat. But, it definitely appears to be related to alerts. I have since turned off the alert, but my internal browser continues to be broken.

As before, deleting c:\ProgramData\Quicken\cache is not fixing the problem. Is there something in C:\Users\vgg65\AppData\*\Quicken that related to alerts? Other than turning off alerts, I'm not sure what 'fixes' Quicken, but will continue to perform operations until it's working again.

Quicken Jasmine

Hello @Galen Gautreaux,

Thank you for providing more information. I would like to submit this issue for further investigation. Could you please provide the exact steps that you took to produce this issue and the exact troubleshooting steps that you have taken to attempt to fix it (and the workaround that you mentioned with turning off alerts)? This is so that I can reproduce the issue and provide further information to my team.

Thanks!