Bootcamp will not recognise x64 Windows 7 ISO or Install Disc

I've never heard of anyone needing to sign individual files within an app before resigning the entire thing, but I'm glad that you found a solution that worked for you. I also didn't have to use the --deep flag, but it's good that someone mentioned it in case it becomes needed for some people. 🙂

When it says "Your bootable USB drive could not be created" try holding the 'option' key then press the 'continue' button. This worked for me!

After editing Info.plist my boot camp start crashing.

I've tried my backup file and I'm still getting the same error.

How do I reinstall it?

Process: Boot Camp Assistant [1336]

Path: /Applications/Utilities/Boot Camp Assistant.app/Contents/MacOS/Boot Camp Assistant

Identifier: com.apple.bootcampassistant

Version: ???

Build Info: BootCampAssistant-5868000000000000~2

Code Type: X86-64 (Native)

Parent Process: ??? [1]

Responsible: Boot Camp Assistant [1336]

User ID: 501

Date/Time: 2015-08-28 20:15:28.990 -0300

OS Version: Mac OS X 10.10.4 (14E46)

Report Version: 11

Anonymous UUID: C9397C98-59EE-6D84-1816-871E945351C4

Time Awake Since Boot: 490 seconds

Crashed Thread: 0

Exception Type: EXC_CRASH (Code Signature Invalid)

Exception Codes: 0x0000000000000000, 0x0000000000000000

kernel messages:

VM Regions Near 0x7fff7475b0a0 (cr2):

__LINKEDIT 00007fff6b39d000-00007fff6b3b1000 [ 80K] r--/rwx SM=COW /usr/lib/dyld

--> Submap 00007fff70000000-00007fff80000000 [256.0M] r--/rwx SM=PRV process-only VM submap

unused shlib __DATA 00007fff73727000-00007fff75d27000 [ 38.0M] rw-/rw- SM=COW system shared lib __DATA not used by this process

Thread 0 Crashed:

0 dyld 0x00007fff6b32e000 _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):

rax: 0x000000000000000d rbx: 0x0000000000000000 rcx: 0x0000000000000000 rdx: 0x0000000000000000

rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x0000000000000000 rsp: 0x00007fff5d43ec18

r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x0000000000000000

r12: 0x0000000000000000 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000

rip: 0x00007fff6b32e000 rfl: 0x0000000000000201 cr2: 0x00007fff7475b0a0

Logical CPU: 0

Error Code: 0x020000f4

Trap Number: 133

Binary Images:

0x7fff6b32d000 - 0x7fff6b363837 dyld (???) <72A99D0F-0B56-3938-ABC5-67A0F33757C4> /usr/lib/dyld

External Modification Summary:

Calls made by other processes targeting this process:

task_for_pid: 0

thread_create: 0

thread_set_state: 0

Calls made by this process:

task_for_pid: 0

thread_create: 0

thread_set_state: 0

Calls made by all processes on this machine:

task_for_pid: 501

thread_create: 0

thread_set_state: 0

VM Region Summary:

ReadOnly portion of Libraries: Total=300K resident=228K(76%) swapped_out_or_unallocated=72K(24%)

Writable regions: Total=8416K written=0K(0%) resident=12K(0%) swapped_out=0K(0%) unallocated=8404K(100%)

REGION TYPE VIRTUAL

=========== =======

STACK GUARD 56.0M

Stack 8192K

VM_ALLOCATE 8K

VM_ALLOCATE (reserved) 4K reserved VM address space (unallocated)

__DATA 228K

__LINKEDIT 80K

__TEXT 220K

mapped file 248K

shared memory 4K

=========== =======

TOTAL 64.8M

TOTAL, minus reserved VM space 64.8M

Model: MacBookAir6,2, BootROM MBA61.0099.B19, 2 processors, Intel Core i5, 1.3 GHz, 4 GB, SMC 2.13f15

Graphics: Intel HD Graphics 5000, Intel HD Graphics 5000, Built-In

Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3230554638454455302D474E2D4620

Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3230554638454455302D474E2D4620

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x117), Broadcom BCM43xx 1.0 (7.15.166.24.3)

Bluetooth: Version 4.3.5f8 15969, 3 services, 18 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

Serial ATA Device: APPLE SSD SD0128F, 121.33 GB

USB Device: Internal Memory Card Reader

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

USB Device: USB Mass Storage Device

Thunderbolt Bus: MacBook Air, Apple Inc., 23.6

Thank you for answer, it saved me to a point where I had to sign up just to thank you!

After going round and round, trying workarounds, this was all it was! I unmounted the iso, then I could uses it! Thanks.

UNMOUNT IT. After you download the iso file it automatically mounts. Unmount it in disk utility. Simple!

UNMOUNT IT. After you download the iso file it automatically mounts. Unmount it in disk utility. Simple!

did not work for me. thx anyway

Hello,

I see a lot of you guys struggling to get it to work.

I received the error "Bootcamp will not recognise x64 Windows 7" as well.

So it frustrated me and started searching on the web for solutions.

And I had read someone saying "unmounting the image" solved it for them.

Anyways, straight to the point.

1. Go to Applications/Utilities
2. Open Disk Utility and keep it open
3. Open Bootcamp, check the top option and leave the two underneath unchecked
4. Click continue and then select your Windows 7 ISO file
5. If it failed again, go to Disk Utility
6. Check if you can see the Disk Images tab under the External tab
7. If you can see images that are called DVD eject those
8. If you can see "Apple write" or something, ejecting these did the trick for me
9. Select one of the images "Apple write" and go on file and hit eject there
10. Eject all of them
11. Go back to Bootcamp
12. Select your Windows 7 ISO once again and that should do the trick for you as well.

Please keep in mind that I'm using El Capitan.

Duplicate "Boot Camp Assistant.app" so you have 2 of them: Boot Camp Assistant.app and Boot Camp Assistant copy.app, the copy is perfectly editable, just remember to launch it by clicking the file Boot Camp Assistant copy.app from the application folder in finder, since it will not show up in launchpad.

Un-mounting was it for me. Thanks!

Same problem here. Eject the IOS file and it works.

Worked as you said. Thank you!

Thanks!! unmounting the image solved the problem for windows 10 x64 in mac os sierra

I've tried everything on here, and this was the fix. Thanks!