At least that's a more respectful of the end-user, but I agree that doesn't mean Avast has won our trust back yet. Regarding your reply, I did proceed with installing Avast on a different computer and did notice that the current version no longer installs the "SafePrice feature" by default (one of the problems you mention in your article), but instead offers it as a separate browser extension. So I will abandon the installation problem for now. But since no-one has answered, I'm guessing the issue is very specific to my friend's situation, and not easily answerable. Really I was just hoping for some suggestions on how to get around an ornery installer which happens to be anti-virus software. I didn't want this thread to focus on anti-virus. The Mac world is a better place because of your efforts. Also, let me say that you have my high respect for your contributions of your two very helpful websites. I too have been anti-anti-virus for many years and have talked dozens of people out of running it over the years on the simple premise that they tend to cause more problems than the prevent/solve. Have submitted a ticket to Avast, but only a canned response so far. Just looking for suggestions on the installation problem itself. I realize there are other virus protection solutions and I realize there's some debate on whether or not anti-virus software SHOULD be installed on a Mac.
I suppose I could give up on Avast and go to ClamAV, but he’s “sold” on Avast. I don’t have enough experience with Avast to know whether or not this is an “Avast problem”, but I certainly have more experience with installing under Mavericks to say Avast is most likely the culprit here. So, here are the things the DIDN'T solve the problemħ) ran Disk Repair, which led me to booting into Recovery Mode to fix a couple directory structure mismatches.Īny ideas what else it could be tripping up this install? "CoreServicesUIAgent: Error: qtn_file_apply_to_path error: Read-only file system" One specific log line item says (which might be the key if someone can interpret, my Google searches haven't been able to untangle): or perhaps it wasn’t happy that Chrome was not installed. Perhaps it was tripping over a permission problem. Looking at the console log, lead me to believe a couple things: The problem, the installer fails at the final stage with a completely generic message that's no help. I had installed Avast on another machine of his and it did some good, so he wanted it on his MBAir. Trying to install the latest Avast on a MBA running 10.9.5.
0 kommentar(er)
