Clicking OFX file opens Windows Installer

If you haven't already, you may want to follow:

I got the very same problem using Q15, update 12. And the register window where new transactions are accepted no longer appears so I can't accept updates for any account.

I got the very same problem using Q15, update 12. And the register window where new transactions are accepted no longer appears so I can't accept updates for any account.

"Jim" wrote

When I attempt to open my bank's OFX file (for either of 2 accounts in separate QUicken files), with Quicken open, instead it opens a small Windows Quicken 2016 installer window and eventually asks for a source file, suggesting the 2016 CD).

------------------------------------------------------

I get the same dialog when I initiate a QFX download (attempted with Bank of America and Empower). [I have Q2016 R12 installed, but I also have Q2015 R12 and Q2017 R6 installed. I only use Q2016 and Q2017 for testing; and the unwanted install dialog pops up even when no Quicken version is running.]

But, once I cancel the unwanted install dialog, I find that the QFX download has succeeded (*), and I can use File > File Import > Web Connect File to import that downloaded QFX file.

So at this point, the unwanted install dialog is just an annoyance for me; it is not preventing the QFX download or the import of the downloaded QFX file.

But, once I cancel the unwanted install dialog, I find that the QFX download has succeeded (*), and I can use File > File Import > Web Connect File to import that downloaded QFX file.

-----------------------------------------------

Sorry, I forgot to make it clear that my regular Quicken version is Q2015 R12 and that is the version that I used to successfully import the downloaded QFX file.

But, once I cancel the unwanted install dialog, I find that the QFX download has succeeded (*), and I can use File > File Import > Web Connect File to import that downloaded QFX file.

---------------------------------------------------------

I have now successfully done the same File Import using Q2016 R12.

Thanks

I manually entered the transactions for one account. The import method worked just now for a different one although when I started Q 2016, I was given a Win 10 Security alert "Do you want to allow BindContent to make changes..." (leftover from the prior install session I suppose.) I answered no and Q opened and told me it was "successfully installed". Hopefully there's no issues from that, and that a patch comes along.

Yesterday evening, OSU prompted for the Intuit ID password. This morning, the issue appears to have been resolved. I am again able to use Windows to open the QFX and QDF files and access Life Planner (QW2016 R 12 Windows 7) If you're still able to reproduce the issue, I suggest resetting the Intu it ID password to see if authenticating might resolve the issue..

Will see what the next step is. Interesting you mention the Intuit ID password. In the year or so I have had the 2016 product, it has only on rare occasions asked for it. Usually starts without it. Maybe this is just when there are program updates??

Quicken support claims this is fixed, but ... Now, every time I open Quicken I get a Win 10 Permission dialog stating that Bindcontent.exe wants to make changes. So far I've said "no" each time but would like to stop this happening. I'm afraid of something else going wrong if I say yes.

Also, minor annoyance but even though the file history is present, I now have to manually choose a file to open each time I open Quicken.

Jim

-------------------------------------------------------------------------------------

Quicken support claims this is fixed, but ... Now, every time I open Quicken I get a Win 10 Permission dialog stating that Bindcontent.exe wants to make changes. So far I've said "no" each time but would like to stop this happening. I'm afraid of something else going wrong if I say yes.

Also, minor annoyance but even though the file history is present, I now have to manually choose a file to open each time I open Quicken.

----------------------------------------------------------------------------------------------

I believe the original problem is fixed. I see neither of your problems in Q2015 R12 or Q2016 R12. I am running 64 bit Windows 7.

You can try reinstalling Quicken and making sure you are updated to R12.

If you only use ONE Quicken file then make an icon the runs that file and Quicken will open it due to file association. Alternative is add the FULL file name to the existing Icon one space AFTER the Quicken command.