title: miniconda installation issue on iMac with Apple M1 chip running macOS Big Sur
body: <p>I am trying to install Miniconda on my new iMac.  I have installed Miniconda on an older macOS system before with no problems, but I am having difficulty with this new computer/system.</p>
  <p>The computer is an iMac with the Apple M1 chip running macOS Big Sur (version 11.3).</p>
  <p>I downloaded the latest miniconda installer and ran the following code: <code>bash Miniconda3-latest-MacOSX-x86_64.sh</code></p>
  <p>This results in the following warning:</p>
  <p>WARNING:
  Your operating system appears not to be 64-bit, but you are trying to
  install a 64-bit version of Miniconda3.
  Are sure you want to continue the installation? [yes|no]</p>
  <p>I am not sure why it is saying that I don't have a 64-bit system - my understanding is that starting with macOS Catalina, everything should be 64-bit (but may be I am wrong?).</p>
  <p>I searched around on the internet, but didn't find a solution, so thought I would try installing it anyway just to see what happens.  It does not complete the install.  I followed the prompts, but at some point, you get this:</p>
  <p>[/Users/jenniferweinert/miniconda3] &gt;&gt;&gt;</p>
  <p>PREFIX=/Users/jenniferweinert/miniconda3</p>
  <p>Unpacking payload ...</p>
  <p>Miniconda3-latest-MacOSX-x86_64.sh: line 411: /Users/jenniferweinert/miniconda3/conda.exe: Bad CPU type in executable</p>
  <p>Miniconda3-latest-MacOSX-x86_64.sh: line 413: /Users/jenniferweinert/miniconda3/conda.exe: Bad CPU type in executable</p>
  <p>Most of what I have found about issues with miniconda (or anaconda) and macOS (Catalina or Big Sur) relates to the differences between bash and zsh and the two extra lines of code that you need to activate miniconda/anaconda.  But I can't even get to that point because I cannot get Miniconda installed!</p>
  <p>I was able to install home-brew and then tried the silent installation.  But that ended up at the same point, unable to install due to the bad cpu type in executable.</p>
  <p>Someone mentioned to me that this might be due to the M1 chip in this computer, but did not have a work-around or solution to suggest.</p>
  <p>If anyone can offer any help with this, I would really appreciate it!  Also, if there is any additional information that I should provide in order for you to help, just let me know.</p>
  <p>Thank you!</p>