F5F Stay Refreshed Software Operating Systems Mac cannot start Windows 10 properly due to compatibility issues.

Mac cannot start Windows 10 properly due to compatibility issues.

Mac cannot start Windows 10 properly due to compatibility issues.

F
fedebizzi
Junior Member
43
07-19-2016, 01:25 AM
#1
I recently acquired an OWC drive (2TB) to swap in for the 500GB drive on my MacBookPro11.5. It came with a case to house the previous drive, so I did that. When trying to boot Windows from it, the process failed (the same problem now). I suspect the attempt to boot from the external enclosure caused damage, as cloning the old drive to the new one with dd didn’t resolve the issue. The drive still worked when the original was still in use, but after removal, it remained unresponsive. Now it appears in the boot menu (chime option). During startup it displays the Windows logo and loading spinner, yet it abruptly shuts down and restarts. On subsequent launches, automatic repair attempts fail to detect any issues. I don’t believe automatic repair has ever succeeded. Windows won’t: keep showing a loading screen indefinitely, display a black screen, or trigger any error messages.

I suspect the NTFS partition remains intact (as seen in macOS), likely because dd was used instead of inferior cloning tools. Currently, I’m booted into macOS from the new drive and it’s operating perfectly as intended. If necessary, I saved a snapshot of the Apple SSD using Clonezilla to my server before attempting any changes, so I could revert if needed. However, cloning the SSD to another third-party device is only possible via the MacBook itself, since the provided enclosure doesn’t support it.

This situation is frustrating because Windows can’t handle NTFS partitions well enough for resizing or moving them. I learned this the hard way when trying to adjust the Windows partition with Disk Utility. I’m looking for more practical Windows troubleshooting advice—anyone have tips? (Sorry, no good answers here)
F
fedebizzi
07-19-2016, 01:25 AM #1

I recently acquired an OWC drive (2TB) to swap in for the 500GB drive on my MacBookPro11.5. It came with a case to house the previous drive, so I did that. When trying to boot Windows from it, the process failed (the same problem now). I suspect the attempt to boot from the external enclosure caused damage, as cloning the old drive to the new one with dd didn’t resolve the issue. The drive still worked when the original was still in use, but after removal, it remained unresponsive. Now it appears in the boot menu (chime option). During startup it displays the Windows logo and loading spinner, yet it abruptly shuts down and restarts. On subsequent launches, automatic repair attempts fail to detect any issues. I don’t believe automatic repair has ever succeeded. Windows won’t: keep showing a loading screen indefinitely, display a black screen, or trigger any error messages.

I suspect the NTFS partition remains intact (as seen in macOS), likely because dd was used instead of inferior cloning tools. Currently, I’m booted into macOS from the new drive and it’s operating perfectly as intended. If necessary, I saved a snapshot of the Apple SSD using Clonezilla to my server before attempting any changes, so I could revert if needed. However, cloning the SSD to another third-party device is only possible via the MacBook itself, since the provided enclosure doesn’t support it.

This situation is frustrating because Windows can’t handle NTFS partitions well enough for resizing or moving them. I learned this the hard way when trying to adjust the Windows partition with Disk Utility. I’m looking for more practical Windows troubleshooting advice—anyone have tips? (Sorry, no good answers here)

P
PitufoGreen
Member
109
07-27-2016, 03:25 AM
#2
It seems the system isn’t fully starting as expected. No typical error messages appear. I’m unsure if it actually launches into Windows or if it stops mid-process. It might be running slowly with some issues. This could be unusual for me.
P
PitufoGreen
07-27-2016, 03:25 AM #2

It seems the system isn’t fully starting as expected. No typical error messages appear. I’m unsure if it actually launches into Windows or if it stops mid-process. It might be running slowly with some issues. This could be unusual for me.

Y
Yokijirou
Member
134
07-27-2016, 08:23 AM
#3
I chose Windows from the boot options. The screen displays the boot menu with the Windows icon and loading indicator. After a short time, it abruptly restarts. When I attempt to launch it again, the automatic diagnostic routine begins: (image credit: TenForums) The repair process fails to identify any issues, and the cycle restarts if you try to boot once more.
Y
Yokijirou
07-27-2016, 08:23 AM #3

I chose Windows from the boot options. The screen displays the boot menu with the Windows icon and loading indicator. After a short time, it abruptly restarts. When I attempt to launch it again, the automatic diagnostic routine begins: (image credit: TenForums) The repair process fails to identify any issues, and the cycle restarts if you try to boot once more.

P
PuddingPop
Junior Member
10
07-27-2016, 10:10 AM
#4
Interesting. It seems the boots are working, but the loading windows aren't opening properly.
P
PuddingPop
07-27-2016, 10:10 AM #4

Interesting. It seems the boots are working, but the loading windows aren't opening properly.

K
Kynedee
Posting Freak
784
07-27-2016, 11:25 AM
#5
K
Kynedee
07-27-2016, 11:25 AM #5

J
JELLY33
Member
180
07-28-2016, 06:15 PM
#6
Checking for boot in safe mode helps identify issues. Success indicates a fault in something safe mode disables, failure suggests it doesn't disable certain parts. It narrows down potential problems.
J
JELLY33
07-28-2016, 06:15 PM #6

Checking for boot in safe mode helps identify issues. Success indicates a fault in something safe mode disables, failure suggests it doesn't disable certain parts. It narrows down potential problems.

B
bishopboys68
Posting Freak
899
08-10-2016, 02:23 AM
#7
wrong. you can boot Linux on that Mac and resize etc. there is a chance this will corrupt it though because Microsoft is stupid and resizing it while not booted into Windows can cause issues so I'd recommend backing the files etc up somewhere else first. regardless that Windows install seems borked and I'd recommend for you to just reinstall it using BootCamp.
B
bishopboys68
08-10-2016, 02:23 AM #7

wrong. you can boot Linux on that Mac and resize etc. there is a chance this will corrupt it though because Microsoft is stupid and resizing it while not booted into Windows can cause issues so I'd recommend backing the files etc up somewhere else first. regardless that Windows install seems borked and I'd recommend for you to just reinstall it using BootCamp.

P
Papyrule
Senior Member
560
08-10-2016, 10:39 AM
#8
Sure, I can help with that. Look for a distro that supports NTFS partitions and has good compatibility with your system. Since you're set on having Windows available, consider trying a lightweight version like Ubuntu or Linux Mint, which often handle NTFS well. Safe Mode booting might also resolve the issue without a full reinstall.
P
Papyrule
08-10-2016, 10:39 AM #8

Sure, I can help with that. Look for a distro that supports NTFS partitions and has good compatibility with your system. Since you're set on having Windows available, consider trying a lightweight version like Ubuntu or Linux Mint, which often handle NTFS well. Safe Mode booting might also resolve the issue without a full reinstall.

F
60
08-10-2016, 03:13 PM
#9
I haven't tested Linux on a 2015 MBP before, only on older models like 2011 and 2012. In theory, the steps are similar. I suggest using Ubuntu because it comes with GParted pre-installed. You can flash it to a USB drive using an app such as Etcher or DD, then restart your Mac, hold down the Option key, and it should appear as EFI Boot. Once booted, open a terminal and type: sudo gparted. Select the built-in SSD in the top right and resize the partition if needed. This process can be tricky. My usual recommendation is to go with Windows 10 since troubleshooting it has become difficult—they removed many helpful features like easy access to safe mode. If it fails, you can simply wipe it and reinstall.
F
FairyKingSloth
08-10-2016, 03:13 PM #9

I haven't tested Linux on a 2015 MBP before, only on older models like 2011 and 2012. In theory, the steps are similar. I suggest using Ubuntu because it comes with GParted pre-installed. You can flash it to a USB drive using an app such as Etcher or DD, then restart your Mac, hold down the Option key, and it should appear as EFI Boot. Once booted, open a terminal and type: sudo gparted. Select the built-in SSD in the top right and resize the partition if needed. This process can be tricky. My usual recommendation is to go with Windows 10 since troubleshooting it has become difficult—they removed many helpful features like easy access to safe mode. If it fails, you can simply wipe it and reinstall.

H
HellNether
Senior Member
731
08-16-2016, 11:35 PM
#10
The EFI on retina MacBooks behaves differently. I attempted the methods you mentioned (Etcher, unetbootin, Rufus, etc.), but they didn't resolve the issue. It took a few clicks through Advanced Options—once for advanced options, again for advanced-er options, then another time for the most advanced settings—and a reboot was needed to reach the screen where Safe Mode could be enabled. The positive outcome came when I booted into Safe Mode with Networking; Windows started normally afterward. That’s great news! Thanks for encouraging me to try Safe Mode—it worked without any complicated steps. Now I can resume using my device. Thank you all!
H
HellNether
08-16-2016, 11:35 PM #10

The EFI on retina MacBooks behaves differently. I attempted the methods you mentioned (Etcher, unetbootin, Rufus, etc.), but they didn't resolve the issue. It took a few clicks through Advanced Options—once for advanced options, again for advanced-er options, then another time for the most advanced settings—and a reboot was needed to reach the screen where Safe Mode could be enabled. The positive outcome came when I booted into Safe Mode with Networking; Windows started normally afterward. That’s great news! Thanks for encouraging me to try Safe Mode—it worked without any complicated steps. Now I can resume using my device. Thank you all!