Bootcamp will not recognise x64 Windows 7 ISO or Install Disc

I was able to simply run the following to get Boot Camp Assistant working again after editing the .plist file.

sudo codesign -fs - /Applications/Utilities/Boot\ Camp\ Assistant.app

Boot Camp Assistant crashes because you've changed its contents, and thus the code's signature becomes invalid.

Almost right, you actually need to do the following:

sudo codesign -fs - /Applications/Utilities/Boot\ Camp\ Assistant.app/Contents/info.plist

Followed by:

sudo codesign -fs - /Applications/Utilities/Boot\ Camp\ Assistant.app

The first command signs the file which was modified, and the second command then re-sgins the whole application. This worked for me on a MBP 15,2.

PyrO_PrOfessOr wrote:

Almost right, you actually need to do the following:

sudo codesign -fs - /Applications/Utilities/Boot\ Camp\ Assistant.app/Contents/info.plist

Followed by:

sudo codesign -fs - /Applications/Utilities/Boot\ Camp\ Assistant.app

The first command signs the file which was modified, and the second command then re-sgins the whole application. This worked for me on a MBP 15,2.

Do not forget the --deep qualifier when signing the whole application.

Loner T wrote:

Do not forget the --deep qualifier when signing the whole application.

Ah OK! It worked for me without the --deep but it could be the first step isn't required with the --deep qualifier. Cool, will check this out.

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. 🙂

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

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.

So NONE of these answers here solved my problem... what DID solve my problem was a solution I found here:

https://superuser.com/questions/908485/boot-camp-assistant-not-accepting-windows -10-iso-file/1082308#1082308?newreg=cea0…

here it is curtesy of Jeremy Banks:

The System Integrity Protection in newer versions of OS X prevents modification of Boot Camp Assistant.app/, as suggested by other answers. I tried duplicating the file and I was able to modify the duplicate, but it didn't fix the issue for me.

I solved this problem by tricking Boot Camp Assistant with a Windows 8 ISO.

Download both Windows 8 and Windows 10 ISOs from Microsoft (you don't need a license to download the installers).

Create a copy of the Windows 8 ISO and name it windows.iso.

Select windows.iso in Boot Camp Assistant. It should accept it.

When it prompts you to confirm that you want to format the disk, wait.

Delete windows.iso.

Open the Trash, right-click on windows.iso and select "Delete Immediately". (Emptying the Trash will fail because it was already opened, but specifying it directly seems to avoid this.)

Rename the Windows 10 ISO to windows.iso.

Return to Boot Camp Assisant and confirm, to continue the process.

After using the Windows 8 ISO to pass the verification process, it can successfully use the Windows 10 ISO we swap in to create and use an installation disk.

good luck - this is the only thing that worked for me.

I had a similar issue -- the iso file I downloaded from Microsoft wouldn't "load" while using the Boot Camp Assistant. I guessed it was something to do with the long iso file name (which was "Win10_1607_English_x64.iso"). In the Mac Finder, I duplicated the iso file and changed the name (to"Win10_64.iso"), then the iso file loaded fine and I was off and running.

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.

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

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

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

Hello!

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

Thanks!

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