Apple Rosetta Install
Channing Rupnick
Remember, this is only for Apple Silicon ARM Macs, and this is not necessary on any Intel Mac (nor would Rosetta 2 install on Intel Macs anyway). Also, this capability is only available in macOS Big Sur or later.
For some quick background, new Apple Silicon Macs run on different architecture, whereas Macs have been running Intel chips for quite some time. Rosetta 2 translates Intel x86 code to ARM so that it can run on the new Apple Silicon hardware. You can read more about the Rosetta 2 translation environment at the Apple developer site gif interested.
i have installed rosetta 2.
when i click on install this is the message i get. how do i get it to invoke rosetta 2? no rosetta message appears under get info. i am lost on how to run older apps on the m1 under big sur.
Rosetta 2 will work automatically to launch Intel apps on Apple Silicon once it is installed and recognizes an Intel binary. You might try rebooting after installing it, if you have not done so already.
I just dowloaded R and Studio on my laptop. Whenever I open the app a popup comes up telling me I should download Rosetta for it to work properly but there's no instalment procedure available, there's only a link to an apple website that tells me how to download it on my Mac but the instructions are unclear. They talk about a terminal that I don't know how to open on my laptop so I haven't been able to install Rosetta. How can I do that?
Only Intel Binary Code. This software will invoke Rosetta 2 to translate the Intel binaries so the operating system can understand and execute the Application. The Applications must be 64 Bit to function on Big Sur, Monterey and Ventura / Sonoma
Universal Binary Software. It contains Both Intel and M1/ M2 / M3 ARMs binary code and refer to ( Universal 2 ) When the user installs a 64 bit Application that contains Both Intel and M1 / M2/ M3 ARMs binaries - depending on factors, the Operating System may or may not invoke Rosetta 2.
error. It says installed successfully, but if I rerun the script it tries again with the same result. If i try to run a policy that installs an Intel package it still errors out saying I need Rosetta.
I thought it might be because at one point I removed Rosetta on this one so I could use it as a test laptop. So I completely reinstalled Big Sur on it and tried again, but I still get the error. Any solutions?
Yes, this is one of the scripts that I tried. I still get the error that it's missing InstallKBytes attribute.
I've seen a couple of other people post that they've gotten this error. Someone said that manually double clicking /System/Library/CoreServices/Rosetta 2 Updater fixes it, but for me that comes back saying an error has occurred, please try again later.
I made a smart group called Macs with ARM Chip so that only those get the package installed.
I just did the command in terminal on a Macbook Pro with a M1 Pro chip. I get the exact same error when entering
I'm on an M1 mini on Monterey. I have multiple Rosetta apps running. There is no "/Library/Apple/System/Library/LaunchDaemons/com.apple.oahd.plist", and there is no process with "oahd" running. There is a "/Library/Apple/usr/share/rosetta/" directory. Every Rosetta install script I have found so far looks for things that do not exist on my mini. At this point I'm not even convinced Apple will allow Rosetta to be command line installed anymore. It seems like unless someone is available to dismiss a GUI dialog box the install fails. Either way, none of the popular install scripts seem to work anymore.
I've been having issues as well with Rosetta over the last week, it's just not getting installed properly by any jamf terminal command or script. So I made a pkg of the installer instead and deploy it at as the only pkg at enrolment to ensure it gets installed. To build the Rosetta pkg do this:
Managed to get hold of the RosettaUpdateAuto.pkg.
Quick question...
We currently run a script to determine if a device is M1 or not - if yes, then "softwareupdate --install-rosetta --agree-to-license". It's set to 'Enrolment'
If I were to create a policy that's set to 'Ongoing' with the RosettaUpdateAuto.pkg as a payload - if I call its trigger from inside our Enrolment script, will it be able to run the policy even though it hasn't finished running the Enrolment policies?
Via 'sudo jamf policy -trigger rosetta' (for example).
To summarise:
In the enrollment script, I'm suggesting replace "softwareupdate --install-rosetta --agree-to-license", with "sudo jamf policy -trigger rosetta"
'rosetta' being the trigger for a policy that is 'Ongoing'
I excluded an m1 mac from the script on enrollment so that rosetta does not get installed that way anymore. Then I ran just the basic command shown below; same error. So it's not the script. I'm on jss version 10.36.1
I do think Rosetta is installing via the old softwareupdate command, if it wasn't then following policies would've failed to run also (even stuff as standard as deploying basic desktop wallpapers).
I will still test deploying our own PKG though. I've seen our DEP script halt a couple of times on M1 Pro Max devices recently. I suspected it was related to our AntiVirus (because I've already recorrected the /usr/bin/python line). Just conscious that something has changed and would rather nothing was missing from Rosetta :D
(b) I will also run a second package to deploy DEP Notify, along with the script and custom triggers.
This process has worked flawlessly on our M1 devices. I like the idea of creating a Rosetta package also, which @tommyandersson provided above. Both methods should be solid.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
One such example is numpy. To provide context, I installed Python 3.9 and pip3 and then decided to use pip to install numpy. To test if Python 3.9 and numpy have been properly installed, I type in terminal python3. I next try importing numpy using the statement import numpy
I have the exact same error when trying to open other applications (eg. SonicWall Mobile Connect) from the apple app store. If anyone has any insight to how to resolve this rosetta error it would be very much appreciated.
I had the same issue on Apple Silicon (M1Pro) running on Mac OS Monterey (12.0). I installed Rosetta2 and problem persisted. I deleted and reinstalled Docker but that did not fix the problem. After reading other answers on this question, I realized that for some people, OS upgrade was solving the problem.
Verify that Rosetta is installed on your Mac. Rosetta should be installed automatically when you try to run an Intel-based application on an Apple Silicon Mac. If it's not installed, you can manually install Rosetta using the following command:
The same problem has occurred for me as well, but with Big Sur 11.5 update as another comment has pointed out before me.
What I did to fix the error was to update from Big Sur 11.5 to Big Sur 11.6.
From there the issue resolved itself for me.
I am using M1 Mac Monterey 12.3.1, I had to switch over to using Docker Compose V2. After I did this and restarted the Docker for Mac engine client app, the CLI started working again (though the buttons in the app still gave errors).
As it turns out this was an Apple software issue. (I believe it was update 11.4, but I am not 100% sure.) After doing the software update the rosetta issue disappeared and all of the software that was having problems with it earlier now function properly.
Adobe claims to support Macs M1 natively for some products, but all available packages at have the dependency on Rosetta (Installer app is an intel binary). Even some alternative links from support points to packages with intel binaries. So, how to install Adobe app without Rosetta on Apple silicon Macs?
Would you please bookmark -install/kb/apple-silicon-m1-chip.html to be kept up to date regarding Adobe application support for Apple's new processors? I would also recommend reviewing -us/HT211861 to understand better what Rosetta 2 is used for and the difference between Universal and Intel-based apps.
The point is not about installing Rosetta or not. When you have a new maching which does not have Rosetta installed, and the first app you try to install is claimed to be M1 compatible and doesn't require Rosetta to run, but since the installer is not native, one who is not technically sounding, will think the app to be a wrong version as it is asking Rosetta to install. The incomplete information is the issue or confusion here.
The experience of communication is being destroyed here. It was this forum only where I or others got to know that the installer require Rosetta and not the actual app. Hence it was not evident that Adobe Lightroom in my case is native M1 compatible. I was trying to find the M1 compatible app. Hence as per experience, Adobe is to blame here for improper communication. Before coming to Google search for a solution, I contacted Adobe support who themselves were not able to address the same issue as they also did not communicated what @Test Screen Name clearly mentioned. So,
ll of you responding on here hatefully to people not wanting to install Rosetta 2 are asinine. You all have no idea what these people are asking #1 and #2 have no understanding of why they are requesting it. They are pointing out that the installers themselves have not been updated not to require Rosetta 2, and they should be if Adobe is claiming FULL native Apple silicon support. That would indicate that Rosetta 2 is not required at ALL, so they should not need to install Rosetta 2. Yet they are! Also, Rosetta 2 is only a bandaid provided by Apple for lazy developers. They will at some point drop support for it altogether. So if, as a developer, you are going to take the time to update your software to run natively on Apple silicon, then why wouldn't you at the same time update your installer package? Doing this makes no sense at all and is sloppy. I fully understand all these people NOT wanting to install Rosetta 2. Get off their backs and stop being jerks!
c80f0f1006