Quicken Windows: UAC popup on BindContext.Exe

The past few days, I have been getting a UAC popup on BindContext.Exe when I run Quicken Windows in Parallels Desktop on a M3 MacBook Pro. Selecting "Yes" on the UAC prevents Quicken from running (it terminates immediately), selecting "No" allows Quicken to start but it asks for the Quicken.Com username and password every time.

I posted this on the Quicken forum and several other users are reporting similar issues.

Anyone else seeing this and possibly have a solution?

Thanks!
Jim

 

yes, me too. Quicken have apparently found the bug. see here:
https://community.quicken.com/discu...tm_medium=organic-search&utm_term=bindcontent

 

Actually, I reported it to the Quicken forum and found a number of other users are having similar problems. They are looking into it now.
I was able to continue working by using Time Machine to go back to a revision of my W11 VM prior to the last Quicken update and then not accept any additional updates.

 

Quicken support still has no update on this but it appears to be specific to users running Parallels, so maybe their team (parallels) should 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 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.

 

It's a silly error that could easily be worked if the two companies would cooperate. I've sent this suggestion to both companies with a response from crickets.
For the moderators - please note that running quicken for window on macOS was the key reason I purchased the parallels product.

 

Agreed. It seems like something that would take about 5 minutes to fix if a developer would actually looked at it. The ONLY reason I use Parallels is because I have two programs (Quicken Desktop, TurboTax Desktop) that have to be run on Windows. I'll also add that I used Fusion for the last 10-15 years and Quicken worked fine there. The only reason I switched to Parallels is because I read it worked better with Windows 11.

 

I'm having this problem too.... I'm waiting to see if it's fixed in next few weeks before I purchase the Parallels upgrade, otherwise will just try to upgrade Quicken to the Mac version and deal with that (I prefer to use the windows version, that's why I use parallels).