# Vassal 3.6.5 crashes on startup for MacOS 12.2.1 **URL:** \ **Category:** Technical Support & Bugs\ **Created:** [February 16, 2022, 5:47pm UTC](https://forum.vassalengine.org/t/vassal-3-6-5-crashes-on-startup-for-macos-12-2-1/73929 "2022-02-16T17:47:43Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![gdaudin](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/g/71e660/32.png) [@gdaudin](https://forum.vassalengine.org/u/gdaudin)\ **Post date:** [February 16, 2022, 5:47pm UTC](https://forum.vassalengine.org/t/vassal-3-6-5-crashes-on-startup-for-macos-12-2-1/73929/1 "2022-02-16T17:47:43Z")
Hi, I just installed Vassal 3.6.5 and it simply crashes on startup. No error message. I have 16Go of RAM, 3.6.4 works fine, Guillaume ---
**Author:** ![marktb1961](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/marktb1961/32/231_2.png) [@marktb1961](https://forum.vassalengine.org/u/marktb1961)\ **Post date:** [February 16, 2022, 6:07pm UTC](https://forum.vassalengine.org/t/vassal-3-6-5-crashes-on-startup-for-macos-12-2-1/73929/2 "2022-02-16T18:07:15Z")
Sounds like you’ve installed Vassal for the wrong Mac architecture. What Mac model are you using and what install option are you presented with on the Vassal home page, [here](https://vassalengine.org/) (example below) ? ![image](https://forum.vassalengine.org/uploads/default/original/2X/2/286fa8d5c1526e2961d389b29d1ef76551a86348.png) ---
**Author:** ![gdaudin](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/g/71e660/32.png) [@gdaudin](https://forum.vassalengine.org/u/gdaudin)\ **Post date:** [February 16, 2022, 6:19pm UTC](https://forum.vassalengine.org/t/vassal-3-6-5-crashes-on-startup-for-macos-12-2-1/73929/3 "2022-02-16T18:19:47Z")
Thank you for your help. I have Vassal for x86 Intel, and have an Intel Mac. I just realized that holding the command button while double clicking on Vassal leads to a successfull startup sequence (without Apple’s dialogue about unverified application. And then opening Vassal works normally. So the bug must have been linked with Apple’s protection against “unverified” applications ? I have removed and re-installed Vassal and cannot reproduce the bug anyway… Which is good, in a way ! ---
**Author:** ![JoelCFC25](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/joelcfc25/32/2687_2.png) [@JoelCFC25](https://forum.vassalengine.org/u/JoelCFC25)\ **Post date:** [February 16, 2022, 6:27pm UTC](https://forum.vassalengine.org/t/vassal-3-6-5-crashes-on-startup-for-macos-12-2-1/73929/4 "2022-02-16T18:27:57Z")
> [@gdaudin](#): > > So the bug must have been linked with Apple’s protection against “unverified” applications ? This isn’t a bug in VASSAL or MacOS. This is Apple’s Gatekeeper security protocol doing what it’s intended to do. [You can view steps to deal with it here](https://vassalengine.org/wiki/Troubleshooting_Common_Problems#.28Mac.29_.22VASSAL_cannot_be_opened_because_the_developer_cannot_be_verified._MacOS_cannot_verify_that_this_app_is_free_from_malware..22), or Google how to change the Gatekeeper settings in MacOS to something more relaxed (if comfortable doing so). ---
**Author:** ![gdaudin](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/g/71e660/32.png) [@gdaudin](https://forum.vassalengine.org/u/gdaudin)\ **Post date:** [February 16, 2022, 6:48pm UTC](https://forum.vassalengine.org/t/vassal-3-6-5-crashes-on-startup-for-macos-12-2-1/73929/5 "2022-02-16T18:48:45Z")
Maybe. But then I had been through a Gatekeeper dialogu before and did my usual steps to deal with it. I am used at dealing with Gatekeeper, and I had never seen it stop an application startup without a dialogue coming up. Still, probably an issue with the chair-keyboard interface as they say. Thanks again for your work. Guillaume