
- MAC MIGRATION ASSISTANT LOOKING FOR INCOMPATIBLE SOFTWARE TAKES A LONG TIME INSTALL
- MAC MIGRATION ASSISTANT LOOKING FOR INCOMPATIBLE SOFTWARE TAKES A LONG TIME UPDATE
- MAC MIGRATION ASSISTANT LOOKING FOR INCOMPATIBLE SOFTWARE TAKES A LONG TIME MANUAL
- MAC MIGRATION ASSISTANT LOOKING FOR INCOMPATIBLE SOFTWARE TAKES A LONG TIME PRO
- MAC MIGRATION ASSISTANT LOOKING FOR INCOMPATIBLE SOFTWARE TAKES A LONG TIME FREE
This seemed to be meaningful, but was ultimately a wild goose chase. I was unable to boot into Single User Mode ( Cmd+S+Pwr), but it and Verbose Mode ( Cmd+V+Pwr) did show that the boot process was hanging and the last message it displayed was: pci pause: SDXC I reset the SMC ( Shft+Ctrl+Opt+Pwr while off, then Pwr), I reset the PRAM ( Cmd+Opt+P+R+Pwr while booting, then hold until the chime sounds again), I tried to boot into Safe Mode ( Shft+Pwr).
MAC MIGRATION ASSISTANT LOOKING FOR INCOMPATIBLE SOFTWARE TAKES A LONG TIME PRO
Thus when I was notified that it was available, I dutifully upgraded… and then my MacBook Pro Retina wouldn’t reboot.
MAC MIGRATION ASSISTANT LOOKING FOR INCOMPATIBLE SOFTWARE TAKES A LONG TIME UPDATE
After Update, OS X Won’t RebootĪfter upgrading to OS X El Capitan (10.11) when it was released, I had been generally pleased with the new version but there were a few quirks – like random beach ball pauses – that made me think the 10.11.1 update would address some of them. It seems to have left behind a kext named .kext and once I deleted it, things work again. Before I knew this I installed Malwarebytes to check for spyware/adware causing the CPU usage, then uninstalled it after installing the OS X beta. I am using the Beta version because 10.13.2 had very high CPU usage by the WindowServer process that was fixed in 10.13.3. Update – I updated to 10.13.3 High Sierra Beta 5 and once again was unable to boot. Removed everything older than 2016 after running ls -lat. This time I had to remove kexts from /System/Library/Extensions. Update – I updated to 10.12.6 and once again was unable to boot.

Update – This has been an issue for myself and others running OS X Sierra as well. Update – It happened again when I updated to 10.11.4! Even fewer clues this time, additional details and an updated script to remove non-default kext files at the very bottom.

MAC MIGRATION ASSISTANT LOOKING FOR INCOMPATIBLE SOFTWARE TAKES A LONG TIME FREE
Otherwise feel free to read the saga below! :-) And as a reminder of which software I will need on the new machine, I set the finder label "green" to all applications I will need on my new machine.If your OS X El Capitan/Sierra/High Sierra update won’t reboot you can skip to the fix or check here for the (mostly) automated fix script. When mounting the harddiscs, I immediately see what is important and needs to be copied. I even go a step further - On my old MacPro I set all files and directories I want to copy on a red label in the finder. Positive effect of this: you trashed all old things you really do not need. You will definitely miss important files.
MAC MIGRATION ASSISTANT LOOKING FOR INCOMPATIBLE SOFTWARE TAKES A LONG TIME INSTALL
MAC MIGRATION ASSISTANT LOOKING FOR INCOMPATIBLE SOFTWARE TAKES A LONG TIME MANUAL
Not a single file appears on "Macintosh HD" on the new Mac.Īny ideas? Apple can't help me in the store until Monday, so I thought I'd ask here.Īlso not really an answer but more a practical approach.Īnother idea that requires manual work. Here's where it gets really, really bizarre: I can't find any sign of the files transferred on the new Mac after I've stopped it. I've looked on the system drive for a log, but I haven't found one. There's something in the backup or my applications setup that's causing the migration to get stuck in a loop. That being said, this is a refurb, it's possible something is wrong that only affects the new machine during long transfers. I've already run the hardware diagnostics, but nothing shows up. I've tried it 4 times since then (including a complete system reinstall), and the same thing happens every time. By morning it was saying there would be over 250 hours to completion. All the while, the completion time (which was "about a minute" starts creeping up.) The first time I let it run all night. At first, the screen shows "Transferring Applications"/"Transferring files to support applications" pretty fast. I've tried transferring over a direct-connected Ethernet from Mac-to-Mac, as well as a brand new Time Machine backup to an external SSD connected via a Thunderbolt 1 breakout box.Įvery time I try to transfer, the transfer makes it to the applications stage in a reasonable amount of time. The amount of information being transferred is about 120Gb.

I am trying to transfer my existing (Early 2008) Mac Pro to a new (refurb) 2013 Mac Pro.
