Apple launches Apple Store app in India

The Apple Store app provides customers with the most personalized way to shop for Apple’s innovative lineup of products and services. Learn more >

You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

User profile for user: DavidSerpa
DavidSerpa Author
User level: Level 1
4 points

Boot Camp issues after SSD migration on mid 2014 MacBook Pro

Migrated to new larger SSD on my mid 2014 Mackbook Pro and boot camp will not start on new SSD unless in Windows safemode. The previous SSD and Bootcamp worked fine with Windows 10 (and still do if I swap them back). What I did to migrate - After swapping the internal SSD with the new one and connecting the old via USB, I used Disk Utility to "Restore" the Mac OS hard drive onto the new SSD from the old drive, then once booted into Big Sur I ran bootcamp Version 6.1.0 (6272.140.2) to recreate the BOOTCAMP partition and drive. Windows 10 would never fully install and would crash after finishing the installation but before first login after reboot (I suspect this is because it is the latest ISO).


I then tried to "restore" the BOOTCAMP drive from the original SSD onto the new SSD BOOTCAMP drive. The operation is successful, Windows 10 boots up but crashes shortly after the login screen pops up, sometimes I can get into it before it locks up and crashes, which makes me think it is crashing while loading a driver or some service. If I boot into Windows safemode via F8 it works, I can get in manual start some services and what not but no amount of disabling unnecessary services and limiting the startup seems to work outside of safe mode. I don't see anything obvious in the logs. I did have to follow some steps from the recovery disk to get the "restore"d BOOTCAMP drive to boot fixing the EFI and running below commands.


https://apple.stackexchange.com/questions/308729/recover-bootcamp-efi-folder-fix-boot-entries



bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd


Wondering if anyone has successfully moved or cloned a bootcamp installation and if anyone knows how I can fix or troubleshoot this? Going on day 2 of messing with it. :/


Any suggestions would be greatly appreciate!

Dave



[Re-Titled by Moderator]

MacBook Pro 13″, macOS 11.7

Posted on Jan 15, 2025 6:20 PM

Reply
3 replies
User profile for user: DavidSerpa
DavidSerpa Author
User level: Level 1
4 points

Jan 17, 2025 2:19 PM in response to DavidSerpa

Was able to stabilize the Windows 10 installation on the new SSD by disabling the "power" service in windows 10. I had to do this in safe mode, once I did and rebooted the system works fine. I disabled the power service via sysconfig. It took awhile to find the service that was causing the system to crash and I am hoping sharing this will help anyone else who is having this issue. I do not know why the old disk did not have this issue but the new SSD does, not sure if it is a clone issue or what. I did find some info on the Windows support forums suggesting that the power service can malfunction if there is a piece of incompatible hardware.


The SSD I used was OWC 1.0TB Aura Pro X2 Complete to replace the Apple SSD that came with the MacBook. That is the only hardware that is new, so if it is a hardware compatibility issue that explains why the Windows 10 image boots fine on my old SSD but not the new one. Glad I got it to work and I can live without the power service running!

Reply
User profile for user: DavidSerpa
DavidSerpa Author
User level: Level 1
4 points

Jan 17, 2025 2:29 PM in response to 6x6

Thank you for your response. There are some additional steps I had to take in order to run an installer in safe mode, which I did, but did not help. My original thought was it was the bootcamp service having issues form being cloned or "restored". However I am not sure that is what was happening.


After a few days of troubleshooting I did find the service that was causing the crash. It ended up being the "Power" service in Windows 10 and reading a few threads on the Windows support forums it seems this can happen when there is some piece of hardware that the windows kernel does not like (I am guessing it is the SSD I put in). Disabling it allows me to run everything normally and causes no issues with Windows. So, now my MacBook is upgraded, fully functional on both the MacOS and Windows 10 side and I can hopefully keep my MacBook going for a few more years. :)

Reply

Boot Camp issues after SSD migration on mid 2014 MacBook Pro

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up