Copy link to clipboard
Copied
I'm trying to install Adobe DC in Parallels on my Macbook Pro M1. I keep getting an error message code 405 and a note saying that Adobe DC is not yet available for your device?
Does anyone know of a workaround...?
Thanks.
Copy link to clipboard
Copied
Even using a Windows emulator, you are still running on an M1 processor, not an Intel processor... so trying to install a Windows program on the processor may never work
Copy link to clipboard
Copied
Acrobat does not support Windows on ARM processors.
Copy link to clipboard
Copied
Same problem! Error 405 trying to install Adobe Standard Desktop on a MacBook Pro (Apple M1 chip). Interestingly "Adobe Acrobat Reader" does install without any problems. However Adobe Acrobat Standard does not (on a MacBook Pro with Apple M1 Pro Chip) inside a "Paralles" Windows 11 Pro shell. Has anybody found a solution ?
Copy link to clipboard
Copied
yes, install on your mac without the complication of os emulation.
Copy link to clipboard
Copied
This is not possible in this case beause we need to access a "Windows only" business application (the reason we have installed "Paralles" on the MacBook pro) and Adobe Acrobat on the same OS environement. To constantly switch OS is to cumbersome.
Copy link to clipboard
Copied
According to Adobe, your Apple silicon should now be able to handle programs that might've been designed with Intel-based features in mind and no need to install Rosetta.
However, that makes me curious: If this issue happening with Rosetta installed on your macOS or not?
And if it is installed, is this happening with Rosetta 1 or Rosetta 2?
Copy link to clipboard
Copied
I have been able (after several attempts) to install Acrobat DC in Windows 11 running in Parallels on a MacBook Pro with an M1 chip and it seems to run as expected. So I think it can be done. However, I have but have not been able to install the Adobe PDF printer that should come with the program, receivng a message to install ACROBATPDF.DLL.
Copy link to clipboard
Copied
Please share a screenshot of the entire message.
Meanwhile, is this happening after upgrading or downgrading Parallels to correspond with your current macOS version?
See here: