Just upgraded to 11.2 and now I can not run .exe apps directly like in previous versions. When i try to run one, crossover now opens the install window to install the app as if it's an install file. I know I can use the run command, but was much easier to just double click. Is there a setting to change to go back to the old way, or is this the new way of crossover working?
This issue has been forwarded to the Official CodeWeavers Ticket System. If you have observed this issue and would like to report it as well, please open a support ticket or send an email to info@codeweavers.com with a description of what you are seeing and a link to this post.
This is actually intentional - I'm sorry for the inconvenience, here. We found that in a fairly strong majority of cases, especially with new users, the expected behavior upon clicking an .exe file was that Crossover would attempt an install (i.e. this was the behavior that most users reasonably expected to see). This, as you know, was not the case. Double-clicking on the .exe file caused "run command" to execute, and for a new user who did not have a bottle already created, this resulted in a confusing failure about the lack of a default bottle.
So - we swapped the default double-click behavior from cxrun to cxinstaller. I'm sorry to say that your primary use for double-click, here, has been thrown under the proverbial bus.
If it helps, you can create a launcher item directed to your .exe file from Run Command, so that you don't have to manually use Run Command each time:
Please Note: This Forum is for non-application specific questions relating to installation/configuration of CrossOver. All application-specific posts to this Forum will be moved to their appropriate Compatibility Center Forum.
CrossOver Forums: the place to discuss running Windows applications on Mac and Linux
CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.