Warning: SUID file "System/Library/CoreServices" has been modified and will not be repaired.

Hello Cadent,I had big problems with this because when that permisssion is not repaired Apples professional[??] recording sofware "Logic Pro" loses its audio output.

Re installing the OS[10.8 in my case] does fix that but some posters were suggesting that zipping that app might keep it from being modified from outside, I certainly don't need or use it, but am not smart enough to know if that would work.

Yesterday I downloaded an update for 10.8.5 that had a new version of that app, but again apple are not very interested in what they are doing since the unfortunate passing of Steve Jobs, they certainly don't look at these forums and and most people report that only calling them will get any results, the result I got was that I should re install the OS it does work but I too find the support under the present management sub par,to say the least.

You sound like someone who knows a lot more than me so if you think zipping the app would help please post back.

I fear zipping it might change its permissions and mean another 3 hour re install.

The best place to ask about this would be in the Logic Pro forum.

Hi Varjack, this unrepaired permission does cause serious problems if one is using apples so called "Proffessional" app Logic Pro- all audio output is gone[ safari and iTunes still have audio output] but Logic loses it when this appears in the list of repaired permissions, or should I not say NOT repaired.

I called apple care and was told to reinstall the OS[10.8 in my case] that did put a new copy in place but I don't think I will try repairing permissins again until I have moved some important work to a more dependable system.

I did get an update yesterday that included a new version of the ARD app; it said th it would solve some issues with the firewall, we shall see.

As mentioned previously by a few people, Disk Utility hasn't been updated recently to reflect certain changes in the OS, and as such they pop up at permission exceptions. They don't cause a problem on their own however.

i have also got this message will it cause any damage.....????

yadavshai wrote:

i have also got this message will it cause any damage.....????

Very unlikely. When you do a Permissions Repair you will get a long string of 'errors': as long as at the bottom of the list it says 'Permissions Repair completed' you can ignore them.

I just noticed this warning on doing a permission repair and searched and came here.

I noticed that ARDAgent.app was Created September 13, 2013 at 1:16 am

This was modified Tuesday December 3, 2013

Last opened at the same date and time

The Version is 3.7.1

Immediately prior to September 13, the Version was 3.7

At various dates backwadrs the Version was 3.6.x etc

There were modification a few trimes between Version change

I do not use Screen Sharing or Remote Management

Hope this helps

I also have this problem with permissions. I am running Mavericks. I decided to try the Repair Permissions facility in Drive Genius 3 because I read above that this problem is directly related to the NON updating of Disk Utility by Apple. Surprise, surprise, I get exactly the same result from Drive Genius !

So, is it a problem or not?

Maybe Drive Genius is simply using already built-in facilities and therefore selling the 'King's New Cloths'. If that's NOT the case, then this would appear to be a more serious problem. If it IS the case, then maybe further investigation of just what we are paying for might be in order ! It leaves a nasty taste with me if I feel that I am being ripped off, or misled.

Hope this adds something worthwhile.

Roger Wilmut1 wrote:

... as long as at the bottom of the list it says 'Permissions Repair completed' you can ignore them.

Thanks for helping clarify this. As you said, the Apple KB article says it's normal.

However -- in the interest of accuracy, is it "Permissions Repair completed", or "Permissions verification complete", and does this vary based on whether you're doing a Permissions Verify or Repair?

'Permissions Verification' consists of checking the disk to list any Permissions errors but does not take any action. 'Permissions Repair' consists of also repairing any errors that can be repaired. You get the 'complete' message relevant to the process you instigated. As said, there are a lot of errors which aren't actually errors and don't get 'repaired'.

I would take it serious.

the same here, exactly as reported before but w. Mavericks 10.9.1 !

"My MBP just started getting this error and it also has started slowing way down. Don't ignore the error. It's clear there is a relation."

For those who wrote

I spoke with Apple Care Netherlands[where I live] and they said use the much beter version of disk Utility in the recovery mode and it did repair permissions without damaging Logic pro and I was able to repair my home folders permissions [ACL's ] there by opening terminal there and typing res and then pressing tab that brught up the reset password box but I didn't want to reset the password and under the reset password box is another for repairing one users home folder,since I am the only user my user name appeared in the correct place and I could repair my home folders permissions-this was advice from Logic Pro entrprise support and it did fix several issues Mr. Wilmut.

Hi everyone

I do love a good debate. The users saying that this message isn't a problem seem to be correct, Apple themselves have confirmed that this is nothing to worry about.

I am posting to support the fact that this is not limited to Snow Leopard where I first came across the problem a few years ago, I am now using Mavericks. After upgrading I ran disk utility to repair my permission which it did, I always re-run it a second time as a 'peace of mind' it's usually unnecessary but that is just what I do. On the second run after installing Mavericks the message appeared.

This is a random error, sometimes it will appear and others it won't, I have fixed it in the past on Snow Leopard but I can't for the life of me remember which method I used.

For those worried, I would suggest doing a safe boot and running disk utility during the safe boot, but you will find that even after what feels like the problem has been fixed at some point it will randomly re-appear.

Good debate, but... I'm a bit paranoid. So the idea to have some unknown stuff that do something isn't really pleasing me, especially in the post Snowden era... This (old) article is giving an interesting hindsight:

http://www.macworld.com/article/1134165/ardagent.html

I didn't have though to Zip and just deleted the folder. No more permission issues. But as I said, I'm a bit paranoid...

I don't want a debate - just a concrete, autoritative official statement from Apple - why is that so difficult? If Apple's disc utility produces false information why would anybody rely on it? Remove it from the OS or fix it. It's perplexing that Apple remains silent on the matter and all I get is well intentioned techs that parrot somebody else. That is not tech support.

However, using 2 Macs I believe I found the culprit that creates this issue:

Using an OS 10.6 disc I did fresh installs. On one Mac I permitted all post install "updates" to be installed and sequestered the other Mac from any updates. Running the disc utility on the non-updated Mac produced a clean report, but the updated Mac produced 32 permanent incorrect java permissions, 5 "RemoteMangement" and one SUID warning. Inspite of "correcting" the disc utility permissons a re-verify indicated the same incorrect permissions - over and over again.

On the non-updated machine I prepared to install one update at a time and running the disc utility after each update. I didn't get far - the "Remote Management" install and "java" related updates immediately produced the permissions issues. Re-installing OS 10.6 w/o the updates seems to have solved my issues with the disc utility. So, I did a second re-install and updated only java and found a clean bill of health for my OS 10.6.8. So, without the "remote management" update I have no issues to report. Perhaps we need a better understanding of just what remote management does and who can access it? It might explain why my wife's iMac wakes up in the middle of the night?