Hi there everyone,
I've been a Mac user for 14 years but somehow this is the first time I've posted here, though I've been aware of the site for many years. I'm having a boot issue - I'll try to be detailed:
I have a Late 2014 Mac Mini mid-level model (2.6 GHz Core i5, 8GB RAM, Intel Iris graphics). Internal storage is a 500GB Samsung EVO 850 SSD installed about 2 years ago. I'm running macOS Sierra 10.12.5, and Windows 10 Pro x64 v1607 via Bootcamp.
It's been a while since I've had any Bootcamp problems, and I only use Windows once or twice a week. Suddenly, Windows is no longer listed when I hold down option for the boot selection menu. I usually restart into Windows directly using a utility called BootChamp. It is no longer in development because of the introduction of System Integrity Protection in El Capitan, but if you disable SIP, it works fine. I'd lived just fine without SIP since Panther, so it's never been an issue.
I initially restarted with the utility and ran into an error message in a DOS-typical font saying that there is no boot disk, insert one and press any key to continue. That's when I tried the normal option-key boot menu method and discovered Windows was missing.
Paragon NTFS for Mac 15 mounts my BOOTCAMP partition just fine anytime I log into macOS. One thing I did notice is that the Paragon menu icon, which used to refer to Windows as UEFI, now reports it as Legacy.
Already Tried:
1) "Correct Bootcamp Boot Record" in Paragon Hard Disk Manager - completes no problem.
2) "Correct Bootcamp BCD Files" in Paragon Hard Disk Manager - completes no problem.
3) Disk Utility First Aid in Recovery Mode on the macOS partition - completes no problem. (Can't run first aid on the NTFS partition, of course.)
4) Disk Utility First Aid in Recovery Mode on the Samsung SSD volume as a whole - reports problems related to booting, and says that I need to run First Aid in Recovery Mode (which is exactly what I'm doing.... thanks for your excellent programming, Apple.)
5) Checked the partition table using GPT Fdisk - everything looks as it normally would. (I always have gdisk installed.)
I don't know if it's relevant, but a few weeks ago I gave up on installing the Win10 Creators Update (v1703) because it kept failing at 32%. I did have all Windows Updates installed for v1607 last time I used it a week or so ago, as well as Bitdefender.
Files on the NTFS drive are still accessible.
Any ideas?
Alex
I've been a Mac user for 14 years but somehow this is the first time I've posted here, though I've been aware of the site for many years. I'm having a boot issue - I'll try to be detailed:
I have a Late 2014 Mac Mini mid-level model (2.6 GHz Core i5, 8GB RAM, Intel Iris graphics). Internal storage is a 500GB Samsung EVO 850 SSD installed about 2 years ago. I'm running macOS Sierra 10.12.5, and Windows 10 Pro x64 v1607 via Bootcamp.
It's been a while since I've had any Bootcamp problems, and I only use Windows once or twice a week. Suddenly, Windows is no longer listed when I hold down option for the boot selection menu. I usually restart into Windows directly using a utility called BootChamp. It is no longer in development because of the introduction of System Integrity Protection in El Capitan, but if you disable SIP, it works fine. I'd lived just fine without SIP since Panther, so it's never been an issue.
I initially restarted with the utility and ran into an error message in a DOS-typical font saying that there is no boot disk, insert one and press any key to continue. That's when I tried the normal option-key boot menu method and discovered Windows was missing.
Paragon NTFS for Mac 15 mounts my BOOTCAMP partition just fine anytime I log into macOS. One thing I did notice is that the Paragon menu icon, which used to refer to Windows as UEFI, now reports it as Legacy.
Already Tried:
1) "Correct Bootcamp Boot Record" in Paragon Hard Disk Manager - completes no problem.
2) "Correct Bootcamp BCD Files" in Paragon Hard Disk Manager - completes no problem.
3) Disk Utility First Aid in Recovery Mode on the macOS partition - completes no problem. (Can't run first aid on the NTFS partition, of course.)
4) Disk Utility First Aid in Recovery Mode on the Samsung SSD volume as a whole - reports problems related to booting, and says that I need to run First Aid in Recovery Mode (which is exactly what I'm doing.... thanks for your excellent programming, Apple.)
5) Checked the partition table using GPT Fdisk - everything looks as it normally would. (I always have gdisk installed.)
I don't know if it's relevant, but a few weeks ago I gave up on installing the Win10 Creators Update (v1703) because it kept failing at 32%. I did have all Windows Updates installed for v1607 last time I used it a week or so ago, as well as Bitdefender.
Files on the NTFS drive are still accessible.
Any ideas?
Alex