Advice on upgrading to El Capitan

A combination of inertia and the dislike of change kept me from the reclassification of Yosemite to El Capitan, but now that Sierra is on the horizon, I think I should make the trip.  I use 3.1 GHz iMac bought in February 2015 with 16 GB of memory. Should I seek or be cautious in making the upgrade from?

Thanks in advance - this community is always friendly and helpful!

backup before doing anything else.

Make sure that all your applications 3rd party and external hardware is compatible by contacting the developers. Sites related to compatibility are often not regulated and prone to misinformation of the user.

Make a copy of all of your passwords and serial numbers or keep them accessible when the computer is upgraded.

Add El Capitan to your Apple ID to store when arrived on September 20 and is no longer in the download store is available in your account and receiving grandfathered in.

You can download the installer and check it for more late without installing it.

the installer is placed in

Macintosh HD/Applications/install El Capitan

Once installed, the installer will remove itself, make a backup.

Tags: Mac OS & System Software

Similar Questions

  • Crash when upgrading to El Capitan

    My brother has a 2009 MacBook Pro with Snow Leopard running he'd like to upgrade to El Capitan.

    He began by upgrading to the latest version of Snow Leopard then went to the App Store, logged into his account and started the upgrade. The download went as planned but it got an error message. He saved the Setup log. It is approximately 1.2 MB. Not sure as what to do, but which seems to me to be a relevant article of it, I copied below.

    Any advice would be appreciated!

    Thank you!!

    28 Mar 15:40:33 MacBook - Pro OSInstaller [453]: from Application Migration:

    = System Migration request =.

    SMSystem 0, SMSystem_Daemon. Primary ID: file:///Volumes/Trevors240/Recovered%20Items/ (ServerType: 1).

    Status: Standard

    Type: upgrade the operating system

    2 user (s) to the migration:

    {

    preserveExisting: 0

    short name: trevorandrews

    deleteOnDest: 0

    longName: Trevor Andrews

    newLongName: Trevor Andrews

    userObject: FV:0 501:20 [1BF1C9F2-A34C-4653-886E-C320FAAEEA64] trevorandrews (Trevor Andrews) MNC:0 PHU:0 ADM:1 iCloud:)

    ) ; ShadowHash;

    [file:///Library/User%20Pictures/Fun/Beach%20Ball.tif]

    file:///users/trevorandrews/ (((null)))

    Exclude: (null)

    newShortName: trevorandrews

    oldShortName: trevorandrews

    }

    {

    preserveExisting: 0

    shortName: root

    deleteOnDest: 1

    longName: System Administrator

    nonConflictingShortName: root

    newLongName: System Administrator

    userObject: root (System Administrator) 0:0 [FFFFEEEE-DDDD-CCCC-BBBB-AAAA00000000] FV:0 MNC:1 PHU:0 ADM:1 iCloud:)

    ) ; Base;

    [(null)]

    file:///private/var/root/ ((file: / / / Volumes/Trevors240/Recovered%20Items/private/var/root/))))

    Exclude: (null)

    newShortName: root

    oldShortName: root

    }

    FileGroupings =)

    1,

    2,

    5,

    3,

    4

    )

    copiesNetworkSettings = Yes

    copiesTimeZoneSettings = Yes

    copiesMachineSettings = Yes

    copiesHomeDirectories = No

    copiesUsers = No

    Incompatible applications =)

    )

    = End =.

    28 Mar 15:40:33 MacBook - Pro OSInstaller [453]: translation UID: old system UID 0 will be UID 0 after Migration.

    28 Mar 15:40:33 MacBook - Pro OSInstaller [453]: GID translation: old system GID 0 will use GID 0 after Migration.

    28 Mar 15:40:33 MacBook - Pro OSInstaller [453]: UID translation: found no existing on the system user registration target with the name 'trevorandrews '.

    28 Mar 15:40:33 MacBook - Pro OSInstaller [453]: translation UID: old system UID 501 will be UID 501 after the Migration.

    28 Mar 15:40:33 MacBook - Pro OSInstaller [453]: translation GID: former GID 20 system will use GID 20 after Migration.

    28 Mar 15:40:33 MacBook - Pro OSInstaller [453]: Migration suspends the Time Machine and Spotlight indexing, preventing the idle sleep

    28 Mar 15:40:33 MacBook - Pro OSInstaller [453]: prevent the sleep of the machine.

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453 - customer: "OS X Installer", came out with 3 sessions 3 node (s) and 0 or more active requests

    28 Mar 15:40:34 - MacBookPro Language Chooser [429]: child process exited 8

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453.65 - ODNodeRelease request, NodeID: 7CC2B2D3-68CA-46C5-A560-D1871B08AEED

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453.66 - ODNodeRelease request, NodeID: 9322825E-8538-4B8D-984C-AA115086E5A5

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453.67 - ODNodeRelease request, NodeID: 96942C78-E0B0-4E8A-A901-43E82B8530C1

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453.68 - ODSessionRelease request, SessionID: 27A22409-C946-49CF-BDD0-497E3E17CC95

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453.69 - ODSessionRelease request, SessionID: 42AB3A92-439A-4684-8FE7-93291DC60209

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453.70 - ODSessionRelease request, SessionID: F06D7194-DDB5-41DA-A391-7BA69E4F6647

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453.65, node: / Local by default - ODNodeRelease completed

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453.66, node: / Local by default - ODNodeRelease completed

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453.67, node: / Local by default - ODNodeRelease completed

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453.68 - completed ODSessionRelease

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: 453.69 - completed ODSessionRelease

    28 Mar 15:40:34 MacBook-Pro opendirectoryd [123]: ODSessionRelease 453.70 - completed

    28 Mar 15:40:36 MacBook-Pro storagekitd [455]: removal of client connection < SKDaemonConnection: 0x7f8eb8404ba0 >

    28 Mar 15:40:36 MacBook-Pro storagekitd [455]: no more connections, storagekitd will leave...

    28 Mar 15:40:36 unknown MacBook Pro [2622]: launch of Installer Crash Log Viewer

    28 Mar 15:40:39 - MacBookPro Viewer [2623]: LSExceptions [0x7fe5b9d22b50] loaded

    28 Mar 15:40:40 - MacBookPro Viewer [2623]: ISAP: Abort progress called user interface.

    28 Mar 15:40:40 MacBook-Pro Installer progress [423]: sending end progress UI to delegate.

    28 Mar 15:40:40 MacBook-Pro Installer progress [423]: end of progress called user interface...

    28 Mar 15:40:50 - MacBookPro Viewer [2623]: LSExceptions [0x7fe5b9d22b50] unloaded

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.71 - Client: ReportCrash, UID: EUID, 0: 0, GID: 0, EGID: 0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.71 - ODNodeCreateWithNameAndOptions request, SessionID: 00000000-0000-0000-0000-000000000000, name: / Local by default, Options: 0x0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.71, node: / Local/Default - assigned node UUID - 8BE4C568-EE69-47CA-802B-03C2034E55FD

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.71, node: / Local by default - ODNodeCreateWithNameAndOptions completed

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.72 - Client: ReportCrash, UID: EUID, 0: 0, GID: 0, EGID: 0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.72 - ODNodeCopyDetails request, NodeID: 8BE4C568-EE69 - 47CA - 802 - 03C2034E55FD, keys: dsAttrTypeStandard:NodePath

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.72, node: / Local/default, Module: PlistFile - over ODNodeCopyDetails, delivered 1 result

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.73 - Client: ReportCrash, UID: EUID, 0: 0, GID: 0, EGID: 0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.73 - ODNodeRelease request, NodeID: 8BE4C568-EE69-47CA-802B-03C2034E55FD

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.73, node: / Local by default - ODNodeRelease completed

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.74 - Client: ReportCrash, UID: EUID, 0: 0, GID: 0, EGID: 0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.74 - ODNodeCreateWithNameAndOptions request, SessionID: 00000000-0000-0000-0000-000000000000, name: /Search, Options: 0x0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.74 - ODNodeCreateWithNameAndOptions failed with error ' node name unknown "(2000)

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.75 - Client: ReportCrash, UID: EUID, 0: 0, GID: 0, EGID: 0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.75 - ODNodeCreateWithNameAndOptions request, SessionID: 00000000-0000-0000-0000-000000000000, name: /Search, Options: 0x0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.75 - ODNodeCreateWithNameAndOptions failed with error ' node name unknown "(2000)

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.76 - Client: ReportCrash, UID: EUID, 0: 0, GID: 0, EGID: 0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.76 - ODNodeCreateWithNameAndOptions request, SessionID: 00000000-0000-0000-0000-000000000000, name: / Local by default, Options: 0x0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.76, node: / Local/Default - assigned node UUID - FF17241D-BC11-43AD-82D6-1DB36B4377E8

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.76, node: / Local by default - ODNodeCreateWithNameAndOptions completed

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.77 - Client: ReportCrash, UID: EUID, 0: 0, GID: 0, EGID: 0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.77 - ODQueryCreateWithNode request, NodeID: FF17241D-B11-43AD - 82 D 6-1DB36B4377E8, RecordType (s): dsRecTypeStandard:Users, attribute: dsAttrTypeStandard:RecordName, MatchType: all, equality: CaseIgnore, value (s): dsRecordsAll, attributes requested: dsAttrTypeStandard:GeneratedUID, dsAttrTypeNative:LinkedIdentity, dsAttrTypeStand ard:RealName, dsAttrTypeStandard:GroupMembership, dsAttrTypeNative:IsHidden, dsAttr, TypeStandard:Picture, dsAttrTypeStandard:UserCertificate, dsAttrTypeStandard:Apple, MetaNodeLocation, dsAttrTypeStandard:RecordType, dsAttrTypeStandard:Comment, dsAttr TypeStandard:NestedGroups, dsAttrTypeStandard:PrimaryGroupID, dsAttrTypeStandard:A uthenticationAuthority , dsAttrTypeStandard:Keywords, dsAttrTypeStandard:RecordName, dsAttrTypeStandard: JPEGPhoto, dsAttrTypeNative:_guest, dsAttrTypeStandard:AppleMe, taRecordName, dsAttrTypeStandard:UserShell, dsAttrTypeStandard:GroupMembers, dsAttr, TypeStandard:UniqueID, dsAttrTypeStandard:EMailAddress, dsAttrTypeStandard:NFSHome, directory, Max results: 2147483647

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.77, node: / Local/default, Module: PlistFile - over ODQueryCreateWithNode, delivered 86 results

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.78 - Client: ReportCrash, UID: EUID, 0: 0, GID: 0, EGID: 0

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.78 - ODNodeRelease request, NodeID: FF17241D-BC11-43AD-82D6-1DB36B4377E8

    28 Mar 15:41:17 MacBook Pro opendirectoryd [123]: 2620.78, node: / Local by default - ODNodeRelease completed

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: process: OS X Installer [453]

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: path: / Volumes/VOLUME / * / install OS X Installer.app/Contents/MacOS/OS X

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: identifier: the installer for OS X

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]: Version: 1.0 (733)

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]: Code Type: X 86-64 (Native)

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: Parent process:? [429]

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: Manager: Setup OS X [453]

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: user ID: 0

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: Date/time: 2016-03-28 15:40:37.144-0700

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: OS Version: Mac OS X 10.11.4 (15E65)

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: report Version: 11

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: anonymous UUID: 56972A61-D95B-4B34-B2A9-FE712E828D64

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: time awake since Boot: 2100 seconds

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: system integrity Protection: disabled

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: crashed Thread: 8 dispatch queue: com.apple.root.default - qos

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]: Exception Type: EXC_ARITHMETIC (SIGFPE)

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: Codes of Exception: EXC_I386_DIV (division by zero)

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: Note of the Exception: EXC_CORPSE_NOTIFY

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: Thread 0: send queue: com.apple.main - wire

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 0 libsystem_kernel.dylib 0x0000000111342f72 mach_msg_trap + 10

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 1 libsystem_kernel.dylib 0x00000001113423b3 mach_msg + 55

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 2 com.apple.CoreFoundation 0x000000010dd6d1c4 __CFRunLoopServiceMachPort + 212

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 3 com.apple.CoreFoundation 0x000000010dd6c68c __CFRunLoopRun + 1356

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 4 com.apple.CoreFoundation 0x000000010dd6bed8 CFRunLoopRunSpecific + 296

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 5 com.apple.HIToolbox 0x0000000115e5d935 RunCurrentEventLoopInMode + 235

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 6 com.apple.HIToolbox 0x0000000115e5d76f ReceiveNextEventCommon + 432

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 7 com.apple.HIToolbox 0x0000000115e5d5af _BlockUntilNextEventMatchingListInModeWithFilter + 71

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 8 com.apple.AppKit 0x000000010c856efa _DPSNextEvent + 1067

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 9 com.apple.AppKit 0x000000010c85632a-[NSApplication _nextEventMatchingEventMask:untilDate:inMode: dequeue:] + 454

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 10 com.apple.AppKit 0x000000010c84ae84-[NSApplication run] + 682

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 11 com.apple.AppKit 0x000000010c81446c NSApplicationMain + 1176

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 12 com.apple.OS - X-install 0x000000010b96f9b3 0x10b96e000 + 6579

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: start of 13 libdyld.dylib 0x00000001111635ad + 1

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 1 wire: send queue: com.apple.root.utility - qos

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 0 libsystem_kernel.dylib 0x0000000111342f72 mach_msg_trap + 10

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 1 libsystem_kernel.dylib 0x00000001113423b3 mach_msg + 55

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 2 com.apple.CoreFoundation 0x000000010dd6d1c4 __CFRunLoopServiceMachPort + 212

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 3 com.apple.CoreFoundation 0x000000010dd6c68c __CFRunLoopRun + 1356

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 4 com.apple.CoreFoundation 0x000000010dd6bed8 CFRunLoopRunSpecific + 296

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 5 com.apple.Foundation 0x000000010bdeedd9-[NSRunLoop (NSRunLoop) runMode:beforeDate:] + 270

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 6 com.apple.Foundation 0x000000010be82f43-[NSRunLoop (NSRunLoop) runUntilDate:] + 108

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 7 com.apple.OSInstaller 0x000000010b9eb3f1-[OSIMigrateElement runReturningError:] + 1450

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 8 com.apple.OSInstaller 0x000000010b9e08f9 __35-[OSInstallController startInstall] _block_invoke + 1612

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 9 libdispatch.dylib 0x000000011111593d _dispatch_call_block_and_release + 12

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 10 libdispatch.dylib 0x000000011110a40b _dispatch_client_callout + 8

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 11 libdispatch.dylib 0x000000011110e29b _dispatch_root_queue_drain + 1890

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 12 0x000000011110db00 _dispatch_worker_thread3 + 91 libdispatch.dylib

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 13 libsystem_pthread.dylib 0x00000001114bc4de _pthread_wqthread + 1129

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 14 libsystem_pthread.dylib 0x00000001114ba341 start_wqthread + 13

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: put 2: send queue: com.apple.libdispatch - Manager

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 0 libsystem_kernel.dylib 0x0000000111349efa kevent_qos + 10

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 1 libdispatch.dylib 0 0000000111110165 _dispatch_mgr_invoke + 216 x

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 2 libdispatch.dylib 0x000000011110fdcd _dispatch_mgr_thread + 52

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 3 wire:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 0 libsystem_kernel.dylib 0x000000011134910a __semwait_signal + 10

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 1 libsystem_c.dylib 0x000000011125cd17 nanosleep + 199

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 2 libsystem_c.dylib 0x000000011125cb77 sleep + 42

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 3 com.apple.IASUtilities 0x000000010bd805f8 do_log_watch + 43

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 4 libsystem_pthread.dylib 0x00000001114bc99d _pthread_body + 131

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 5 libsystem_pthread.dylib 0x00000001114bc91a _pthread_start + 168

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 6 libsystem_pthread.dylib 0x00000001114ba351 thread_start + 13

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: pull 4: com.apple.NSEventThread

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 0 libsystem_kernel.dylib 0x0000000111342f72 mach_msg_trap + 10

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 1 libsystem_kernel.dylib 0x00000001113423b3 mach_msg + 55

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 2 com.apple.CoreFoundation 0x000000010dd6d1c4 __CFRunLoopServiceMachPort + 212

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 3 com.apple.CoreFoundation 0x000000010dd6c68c __CFRunLoopRun + 1356

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 4 com.apple.CoreFoundation 0x000000010dd6bed8 CFRunLoopRunSpecific + 296

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 5 com.apple.AppKit 0x000000010c9ace99 _NSEventThread + 149

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 6 libsystem_pthread.dylib 0x00000001114bc99d _pthread_body + 131

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 7 libsystem_pthread.dylib 0x00000001114bc91a _pthread_start + 168

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 8 libsystem_pthread.dylib 0x00000001114ba351 thread_start + 13

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: put on 5: com.apple.NSURLConnectionLoader

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 0 libsystem_kernel.dylib 0x0000000111342f72 mach_msg_trap + 10

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 1 libsystem_kernel.dylib 0x00000001113423b3 mach_msg + 55

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 2 com.apple.CoreFoundation 0x000000010dd6d1c4 __CFRunLoopServiceMachPort + 212

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 3 com.apple.CoreFoundation 0x000000010dd6c68c __CFRunLoopRun + 1356

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 4 com.apple.CoreFoundation 0x000000010dd6bed8 CFRunLoopRunSpecific + 296

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 5 com.apple.CFNetwork 0x00000001105e2111 + [NSURLConnection (Loader) _resourceLoadLoop:] + 412

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 6 com.apple.Foundation 0x000000010bdffd64 __NSThread__start__ + 1351

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 7 libsystem_pthread.dylib 0x00000001114bc99d _pthread_body + 131

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 8 libsystem_pthread.dylib 0x00000001114bc91a _pthread_start + 168

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 9 libsystem_pthread.dylib 0x00000001114ba351 thread_start + 13

    28 Mar 15:41:18 MacBook-Pro ReportCrash [2620]:

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: put on 6: JavaScriptCore::Marking

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 0 libsystem_kernel.dylib 0x0000000111348db6 __psynch_cvwait + 10

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 1 libsystem_pthread.dylib 0x00000001114bd728 _pthread_cond_wait + 767

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 2 libc ++.1.dylib 0x0000000110f3a68f std::__1:condition_variable:wait(std::__1::unique_lock<std::__1::mutex>&) + 47

    28 Mar 15:41:18 MacBook - Pro ReportCrash [2620]: 3 com.apple.JavaScriptCore 0x000000010f82f5ab JSC::GCThread::waitForNextPhase() + 171

    28 Mar 15:41:18 - MacBookPro Rep

    Try a reboot.

    Make a backup using Time Machine or a cloning program, to ensure that data files can be recovered. Two backups are better than one.

    Try to set up another admin user account to see if the same problem persists. If back to my Mac is enabled in system preferences, the guest account will not work. The intention is to see if it is specific to an account or a system wide problem. This account can be deleted later.

    Isolate a problem by using a different user account

    If the problem is still there, try to start safe mode using your usual account.  Disconnect all devices except those necessary for the test. Shut down the computer and then put it up after a 10 second wait. Immediately after hearing the startup chime, hold down the SHIFT key and continue to hold it until the gray Apple icon and a progress bar appear. Startup is considerably slower than normal. This will reset some caches, forces a check for directory and disables all start-up and connection, among other things. When you restart normally, the initial restart may be slower than normal. If the system is operating normally, there may be 3rd party applications that pose a problem. Try to delete/disable the third-party applications after a reboot using the UN-Installer. For each disable/remove, you need to restart if you do them all at once.

    Safe mode

  • upgrade to el capitan, now error message at first upward...

    last night I clicked on free upgrade to el capitan on the itunes site... download for a long time, then when done... the system restarts and I get the following error message

    and it does not start... Please help...

    If you do not already have a current backup, please backup all data, and then reinstall the OS. * you don't need to erase the boot volume, and you won't need the backup unless something is wrong. If the system has been upgraded an earlier version of Mac OS X, you may need to the Apple ID and password to use.

    There are ways to back up a computer that is not fully functional. Ask if you need advice.

    If you installed the runtime Java distributed by Apple, and still need, you will need to reinstall it. It goes the same for Xcode. All other data will be preserved.

    Related support article refers to OS X 10.11 ("El Capitan"), but the procedure is the same for OS X 10.7 ("Lion") and later versions.

  • Upgrade to El Capitan has replaced the boot on Configuration partition dual boot

    I've been using find for a dual-boot my Macbook Pro with OSX and Ubuntu.  Today, I decided to upgrade my OSX Yosemite to El Capitan.

    After downloading all the 6G, which took about six hours, and the installation program, I received a prompt to restart my computer.  After that, and waiting more than 10 minutes staring at a blank screen, I pressed the power button, but nothing happened.  After doing this several times and get in trouble in the meantime, I pressed and held.  To my surprise the blank screen is having a background slightly shine completely black color.  Then, I realized that the computer was actually still on, and I interrupted probably something I shouldn't.

    Then I turned on my computer, and instead of being presented to the screen where I choose which operating system to load, I got OSX loading screen with the Apple logo and progress bar.  After some time, the OSX installer appeared and told me that it would take 19 minutes to install OSX.  However, after a minute and a half, the installer left with the message:

    OS X could not be installed on your computer

    A partition of start-up assistance is required when working with the storage of carrots.

    Exit Setup to restart your computer and try again.


    Product restarts the same result, as described above.

    Using the disk utility program, I see that I still have my Ubuntu partition, although not like OS X doesn't shows being available and has no information about it other than its size.

    As a customer, I am pretty upset by this situation.

    Why don't/that the installer should overwrite the MBR?  It's totally useless!  Why the installation program could not upgrade the OS that he treated and leave the rest alone computer?  If someone at Apple has not considered the possibility that some of their users will want to double to start their systems?

    Why are there not warnings or other information displayed during the preparation phase indicating that this would happen?  Why me staring at a screen empty while something, probably important, took place in the background and leading me to believe that my computer had hung up?  Surely a window could have been displayed saying something like "do not turn off your computer.

    Now that I have my setup porked, I need to recover from an old backup, get kind of rEFInd running again, back up my Ubuntu installation and probably delete the partition.  Then try to upgrade to El Capitan again after the download of an another 6G.  Once El Capitan is at work, I'll have to recreate the EXT4 partition and restore Ubuntu top and install rEFInd.  This seems to be an arrangement rather STUPID having to cross in 2016.

    Has anyone else had this problem?  If so, advice on how to get all this done effectively?

    New user account is not happy!


    Well, it seems that the recovery of my Time Machine backup is not so simple...

    In the setup of OS X, utilities disk is available, so I ran it.

    I've selected the partition where OS X is installed and choose the editing command-> restore from the menu, and then set the "restore from:' location to my partition backup (located on an external USB drive) and press ."

    This produces a message saying "restore process has failed. Press OK to continue.  (Continue where?)

    Open the details view showed me:

    Validation of targets...

    Validation of source...

    Could not unmount volume "/ Volumes/Image . (No end of quote)

    " Volume" (busy resource) (Who's using it?  (Not me!)

    Operation failed...


    I installed the following devices:

    SM0512F SSD APPLE (disk0)

    MyOSX (disc 1)

    HGST (disk4) external drive

    OSX_Backup (disk4s2)

    Apple Media (DIS3) disk image

    System basis of OS x (disk3s1)

    Apple Media disk image (2)

    OS X install ESD (disk2s2)

    What volumes cannot be disassembled?  Apple media disk image?  Why?  What these volumes As make me writing disk4s2 to disk1?

    I'll try to disassemble the Terminal and see if disk utility can help you.


  • Upgrade to El Capitan and migration of opening

    I've been a user for a long time to open and I plan to spend my photos from opening in the Photos.  At the present time, I always use the opening running Yosemiti and although I read several accounts that works fine opening under El Capitan, I know at some point I need to migrate to another photo manager.  It would be better to upgrade to El Capitan before migrating my Libarary opening, or should I migrate the Aperture library, and then move on to El Capitan?  Any advice would be greatly appreciated.

    Ed

    I'd wait until after the upgrade to El Capitan. Several bug fixes of Photos have been for Yosemite, migration should be smoother on El Capitan.

    I would repair the Aperture library prior to migration to ensure that there are no glitches.

    http://documentation.Apple.com/en/aperture/UserManual/index.html#Chapter=27%26se ction = 10% 26tasks = true

    This trick of user like some advice on what should be taken into account when migrating from an Aperture library: Notes on the migration of an Aperture of Aperture for photo for Mac library

  • Upgrade to el capitan is the way course?

    MY last update to yosemite was a total puzzle. I lost my bootcamp partition and was able to recover with the help of solitaire. Im a little hesitant to upgrade to el capitan, I really want to repeat the same steps. Is it possible to make sure I update in a safe way? Thanks for any advice.

    If we did the recovery correctly and properly, you should have no problem with the upgrade. I still recommend a good backup of OS X and Windows (separate readers) if possible. Also, please create a Windows system restore point.

    If you do not really need features to El Capitan, I'd say staying on Yosemite, if it is stable and functional.

  • When the Mac OS upgrade to el Capitan, CS5 can be reinstalled?

    Hello

    My Mac OS is outdated, and I'm looking into upgrading to El Capitan. Adobe CS5 will disappear? Will I need to re - install CS5? If so, I hear CS5 has problems with installation on El Capitan, but can it be fixed?

    I don't want to move for fear of losing the CS5, but seeks advice if possible.

    Thank you very much for your answers.

    CS6 and previous programs have not been tested and will not be updated to run on Mac El Capitan

    -which means you are trying to use CS6 and earlier at YOUR risk of having problems

    -You can get CS6 and previous programs to install and run, or you can not (some do, some don't)

    -Java https://helpx.adobe.com/dreamweaver/kb/dreamweaver-java-se-6-runtime.html can help

    Install CS5 on Mac 10.11 https://forums.adobe.com/thread/2003455 can help (also for others than CS5)

    -also a TEMPORARY security change https://forums.adobe.com/thread/2039319

    -http://mac-how-to.wonderhowto.com/how-to/open-third-party-apps-from-unidentified-developer s-mac-os-x-0158095 /

    -the guardian https://support.apple.com/en-au/HT202491

  • Benefits of upgrading to El Capitan

    Hello

    I'm looking for some advice on upgrading my Mac OS.  Currently I am running OS X Yosemite 10.10.5.  Is there an advantage to using Adobe CC, for the upgrade of OS X El Capitan?  I'm not so concerned about the spotlight and other improvements. I have heard a lot about improvements in speed and performance and wonder if those who apply after Adobe CC.

    Here are my system specs.

    MacPro (mid-2010)

    2x2.66 GHz 6-core Intel Xeon

    64 GB 1333 MHz DDR3 ECC

    Graphics card: ATI Radeon HD 5770 1024 mb

    all the tips, pro or con, would be greatly appreciated.

    Thank you

    Joey

    Please see the document: Mac OS X El Capitan (10.11) Compatibility FAQ | CC

    Concerning

    Stéphane

  • Upgrade to El Capitan in Yosemite

    I have a fairly new MacBook Pro running Yosemite. I was going to upgrade to El Capitan, but now he me Sierra offers instead. I don't want to do because of the risk that £500 dollars worth of software (File Maker Pro 11, final draft 8, Office 2011) will stop working.

    My office is running El Cap, and applications above all work fine.

    In my view, there is the ease of upgrade to El Cap, but he seems to be reserved for people running older versions. Do you think I can upgrade using this path? Or everything will go horribly wrong?

    Thank you

    Have you tried these steps: update of OS X El Capitan - Apple Support

    There is a link on this site in order to download the installer from El Capitan of App store.

  • I am running Yosemite. Should I upgrade to El Capitan before moving on to the Sierra?

    I am running Yosemite. Should I upgrade to El Capitan before moving on to the Sierra?

    No you do not.  Lion 10.7.5 or higher, you're in the clear.

    MacOS Sierra - technical specifications

  • I've been upgraded to El Capitan and electricity went off and stopped the session.  I don't have time to continue for 12 hours.  It is the CV.  How can I cancel until I have more time?

    I've been upgraded to El Capitan and electricity went off and stopped the session.  I don't have time to continue for 12 hours.  It is the CV.  How can I cancel until I have more time?

    Hello nancy milano,.

    Thanks for this info and choosing the communities Support from Apple. I know how important is able to complete your update to El Capitan at a later date! The good news is that you can simply delete the "install Mac OS X" install app in the Applications folder on your Mac. Then you can open the Mac App Store when you're ready to update and restart the download from the tab updates or searching through the Mac App Store for El Capitan. This is a resource that explains the process of update more:

    Update of OS X El Capitan

    See you soon!

  • MacBook Pro has started to randomly stop when it is on battery since the upgrade to El Capitan

    I have a MacBook Pro (15 inch, early 2011) which works very well on the Mountain Lion for a long time. I finally got round to upgrading to El Capitan last week: directly to 10.11.6. A few days later he just powered down without warning while I was working. He was so very well for a few days, but then made several times in the last 48 hours.

    I am moderately sure it happens only when it is on battery (it did not in the past hours 8 while that plugged). Whenever it happens, that there is no warning and the Mac then fine restarts (manually) - Although the clock resets always in 1970 until he can contact an NTP server. One of the curious side effects is that my PostScript fonts were blank on the screen in Excel for a few reboots yesterday but then OK once again!

    No hardware has changed. Major software change is only El Capitan and possibly an iStat Menus update.

    I have reset PRAM and SMC. I ran the short AHT. I disassembled the machine and clean the fans. they were OK, but the problem seems to occur when the Mac is hot.

    Spotlight and Time Machine sometimes seemed to be struggling for the upgrade, and I also saw rpcsvchost with 100% of a core for a while. The machine feels sometimes slow - but for the last 8 hours, it was very good. The only model that I put in place, is that it seems to occur only on battery; It's even happened then that the Dock (etc.) were loading after logging in after an unexpected shutdown.

    The other thing common is in the newspapers every time:

    Cause of previous stop:-128

    I scanned a number of related posts to aspects of it, but do not look at who blames El Capitan rather than material. Yet, many people reported this kind of problem after the upgrade... Coincidence?

    Any ideas?

    Thank you.

    Cause of previous stop:-128

    A negative stop code generally indicates a hardware failure. Have the Apple to assess your Mac. The fix may be as simple as a spare battery.

    Start here: contact support

  • After that upgrade to El Capitan about this Mac does not work"

    After the upgrade to El Capitan by clicking on about this Mac, nothing happens and by double clicking on System profiler I get the error message from the Application "System information" cannot be opened.  I ran disk utility, tried in safe mode and as a guest and all user are the same.

    It is a late 2008 MacBook.  It's on 10.5.8.  I did a clean install of 10.6.3 with upgrades to 10.6.8 to give birth to El Capitan.  According to me, that he was working at that time.  Then, I migrated the user of a backup image of the 10.5.8 account. Who could have when it stopped, but I'm not sure.

    I had two newspapers @ pastbin.com/Mca6LS4H

    Hello mrtrytofixit,

    Thank you for reaching out to the Community Support from Apple. I know how it is important to be able to rely on public services provides your Mac and I want to help you get things working again. With troubleshooting, you have already done, it seems that it is a systemic problem.

    From there, what I recommend is reinstall OS X El Capitan using OS X Recovery on your Mac. It should not remove or erasure of your data, but it is recommended that you make backup before you do incase of an emergency.

    These articles will guide you through the backup and reinstallation:
    Use Time Machine to back up or restore your Mac
    How to reinstall OS X

    If you have any questions or concerns, inform the community. We are all here to help.
    Best regards.

  • Printing problems since upgrading to El Capitan

    Two weeks ago, that I've upgraded to El Capitan. Since then I was able to print from Adobe Acrobat or Microsoft Office programs. I use my Macbook for business purposes, and there is downtime with my work on this issue. This has nothing to do with printer drivers that I can't print to PDF either.

    I've used nothing helps Apple telephone support. I went to an Apple genius bar and they could not understand either. They have wiped my phone, and then I went home and restored the time upward from the standby machine. The problem was still there. So I uninstalled Microsoft office (last resort recommended by technician at the genius bar) and reinstalled. The problem is still there, and worse yet the Outlook is freezing. I rang a repairer of random computer company this morning specializing in Macs. They said they couldn't help me because they would only do what I've done. My Macbook Pro is just a few years, and now I'm looking down the barrel of the purchase of a new laptop - all because I upgraded to El Capitan!

    Troubleshoot printer on your Mac - Apple Support

    cant - print.html http://www.Macworld.com/article/2029528/Mac-Troubleshooting-What-to-do-When-You-

  • My MacBook Pro (late2009) stalled for 2 days now trying to upgrade to El Capitan. It neither improved nor returned to Yosemite. Help, please.

    I have macbook pro late 2009. I started to upgrade to El Capitan 2 days ago. Downloaded, it stalled during installation. It has frozen about 95% installation and remained so for 2 days. Help, please.

    Try to Safe Mode Setup:

    https://support.Apple.com/en-us/HT201262

    Start safe mode and see if the problem persists:

    Restart now ' shift '.

    (Wait to take more time to start in this way because it runs a check of directory first. Also give it some time after the start because he runs maintenance routines at the beginning.)

Maybe you are looking for