Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I also had trouble until I moved the packages out of the Download folder. As suggested by a couple of people above the security setup prevents installation of at least some packages from the Download folder. It makes sense to perhaps not install from the Download folder. Not sure you want the Installer.app to work in all parts of your drive. But I am not an IT person.
 
Just a quick followup. The installer program is also listed in the path under system settings... /Privacy & Settings/Files and Folders/Installer. Clicking on this reveals two toggle keys to activate the Desktop Folder and another one to activate the Downloads Folder. So again you do not have to allow installer full access to your drive.
 
I had the zoom pkg file downloaded, and moved to Application folder before double-clicking for installation. This time, it worked. I want to share with Mac users here and hope it helps.
This works. Thanks! But Apple needs to fix this. We shouldn't have to have a workaround to install software.
 
Hi All, returning to this issue as I have just started sharing the same problem. Anyone found a permanent solution? I chatted with an Apple support person today and they suggested that a VPN or third party software could be causing the problem? I don’t believe that tbh….Meanwhile I’ve just been doing the Full Disk Access thing, but even that didn’t work for one particular pkg installation earlier today….I suspect a return to Monterey may be on the horizon…..
 
Erm..no. It’s an Apple issue because it affects EACH AND EVERY dmg/pkg app installation.
Coincidentally, I’ve just installed GDATA-Antivirus.pkg in Ventura 13.5. During installation, the installer asked for permission to access the folder from where it was installed <“Installer” would like to access files in your Downloads folder.> and the installation was successful.
GDATA-Antivirus.pkg-.jpg
So, good installers behave properly. ;-)
 
Very interesting! My current workaround is to move the Installer to my Applications folder. It seems to work from there....
 
It’s an Apple issue because it affects EACH AND EVERY dmg/pkg app installation.

More likely a local configuration issue. Millions of packages are installed each (day?) and haven't seen any other reports of this problem.
 
More likely a local configuration issue. Millions of packages are installed each (day?) and haven't seen any other reports of this problem.
Apart from these, that is:

 
Hey all, This issue Just showed up on Monterey 12.7.1. Prior to this I didn't have any issues. What's odd is, the packages I'm working with Are Apple's InstallAssistant packages.
They fail from the Downloads folder, and the desktop folder, or a folder I have on the desktop called misc. They did work if I moved them to /Applications. The installer is not listed in Full disc access for me, or in Files and Folders.
 
It's a glitch where the TCC attributes don't get set, but it then doesn't ask if you'd like to grant access to the Downloads folder so you get stuck with the situation that you can't grant Installer access to the Downloads folder and it therefore fails. Have a look at Eclectic Light blog
 
Hey all, This issue Just showed up on Monterey 12.7.1. Prior to this I didn't have any issues. What's odd is, the packages I'm working with Are Apple's InstallAssistant packages.
They fail from the Downloads folder, and the desktop folder, or a folder I have on the desktop called misc. They did work if I moved them to /Applications. The installer is not listed in Full disc access for me, or in Files and Folders.
Are you just trying to get macOS installers? If so, use softwareupdate in Terminal with the fetch-full-installer flag as shown here: How to Download Full MacOS Installers from Command Line (osxdaily.com)
 
That is true. This app will work though: GitHub - ninxsoft/Mist: A Mac utility that automatically downloads macOS Firmwares / Installers. It requires macOS Monterey 12.0 or later.
@chrfr OK, well downloading Mist gave me an answer, I selected pkg from assists and ran it from the downloads. It worked fine, so for the time being it seems like it's only the Apple installers failing to run from that location. So it may not be a TCC issue, or at least not on my end.

I'm also in the process of creating a Monterey VM of a clean install of 12.7.1, and going to do some testing in that, I need to make sure my system didn't suffer damage from when my UPS failed and shut it off suddenly a few times.

If I have the same issue on a stock install, I'll be more at ease nothing got corrupted, even though Disk Utility said all is well, and if it is my install, well, I'll clean install to have a fresh start. I have stuff i don't use and i have a time machine backup, so starting clean will take a bit of time, but won't be an extra hassle in these circumstances. So will do the VM first as a test subject to know for sure.

Thanks again.
 
Last edited:
OK, I'm coming back here with an update. I installed Monterey 12.7.1 as a clean install in a VMWare Fusion Machine. and got the same installer failure message even after installer was granted permissions. So, this seems like an Apple thing, and nothing wrong with my main install of macOS. I like the Mist Application, it works well, so will more than likely just use that for installers now. Looks like it can also be used to create .iso files for a VM when the built in create media function doesn't work with Fusion.

Thanks guys for the feedback, and help. I feel much better now knowing my install is fine, and I won't have to start from scratch. I'm going to try the Sonoma InstallAsistant.pkg in the VM to see if it fails as well, for the public release of 14.1. That also failed in the VM. Here is what happens specifically when those particular Pkgs fail from Downloads, or Desktop., or any folder on the Desktop. The .app file gets created in /Applications as it should, but it's only about 42 MB vs the 11, or 12 GB of the pkg file. So I wonder if it's more than a permission problem since they partially install, but the resulting file is the wrong size. Again, thanks, I will use other methods to deal with Apple installers now and glad my system isn't broken.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.