Simply use BootChamp (Free) to bounce back and forth between Win 10 and macOS HS. It works perfect for me. Have you tried it?
Last edited:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Slow boot
- Thread starter darkweather
- Start date
- Sort by reaction score
Simply use BootChamp (Free) to bounce back and forth between Win 10 and macOS HS. It works perfect for me. Have you tried it?
Yes, I am using this method at this moment. It work flawlessly. Just a bit annoying when perform Windows update (require restart, but reboot back to MacOS by default).
The following process give my back a startup time of 17 sec. from 1:20 sec. with the same software setup:
- Copy MacOS with Carbon Copy Cloner to external HD with HFS
- Delete APFS containers and filesystem compledly
- Reformat internal SSD with HFS
- Restore MacOS with Carbon Copy Cloner
- Active File Vault 2
- Convert Filessystem from HFS to APFS
My 2011 was having issues, as they all have, and I wanted a 2015 so I bought one. The build date is from June 2017 and it had Sierra on it. Sticking with MacOS Sierra for now. Until I see an update fixing this, I'm not going to bother with High Sierra.
fwiw, 23 secs boot without my external HDs, on Sierra, from chime to desktop (automatic login on). It's gonna take some real improvements before I try HS again...
What gets me is that I have two late 2016's Pro's, purchased at the same time, but one has just the Intel Graphics and the other has Radeon Pro 460 4 GB + Intel HD Graphics 530 1536 MB
For these not to boot the same is totally messed to say the least. I would hate to think the graphics driver could be the cause...but ????? I do have an issue with the graphics for sometime I get a stuck image in RAM that is only cleared by a reboot. Does not move or anything, just stays.
Is there a way to disable the Radeon Pro 460 so the drivers do not load and see if that is doing it? You never know these days.
For these not to boot the same is totally messed to say the least. I would hate to think the graphics driver could be the cause...but ????? I do have an issue with the graphics for sometime I get a stuck image in RAM that is only cleared by a reboot. Does not move or anything, just stays.
Is there a way to disable the Radeon Pro 460 so the drivers do not load and see if that is doing it? You never know these days.
Attachments
Since 10.3.2 the slow boot is even slower than 10.3.1, but there is no black screen at a moment. The moment where the boot becomes slow lets me think that the graphic card could be concerned.
There is an Nvidia update for Geforce graphic Cards, released at 1st december. I did not try yet, but I wonder if it could help to get a faster boot process. I did not try because it is still in beta support for my machine, and also I don't like to update this kind of drivers as for a common PC, I prefer the driver update to be done by Apple with a new release of macOS.
There is an Nvidia update for Geforce graphic Cards, released at 1st december. I did not try yet, but I wonder if it could help to get a faster boot process. I did not try because it is still in beta support for my machine, and also I don't like to update this kind of drivers as for a common PC, I prefer the driver update to be done by Apple with a new release of macOS.
Yes, startup process 2/3 then pause, black screen 1 - 2 seconds then continue boot up process is no longer on iMac circa 2012 with 10.13.2. Now takes iMac about 45 seconds to boot (Rotational HD). 12' Retina MacBook 2016 all SSD 10.13.2 takes about 25 - 27 seconds to boot.
As for using Beta Nvidia drivers or web-drivers - - Apple is a very closed Ecosystem and run risk of issues
As for using Beta Nvidia drivers or web-drivers - - Apple is a very closed Ecosystem and run risk of issues
Since I am running a GTX1080Ti, Nvidia web driver is a must for me. And I can tell, this has nothing to do with the slow boot in my case. The single most important factor is definitely the trimforce status. As long as I set trimforce to disable, my boot time is fast, all HDD will mount properly, and no Finder micro freeze.
Hey...Was not saying it was the video driver, was just saying what I had seen and thought I would mention it just in case.
So this morning I got the notice of 10.13.2 being out, I took the update and it totally trashed my MacBook Pro (Later 2016) It would boot, get to the login screen and if I did not touch it, 48 seconds later it would crash out to the black screen saying it crashed out and rebooted. Same thing over and over even if I logged it, at about 48 seconds, BAM reboot.
I reset both SMC and NVRAM with no change. I rebooted in safe mode and it would run and was able to look at the crash log, the last thing to load, funny enough, was something for video. Which I find strange as video drivers must have been loaded to see login.
I then tried to recover re-install over the top. Same result. Reboot in 48 seconds.
So I booted into recover again and erased the drive and then did another reinstall.
When it gave me the option to migrate over my files, I did so from my Time Machine backup and I am back and running on ver 10.13.2. I spent about 6 hours on this issue from taking the update to getting back running again. The BIG time saver for me is I have a USB-C 1TB SSD drive connected that also had my backup on it. As such, restoring went very quick when the time came to do that part. The slow part was needing to download the OS each time. (I wish they had it stored on another partition and checked the version you have before downloading and thus only download if needed.)
The Good News...After all of this my MacBook Pro is back to full speed even with a 20 second boot! However, what a scary time it was trying to get back running after taking the 10.13.2 update.
So this morning I got the notice of 10.13.2 being out, I took the update and it totally trashed my MacBook Pro (Later 2016) It would boot, get to the login screen and if I did not touch it, 48 seconds later it would crash out to the black screen saying it crashed out and rebooted. Same thing over and over even if I logged it, at about 48 seconds, BAM reboot.
I reset both SMC and NVRAM with no change. I rebooted in safe mode and it would run and was able to look at the crash log, the last thing to load, funny enough, was something for video. Which I find strange as video drivers must have been loaded to see login.
I then tried to recover re-install over the top. Same result. Reboot in 48 seconds.
So I booted into recover again and erased the drive and then did another reinstall.
When it gave me the option to migrate over my files, I did so from my Time Machine backup and I am back and running on ver 10.13.2. I spent about 6 hours on this issue from taking the update to getting back running again. The BIG time saver for me is I have a USB-C 1TB SSD drive connected that also had my backup on it. As such, restoring went very quick when the time came to do that part. The slow part was needing to download the OS each time. (I wish they had it stored on another partition and checked the version you have before downloading and thus only download if needed.)
The Good News...After all of this my MacBook Pro is back to full speed even with a 20 second boot! However, what a scary time it was trying to get back running after taking the 10.13.2 update.
I'm having the same slow boot in MBP Early 2013 with Apple original SSD.
My MBP takes 50' to boot. 20-30 seconds more than before.
I've filled a bug to Apple. I hope they fix it soon!
I'm using the latest beta version and the problem persists 10.13.3 Beta (17D34a)
My MBP takes 50' to boot. 20-30 seconds more than before.
I've filled a bug to Apple. I hope they fix it soon!
I'm using the latest beta version and the problem persists 10.13.3 Beta (17D34a)
I wish there was some clear-cut explanation for this thing, so far I've seen vague reports about some checks/verification being done during the boot phase. So far, we kinda know it's related to TRIM because some of us, including me, made some quick and rough tests (which led me to roll back to Sierra!) - but some Macs are not affected, why? Is it something we're going to have to live with from now on? Is it something that needs fixing? Is it a bug? The software I use the most, Pro Tools, is now compatible High Sierra, but for now I'm not interested.
High Sierra is now 4 month old and nothing suggests this issue will be addressed anytime soon. Also apps take a little longer to launch in HS, why? In short HS is slower than Sierra whereas it's supposed to be an, um, "elevated" experience over the previous OS...
That's a lot of questions but some answers wouldn't hurt...
High Sierra is now 4 month old and nothing suggests this issue will be addressed anytime soon. Also apps take a little longer to launch in HS, why? In short HS is slower than Sierra whereas it's supposed to be an, um, "elevated" experience over the previous OS...
That's a lot of questions but some answers wouldn't hurt...
They don't care because the problem affects only non Apple SSDs.
Personally I stay away from APFS and don't have the problem.
They don't care because the problem affects only non Apple SSDs.
My Macs with Apple SSDs are affected. Boot times are easily twice as long as Sierra.
They don't care because the problem affects only non Apple SSDs.
Personally I stay away from APFS and don't have the problem.
AFAIK, it's not 3rd SSD's issue, but APFS and TRIM together may cause the Mac stuck at this position during boot for a few seconds (up to something like 2min).
This screen capture from a Early 2013 MacBook Pro with the factory Apple SSD.
Mac Pro (Late 2013) ME253B/A
I have had this issue immediately after upgrading to macOS High Sierra from macOS Sierra 10.12.6. Startup time has become much longer than usual and I am now experiencing some graphical issues also. The SSD in my Mac Pro is the stock factory Apple SSD.
Another MacRumors member by the name of shirogane suggested trying the following method to fix the slow startup times...
1. Open System Preferences > Startup Disk
2. Unlock the preference lock and enter admin password
3. Click and highlight Macintosh HD as the startup disk
4. Click and lock system preferences and close it
5. Reboot and it should be back to macOS Sierra boot speeds again!
This has worked for me however the issue always comes back when updating macOS High Sierra.
I have had this issue immediately after upgrading to macOS High Sierra from macOS Sierra 10.12.6. Startup time has become much longer than usual and I am now experiencing some graphical issues also. The SSD in my Mac Pro is the stock factory Apple SSD.
Another MacRumors member by the name of shirogane suggested trying the following method to fix the slow startup times...
1. Open System Preferences > Startup Disk
2. Unlock the preference lock and enter admin password
3. Click and highlight Macintosh HD as the startup disk
4. Click and lock system preferences and close it
5. Reboot and it should be back to macOS Sierra boot speeds again!
This has worked for me however the issue always comes back when updating macOS High Sierra.
I finally move back to HFS+, and I am very happy with the result.
I have a daily bootable CCC clone of my primary boot drive. So I boot to the clone, format the SSD back to HFS+, and clone everything back.
The result is good, no more slow boot, TRIM is working properly, no Finder micro freeze (so far), I can easily go back to macOS in Bootcamp Windows, and the system can always report correct space available now.
I tried APFS since 10.13.0, doesn't really like it. And can't see much benefit for far. So, most likely I will stay at HFS+ until Apple force to "upgrade".
I have a daily bootable CCC clone of my primary boot drive. So I boot to the clone, format the SSD back to HFS+, and clone everything back.
The result is good, no more slow boot, TRIM is working properly, no Finder micro freeze (so far), I can easily go back to macOS in Bootcamp Windows, and the system can always report correct space available now.
I tried APFS since 10.13.0, doesn't really like it. And can't see much benefit for far. So, most likely I will stay at HFS+ until Apple force to "upgrade".