BindContent.Exe preventing Quicken from running
Answers
-
This is getting really annoying already. Great product support! My sarcasm.
0 -
Nothing today……
0 -
anyone have any luck with getting the bind connect issue resolved?
0 -
As I said a few messages ago, I was able to use Time Machine to go back to a version prior to the update and everything is working fine.
0 -
I tried that and it’s still not working. Let me try it again with the walk around. I have to reinstall quicken again to see if it works. Just wish they would resolve the issue.
0 -
I am sorry which update are you referring to ? Quicken or the Mac OS ?
0 -
Drock, I installed this morning's update and was able to successfully link and download Citi's activity. NO change in the BindContent issue but at least this has been resolved.
0 -
Hey thanks for the update. I went back to a previous snapshot and got it working. I didn’t realize there was a quicken update today.
0 -
I got a popup notification this morning.
0 -
oh will have to go back in and check.
0 -
what version of quicken do you have? I checked for updates but none were available. Will check which version or update I have in the am
0 -
R59.10
0 -
I have R53.32. I think they are rolling that one out slowly
0 -
More ancillary info:
- Running Quicken Classic Premier vR59.10, build 27.1.59.10
- Windows 11 v23H2, build 22631.4317
- Parallels Desktop Pro v20.0.1 build 55659
- Just installed all this on recently purchased MacBook Air (M3), MacOS 14.6.1
I clicked NO on the BindContent question.
- Program seems to be running mostly fine after 5 minutes of testing.
- Doesn't seem to remember to open the last quicken file I used. Have to manually open quicken file.
- As others have stated, I have to re-login into my Quicken.com account when updating transactions.
- I tried using the Mac version of Quicken but it seems to be missing features that Windows version has. This forced me to use the Parallels/Windows version of Quicken. I wish the 2 Quicken platforms were feature equivalent…
0 -
Don't see a reply option to reply a particular post. so here goes to 2 fixes I've found, one a workaround another a accidental complete fix.
Fix workaround #1
BoatnmaniacQuicken Windows Subscription SuperUser ✭✭✭✭✭September 22I guess I should have been more specific. The workaround is in the 2nd post in that thread, not in the 1st post. The 2nd post says:I got around the BindContent problem by renaming the BindContent.exe file to BindContent.exe.old in:C:\Program Files (x86)\QuickenIf Quicken can't find the program, it ignores it.Tried this, clicking on NO in Bindcontrol.exe dialog box was only way to get quiken to run, renamed BindContent.exe file, ran quicken, program started and then would not open data document, had to manually open my document data file. Repeatable , sorta a fix.
#2 Complete fix: (for me, don't try unless your brave, or stupid fat fingered like me)
So I was working on configuring my Windows 11.pvm in parallels on my Macbook Air 15", and believe it or not accidentally deleted the windows pvm file. Ooooops !
My gosh another 1 to 2 days recreating a windows pvm ?, Nope
I was at the time NOT having the bindcontrol.exe issues on my Imac m3.
Fiirst I copied the .pvm I had on my desktop Imac M3 over wi-fi (or direct thunderbolt cable, or ethernet?) from my desktop to the parallels folder that usually contains the pvm files on my Macbook Air, and then copied the parallels windows application folder to my Macbook Air. Then redownloaded windows 11 and installed it. This allowed the parallels control center to show the windows .pvm , and allowed me to run windows 11 in parallel's.
I was really experimenting with this idea.
Believe it or not it worked, not only did I solve the bindcontrol.exe issue with quicken but also managed to get windows 11 on my macbook air back up and running without 2 days of reconfiguring and reinstalling applications. Just a few tweaks to some programs to get them configured correctly. Most the windows programs on my Imac m3 are the same on my laptop.
So now quiken running without bindcontrol.exe error and opens data document, i.e. running just fine.
Now I have no idea why the working quicken on the Imac M3 desktop didn't crash, but sure found a way to get windows 11 up and running on my macbook air M3 and without all the work to configure it again.
Needless to say I plan to backup my macbook air M3 right away, and will refrain from updating quicken on either machine to a newer version until I hear quicken has fixed the bindcontrol.exe error.
AZquikennaber
0 -
Does this mean it's more of a Quicken/Parallels issue than a Quicken/Windows issue? It sure seems like a long time for the programmers to figure this out.
0 -
I believe that all reports involve Parallels.
0 -
Same problem here; any update from Quicken or from Parallels?
0 -
Right now I have two Windows VMs— one from a backup I did prior to the BindContext.Exe issue and one with the updated Quicken software. I update the second VM on every Quicken update, and I am still seeing the error (as of the last update). The backup version with the non-updated software appears to be working correctly.
I would be curious is anyone using a Snapdragon Windows laptop is seeing the same error.
0 -
Got same issue…
Parallels: Version 20.1.1 (55740)
Older Windows VM Windows 11 Home 21H2 running Quicken 59.18 does not get the issue
Newly installed VM Windows 11 Pro 24H2 running Quicken 59.18 gets the BindContext.exe prompt on startup
1 -
Quicken support still has no update (or any info at all) on this but it appears to be specific to users running Parallels, so maybe their team (parallels) should also be looking into it. I would also think there's more programming knowledge on the Parallels side... Quicken is pretty basic and the development team doesn't seem to put a lot of time or energy into the Windows desktop version. I sent a support request to Parallels along with a Technical Data report but the number of Quicken Desktop users who also run Parallels is pretty small, so it might require several of us to make the same request.
0 -
@ifunlisted I agree. If Quicken Windows users running Quicken on a native Windows 11 machine are not having the problem, that seems to clear both Microsoft and Quicken of responsibility. This issue is happening running Quicken on Windows 11 on Parallels, so it seems it should be a Parallels problem to solve.
Quicken Mac Subscription • Quicken user since 19930 -
At the very least, since BindContent.exe lives in the Quicken folder maybe the Quicken folks can share the purpose of BindContent.exe so we can pass that along to Parallels support to help troubleshoot
0 -
The people who are not reporting this issue are all Windows users running on Intel processors. I have asked if anyone with Windows running on a Snapdragon processors are seeing this issue, but no one has reported that (or we have no users on this forum using Windows on ARM). I would not say that the issue is specific to Parallels until someone running WoA reports one way or the other whether it works.
Also, the issue occurred from a Quicken update not an update to Parallels or OSX. Going back to a previous release of Quicken always addresses the issue, even as updates have been released for Parallels and OSX. The issue is likely from a change to the Quicken code or a library they are importing during their build (possibly an old or deprecated version of a .NET library that is not compatible with the WoA Translation layer).0 -
It's definitely a Quicken issue, but since it only seems to be happening with users running Parallels, I think the hope is that there are some brighter minds on the Parallels Team who might be able to provide some helpful insight to the Quicken Team.
If it takes longer than a week to figure out a problem that seems like it should be simple to fix with an update (but has a major affect on usability), it suggests that the developers either don't have the knowledge/skills to fix it or just don't care enough to make it a priority. And it's now been 6-7 weeks.
It would be interesting to hear from WoA users but I'd venture to guess that most people here are not familiar with ARM or Snapdragon processors, and the ones who are are a pretty small minority. What we do know (based on the reports so far) is that Quicken users on Parallels have the issue, Quicken users not on Parallels don't have the issue.
I'm on a 2019 Macbook Pro (Intel I9) running the Sonoma OS 14.6.1, Parallels Standard 20.1.1, Windows 11 ver 24H2.
-1 -
Mac Studio M1 running Parallels WoA. I have 2 different VM instances (see post above). The older Windows 11 Home 21H2 does not have the issue, but at some point it stopped updating the OS through Windows Update. So I recently created a new VM which installed Windows 11 Pro 24H2, installed Quicken, and it did get the BindContent.exe issue. Both VMs running the latest version of Parallels and Quicken for Windows Desktop. The "fixes" above are a bit too hacky for me, so I am sticking with the older vm until an "official" fix found. So the issue appears related to a combination of Quicken version, Parallels and/or Windows Version.
1 -
It's now been two MONTHS and no resolution. Adding insult to injury, I was just billed for my annual subscription.🤬
0 -
@Jack's iMac I'm curious why you think Quicken should be doing anything, as it seems to be a problem in either Parallels or Windows for ARM. (I don't even know if Quicken tests their software for compatibility with various VM environments.) Have you pursued this issue with Parallels tech support?
Quicken Mac Subscription • Quicken user since 19930 -
Duplicate
0 -
jacobs, I've been using Quicken on a Mac since 2012. I've experienced various issues over the years but most are resolved in a reasonable amount of time. This issue, however, persists. It appears certain that the issue is confined to Parallels users but it'e caused by the Quicken application! I don't like workarounds for an application that I use daily and am paying for!
-1
