corifromauckland

Q: Bootcamp will not recognise x64 Windows 7 ISO or Install Disc

27" iMac late 2012

 

I've tried using both my Windows 7 ISO to create a bootable drive, and also attempted using a disc burnt using disc utility, but I keep encountering the following message with Bootcamp. My Windows 7 install disc is a mixed x32 and x64 (I would obviously choose x64 bit when running windows install later) But is displaying the following image?

 

I used the same windows disc to install the x64 bit version on my 2011 27" with no problems, I've also tried to use another Windows 7 install disc but it's giving the same error...

 

"Boot Camp only supports 64-bit Windows installation on this platform. Please use a ISO file for 64-bit Windows installation."

 

Any ideas how I could fix this?

 

 

 

 

 

Screen Shot 2013-01-27 at 11.29.36 PM.png

iMac, OS X Mountain Lion (10.8.2)

Posted on Jan 27, 2013 2:41 AM

Close

Q: Bootcamp will not recognise x64 Windows 7 ISO or Install Disc

  • All replies
  • Helpful answers

Page 1 of 3 last Next
  • by mende1,

    mende1 mende1 Jan 27, 2013 2:44 AM in response to corifromauckland
    Level 10 (93,314 points)
    Desktops
    Jan 27, 2013 2:44 AM in response to corifromauckland

    You need a 64-bit only Windows 7 ISO. Mixed versions aren't compatible with the Late 2012 iMac (I suppose that they contain 32-bit files that Boot Camp detects, refusing to use that file). Download a 64-bit only Windows 7 ISO and it should work correctly

  • by Akominatus,Helpful

    Akominatus Akominatus Aug 22, 2013 5:01 AM in response to corifromauckland
    Level 1 (14 points)
    Windows Software
    Aug 22, 2013 5:01 AM in response to corifromauckland

    I had the same problem, and found the solution on MacRumours, posted by one "falkas", to whom all credit is due. I tried it, and it worked first time, like a charm.

     

    It is possible to use the Windows 7 ISO with both x86 and x64 on the same install file. Bootcamp 5 will see this as a x86 install file though and won't allow it to continue. To fix this just follow these steps.

     

    1. Open a Finder window.

     

    2. Navigate to Applications>Utilities

     

    3. Control Click or Right Click on Boot Camp Assistant and select "Show Package Contents"

     

    4. Open the Contents folder

     

    5. Drag the file "info.plist" to your desktop (I also recommend saving it in another place as well in case you want to revert to the original)

     

    6. Open info.plist on your desktop with a text editor

     

    7. Find the field labeled as below:

    <key>32BitSupportedModels</key>

    <array>

    <string>MacBook7,1</string>

    <string>MacBookAir5,2</string>

    <string>MacBookPro10,1</string>

    <string>MacPro5,1</string>

    <string>Macmini5,3</string>

    <string>iMac12,2</string>

    </array>

     

    8. Time to find what your Mac is. Click the Apple in the top left hand corner and select About This Mac

    -Click More Info...

    -Click System Report...

    -Under Hardware Overview, look for Model Identifier and copy it

     

    9. With your Mac's Identifier copied, go back to your open info.plist file create a string at the TOP of the entries. So if your Mac identifier was "iMac13,2" then it would look like this:

    <key>32BitSupportedModels</key>

    <array>

    <string>iMac13,2</string>

    <string>MacBook7,1</string>

    <string>MacBookAir5,2</string>

    <string>MacBookPro10,1</string>

    <string>MacPro5,1</string>

    <string>Macmini5,3</string>

    <string>iMac12,2</string>

    </array>

     

    10. Save and close info.plist. Drag info.plist back into the Contents folder and select replace. (You may have to authenticate and enter your admin password).

     

    11. Start Bootcamp and it should allow you to use your Disk/USB with both versions. I wouldn't recommend installing the x86 (32 bit) version of Windows 7, but this will allow you to get to the point of the installation to select x64 (64 bit) if you have an ISO file with both 32 bit and 64 bit combined. Hope this helps.

  • by Jeb_Leeds,

    Jeb_Leeds Jeb_Leeds Aug 28, 2013 9:25 AM in response to Akominatus
    Level 1 (0 points)
    Aug 28, 2013 9:25 AM in response to Akominatus

    I have tried using this method explained by Akominatus, however when you get to step 9.

     

    9. With your Mac's Identifier copied, go back to your open info.plist file create a string at the TOP of the entries. So if your Mac identifier was "iMac13,2" then it would look like this:

     

    The info.plist file is locked and you cannot make changes to it.

    error message

    You don't own the file "Info.plist" and dont have permission to write to it.

    You can duplicate this document and edit the duplicate.  Only the duplicate will unclude your changes.

     

    The duplicate does not save as .plist as it is in text edit.

     

    This is getting rather confusing because now we are in another topic of editing locked .plist documents.

     

    I'm not sure what is going on but I am running a new mini with no changes made to it and the error message comes up where as I do not see other people running into this .plist problem.

     

    Any advice to get past step 9?

     


  • by Slap-Shot,

    Slap-Shot Slap-Shot Sep 23, 2013 4:03 AM in response to Jeb_Leeds
    Level 1 (0 points)
    Sep 23, 2013 4:03 AM in response to Jeb_Leeds

    Jeb_Leeds

     

    You need to stop the Boot Camp Assistant which might be running (assuming you are part way through the setup process).  I had the same issue until I realized it was running.

     

    You will also need to authenticate the new version of info.plist when you save it back to the contents folder.

     

    SS

  • by allexandra1990,

    allexandra1990 allexandra1990 Dec 10, 2013 1:06 AM in response to corifromauckland
    Level 1 (0 points)
    Dec 10, 2013 1:06 AM in response to corifromauckland

    I tried doing what it says here and now my boot camp wont open?

  • by jfcartier,

    jfcartier jfcartier Dec 17, 2013 9:13 AM in response to Akominatus
    Level 1 (0 points)
    Dec 17, 2013 9:13 AM in response to Akominatus

    I also tried your proposition, but afterward, my BootCamp wont open as well.

  • by hasurkar,

    hasurkar hasurkar Jan 31, 2014 11:18 AM in response to corifromauckland
    Level 1 (0 points)
    Jan 31, 2014 11:18 AM in response to corifromauckland

    Akominatus i tried what you have mention but after that my boot camp stop working so i had to revet back the info file any other solution or can you suggest where we are going wrong ..

    Thank you

    Girish

  • by erwan901,

    erwan901 erwan901 Feb 1, 2014 3:26 PM in response to corifromauckland
    Level 1 (0 points)
    Feb 1, 2014 3:26 PM in response to corifromauckland

    Hello!

     

    I have the exact same problem, does anyone has a workaround for this?

    Thanks!

  • by Hpizaia,

    Hpizaia Hpizaia Feb 21, 2014 5:35 AM in response to Akominatus
    Level 1 (0 points)
    Feb 21, 2014 5:35 AM in response to Akominatus

    After change info.plist my BootCamp wont open too :/ 

  • by turbostar,

    turbostar turbostar Feb 21, 2014 6:40 AM in response to Hpizaia
    Level 4 (2,925 points)
    Feb 21, 2014 6:40 AM in response to Hpizaia
  • by xcom97,

    xcom97 xcom97 Feb 21, 2014 6:17 PM in response to Akominatus
    Level 1 (15 points)
    Feb 21, 2014 6:17 PM in response to Akominatus

    The problesm with this "fix" is that it will UNFIX your Bootcamp assistant because you do not have the code signature/ right to edit this Plist. If yo do edit it BootCamp assistant will crash on you over and over and over again until ..like me you happen to be smart enough /luck enough  to have created a time machine back up that can restore the original file. A copy of the file you make WILL NOT work ...it must be untouched.

  • by erwan901,

    erwan901 erwan901 Feb 24, 2014 2:23 AM in response to corifromauckland
    Level 1 (0 points)
    Feb 24, 2014 2:23 AM in response to corifromauckland

    I agree, messing up with the info.plist enables to start the windowns install; but for me it stopped in the middle of the installation afterwards; so it is not a working solution (I tried on a MBA 2013 and a MBP 2013)

     

    Solution was to download a x64 ISO (recognized by bootcamp without a problem) and then follow the bootcamp guide.

  • by ericisaac,Helpful

    ericisaac ericisaac Mar 7, 2014 10:17 PM in response to corifromauckland
    Level 1 (5 points)
    Mar 7, 2014 10:17 PM in response to corifromauckland

    i just had this same issue. I found that the problem was that i had the disk mounted on my computer. once I ejected it, it worked without issue.

  • by t.truong,Helpful

    t.truong t.truong Apr 11, 2014 8:04 PM in response to corifromauckland
    Level 1 (5 points)
    Apr 11, 2014 8:04 PM in response to corifromauckland

    Found the solution. Rename the extension from .ISO to .DMG

Page 1 of 3 last Next