Insecure startup items folder detected mac

Sep 12, 9: Insecure Startup Items folder detected. More Less. Communities Contact Support.

Sign in. Browse Search. Ask a question. User profile for user: A7xmaster A7xmaster.

Logging in gives an "Insecure Startup Items folder" error - CNET

I'm getting an error message after log in in. I deleted the folder, and restarted, and also made sure I didn't have any applications starting up at login, but nothing seems to work.

  • pos system for mac uk!
  • All replies!
  • Network error 1316 occurred while attempting to read the file!

Any ideas? Running Snow Leopard, Fresh Install.

Share your voice

All replies Drop Down menu. Loading page content. Reply Helpful Thread reply - more options Link to this Post. The message is still there each time I login It is just there on the 17" I ran disk repair and it did not help. I do not know if it is supposed to assure me that more people are having the same problem. I would have expected after a year delay we would get something that works Very frustrating.. I am really regretting having migrated..

I own 6 Mac's and in the past have been very happy but I am not that happy now.. Too many problems this is only one of many.

Vinmar Vinmar. A clean install should also take care of it. The most common is the "login items" list for each account in the "Accounts" system preferences; however, there are others including the "Startup Items" folder in the global library, which is primarily used by applications that need to start a helper process at startup. The StartupItems folder and items in it need to have special permissions in order for the system to properly access and launch the items. If the permissions are not set properly, the system will output this error people have been getting, and not allow items in the StartupItems folder to run.

Logging in gives an "Insecure Startup Items folder" error

In order to fix the permissions, you will need to set the owner and group of the folder and its contents to "root" and "wheel", respectively. Additionally, executable files programs should have the permissions set to readable and executable by everyone, but only writable by root and have non-executable files be set to readable by everyone, and only writable by root. While Disk Utility's "Permissions Fix" routine may detect incorrect permissions on the folder, it may not properly change the ownership and permissions of items in the folder.

For the most part, applications in the folder should be executable by the appropriate groups so changing the permissions on them will not matter too much, but if you decide to change permissions on all items, you can set the permissions of everything in the folder to "", which will flag non-executable files as executable, but that will not harm anything.

Non-Executable files that have been flagged as executable should behave the same as when they are not flagged as executable. If you try to explicitly run as programs using the Terminal you will just receive an error.

With this in mind, to change the permissions of the Startup Folder and files within it, run the following commands in the Terminal:. After these commands have been run, you can double-check the permissions with Disk Utility's "Permissions Fix" feature, and then restart your system to see if the error persists. Post them below or email us! How to watch the Galaxy S10 launch: