These are often known as “R” releases, such as R3, R4, R5 and so on. QuickBooks by default is configured to automatically download patch releases. To Repair the QuickBooks installation, see QuickBooks Support – How to Repair QuickBooks If you’re experiencing QuickBooks connectivity issues, issues with QuickBooks ability to talk to other applications, or QB won’t run (or similar issues), then Repairing the QB installation will often help.
These issues can include instability, issues after applying a new release of your version year of QuickBooks, problems with QuickBooks’ ability to connect to external applications, and even the ability to install a patch release. We are tracking this problem, and if you start a support ticket, we will inform you when we learn more about the bug.Sometimes a QuickBooks installation causes issues and needs to be fixed. I also encourage you to write into CodeWeavers with a support ticket (reference bug number 12857). Once this is complete, it seems that you are able to launch Quicken again. Once the Wine Configuration window appears, make sure you have the "Applications" tab selected, and look at the bottom for the drop-down box labelled "Windows Version." Change this from "Windows 7" to "Windows XP." Press "OK" to exit Wine Configuration. Find the 'Control Panels' section at the bottom of CrossOver's main screen, and click on the icon labelled "Wine Configuration."
In order to do that, you can launch CrossOver and select the Quicken bottle. (Even though Quicken will not currently open for you, your data should be fine, so it is important to take care not to harm your data during the process of restoring Quicken to a working state).Īnother option which appears to work is to change the "bottle type" which CrossOver reports to Quicken. I would not recommend that you delete your Quicken entirely before creating a new one unless you are familiar with what you are doing, as I do not want you to risk losing data. If you are able to create a brand-new installation of Quicken in CrossOver, that appears to be a solution because new installs are able to successfully apply the Quicken update, whereas existing installations are not. A Quicken update released today has caused this to happen to many users.
0 kommentar(er)
