This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can't install or uninstall

I had been running Sophos AV for Mac (free) for about a year when it suddenly quit working.  When I tried to uninstall it, I got an error message.  I dragged the Sophos and the Sophos Uninstall to the trash and emptied the trash.  Thinking that I would download and reinstall, now when trying to reinstall, I get the error message that the program is already installed and can't be reinstalled until it is uninstalled (Catch 22?).  Where is it hiding?  

Thanks in advance for your help.

:1012380


This thread was automatically locked due to age.
Parents
  • Bob...

    VICTORY.

    I began to look at things a bit differently, trying to approach the problem more in terms of processes than sophos- or savos-specific investigative work.

    Although I realize there is obviously a problem within the booting process, & lauchd thinks SophosUIServer still exists, I had to accept, finally, that it was simply an anomaly (rare if not impossible in the work of coding, no?), or buried within something so well-masked I couldn't recognize it.

    I began working more with Console & Activity Monitor.

    I could see processes such as Page Reporter, but eliminating them proved futile.

    I managed to deviate my Preferences in Security & Privacy, so that the Pop-up Problem Page was no longer seeking to Report Problem to Apple...so I knew I was onto something.

    I returned to CrashReporter, which you remember had the only Sophos .plist which I couldn't erase.

    Still, it has continued to seem to me that CrashReporter was the culprit, or if not the culprit then the source of a possible resoultion.

    I had researched & read of adjusting my CrashReporter Preference to Server, which would cancel out the Pop-up box, but CrashReporter would continue, indefinitely evidently, writing the perpetual crashes.

    It seemed a bit of a cheat solution, but at least the Pop-up would vanish & the computer would cease locking-up.

    & Then I found it.

    It was a Terminal command, which I was glad of, as this is my first experience with code & I wanted to succeed using it.

    The command is: defaults write com.apple.CrashReporter DialogType none

    Shut it completely down.

    No more friggin' box.

    & So, another maddening chapter comes to a close.

    Thanks for your help, your advice.

    Hang in there!

    Take care...

                              ~Mark33

    :1012598
Reply
  • Bob...

    VICTORY.

    I began to look at things a bit differently, trying to approach the problem more in terms of processes than sophos- or savos-specific investigative work.

    Although I realize there is obviously a problem within the booting process, & lauchd thinks SophosUIServer still exists, I had to accept, finally, that it was simply an anomaly (rare if not impossible in the work of coding, no?), or buried within something so well-masked I couldn't recognize it.

    I began working more with Console & Activity Monitor.

    I could see processes such as Page Reporter, but eliminating them proved futile.

    I managed to deviate my Preferences in Security & Privacy, so that the Pop-up Problem Page was no longer seeking to Report Problem to Apple...so I knew I was onto something.

    I returned to CrashReporter, which you remember had the only Sophos .plist which I couldn't erase.

    Still, it has continued to seem to me that CrashReporter was the culprit, or if not the culprit then the source of a possible resoultion.

    I had researched & read of adjusting my CrashReporter Preference to Server, which would cancel out the Pop-up box, but CrashReporter would continue, indefinitely evidently, writing the perpetual crashes.

    It seemed a bit of a cheat solution, but at least the Pop-up would vanish & the computer would cease locking-up.

    & Then I found it.

    It was a Terminal command, which I was glad of, as this is my first experience with code & I wanted to succeed using it.

    The command is: defaults write com.apple.CrashReporter DialogType none

    Shut it completely down.

    No more friggin' box.

    & So, another maddening chapter comes to a close.

    Thanks for your help, your advice.

    Hang in there!

    Take care...

                              ~Mark33

    :1012598
Children
No Data