1 2 Previous Next 18 Replies Latest reply: Jun 10, 2014 6:56 AM by brunob89
netscraper Level 1 Level 1 (0 points)
Sorry - posted this inadvertently in the ML-Section.....OK, here we go again...

 

 

Hi community, I'm running a (almost) brandnew late 2013 MBPr 15", OSX10.9., 16 GB RAM , 1TB SSD. Startup ist reasonably fast, but the shutdown ist awfully slow. If I press the Power button, the screen gets light grey, after a while a spinning wheel appears and after approx. 50 sec up to a minute the machine shuts down. I didnt't install any crapware such as MacHelper but scanning through the threads in this community I noticed that Parallels seems to cause many issues concerning a slow shutdown and I'm indeed running a Win 7 prof-VM under Parallels 9.

 

About the first appearance of the shutdown lag I'm unsure since the first few days I didn't shut down the MB but put it to sleep.

 

So far I've only disabled (and de-installed) Sophos AV-software, iCloud and Synology CloudStation - to no avail. Also I've looked in the Konsole logs which looked quite frightening whith lots of "faults" and such....but didn' give me any clues and repaired permissions. I'm unsure about deinstalling Parallels because I need it for work. Is there any other possibility to determine wether Parallels is causing these lags ?

 

Compared to my iMac (early 2008, 10.6.8), which is loaded with all kind of data and software (but not Parallels !), the latter shuts down in about 10 secs....my MacBook should make it much faster...

 

Any suggestions ?


MACBOOK PRO (RETINA, 15-INCH, LATE 2013), OS X Mavericks (10.9), 24'' iMac Intel DualCore early 2008
  • 1. Re: MacBook Pro Retina 2013 very slow shutdown
    Eric Root Level 6 Level 6 (16,200 points)

    Some people in this discussion have been able to speedup their shutdown.

     

    https://discussions.apple.com/thread/4139846?start=15&tstart=0

  • 2. Re: MacBook Pro Retina 2013 very slow shutdown
    netscraper Level 1 Level 1 (0 points)

    Hi Eric, I know the discussion you mentioned above. I don't like to meddle with Terminal commands I dont't really understand. If I'm right, they only treat the symptoms and do not pinpoint or eliminate the real problem.

     

    A few of the other users in the beforementionend discussion could pin the slowdown on some software or system related processes.

     

    So far third party software I installed are:

     

    MS Office for Mac 2008

    Sophos AV (the free version)--> uninstalled: no changes

    Synology CloudStation--> disabled: no changes

     

    none of these caused any glitches in my old iMac.

     

    Paralles 9 (running a VM under Windows 7 prof and another under Ubuntu, no Paralles on the old Mac)

     

    No things as MacKeeper or other intrusive software is on this machine (need it for work !!!).

     

    I'm using the MacBook in my company within a Windows network, at home in a wireless network provided by an AVM FritzBox. Unfortunately I did not shut it down during the first few days, so I'm unsure as to when the slowdowns really started.

     

    I'm suspecting Parallels since lots of users in differents discussions mentioned problems with shutdown if Parallels is installed. Or perhaps the different network environments ??? No idea there...

     

    As a first step I would like to determine what process or software is slowing the shutdown.

    I have looked in the Konsole logs but I'm totally unsure where to find any hints. These logs are mile-long gobbledegooks which are nearly impossible to post over here. I also found something called Etrecheck was used sometimes but couldn't try it yet.

     

    Where can I find the critical entries in the Konsole logs ? I would like to post them here instead of the whole sheebang...

     

    Should I run an Etrecheck log and post it here ?

  • 3. Re: MacBook Pro Retina 2013 very slow shutdown
    Eric Root Level 6 Level 6 (16,200 points)

    It wouldn't hurt to run Etrecheck. Copy and paste the results. Screen shots can be hard to read.

  • 4. Re: MacBook Pro Retina 2013 very slow shutdown
    Linc Davis Level 10 Level 10 (118,005 points)

    Is there any other possibility to determine wether Parallels is causing these lags ?

     

    Yes: uninstall it according to the developer's instructions. "Etrecheck" will not tell you whether any particular software is causing the slow shutdowns.

  • 5. Re: MacBook Pro Retina 2013 very slow shutdown
    netscraper Level 1 Level 1 (0 points)

    Sorry. The question should have been: ...to determine wether Parallels is causing theses lags short of uninstalling it.

     

    First of all I would like to have a look in konsole logs. In former version osx featured a shutdown log which mavericks doesn't have anymore. Right ?

     

    Where do I have to look now ? System logs ? And what to look for  ?

    And what is Etrecheck good for ?

     

    Since I don't have the MB during the weekend I'll be back on monday....

  • 6. Re: MacBook Pro Retina 2013 very slow shutdown
    Linc Davis Level 10 Level 10 (118,005 points)

    If you have more than one user account, these instructions must be carried out as an administrator.

    Launch the Console application in any of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.

    Step 1

    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select

    View Show Log List

    from the menu bar.

     

    Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time after  you had the problem. Select the messages logged before the boot, while the system was unresponsive or was failing to shut down. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V). Please include the BOOT_TIME message at the end of the log extract.

    If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.

    When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.

    Please do not indiscriminately dump thousands of lines from the log into this discussion.

    Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

    Step 2

    Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post any other kind of report — it will be very long and not helpful.

  • 7. Re: MacBook Pro Retina 2013 very slow shutdown
    netscraper Level 1 Level 1 (0 points)

    Thanks for that...

     

    As I mentioned above: I'llbe back on monday or tuesday due to the MB having it's bottom replaced (had a little dent...).

     

    I tried it alredy on my iMac and will be ready next week.

  • 8. Re: MacBook Pro Retina 2013 very slow shutdown
    netscraper Level 1 Level 1 (0 points)

    OK, here we go: the last system.log, hope it's enough and not to much.....

     

     

    Dec 16 14:49:12 My-MacBook-Pro kernel[0]: com_parallels_kext_prl_vnic_bus::detach_handler for 1

    Dec 16 14:49:12 My-MacBook-Pro kernel[0]: com_parallels_kext_prl_vnic_bus: detached 1

    Dec 16 14:49:12 My-MacBook-Pro kernel[0]: com_parallels_kext_prl_vnic: destroyed vnic1

    Dec 16 14:49:12 My-MacBook-Pro.local mDNSResponder[40]: getExtendedFlags: SIOCGIFEFLAGS failed, errno = 6 (Device not configured)

    Dec 16 14:49:12 --- last message repeated 1 time ---

    Dec 16 14:49:12 My-MacBook-Pro.local Parallels[4494]: Unloading kernel extension prl_usb_connect.kext

    Dec 16 14:49:12 My-MacBook-Pro.local Parallels[4499]:  - kext com.parallels.kext.usbconnect found loaded.

    Dec 16 14:49:13 My-MacBook-Pro.local Parallels[4506]: Unloading kernel extension prl_hid_hook.kext

    Dec 16 14:49:13 My-MacBook-Pro.local Parallels[4511]:  - kext com.parallels.kext.hidhook found loaded.

    Dec 16 14:49:13 My-MacBook-Pro kernel[0]: /prl_hid/ Parallels HID Helper stopped.

    Dec 16 14:49:13 My-MacBook-Pro.local Parallels[4518]: Unloading kernel extension prl_hypervisor.kext

    Dec 16 14:49:13 My-MacBook-Pro.local Parallels[4523]:  - kext com.parallels.kext.hypervisor found loaded.

    Dec 16 14:49:13 My-MacBook-Pro.local Parallels[4530]: Unloading kernel extension prlufs.kext

    Dec 16 14:49:13 My-MacBook-Pro.local Parallels[4535]:  - kext com.parallels.filesystems.prlufs found loaded.

    Dec 16 14:49:13 My-MacBook-Pro kernel[0]: PRLUFS: stopping (version 2010.12.28, May 5 2011, 01:26:58)

    Dec 16 14:49:13 My-MacBook-Pro.local Parallels[4547]: Reset owners for /Applications/Parallels Desktop.app/Contents/Library/Extensions/10.6

    Dec 16 14:49:14 My-MacBook-Pro.local launcher[4578]: Stop finished. Agents: 0; Service: 0; LaunchdSetup: 0

    Dec 16 14:49:16 My-MacBook-Pro.local ntpd[60]: ntpd: time set +0.279766 s

    Dec 16 14:49:16 My-MacBook-Pro.local SophosAntiVirus[109]: reloading scheduled scans...

    Dec 16 14:49:16 My-MacBook-Pro.local com.apple.time[181]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).

    Dec 16 14:49:34 --- last message repeated 1 time ---

    Dec 16 14:49:34 My-MacBook-Pro.local Finder[191]: CreateWithFileInfo failed to create URL with FSRef, falling back to blank icon.

    Dec 16 14:50:04 --- last message repeated 1 time ---

    Dec 16 14:54:52 My-MacBook-Pro.local Finder[191]: CGSCopyDisplayUUID: Invalid display 0x1b55ff5e

    Dec 16 14:54:55 My-MacBook-Pro.local Finder[191]: CGSCopyDisplayUUID: Invalid display 0x1b55ff5e

    Dec 16 14:54:56 My-MacBook-Pro com.apple.launchd.peruser.501[177] (com.apple.PackageKit.InstallStatus): Throttling respawn: Will start in 9 seconds

    Dec 16 14:54:56 My-MacBook-Pro.local WindowServer[130]: CGXGetConnectionProperty: Invalid connection 52491

    Dec 16 14:54:56 --- last message repeated 8 times ---

    Dec 16 14:54:56 My-MacBook-Pro com.apple.launchd.peruser.501[177] (com.apple.EscrowSecurityAlert[2060]): Exited: Killed: 9

    Dec 16 14:54:56 My-MacBook-Pro com.apple.launchd[1] (com.apple.MailServiceAgent[353]): Exited: Killed: 9

    Dec 16 14:54:56 My-MacBook-Pro com.apple.launchd[1] (com.apple.ShareKitHelper[247]): Exited: Killed: 9

    Dec 16 14:54:56 My-MacBook-Pro com.apple.launchd[1] (com.apple.internetaccounts[253]): Exited: Killed: 9

    Dec 16 14:54:56 My-MacBook-Pro com.apple.launchd.peruser.501[177] (com.brother.utility.USBserver.38752[258]): Exited: Terminated: 15

    Dec 16 14:54:56 My-MacBook-Pro com.apple.launchd.peruser.501[177] (com.brother.utility.NETserver.38928[263]): Exited: Terminated: 15

    Dec 16 14:54:56 My-MacBook-Pro com.apple.launchd.peruser.501[177] ([0x0-0x21021].com.apple.AppleSpell[326]): Exited: Killed: 9

    Dec 16 14:54:56 My-MacBook-Pro com.apple.launchd.peruser.501[177] (com.apple.gamed[237]): Exited: Killed: 9

    Dec 16 14:54:58 My-MacBook-Pro.local xpcd[197]: Info.plist does not contain an XPCService dictionary: /System/Library/Frameworks/Security.framework/XPCServices/SecurityAgent.xpc

    Dec 16 14:54:58 --- last message repeated 1 time ---

    Dec 16 14:54:58 My-MacBook-Pro xpcproxy[4628]: assertion failed: 13A3017: xpcproxy + 3438 [3AB894B7-5C91-3252-A567-8EE4A311091E]: 0x2

    Dec 16 14:54:58 My-MacBook-Pro.local xpcd[197]: Info.plist does not contain an XPCService dictionary: /System/Library/Frameworks/Security.framework/XPCServices/SecurityAgent.xpc

    Dec 16 14:54:58 My-MacBook-Pro xpcproxy[4629]: assertion failed: 13A3017: xpcproxy + 3438 [3AB894B7-5C91-3252-A567-8EE4A311091E]: 0x2

    Dec 16 14:54:58 My-MacBook-Pro.local xpcd[197]: Info.plist does not contain an XPCService dictionary: /System/Library/Frameworks/Security.framework/XPCServices/SecurityAgent.xpc

    Dec 16 14:55:00 My-MacBook-Pro.local com.apple.SecurityServer[15]: Killing auth hosts

    Dec 16 14:55:00 My-MacBook-Pro.local com.apple.SecurityServer[15]: Session 100022 destroyed

    Dec 16 14:55:00 My-MacBook-Pro.local xpcd[197]: Info.plist does not contain an XPCService dictionary: /System/Library/Frameworks/Security.framework/XPCServices/SecurityAgent.xpc

    Dec 16 14:55:00 My-MacBook-Pro.local com.apple.SecurityServer[15]: Session 100030 created

    Dec 16 14:55:00 My-MacBook-Pro.local com.apple.NotesMigratorService[280]: Joined Aqua audit session

    Dec 16 14:55:00 My-MacBook-Pro.local com.apple.internetaccounts[4629]: *** -[IADomainCache init]: IA domains cache couldn't be read.

    Dec 16 14:55:00 My-MacBook-Pro.local com.apple.internetaccounts[4629]: -[IAPluginManager allAListPlugins] [546] -- *** warning: we're on the slow path.

    Dec 16 14:55:00 My-MacBook-Pro.local com.apple.internetaccounts[4629]: An instance 0x7f8f3bc371a0 of class IMAPMailbox was deallocated while key value observers were still registered with it. Observation info was leaked, and may even become mistakenly attached to some other object. Set a breakpoint on NSKVODeallocateBreak to stop here in the debugger. Here's the current observation info:

                <NSKeyValueObservationInfo 0x7f8f3bc32b60> (

                <NSKeyValueObservance 0x7f8f397aa690: Observer: 0x7f8f3bc28e80, Key path: uidNext, Options: <New: NO, Old: NO, Prior: NO> Context: 0x7fff96f6f44b, Property: 0x7f8f39476f20>

                )

    Dec 16 14:55:00 My-MacBook-Pro.local com.apple.time[181]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).

    Dec 16 14:55:00 My-MacBook-Pro.local com.apple.internetaccounts[4629]: -[IAPluginManager allAListPlugins] [546] -- *** warning: we're on the slow path.

    Dec 16 14:55:00 --- last message repeated 3 times ---

    Dec 16 14:55:00 My-MacBook-Pro.local syncdefaultsd[4627]: *** -[IADomainCache init]: IA domains cache couldn't be read.

    Dec 16 14:55:00 My-MacBook-Pro.local syncdefaultsd[4627]: -[IAPluginManager allAListPlugins] [546] -- *** warning: we're on the slow path.

    Dec 16 14:55:06 My-MacBook-Pro.local loginwindow[83]: ERROR | -[ApplicationManager quitPrivateProcesses] | Private process did not quit

    Dec 16 14:55:07 My-MacBook-Pro.local sessionlogoutd[4633]: sessionlogoutd Launched

    Dec 16 14:55:07 My-MacBook-Pro.local sessionlogoutd[4633]: DEAD_PROCESS: 83 console

    Dec 16 14:55:07 My-MacBook-Pro.local shutdown[4634]: halt by _cvmsroot:

    Dec 16 14:55:07 My-MacBook-Pro kernel[0]: Kext loading now disabled.

    Dec 16 14:55:07 My-MacBook-Pro.local shutdown[4634]: SHUTDOWN_TIME: 1387202107 58948

    Dec 16 14:55:07 My-MacBook-Pro kernel[0]: Kext unloading now disabled.

    Dec 16 14:55:07 My-MacBook-Pro kernel[0]: Kext autounloading now disabled.

    Dec 16 14:55:07 My-MacBook-Pro kernel[0]: Kernel requests now disabled.

    Dec 16 14:55:07 My-MacBook-Pro.local Finder[4624]: XPC error messaging com.apple.IconServicesAgent: Connection interrupted

    Dec 16 14:55:07 My-MacBook-Pro.local Finder[4624]: XPC error messaging com.apple.IconServicesAgent: Connection invalid

    Dec 16 14:55:07 My-MacBook-Pro.local scanserver[1548]: Scan server shutting down...

     

    In System Diagnostic reports I found lots of logs which ended with "shutdown stall", the last one was titled:

     

    aosnotifyd,diskarbitrationd,HWNetCfg,HWPortCfg,HWPortCfg,sudo_2013-12-10-115014_ My-MacBook-Pro.shutdownStall

     

    much of the earlier logs were titled:

     

    cloud-eventd,CVMCompiler,CVMCompiler,CVMServer,diskarbitrationd,_2013-12-04-1633 46_My-MacBook-Pro.shutdownStall

     

    Since these logs are really long, I'd like to post them only if its necessary.

     

    But "shutdownStall" indicates for me they have something to do with my problem....

  • 9. Re: MacBook Pro Retina 2013 very slow shutdown
    netscraper Level 1 Level 1 (0 points)

    Sorry - forgot something: I am not sure if this is important, during the last shutdown/start-cycle, the MB was connected to the LAN in my company via cable.....

  • 10. Re: MacBook Pro Retina 2013 very slow shutdown
    Linc Davis Level 10 Level 10 (118,005 points)

    Remove the Sophos product by following the instructions on this page. If you have a different version, the procedure may be different.

    Back up all data before making any changes.

  • 11. Re: MacBook Pro Retina 2013 very slow shutdown
    netscraper Level 1 Level 1 (0 points)

    Hi Linc,

     

    removing Sophos brought shutdown times back to env 15 sec.

     

    Per chance I found another one: I tried a Huawei Stick which left some residue in "StartUpItems" despite trashing the app. This one scanned ports on every start up and mounted a the stick (which btw wasn't really there...). I removed these prior to Sophos and had gained already about 30 secs.

     

    Ok - in my opinion it's quite normal that if you use your machine as intensely as I do you always have some process running and 15 secs shutdown seem quite normal for me - despite other opinions in some discussions. Anyway: I can live with this.

     

    Since I wanted to be on the safe side (I need the machine for working and can't risk any virus or such) I put Sophos back on. At least I know what happened and I can be quite sure it's software related and not some corruption of the OS or hardware....

     

    Thank you very much for looking in this matter !!!

  • 12. Re: MacBook Pro Retina 2013 very slow shutdown
    Linc Davis Level 10 Level 10 (118,005 points)
    1. This is a comment on what you should and should not do to protect yourself from malicious software ("malware") that circulates on the Internet. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the victim's computer. That threat is in a different category, and there's no easy way to defend against it. If you have reason to suspect that you're the target of such an attack, you need expert help.
      
    If you find this comment too long or too technical, read only sections 5, 6, and 10.
      
    OS X now implements three layers of built-in protection specifically against malware, not counting runtime protections such as execute disable, sandboxing, system library randomization, and address space layout randomization that may also guard against other kinds of exploits.

    2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files, and to block insecure web plugins. This feature is transparent to the user, but internally Apple calls it "XProtect." The malware recognition database is automatically checked for updates once a day; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.
       
    The following caveats apply to XProtect:
    • It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets.
    • It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.
    As new versions of OS X are released, it's not clear whether Apple will indefinitely continue to maintain the XProtect database of older versions such as 10.6. The security of obsolete system versions may eventually be degraded. Security updates to the code of obsolete systems will stop being released at some point, and that may leave them open to other kinds of attack besides malware.
      
    3. Starting with OS X 10.7.5, there has been a second layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't necessarily been tested by Apple, but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. That may not mean much if the developer lives in a country with a weak legal system (see below.)
       
    Gatekeeper doesn't depend on a database of known malware. It has, however, the same limitations as XProtect, and in addition the following:
    • It can easily be disabled or overridden by the user.
    • A malware attacker could get control of a code-signing certificate under false pretenses, or could simply ignore the consequences of distributing codesigned malware.
    • An App Store developer could find a way to bypass Apple's oversight, or the oversight could fail due to human error.
    For the reasons given above, App Store products, and other applications recognized by Gatekeeper as signed, are safer than others, but they can't be considered absolutely safe. "Sandboxed" applications may prompt for access to private data, such as your contacts, or for access to the network. Think before granting that access. OS X security is based on user input. Never click through any request for authorization without thinking.
           
    4. Starting with OS X 10.8.3, a third layer of protection has been added: a "Malware Removal Tool" (MRT). MRT runs automatically in the background when you update the OS. It checks for, and removes, malware that may have evaded the other protections via a Java exploit (see below.) MRT also runs when you install or update the Apple-supplied Java runtime (but not the Oracle runtime.) Like XProtect, MRT is effective against known threats, but not against unknown ones. It notifies you if it finds malware, but otherwise there's no user interface to MRT.
     
    5. The built-in security features of OS X reduce the risk of malware attack, but they're not absolute protection. The first and best line of defense is always going to be your own intelligence. With the possible exception of Java exploits, all known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "Trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore amounts to a battle of wits between you and the malware attacker. If you're smarter than he thinks you are, you'll win.
        
    That means, in practice, that you always stay within a safe harbor of computing practices. How do you know what is safe?
    • Any website that prompts you to install a “codec,” “plug-in,” "player," "extractor," or “certificate” that comes from that same site, or an unknown one, is unsafe.
    • A web operator who tells you that you have a “virus,” or that anything else is wrong with your computer, or that you have won a prize in a contest you never entered, is trying to commit a crime with you as the victim. (Some reputable websites did legitimately warn visitors who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)
    • Pirated copies or "cracks" of commercial software, no matter where they come from, are unsafe.
    • Software of any kind downloaded from a BitTorrent or from a Usenet binary newsgroup is unsafe.
    • Software that purports to help you do something that's illegal or that infringes copyright, such as saving streamed audio or video for reuse without permission, is unsafe. All YouTube "downloaders" are outside the safe harbor, though not all are necessarily harmful.
    • Software with a corporate brand, such as Adobe Flash Player, must be downloaded directly from the developer’s website. If it comes from any other source, it's unsafe. For instance, if a web page warns you that Flash is out of date, do not follow an offered link to an update. Go to the Adobe website to download it, if you need it at all.
    • Even signed applications, no matter what the source, should not be trusted if they do something unexpected, such as asking for permission to access your contacts, your location, or the Internet for no obvious reason.
    • "FREE WI-FI !!!" networks in public places are unsafe unless you can verify that the network is not a trap (which you probably can't.) Even then, do not download any software or transmit any private information while connected to such a network, regardless of where it seems to come from or go to.
    6. Java on the Web (not to be confused with JavaScript, to which it's not related, despite the similarity of the names) is a weak point in the security of any system. Java is, among other things, a platform for running complex applications in a web page, on the client. That was always a bad idea, and Java's developers have proven themselves incapable of implementing it without also creating a portal for malware to enter. Past Java exploits are the closest thing there has ever been to a Windows-style virus affecting OS X. Merely loading a page with malicious Java content could be harmful.
      
    Fortunately, client-side Java on the Web is obsolete and mostly extinct. Only a few outmoded sites still use it. Try to hasten the process of extinction by avoiding those sites, if you have a choice. Forget about playing games or other non-essential uses of Java.
       
    Java is not included in OS X 10.7 and later. Discrete Java installers are distributed by Apple and by Oracle (the developer of Java.) Don't use either one unless you need it. Most people don't. If Java is installed, disable itnot JavaScript — in your browsers.
       
    Regardless of version, experience has shown that Java on the Web can't be trusted. If you must use a Java applet for a task on a specific site, enable Java only for that site in Safari. Never enable Java for a public website that carries third-party advertising. Use it only on well-known, login-protected, secure websites without ads. In Safari 6 or later, you'll see a lock icon in the address bar with the abbreviation "https" when visiting a secure site.

    Follow the above guidelines, and you’ll be as safe from malware as you can practically be. The rest of this comment concerns what you should not do to protect yourself from malware.

    7. Never install any commercial "anti-virus" or "Internet security" products for the Mac, as they all do more harm than good, if they do any good at all. Any database of known threats is always going to be out of date. Most of the danger is from unknown threats. If you need to be able to detect Windows malware in your files, use one of the free anti-virus products in the Mac App Store — nothing else.
      
    Why shouldn't you use commercial "anti-virus" products?
    • Their design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere.
    • In order to meet that nonexistent threat, the software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.
    • To recognize malware, the software depends on a database of known threats, which is always at least a day out of date. Most of the real-world danger of malware attack comes from highly targeted "zero-day" exploits that are not yet recognized.
    • By modifying the operating system, the software itself may create weaknesses that could be exploited by malware attackers.
    8. An anti-malware product from the App Store, such as "ClamXav," doesn't have these drawbacks. That doesn't mean it's entirely safe. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so will corrupt the Mail database. The messages should be deleted from within the Mail application.
        
    An anti-virus app is not needed, and should not be relied upon, for protection against OS X malware. It's useful only for detecting Windows malware. Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else.
        
    A Windows malware attachment in email is usually easy to recognize. The file name will often be targeted at people who aren't very bright; for example:
      
    ♥♥♥♥♥♥♥♥♥♥♥♥♥♥!!!!!!!H0TBABEZ4U!!!!!!!.AVI♥♥♥♥♥♥♥♥♥♥♥♥♥♥.exe
       
    Anti-virus software may be able to tell you which particular virus or trojan it is, but do you care? In practice, there's seldom a reason to use the software unless a network administrator requires you to do it.
      
    The ClamXav developer won't try to "upsell" you to a paid version of the product. Other developers may do that. Don't be upsold. For one thing, you should not pay to protect Windows users from the consequences of their choice of computing platform. For another, a paid upgrade from a free app will probably have the disadvantages mentioned in section 7.
      
    9. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use in the Sharing preference pane. All are disabled by default.
        
    10. As a Mac user you don't have to live in fear that your computer is going to be infected every time you install an application, read email, or visit a web page. But neither should you have the false idea that you will always be safe, no matter what you do. The greatest harm done by security software is precisely its selling point: it makes people feel safe. They may then feel safe enough to take risks from which the software doesn't protect them. Nothing can lessen the need for safe computing practices.
  • 13. Re: MacBook Pro Retina 2013 very slow shutdown
    netscraper Level 1 Level 1 (0 points)

    Wow ! That's the best summary about Macs and web-related threats I've ever read. Your are perfectly right in your statement that "protection" software often does more harm than really protect your mac as ist best seen in my case. Sophos is free of any charges and offers no in-app purchases, insofar there's no damage done. But it slows down a nearly perfect machine nearly to windows level. On my older iMac this is effect is not this remarkable as it is in general not as fast as the MB. But on the latter it decreases speed of certain processes - namely shutdown - about 10x !

     

    I will remove the Sophos AV - your statement about that is duly noted !

     

    For my own sake I'll go back to ClamXV (already used it before changing to Sophos).

     

    And I certainly will spread your summary esp. to my wife and my daughter who both are using (older) Macs as well.

  • 14. Re: MacBook Pro Retina 2013 very slow shutdown
    RodrigoZV Level 1 Level 1 (5 points)

    Hello!

     

    I've was having a same problem: the system is waiting a 13 seconds to finish. A gray screen with black mouse cursor stay for 10 seconds and after this, the other gray screen showed in 3 seconds!

     

    After a lot of research to try to understand what happens, I ended up discovering using a second identical to my MBP.

     

    Every time I create a new user, initializing it with any Apple account, the problem happens! I did several tests to assess this.

     

    1) - I created an admin user and do not have associated with the Apple ID: Shutdown time: 3.5 seconds.

     

    2) - I created an admin user and I associated with the Apple ID: Shutdown time: 14 seconds!

     

    3) - I created an admin user and do not have associated with the Apple ID. After logon, I entered the "System Preference" and I logged the Apple ID account in iCloud: Shutdown time: 3.5 seconds.

     

    I noticed that this happens only when done a fresh install using the Mavericks 10.9.1. I did not notice this problem using the Lion, for example.

     

    MBP1 : MID 2012, 15", i7, 16GB DDR3, 750GB SSHD (My)

    MBP2 : MID 2012, 15", i7, 8GB DDR3, 1TB SSHD (test)

     

    So if someone is experiencing a slowdown in shutdown, I suggest making a backup of your data and create a new user WITHOUT link the Apple account. Do an association with Apple account after logging in, going to the iCloud icon! A side effect of this is that your name no longer appears just below the iCloud icon. Your e-mail appears only!

     

    I finished session iCloud and unlinked all the AppleID, but not resolved.

     

    I turned off the wifi and disconnected the ethernet cable: not solved.

     

    I disabled the "Find My Mac", but it did not!

     

    I did the same tests on both machines at the same had this problem.

    I even thought it was a problem with my hard drive or memory, but thankfully it is not!

    I believe that this is happening because of a specific problem of some updating, because I realized that after I made a second fresh installation with OSX 10.9.1 is that this problem started appearing.

     

    The only way I found to solve this was to create a new user without linking with the AppleID!

    I think it should still have some active service AppleID it takes to shut down, so session delay finalizing!

     

    If anyone knows how to work around this problem without having to create a new user, suggestions are very welcome!

     

    Thanks.

1 2 Previous Next