Problems migrating Bootcamp to New Retina MBP

Question

Level 1

4 points

Problems migrating Bootcamp to New Retina MBP

I have used Winclone to migrate my Bootcamp Win7 partition from hard drive to hard drive successfully many times for my Mid-2010 MBP. However when I moved it to my new Retina MBP, it blue screens on startup because of driver issues. It won't even boot in safe mode or safe mode with command prompt.

I tried installing the new drivers from the source hard drive on my old MBP, but it fails because it recognizes it's not a retina MBP.

I've also tried booting to the Win7 install and try to install the drivers through the repair function, but it doesn't like the .exe's.

Any ideas on how I can get the new drivers loaded without reinstalling Windows entirely?

MacBook Pro with Retina display, OS X Mountain Lion (10.8.1)

Posted on Aug 25, 2012 5:53 PM

Reply

Answer 1

Shootist007

Level 6

16,703 points

Aug 25, 2012 6:06 PM in response to boogybren

I don't think you can. With a Normal install on a PC you could do a Repair install or used WinPE to remove the Hardware Extraction Layer part of the Registry and then at first boot it would of loaded generic drives to boot to the desktop where you could load the new Apple support drivers. But your Win install is looking for old hardware and with BC there is not way around that, to my knowledge.

EDIT:

At boot of Windows have the Win DVD in the drive and hold down the F8 key. That brings up a Windows one time boot menu. You may be able to start a repair install from there.

Reply

Answer 2

boogybren Author

Level 1

4 points

Aug 25, 2012 10:12 PM in response to Shootist007

I did boot to the Win7 install. The repair options are limited to repairing the boot record and not the full installation (tried it and it didn't work of course). The only way to do a repair is if you can boot into the OS.

But it got me thinking. I booted back into OS X and opened the bootcamp install from VMWare Fusion. I was at least able to get the OS up.

I manually extracted all of the drivers that I could but the chipset ones (which I am almost certain is the ones I need) is quite a bit more involved and the setup fails because it can't find the chipset from within my VM.

I am going to try a repair from here and see where it takes me.

Wish me luck!

Reply