CrossOver Support - Community Forums

As of today, June 10 2023, Quicken (fully updated) is now asking for Webview2 Runtime. I have installed Webview2 Runtime from the Crossover install menu, which indicates "limited functionality" of the program, into the bottle containing Quicken, but in spite of this Quicken still asks for it to be installed and apparently will not run without it.

Is there a workaround, and, if not, is a fix in the making?

I just hit this issue too.

I Tried installing Webview2 runtime into my existing Windows 10 bottle, but the installation fails with "Failed to cache the dowloaded installer. Error: 0x800b0109".

Also tried installing Webview2 runtime into a new Win 7 32-bit bottle (the tie indicated only Win 7 32-bit and Win7 64-bit are compatible.). Then did a complete Quicken installation into that bottle. No errors during install, but Quicken is still complaining that the Webview2 Runtime is not installed and refuses to run.

I also discovered the same issue this morning(June 10,2023) so you are not alone. I'll throw some time at it after lunch. A fix or workaround would be most welcomed. Perhaps the quicken manual patch might work better after the Webview2 Runtime install..

Same thing. Tried installing webview2, and edge in the same bottle as quicken. No go.

I am also having this problem. Reinstalled Quicken in a new bottle. Still doesn't work.

I'm in the same boat !

6-10 Quicken did some update for me as well. I'm running Debian 11 Bullseye (should it matter). I have no issues, still, running quicken.

I've had hassles and issues with Quicken and found enabling setting Emulate a virtual desktop fixes many of the graphics problems. Wine Configuration - Graphics tab, set Desktop size to monitor resolution.

I'm not real happy with it as it overtake my desktop (fortunate to have dual monitor), but it's more productive.

Don't know if the may or may not help. It doesn't actually "fix" anything, but it gets things working.

Hi folks,

Our developers are looking into a fix to get Quicken working again after its latest update. We don't have a workaround at this time, but please make sure to submit a support ticket so we can notify you once we have a fix for CrossOver. Apologies for the inconvenience; we know how frustrating it is when apps update and break.

All the best,
Meredith

I enabled "Emulate a virtual desktop" in the wine display configuration, and Quicken now seems to be working just fine. I have the dimensions set smaller than my actual display size so it doesn't take over the whole display.

Turning off the emulation and restarting causes Quicken to crash again.

Where is the wine config in the Crossover app ? Thanks

In the Crossover app, select the bottle you want to configure, and in the right pane look for "Wine Configuration" under "Control Panels". Open that and select the "Graphics" tab.

Thanks I found it but it will not let me click to change it. Thanks

Today I logged into quicken I got the webview2 message again but this time it was with the virtual desktop enabled. I tried toggling that off and then back on but that did not work. Quicken was working until I logged off and then it immediately returned to the webview2 download screen.

June 17, 2023
Quicken Deluxe Version DR50.8 Build 27.1.50.9 - Microsoft Windows 11
Crossover 22.1.1 on Debian 11 Bullseye

Everything still working without issue. As noted previously: In the bottle control panels > Wine Configuration, Graphics tab I enabled Emulate a Virtual Desktop. I found this "fixed" or otherwise eliminated some of the visual aspects. I'm not completely happy with this mode, but it's way less hassle.

Weather is the Win 11 and/or Virtual Desktop - Quicken still functions (opening and closing)

No issues

I had the webview2 message pop up once with virtual desktop enabled (after having it work fine numerous times). Quitting/restarting Quicken resolved the issue.

Peter, maybe try quitting/restarting Quicken a couple times but always with virtual desktop enabled?

please make sure to submit a support ticket so we can notify you once we have a fix for CrossOver.

Meredith

Jun 26, 2023
MacOS Ventura 13.4.1, Crossover 22.1.1
Quicken 2020 Deluxe V50.14, Windows 10 Bottle

I stumbled on this thread and discovered all of the same problems described, but I'm on a Mac and not Linux.
Wanted to be on the notification list just the same.

Thanks,
Jack Fecher

Jack Fecher wrote:

please make sure to submit a support ticket so we can notify you once we have a fix for CrossOver.

Meredith

Jun 26, 2023
MacOS Ventura 13.4.1, Crossover 22.1.1
Quicken 2020 Deluxe V50.14, Windows 10 Bottle

I stumbled on this thread and discovered all of the same problems described, but I'm on a Mac and not Linux.
Wanted to be on the notification list just the same.

Thanks,
Jack Fecher

Hi Jack,

You can submit a ticket here: https://www.codeweavers.com/contact-us

Best,
Meredith

I am having the same problem. I have submitted a ticket so I guess we just wait for a fix.

I've figured out how to roll back to an earlier version of Quicken as a temporary solution until this gets fixed.
I successfully rolled back to version R49.33 (it's version 50 and higher that doesn't work) by following these steps:

Download the current version from this page:
https://www.quicken.com/activate
by choosing "I'm installing or reinstalling Quicken".

Install that version into a new bottle using the "Quicken 2020" script in Crossover.
It looks like CodeWeavers has now added installation of WebView2 to the script, but that fails since it's only compatible with a Windows 7 32-bit bottle and not with the Windows 10 32-bit bottle that the script creates. You can safely ignore this error.
IMPORTANT: Do NOT actually run this version (uncheck the "Launch Quicken" box on the very last step of installation).

Download an earlier version (R49.33) from this page:
https://www.quicken.com/support/reinstalling-and-patching-your-quicken-subscription-version-after-your-membership-has

Run the patch in the new Quicken bottle created above.
IMPORTANT: Do NOT actually run this version yet (uncheck the "Launch Quicken" box on the very last step of installation).

In order to prevent Quicken from auto-updating and breaking, go to the C: drive of the bottle (click on "Open C: Drive" under "Bottle Actions"). Open the "ProgramFiles\Quicken" folder and rename "quickenPatch.exe" to "quickenPatch.exe.disabled".

Finally, start Quicken and you should be good to go.

Hope this is useful to others!

John Mostenan wrote:

I've figured out how to roll back to an earlier version of Quicken as a temporary solution until this gets fixed.
I successfully rolled back to version R49.33 (it's version 50 and higher that doesn't work) by following these steps:

Download the current version from this page:
https://www.quicken.com/activate
by choosing "I'm installing or reinstalling Quicken".

Install that version into a new bottle using the "Quicken 2020" script in Crossover.
It looks like CodeWeavers has now added installation of WebView2 to the script, but that fails since it's only compatible with a Windows 7 32-bit bottle and not with the Windows 10 32-bit bottle that the script creates. You can safely ignore this error.
IMPORTANT: Do NOT actually run this version (uncheck the "Launch Quicken" box on the very last step of installation).

Download an earlier version (R49.33) from this page:
https://www.quicken.com/support/reinstalling-and-patching-your-quicken-subscription-version-after-your-membership-has

Run the patch in the new Quicken bottle created above.
IMPORTANT: Do NOT actually run this version yet (uncheck the "Launch Quicken" box on the very last step of installation).

In order to prevent Quicken from auto-updating and breaking, go to the C: drive of the bottle (click on "Open C: Drive" under "Bottle Actions"). Open the "ProgramFiles\Quicken" folder and rename "quickenPatch.exe" to "quickenPatch.exe.disabled".

Finally, start Quicken and you should be good to go.

Hope this is useful to others!

Brilliant! Worked for me.

Thanks for the effort.

That IS a clever solution; I had wondered if that was possible, good to know that it is.
We've been limping along using a dual-boot laptop, but it is annoying to deal with the Windows interface. At least we can do our banking while we await the Crossover update.
Forrest & Kathy

Seems you can't add screen shots to posts. I'm still not dealing with this issue and would like to share my configuration with others...

Quicken Delux version R50.15 Build 27.1.50.15 - Windows 11 [as reported by Quicken]

Crossover 22.1.1 Bottle Type Windows 10 32-bit

OS: Debian 11.7 [Bullseye]

I do keep regular back-up on a FAT32 drive for emergency Windows use. (There's an old laptop or drive swapping, each requiring hour updating each time I use it. Dual booting, don't have enough use/need for Windows to bother anymore)

I know what it's like to be dependent upon Quicken! I hope you discover a recourse very soon.

Sincere thanks. It's working now for me also, after almost four weeks of frustration. I guess the next step is for Codeweavers to modify the script so that we can use the latest version.

One more Mac user with the same problem :-)

My current Quicken installation was a W7 32 bit bottle, and Quicken immediately exits as soon as the icon shows up (I don't even see a splash screen). I tried installing it fresh, where it suggested as W10 32 bit bottle, but that failed with the Webview2 runtime problem. Rather than force Quicken back to R49.x, I think I'm just going to use a VM for a bit, until this is resolved; otherwise, I'll never remember to reenable the automatic updates ;-)

I just reinstalled the latest Quicken (the website gave me R48.something, and it updated to R50.16) into a new bottle, but instead of choosing the default Win10, I chose a 32 bit Windows 7 bottle. It said it was incompatible, but it installed just fine, and the update to R50.16 succeeded without any issues.

One last message -- I just noticed that Webview2 is required if I have High Resolution Mode on, but not if I turn it off. Might be worth trying...

Thank you John Mostenen for your work around solution! It works just the way you listed the steps! Many thanks John!

Thanks John Mostenan. That worked for me except I just duplicated my existing non-working bottle rather than create a new one from scratch. I installed the version 49 patch over that and it seems to have downgraded it fine.

Limited Success. I found that if I launch Quicken without being connected to the Internet, then Quicken will load and run. But, if I reconnect to the Internet and attempt to update account info it stops running. So at least I can manually keep Quicken up to date. Once Quicken is up and running, its OK to log back on to the Internet -- just don't try anything that requires Quicken to access the Internet.

Does anybody if Codeweavers or Quicken are working on a fix. How widespread is this problem?

Yes, Crossover is aware: https://www.codeweavers.com/support/forums/general/?t=26;mhl=282604;msg=279606#c8

I've been using the "Emulate a virtual desktop" workaround successfully for a month now: https://www.codeweavers.com/support/forums/general/?t=26;mhl=282604;msg=279606#c9

There's another workaround posted in this thread which others are having luck with, but it requires downgrading Quicken to an older version.

John Mostenan wrote:

I've figured out how to roll back to an earlier version of Quicken as a temporary solution until this gets fixed.
I successfully rolled back to version R49.33 (it's version 50 and higher that doesn't work) by following these steps:

Download the current version from this page:
https://www.quicken.com/activate
by choosing "I'm installing or reinstalling Quicken".

Install that version into a new bottle using the "Quicken 2020" script in Crossover.
It looks like CodeWeavers has now added installation of WebView2 to the script, but that fails since it's only compatible with a Windows 7 32-bit bottle and not with the Windows 10 32-bit bottle that the script creates. You can safely ignore this error.
IMPORTANT: Do NOT actually run this version (uncheck the "Launch Quicken" box on the very last step of installation).

Download an earlier version (R49.33) from this page:
https://www.quicken.com/support/reinstalling-and-patching-your-quicken-subscription-version-after-your-membership-has

Run the patch in the new Quicken bottle created above.
IMPORTANT: Do NOT actually run this version yet (uncheck the "Launch Quicken" box on the very last step of installation).

In order to prevent Quicken from auto-updating and breaking, go to the C: drive of the bottle (click on "Open C: Drive" under "Bottle Actions"). Open the "ProgramFiles\Quicken" folder and rename "quickenPatch.exe" to "quickenPatch.exe.disabled".

Finally, start Quicken and you should be good to go.

Hope this is useful to others!

How do you ID 49.33 from the download page?

I also rolled back to ver 49.33 and it seems to be working... just have to make sure Quicken doesn't not update it again. I ran into issues when I renamed the QuickenPatch.exe file... Quicken kept freezing. I changed the name back and it's working fine but I have to cancel every time Quicken tries to update itself (annoying).

For any moderators or Codeweavers staff monitoring this thread, please give us an update on when we can expect a patch to resolve. Thanks!

Been running an old version of Crossover (21.1.0) and didn't have this issue until upgrading to 22. Went back to 21.1.0 and pointed Quicken at my file without issue. Just now Quicken upgraded to R51.12 and still no issue.

Hi folks,

CrossOver 23 is coming out mid-August. Please make sure you have a support ticket entered if you want an update once it's released.

Best,
Meredith

Meredith Johnson wrote:

Hi folks,

CrossOver 23 is coming out mid-August. Please make sure you have a support ticket entered if you want an update once it's released.

Best,
Meredith

v23 will only be available with a support ticket? Will others get some 22.x upgrade at least? or do we have to wait unnecessarily longer to get v23?

Everyone with active support entitlements will have access to CrossOver 23. If you wish to be notified once it has been released, that's where a support ticket entered can help.

Best,
Meredith

I just installed the new CrossOver 23 and then did a fresh install of the latest version of Quicken 2020.
All issues appear to be resolved - thank you CodeWeavers!

John Mostenan wrote:

I just installed the new CrossOver 23 and then did a fresh install of the latest version of Quicken 2020.
All issues appear to be resolved - thank you CodeWeavers!

Updating CrossOver wasn't enough? A fresh install of Quicken to resolve issues? ohh how I despise Windows stuff.

John Mostenan wrote:

I just installed the new CrossOver 23 and then did a fresh install of the latest version of Quicken 2020.
All issues appear to be resolved - thank you CodeWeavers!

Woohoo! Happy to hear it's working for you :)

Meredith

Thank you! I just installed the CrossOver 23, downloaded and reinstalled Quicken 2020 and all issues have been resolved. Great job!

Doug Kummerer wrote:

John Mostenan wrote:

I just installed the new CrossOver 23 and then did a fresh install of the latest version of Quicken 2020.
All issues appear to be resolved - thank you CodeWeavers!

Updating CrossOver wasn't enough? A fresh install of Quicken to resolve issues? ohh how I despise Windows stuff.

After I updated CrossOver, I just launched Quicken in my existing bottle and Quicken successfully upgraded itself to the latest release (R51.12). I did not have to do a new install of Quicken. I hope this works for all of you!

Quicken Inc wrote:

Doug Kummerer wrote:

John Mostenan wrote:

I just installed the new CrossOver 23 and then did a fresh install of the latest version of Quicken 2020.
All issues appear to be resolved - thank you CodeWeavers!

Updating CrossOver wasn't enough? A fresh install of Quicken to resolve issues? ohh how I despise Windows stuff.

After I updated CrossOver, I just launched Quicken in my existing bottle and Quicken successfully upgraded itself to the latest release (R51.12). I did not have to do a new install of Quicken. I hope this works for all of you!

I didn't say that updating CrossOver wasn't enough. I simply reported what I actually did. If you don't want to do a fresh install of Quicken, then don't.

John Mostenan wrote:

I didn't say that updating CrossOver wasn't enough. I simply reported what I actually did. If you don't want to do a fresh install of Quicken, then don't.

Very sorry for misunderstanding. Presumed user's want to get up and running. If it's working... leave well enough alone - if it isn't broke, don't fix it kind of thing.
-- ain't nobody got time for that 😀

Quicken R51.12 continues to with Crossover 22.1.1 for me without issues.