Level 1

8 points

Boot Camp Assistant says I need 64 bit iso file

Hello,

I am trying to install Windows 10 on my MacBook Pro, (13 inch, early 2015 Mojave) but I keep getting stuck after choosing the iso file that I have downloaded from the windows website. When I press install, BCA gives this message and then "quits unexpectedly". The ISO file I am using is Win10_1803_English_x64.iso, the April update.

MacBook Pro 13", macOS 10.14

Posted on Feb 28, 2019 1:03 PM

Similar questions

Boot Camp Assistant thinks my 64-bit Windows 10 ISO isn't one I just completely reset and updated my Early 2015 13" MacBook Air to macOS Catalina, and I wanted to install Windows 10. I downloaded a fresh ISO of 64-bit Windows 10 using Microsoft's Media Creation Tool, and yes, I made sure it's 64-bit only and not "32-bit/64-bit" but Boot Camp Assistant thinks the ISO isn't what it needs. I've searched around on the net and people say to redownload the ISO because it might possibly be corrupt. I've redownloaded the ISO three times now, and it still doesn't work. The error message is as follows: --- Need 64-bit WIndows 10 or later ISO file. Boot Camp only supports 64-bit Windows 10 or later installation on this platform. Please use an ISO file for 64-bit Windows 10 or later installation. --- Please help.
6682 8
Need 64 bit Windows 10 or later ISO Trying to get to use Bootcamp windows 10 but I get the following error: Need 64 bit Windows 10 or later ISO. I'm using the official ISO download from Microsoft and downloading the 64bit file. However when I choose it on the Boot Camp app, it gives me the error. I'm on a MacBook Pro 2019
901 3
Boot camp install fails - need 64-bin windows 10 or later iso file I'm trying to install Windows 10 onto my Macbook Pro using Bootcamp. The install process fails with an error message of 'windows boot camp need 64-bin windows 10 or later iso file' The Windows ISO used was downloaded using MediaCreationTool1903.exe in late July. MD5 sum of the ISO downloaded was 945a4a985c4be0caf4af3ea71d7ea035. The Mac is running the current version of OSX (updated it for the point release the other day). I'm retrying the Windows ISO download to see if that fixes the issue. Is there anything else I should be trying? Is there an alternative source to get the Windows ISO from? cheers Michael
17384 11

37 replies

Var_B123 Author

Level 1

8 points

Mar 5, 2019 6:51 PM in response to Loner T

what is the correct MD5sum?

Also is there another website where I could download an older version of w10? I seem to get an error when I try to download it from the official Microsoft website.

Var_B123 Author

Level 1

8 points

Mar 1, 2019 6:31 AM in response to Loner T

/dev/disk0 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *121.3 GB disk0

1: EFI EFI 209.7 MB disk0s1

2: Apple_APFS Container disk1 121.1 GB disk0s2

/dev/disk1 (synthesized):

#: TYPE NAME SIZE IDENTIFIER

0: APFS Container Scheme - +121.1 GB disk1

Physical Store disk0s2

1: APFS Volume Macintosh HD 73.5 GB disk1s1

2: APFS Volume Preboot 43.8 MB disk1s2

3: APFS Volume Recovery 517.0 MB disk1s3

4: APFS Volume VM 2.1 GB disk1s4

Var_B123 Author

Level 1

8 points

Mar 1, 2019 3:52 PM in response to Loner T

This is what i got when I ran the code in single user mode

-bash-3.2# fsck_apfs -s -o -y /dev/rdisk1

0000: 0000 0000 0000 0000 0000 0000 0000 0000 |................|

. . .

01b0: 0000 0000 0000 0000 0000 0000 0000 00fe |................|

01c0: ffff eefe ffff 0100 0000 cff8 3f00 0000 |................|

01d0: 0000 0000 0000 0000 0000 0000 0000 0000 |................|

. . .

01f0: 0000 0000 0000 0000 0000 0000 0000 55aa |..............U.|

0200: 4546 4920 5041 5254 0000 0100 5c00 0000 |EFI.PART........|

0210: 4545 8214 0000 0000 0100 0000 0000 0000 |EE..............|

0220: cff8 3f00 0000 0000 2200 0000 0000 0000 |................|

0230: aef8 3f00 0000 0000 7882 4beb 3e4a 7543 |........x.K..JuC|

0240: 8401 3f5e 9dda 16e7 0200 0000 0000 0000 |................|

0250: 8000 0000 8000 0000 d7c7 f853 0000 0000 |...........S....|

0260: 0000 0000 0000 0000 0000 0000 0000 0000 |................|

. . .

0400: 0053 4648 0000 aa11 aa11 0030 6543 ecac |.SFH.......0eC..|

0410: 9d54 7abb 6672 bf48 8e33 157b 502a 45b8 |.Tz.fr.H.3..P.E.|

0420: 2800 0000 0000 0000 a7f8 3b00 0000 0000 |................|

0430: 0000 0000 0000 0000 6400 6900 7300 6b00 |........d.i.s.k.|

0440: 2000 6900 6d00 6100 6700 6500 0000 0000 |..i.m.a.g.e.....|

0450: 0000 0000 0000 0000 0000 0000 0000 0000 |................|

. . .

0ff0: 0000 0000 0000 0000 0000 0000 0000 0000 |................|

error: Device does not contain a valid APFS container.

-bash-3.2#

Var_B123 Author

Level 1

8 points

Mar 1, 2019 7:23 PM in response to Loner T

yep, this is what I got

sudo fsck_apfs -n -l /dev/rdisk1

Password:

** Checking the container superblock.

** Checking the EFI jumpstart record.

** Checking the space manager.

** Checking the space manager free queue trees.

** Checking the object map.

** Checking volume.

** Checking the APFS volume superblock.

** The volume Macintosh HD was formatted by hfs_convert (748.21.6) and last modified by apfs_kext (945.241.4).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

warning: apfs_num_other_fsobjects (59) is not valid (61)

Fix apfs_num_other_fsobjects (oid 0x403, xid 0x2ee507)? NO

** Checking volume.

** Checking the APFS volume superblock.

** The volume Preboot was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (945.241.4).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume Recovery was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (945.241.4).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Checking volume.

** Checking the APFS volume superblock.

** The volume VM was formatted by newfs_apfs (748.21.6) and last modified by apfs_kext (945.241.4).

** Checking the object map.

** Checking the snapshot metadata tree.

** Checking the snapshot metadata.

** Checking the extent ref tree.

** Checking the fsroot tree.

** Verifying allocated space.

** Performing deferred repairs.

** The volume /dev/rdisk1 appears to be OK.

Loner T

Level 9

59,536 points

Mar 2, 2019 7:18 AM in response to Var_B123

This may be a bit tedious, but I suggest retrying the Single-User mode procedure several times, and checking if it corrects it. One good sign is that the xid is incrementing and if it continues, it should progress further.

Once this is corrected, we can retry the BC Assistant.

Also, ensure that

the ISO is unmounted
the ISO is not in Downloads
multiple ISOs must be ejected, before you start BCA

Loner T

Level 9

59,536 points

Mar 2, 2019 9:07 AM in response to Var_B123

The fsck_apfs tries to fix file system corruption. You can leave the ISO on the desktop, but it should be unmounted before you start BC Assistant.

Var_B123 Author

Level 1

8 points

Mar 3, 2019 6:57 PM in response to Loner T

FAT partition worked, no errors this time

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Boot Camp Assistant says I need 64 bit iso file