Random slow shutdowns

Hi,
I've been googling and found some info about slow shutdowns but nothing helpful.
I'm running Macbook Pro mid-2012, 10.8.4 with an SSD. Usually the shutdown process takes 1-2 seconds but at least once a day it gets stuck and takes about 10+ seconds. I'll post my shutdown log. Maybe you can at least tell me what's causing it if it can't be fixed.
Thanks!
http://www.upload.ee/download/3500786/13a862d8835fa8b3628/shutdown.txt.zip

In this occasion I normally start with "standard" clearing: delet ALL caches, perform Permission Repairing (with M. Lion Cache cleaner, Onyx or similars) and if you don't get result perform an SMC reset:
http://support.apple.com/kb/ht3964
followed by 2-3 consecutively PRAM restarts.
Cheers
Simon
PS: I do perform cache cleaning and permission repair at each OS update and I do not have 99% of the problems that other may encounter.

Similar Messages

  • Windows 8.1 Random Slow Startups, "Improper Shutdowns"

    Is this the right subforum? I almost chose frezes/hangs but that's not exactly what it is so...
    Please note that this is a copy/paste from another forum where I sought help. Today is another day from the one referenced in the indented text below. In fact, my system had a clean and safe boot with no speed issues or stalling tonight. The issue is not consistent. Though I was seeking help at another forum, I grew uncomfortable with the steps asked of me (deleting caches and temp files that I'd rather keep and using a third-party defragger; getting standoffish when I requested explanation for why I was being asked to run three or more "cleaner" programs and if defragging was honestly necessary on a mostly-new machine that just got a clean bill of health from HP) and was brushed aside with something of an attitude. Here's the original info on the issue:
    Alright, so, yesterday I noticed that it seemed to take a little longer than usual to start up my laptop (HP Pavilion 17-7042nr with Windows 8.1 64-bit; I've only had it a short amount of time and it was purchased refurbished). I didn't think too much of it, however, since I was starting it at the same time as my seven-year-old Vista machine so by comparison it was still way faster (20+ seconds vs. the old one's 2 minutes). After that, didn't think anything of it...
    Today, however, I started it up on its own and it took far too long compared to how it used to behave. I've noticed this a few times in the past, but always figured Windows was adjusting itself after I'd installed stuff etc. But since there was no need for it to do that this time, I got suspicious and started looking in the event viewer. To my shock, it claimed that the last shutdown was improper and that's why it took forever; it was actually rebooting.
    Trouble is, as far as I knew, no it most certainly did not shut down improperly. I turned it off using the power button, which is set from the power plan to perform a shut down. It did the normal thing: processed the shut down, turned off the screen, and shortly after turned off all system lights except of course the one to indicate that it was plugged in. All seemed well, and was not slower than usual or anything of that sort. So I have no clue why or how it's shutting down improperly.
    But not only that, I tracked it back and several times, as far back as the 19th of February (as well as a couple of times while it was in HP's custody for unrelated maintenance; they apparently did not notice it, either, as it was given a clean bill of health before return) this has been occurring. I've transferred a ton of files, settings, programs, etc. since then so I really didn't want to do a Restore. I did, however, consider it... only to discover that my previous Restore Points before the system was returned by HP have been destroyed. So no chance of going back before the 19th, even if I wanted to (I don't, frankly).
    I have no clue what's going on, but here's the events from the first ever time it happened:
    the logoff/power down is listed as:
    Information    2/19/2015 5:09:11 AM    Kernel-Power    109    (103)
               --  "The kernel power manager has initiated a shutdown transition."
    Information    2/19/2015 5:09:37 AM    Winlogon    7002    (1102)
              -- "User Logoff Notification for Customer Experience Improvement Program"
    after that the next relevant things which involve the boot up:
    Information    2/19/2015 4:42:36 PM    Kernel-Boot    20    None
              -- "The last shutdown's sucess status was true. The last boot's success status was true."
    Error    2/19/2015 4:42:36 PM    Kernel-Boot    29    None
             -- "Windows failed fast startup with error status 0xC00000D4"
    Critical    2/19/2015 4:42:45 PM    Kernel-Power    41    (63)
               --"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
    Error    2/19/2015 4:43:14 PM    EventLog    6008    None
             -- "The previous system shutdown at 4:59:42 AM on 2/19/2015 was unexpected."
    Information    2/19/2015 4:43:21 PM    Service Control Manager    7026    None
              --"The following boot-start or system-start driver(s) did not load: dam"
    Those were from the 19 of February, the first time it seems to have happened. The most recent (today) incident is very similar, but not entirely identical.
    The shutdown was:
    Information    3/17/2015 5:12:16 AM    Kernel-Power    109    (103)
             -- "The kernel power manager has initiated a shutdown transition."
    Upon boot the seemingly relevant bits are:
    Information    3/17/2015 4:47:55 PM    Kernel-Boot    20    None
            --"THe last shutdown's success status was true. The last boot's success status was true."
    Error    3/17/2015 4:47:55 PM    Kernel-Boot    29    None
              --"Windows failed fast startup with error status 0xC00000D4."
    Information    3/17/2015 4:47:55 PM    Kernel-General    12    None
                --"The operating system started at system time 2015-03-17T21:47:45.491075600Z." (( What even is up with that time??? ))
    Critical    3/17/2015 4:48:01 PM    Kernel-Power    41    (63)
               --"The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
    Error    3/17/2015 4:48:24 PM    EventLog    6008    None
              --"THe previous system shutdown at 5:12:03 AM on 3/17/2015 was unexpected."
    I tried googling, to no avail, other than a suggestion that it might be caused by some sort of system file issue. So I ran "sfc /scannow" in an admin-level command prompt and when it was finished it said: "Windows Resource Protection found corrupt files but was unable to fix some of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios."
    I tracked down the log file and it's rather huge but toward the end I found that "Amd64\CNBJ2530.DPB" was corrupted. Naturally, I investigated... But according to the thread I found it's some kind of printer-related thing, and I've never even connected a printer to this system, much less a Canon brand one as the info I found suggested. In fact, the thread I linked claims that it shouldn't cause any huge issues, so... Probably not the cause of my shutdown issues, which are more pressing. Thus, I can't find anything to indicate what's causing this problem.
    The only thing I can think of that I had done around the 19th was I was trying to get rid of Beats Audio crap on my laptop. (Don't even get me started on that hot mess!) So I'd been swapping between the Windows default audio drivers and versions of the Realtek High Definition Audio from both HP and Realtek. But I never had a corrupt install and I don't recall installing one over the other without uninstalling first, so I don't know if that's an issue. Somehow, I doubt it, especially since this issue isn't consistent. Then again, I don't consistently use the audio on my computer so who knows. (UPDATE: Used audio extensively, but it managed a clean shutdown after.)
    After all lights are off and the system is shut down, unless I've been using it on battery and it needs a charge, I unplug it to conserve energy. I only ever do this if the battery has a full charge, so I don't think that should be an issue even though hybrid shutdown/fast boot is some kind of hibernation-shutdown combination. I'd prefer to keep fast start/hybrid boot enabled because, well, it's convenient... and I'm extremely hesitant to tamper with the UEFI settings etc. But, of course, if that's the only fix then I'd prefer it to possible hard drive damage caused by the supposed/apparent improper shut down.
    Also of note: nothing is overclocked or running outside specifications, as far as I know. My system stats are:
    Windows 8.1 64-bit
    AMD A10-5745M APU
    AMD Radeon HD 8610G
    UEFI BIOS Mode
    Secure Boot Enabled
    Any help would be greatly appreciated!
    Now, for extra details. Things that were done during the process included looking for unnecessary startup items (not the real issue to be honest; when it doesn't forcibly reboot due to "improper shutdown" the startup is extremely speedy) and looking at some logs. In particular, here's the speccy log created for my system: http://speccy.piriform.com/results/vIEkYCelmSRyJjuJyye2jgD
    I also had to run several "cleaner" tools, which included installing CCleaner, though I chose some files I wished to keep / thought may be important to not just delete willy-nilly. I don't like to randomly delete things that could come back and bite me in the rear, after all. And I'm honestly confused how any of that would related to Windows having inconsistent and seemingly random "improper shutdown" issues which cause it to reboot instead of using fast boot. (I'm not saying it's impossible, I'm saying that I don't logically see how it'd make a difference and when I attempted to ask I was brushed aside.)
    Like I said, by all appearances it seems to shut down properly. It has also never crashed on me. Nor has it ever blue screened or randomly rebooted.  This is very much a silent, behind-the-scenes issue.

    Hi @Alley_Kitten , 
    Thank you for visiting the HP Support Forums and Welcome. I have looked into your issue about your HP Pavilion 17 f042nr Notebook and issues with performance issues or improper shutdowns. 
    I checked the specs of your system and with what you have posted here you have the incorrect Amd driver installed.  Your's as per your product page is a AMD Radeon HD 8610G . I would go to the device manager and remove all graphic driver, check the box for the driver as well.
    Here is a document on recovery options that are available. I do use the refresh your pc method with Windows 8. Please read all the documentation before starting the operation.
    Hope this helps you out.
    Thanks.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

  • Random, Sudden Shutdowns - A redux and other things to rule out first

    Do a google search for "macbook random shutdown" and you'll find many people with similar problems reporting on various forums. At present, this issue has not been picked up by the mainstream PC news media. However, one should also note that only a fraction of those with problems are suffering this particular fault. A large number of other reasons must be ruled out before a MacBook owner should become convinced their machine is one which suffers this problem. Bad RAM, poorly seated RAM, improperly installed hard drive, corrupted OS, corrupted plists, bad batteries, bad chargers, corrupted PMU, and corrupted NVRAM all need to be ruled out first!
    My own MacBook suffered the random sudden shutdown malady and eventually required complete replacement after a logic board replacement did not solve the issue. Some of the MacBooks appear to have a hardware problem which surfaces after a period of use. Many reported their problems starting after a month of ownership. Coincidentally, that also coincided with the release of 10.4.7, but most likely that is not at the root of the sudden, random, shutdown problem.
    (However, 10.4.7 is strongly implicated in a separate MacBook problem - colored vertical lines during boot on some machines. That is probably a separate issue.)
    Description of the Random, Sudden Shutdown Problem
    MacBook suddenly shuts off to a completely powered down state seemingly at random. There are no kernel panic, mouse freezing, or other premonitory symptoms. The machine simply powers down suddenly. The screen goes black. The hard drive spins down and no sleep light illuminates. The machine simply turns itself off.
    The shutdowns may occur on either battery or with AC adapter attached. Some owners report their MacBook is less prone to sudden shut down while on battery vs AC adapter. My own afflicted MacBook would suddenly shutdown on a fully charged battery or on either of two AC adapters.
    The shutdowns occur with either 10.4.6 or 10.4.7 OS loaded. I went through several cycles of clean installs of the base 10.4.6 and the Intel Combo update to 10.4.7 before it became clear that it mattered not which OS was running. Another indicator that this is not an OS issue is that sudden shutdowns can occur in target mode and also when running just the Apple Hardware Test - which relies on minimal software to operate.
    The shutdowns tend to grow more frequent once they begin. They may worsen to the point that a machine will not complete boot up before shutting down. It may take several power up presses to start the machine. Oddly enough, a machine that had difficulty starting up, may be easy to start up several minutes later. It may run for hours or minutes before another sudden shutdown. The frequency is low and random enough that is very difficult to demonstrate this fault to a service technician.
    Some users are able to induce a sudden shutdown by running their CPU's at high load and thus heating up the machine. This is easily done by running the yes command in two Terminal windows. Some users report their MacBook is more prone to sudden shutdowns when their CPU is relatively cool. The bipolar reporting is confusing. There may be more than one type of sudden shutdown being reported. One due to CPU overheating and another due to another hardware problem which has yet to be elucidated.
    Resetting of the PMU and PRAM MAY temporarily reduce the frequency of the sudden shutdowns, but the effect is temporary. Indeed, the effect may not even be real given the randomness of the shutdowns. None-the-less, one must perform PMU and PRAM resets to ensure that some corruption of those devices is not creating a reason for shutdowns. On my own MacBook, resetting PMU and PRAM (four chimes) did not prevent the random sudden shutdowns.
    The sudden shutdowns occur with well seated stock RAM, replacement RAM, and reseated/replaced hard drives. Swapping out and testing both RAM and hard drive helps to eliminate those as the source of the problem. On my own machine, I exchanged the RAM and the hard drive to eliminate them as the cause. This made it considerably easier for the Apple genius to decide it was an internal problem.
    In my case, a logic board replacement did indeed solve the fault, but several days later, sudden shutdowns began again. Presumably either the replacement board has the same weakness as the original or some other component of the machine was the actual reason for the sudden shutdowns. The former is quite likely because the machine was made stable for several days with a new logic board. At that point, I requested to be swapped to a new machine and the Apple Store manager wisely decided to help out his customer. For that I am most grateful. However, it is unlikely that the majority of people will have their machines swapped out, but instead repaired.
    At this time, no official statement regarding cause for or acknowledgment of the MacBook's sudden random shutdown problem has been made. Because the underlying cause has not been revealed, it is impossible to know that a logic board replacement will permanently solve the problem or merely result in the same fault recurring later on the replacement board. Of course, we do not know if it actually is a logic board flaw.
    My advice to MacBook owners whose machines develop the sudden random shutdown symptoms are to...
    1. Get your data backed up immediately. The machine will likely suffer more and more frequent shutdown events.
    2. Revert to stock RAM and hard drive if you have installed after-market replacements. You must do this and see if the shutdowns continue to occur. Otherwise, the first thing blamed will be your RAM and hard drive.
    3a. Perform a PMU reset, by shutting down the MacBook. Removing the battery. Disconnect the AC Adapter. Then, press the power button for five seconds. The reinstall the battery and mains adapter. Restart the machine.
    3b. Reset PRAM by holding option-command-P-R keys down during startup until you hear the chime at least three or four times.
    Resetting the PMU and PRAM are standard procedures you'll otherwise be asked to perform to diagnose your machine.
    4. Do a CLEAN install of the OSX if you wish to totally eliminate a bad OS install as the problem. This will destroy all your data. Alternatively, an archive and install will be helpful without totally destroying your data, but that will not let you exonerate your system files and settings. An alternative is to run Apple's hardware test utility which is found on your OS installation disc. However, an extended hardware test is needed because the shutdown flaw may take hours to surface.
    Note: If your MacBook has become so "narcoleptic" that it cannot even complete a boot up sequence, try holding the power button down until you hear a loud beep. That may allow an otherwise balky machine to start.
    Once you have done the above, and are still seeing random sudden shutdowns, you have largely done the preliminary footwork that you'll need to prove whether your MacBook has this particular problem and not something more common. Then, call AppleCare or visit your Apple Genius to have the machine repaired or replaced. Hopefully, the root cause of this problem will be discovered, disclosed, repaired and prevented. For now, it appears only a fraction of the MacBooks are suffering this fault, but the machine population is still young. Overall, the MacBook is perhaps the finest laptop I've bought from Apple. It will be nice to trust the machine to not lose my work.
    BTW - resetting PMU may induce a separate 10.4.7 related bug which results in your MacBook exhibiting a white screen with progressively more numerous vertical color lines during startup. This appears to be fixable by resetting PRAM and then temporarily changing display resolution to something other than the current setting and then back.

    thanks for the comprehensive info. i experienced this for the first time today. i bought my macbook the day they were released. the shutdown happenned for me after leaving my computer on overnight with no programs running. about two minutes into web browsing it shutdown. it then shutdown in the middle of restarts. i disattached power cord, external hard drive, dvd burner & ethernet & it powered up and has been working for about 20 minutes since.
    this computer has really been a lemon. first my superdrive scratches the **** (just previewed this, i can't believe they sensor the h_ word?) out of discs, then the trackpad button becomes very hard to push. i've been working around those issues using an external dvd burner and mouse, but not sure how to work around sudden shutdowns. i haven't been able to send it in for repairs yet since i bought it cause i needed it's dvd authoring capabilities for a class i was taking, plus i wanted to make sure nothing else went wrong (self fulfilling prophecy?). i was planning on taking it on vacation with me, but guess i better pack my old ibook too (which other than a cd burner which sucked from the start, has been very reliable). i'll send in my macbook when i get back.
    anyway, thanks for the info & advice! i'll back up my crucial data now.
    white macbook, 2GHz, 1GB ram (factory installed) Mac OS X (10.4.7)
    macbook Mac OS X (10.4.6)
    macbook   Mac OS X (10.4.6)  

  • Random Slow Boot Ups

    Hi forum members,
    I have been using Windows 7 64 Bit ultimate for almost 2-3 months. I have noticed this strange slow boot ups(randomly once in 3 or 4 days) during cold boot or restart. The system seems to hang up at the Windows 7 splash screen, but on the contrary its not hanged. The system is taking its own sweet time to boot up to the start up screen.
    During a normal boot up my Razer Lycosa and Lachesis backlights would go off for few seconds and lights up as soon windows 7 start up screen appears. But during the random slow boots I have noticed that the backlight of Razer Lycosa stays on for 2-3 mins before Windows 7 start up screen appears. Another strange thing that I've noticed was the ticking sound on my Logitech Clearchat USB headset during the random slow boot. The ticking sound appears every 3 seconds during the slow boot. What could be the problem guys? Is it because of Hardware or corrupt system files. FYI, I have Razer Lachesis, Lycosa, HP 3500 Deskjet Printer and Logitech USB Headset connected to the USB ports. Logitech USB headset is connected to the USB port of Razer Lycosa.
    I have recently flashed my MOBO to see if it was because of the BIOS, but the problem persists even after flashing.
    Any suggestions members. I would really appreciate your help on this.
    My system specs,
    Intel Core i7 920 2.66
    MSI X58 Pro SLI ( BIOS Version 8.A)
    Corsair DDR3 3 x 2GB DDR3 1333
    2 x 1 TB Seagate SATA II
    EVGA GeForce GTX 295
    Tagan 1100 W BZ Series
    Windows 7 64 Ult
    Regards
    Rahul

    Thanks for the reply Henry. Well I am trying that but as I have mentioned in the POST the problem happens very randomly, like once in 4 days. Funny after posting this thread the system is running fine. I am determined to find the cause of this. I am planning to do couple of cycles of reboot today to determine if its the hardware issue(USB). What can be the other problems apart from the USB issues??

  • My Macbook pro Early 2008 is randomly slow at starting up and when I am backing up to my time capsule I am receiving the following message 'Time machine could not complete the backup. '' ''The backup disk image ''/Volumes/name time capsule/ my name MacBoo

    My Macbook pro Early 2008 is randomly slow at starting up and when I am backing up to my time capsule I am receiving the following message 'Time machine could not complete the backup. '' ''The backup disk image ''/Volumes/name time capsule/ my name MacBook Pro (4).sparsebundle'' could not be accessed (error-1).
    Problem started after deleting parrell desktop and window7 ?
    Please help?

    Look at the more like this column on the right.. this is the most frequently asked question in this discussion area.
    Reboot the TC.. restart the whole network if the simple reboot did not work.. start in order. modem.. router/TC.. clients. 2min gap.
    Read C12 here. http://pondini.org/TM/Troubleshooting.html

  • Slow shutdown after 10.8.2 - securityd / appleevents

    Hi everyone,
    since the last update (10.8.2) I have experience slow shutdown time, with spinning wheel also.
    I use the OWC SSD 120GB 6GB as startup disk since OS Lion and my machine (Macbook Pro 13 late 2011) used to be extremely fast. Talking about shutdown time, it used to be about 2~3 seconds, but now running 10.8.2 it was increased to 20 seconds.
    Using verbose mode it is possible to see:
    com.apple.securityd ----- PID is still valid
    com.apple.securityd ----- Killability: dirty/idle-exit unsupported
    com.apple.coreservices.appleevents ----- PID is still valid
    com.apple.coreservices.appleevents ----- Killability: dirty/idle-exit supported
    com.apple.launchd ----- System: Still alive with 2/1 (normal/anonym
    it repeats 3 times, and after something awas unable to get, it shows
    Killing all processes
    Does anyone have some idea about what is going on?
    Is this bug about the SSD drive? On 10.8.1 I did not notice any issue. It used to be very fast on shutdown...
    Thanks,
    GCalligaris.

    here goes a picture of verbose mode shutdown. Sorry about the poor resolution...
    Thanks again!!
    GCalligaris.

  • Macbook air slow shutdown

    My brand new macbook air 13" seems to have a pretty slow shutdown time (20s+).
    As I am new to mac I spent several days trying to find a fix without any succes.
    After a shutdown I just ran a console search for a exit timeout and found the following:
    01/11/13 00:04:38,068 com.apple.launchd[1]: (com.apple.appkit.xpc.openAndSavePanelService[261]) Exit timeout elapsed (20 seconds). Killing
    I think this might be the problem but I am not sure which terminal command should be used to reduce the killing time.
    Could anyone please help me ?

    I've just read on another thread that it could be lion 10.7.1. I can't say this for sure since I immediately restored my time machine backup. I'll re-install lion and check it out, then, I'll put my time machine back.
    Pffieuw, wish me luck.

  • Possible fix for slow shutdown in Leopard

    After messing with a slow shutdown issue on a mini and mac book pro (clean install and intel on both), I finally found a solution for the shutdown taking anywhere up to two minutes.
    I noticed that if I logged out first, then shutdown my shutdown time was back within reason. If I killed any extra processes running under my name before I shutdown it would shutdown within about 5-10 seconds. The two processes that solved my shutdown issue were: ituneshelper and tunnelblick.
    It looks like the shutdown issue for me has something to do with the shutdown process somewhat hanging on user processes running when a shutdown is initiated. Try killing non-essential programs running under your name in Activity Monitor and see if that speeds up the shutdown.
    For some reason checking the ituneshelper and tunnelblick login items under Accounts did not stop them from starting up. I had to completely remove them from the login item list.
    Hope this helps someone out there.

    If you literally "checked" them, meaning the checkboxes, that only affects their visibility. To remove them, select one and then click on the "minus" part of the "plus minus" at lower left.
    Doug

  • MacBook Pro Retina 2013 very slow shutdown

    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 ?

    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 it — not 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.

  • Slow Shutdown & Startup on MacBookPro OS ML 10.8.2

    I have faced slow shutdown & startup on my MacBook Pro Late 2011 , OS X Mountain Lion 10.8.2 for a while.
    I have done searching for solution and had tried some but no luck.
    Could someone please help.
    Thanks!
    Below are the message from console
    Dec 24 23:07:28 --- last message repeated 4 times ---
    Dec 24 23:07:28 com.apple.launchd[1] (com.apple.ShareKitHelper[258]): Exited: Killed: 9
    Dec 24 23:07:28 com.apple.launchd.peruser.501[146] (com.apple.PackageKit.InstallStatus[394]): Exited: Terminated: 15
    Dec 24 23:07:28 com.apple.launchd.peruser.501[146] (com.apple.PackageKit.InstallStatus): Throttling respawn: Will start in 10 seconds
    Dec 24 23:07:28 com.apple.launchd.peruser.501[146] ([0x0-0x11011].com.apple.inputmethod.ironwood[203]): Exited: Killed: 9
    Dec 24 23:07:28 MacBook-Pro.local coreservicesd[26]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=143
    Dec 24 23:07:28 --- last message repeated 1 time ---
    Dec 24 23:07:28 MacBook-Pro com.apple.launchd.peruser.501[146] (com.apple.talagent[159]): Exited: Killed: 9
    Dec 24 23:07:28 MacBook-Pro.local coreservicesd[26]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=243
    Dec 24 23:07:28 MacBook-Pro.local UserEventAgent[11]: Captive: [UserAgentDied:139] User Agent @port=41995 Died
    Dec 24 23:07:28 MacBook-Pro.local coreservicesd[26]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=159
    Dec 24 23:07:28 MacBook-Pro.local coreservicesd[26]: SendFlattenedData, got error #268435460 (ipc/send) timed out from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=100
    Dec 24 23:07:28 MacBook-Pro com.apple.launchd.peruser.501[146] ([0x0-0x1a01a].com.apple.AppleSpell[235]): Exited: Terminated: 15
    Dec 24 23:07:28 MacBook-Pro com.apple.launchd.peruser.501[146] (com.apple.UserEventAgent-Aqua[149]): Exited: Killed: 9
    Dec 24 23:07:28 MacBook-Pro com.apple.launchd.peruser.501[146] (com.apple.storeagent[255]): Exited: Killed: 9
    Dec 24 23:07:28 MacBook-Pro com.apple.launchd.peruser.501[146] (com.apple.mdworker.shared.04000000-0000-0000-0000-000000000000[239]): Exited: Killed: 9
    Dec 24 23:07:28 MacBook-Pro com.apple.launchd.peruser.501[146] ([0x0-0xc00c].com.apple.iTunesHelper[185]): Exited with code: 1
    Dec 24 23:07:28 MacBook-Pro.local WindowServer[101]: CGXGetConnectionProperty: Invalid connection 38659
    Dec 24 23:07:28 --- last message repeated 4 times ---
    Dec 24 23:07:28 MacBook-Pro.local loginwindow[48]: DEAD_PROCESS: 48 console
    Dec 24 23:07:28 MacBook-Pro.local airportd[395]: _doAutoJoin: Already associated to “Internet_Mobility”. Bailing on auto-join.
    Dec 24 23:07:28 MacBook-Pro.local coreservicesd[26]: SendFlattenedData, got error #268435459 (ipc/send) invalid destination port from ::mach_msg(), sending notification kLSNotifyApplicationDeath to notificationID=131
    Dec 24 23:07:28 MacBook-Pro.local WindowServer[101]: CGXGetConnectionProperty: Invalid connection 38659
    Dec 24 23:07:28 --- last message repeated 4 times ---
    Dec 24 23:07:28 MacBook-Pro.local shutdown[396]: halt by Keant:
    Dec 24 23:07:28 MacBook-Pro.local shutdown[396]: SHUTDOWN_TIME: 1356361648 592277

    This fixed mine
    > sys pref
    >network
    >Advanced
    > DNS
    check DNS numbers are correct, mine was showing the router and greyed out so I added my IP specific numbers
    >Restart (not sure if you need this step but I did it)
    Page loading improved significantly from very slow to acceptable on some to blistering fast in others
    AND emails just flew out really quickly
    Also make sure you have the right ports for your IP because I had been given an alternate one to try and that upset the incoming messages
    >Mail
    >preferences
    > advanced
    > port (you can find this by searching your the help section of your IP)

  • Mavericks very slow shutdown, how to fix it?

    Since I updated my 13' late 2012 MacbookPro to OSX Mavericks it won't shut down at all or it takes extremely long (about 1 hour!). Someone any idea how to solve this problem? The only options for me at the moment ar shutting the system down by holding the shutdown/boot button or just leaving my Macbook on all the time, which isn't quite nice .
    Hope you guys can help me!

    SOLVED slow shutdown as follows:
    WhiteHat Aviator was repeatedly showing up as com.whitehatsec.aviator.dmg in Disk Utility.  There's no uninstaller, but I removed Aviator by deleting:
    Library/LaunchAgents/com.aviator.agent.plist
    Library/Aviator  (containing com.aviatorupdate.agent, RunUpdate, UpdateAviator, etc.)
    Library/Caches/Aviator
    Library/Caches/AviatorEngine
    Library/Caches/UpdateEngine-Temp/com.whitehatsec.aviator.dmg-etc.
    Library/Caches/UpdateEngine.503/Downloads/com.whitehatsec.aviator.dmg
    Library/LaunchAgents/com.aviator.agent.plist
    Library/Application Support/Aviator
    Library/Preferences/com.whitehatsec.aviator.plist
    Library/Saved Application State/com.whitehatsec.aviator.savedState
    As a huge side benefit, my system no longer hangs for a minute on shutdown!
    For further details, see solmaker posts at: https://discussions.apple.com/thread/6337331

  • Very slow shutdowns

    This is a new Toshiba S855-S5254 which is now having *very* slow shutdowns. The shutdown startes and then hands at the "shutting down" message till it finally shuts down. The event log for System showed the following error "A timeout (30000 milliseconds) was reached while waiting for a transaction response from the TOSHIBA eco Utility Service service". So, I uninstalled the TOSHIBA eco Utility using Windows add/Remove programs and on checking Power Options the Eco option is no longer present. But- the long slow shutdowns persists despite 2 reboots. System Event log shows the following repeated error: The device, \Device\CdRom0, has a bad block. Not sure what that means and there is no CD in the drive. Help anyone? Thanks.
    Solved!
    Go to Solution.

    What do I do about it?
    Your turn to think. Read the article to which I linked and make inferences.
    -Jerry

  • EAP service causes slow shutdown

    Hi
    I've got a problem with my desktop PC Win7 pro. serv. pack 1.
    All of the sudden I have a very slow shutdown (2-3 min) - for no apparent reason.
    I've pinned the problem down to the service EAP (extensible authentication protocol) when this service is stopped Win7 shuts down normally (5 sec).
    But I need EAP for internet - currently EAP is set to manual...
    Clear pagefile at shutdown is disabled and waittokill is set to the min. value of 2000
    Any suggestions?
    I've got a etl shutdown trace file for Win performance analyzer, can anybody help me interpret it?
    By the way I've got all of my drivers updated..!

    I solved the problem on my own - a bit embarrassing perhaps, but here goes.
    I found out that "IsDegradation "true" means that some Windows built-in application or service has caused this slowdown. For example
    sidebar.exe (Desktop Gadgets) or ssdpsrv (SSDP Discovery). If it reads "false", the problem lies elsewhere." (thanks https://www.winhelp.us/troubleshoot-performance-in-windows-vista-and-7.html)
    When I connect direct lan (cable in PC) shutdown was normal, so it had to do with the wireless network connection,  I had another look at adapter settings and I always had two connections there with a red cross (active but not connected) those where:
    Intel(R) 82579V Gigabit Network Connection and Microsoft Virtual WiFi Miniport Adapter #2 - I deactivated those two (right click and deactivate) and problem was solved, PC shutdown is back to 8 sec. (wireless setting on Atheros must have been changed somehow
    conflicting with other inactive connections?) but inactive conn. most probably should have been deactivated long time ago #)
    So - Controlpanel - Network and sharing center - Change adapter settings - Deactivate all other connections than Qualcomm Atheros AR9287.

  • Slow shutdown of WinXP with SB X

    Hi!
    My Windows XP takes forever (or at least that's what it feels like) to shutdown after I have installed the X-Fi Fatalty. It's shutdowns fine up until I install the drivers and the software. Then it slows down and seems to be waiting for something to close. The harddri'ves aren't working, and when I press ctrl-alt-del nothing happens, so I can't see what program isn't responding.
    I first downloaded and installed the update without change. Then I formatted my system and re-installed Windows, with the same result. I have all the updates for Windows, firewall and Antivirus.
    It's may not be a big problem, but it's annoying.
    My system:
    MB: Asus p5gdc deluxe (intel 95p chipset)
    RAM: 2x mb ddr3200 in dual channel mode
    CPU: P4 3.8 (670)
    GPU: Asus GF 7600GT 256 MB
    OS: Windows XP SP2

    Well the problem is that I like having the Volume panel running, because it's comfortably available when I need it, which is quite often. I play games, listen to music and have my guitar connected to it so i constantly change modes. Having to go to start->programs->creative... every time is even more annoying than a slow shutdown. I just can't understand why they're so slow to shut down. They aren't that big "system hogs", at least not compared to firewall and antivirus, which shuts down instantly.

  • Super fast boot but very slow shutdown

    Just installed Vertex 3 SSD into new MacBook pro (late 2011), startup time in Lion is now very quick (about 17s) but shutdown time is about 25s.  I have repaired permissions using disk utility but the problem persists.  Please help

    OK, found the solution.  I looked at
    Apple > About this mac > More Info > System Report...
    And noticed an item in the startup items for some HP software that I had installed.
    I ran the HP software uninstaller and after another long shutdown, the next shutdown was back down to a second or two.
    Seems third party software is to blame for a lot of slow shutdown problems!

Maybe you are looking for