Bootcamp Issues - Windows Cannot Locate Disc

You should see a screen similar to the one shown in Welcome to Boot Camp Assistant - Apple Support . On your model, you can bypass BC Assistant and directly use the Windows installer on a USB2 flash drive after you manually create a FAT32 partition using Disk Utility.

I have exactly the same problem - but it didn't crop up until I installed High Sierra. I had installed Win 10 Boot Camp under Sierra, but there were lots of issues when HS was installed. I took out the partition, tried to reinstall Win 10 BC and the same problem arose. I even erased the disk and reinstalled HS, tried a number of ISOs and same problem. Have been working with Apple Support, who has referred this to Engineering, who supposedly has been working on this for the last month but there's been nothing from them.

At what point do I take back the machine???

I had a look with Disk Utility, and there were only 2 partitions - the BC and Mac OS, although the Mac OS partition has a cross-hatched segment to it (with no identifiers at all). I ran BC Helper and went back to a single Mac OS partition. The cross-hatched area is still here.

$ diskutil list

/dev/disk0 (internal):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme 121.3 GB disk0

1: EFI EFI 314.6 MB disk0s1

2: Apple_CoreStorage Macintosh HD 120.9 GB disk0s2

3: Apple_Boot Boot OS X 134.2 MB disk0s3

/dev/disk1 (internal, physical):

#: TYPE NAME SIZE IDENTIFIER

0: GUID_partition_scheme *3.0 TB disk1

1: EFI EFI 209.7 MB disk1s1

2: Apple_CoreStorage Macintosh HD 3.0 TB disk1s2

3: Apple_Boot Recovery HD 650.0 MB disk1s4

/dev/disk2 (internal, virtual):

#: TYPE NAME SIZE IDENTIFIER

0: Apple_HFS Macintosh HD +3.1 TB disk2

Logical Volume on disk0s2, disk1s2

79FDCE40-74F3-4EC6-AE51-C7623C6FBB8E

Unencrypted Fusion Drive

I don’t understand what you mean about the screen.

It’s not quite as simple as all that I think. The installer would have to be an an EXFAT flash drive, and you’d have to make it bootable which isn’t easy unless you have another windows machine. Then you’ll still need another drive with BC drivers to install again after getting Windows on. I think it would be a process. Lots of specific steps.

Well, Loner T, whoever you are, you are more awesome than Apple Tech Support.

While I was reading the other suggested postings and how you helped some others, one thing that you mentioned there struck me. If you had multiple failed installs, then reset the SMC and NVRAM. I went, "Hmmm." So I did the following:

1. reset SMC as per Apple's protocol.

2. reset the NVRAM

3. I had a Time Capsule on the network - so I powered it off. There were no other drives attached, but it made me wonder so I thought I'd give it a shot.

4. There is also a NAS on the network, which I had not set up to recognize since resinstalling High Sierra, but I powered it off anyway.

...and then proceeded with normal Boot Camp installation using the Helper.

And everything installed perfectly, including the Restart in Mac OS option in the Boot Camp app on the Windows Taskbar (which isn't the case on my MacBook Pro). No hitches at all.

So thank you for your direction. I didn't have to quite follow it, but got the info I needed to sort out a problem that's plagued me since HS was released.

You're clearly awesome.

I also need help with this and have been reading all of these discussions.

Did you disable time capsule because it was set up with time machine?

Were you using time capsule as your router?

What is NAS?

Thank you!

The AutoUnattend.xml created by BC assistant is incorrect. Remove the current BC/Windows partition (using BCA only), disconnect all external storage, and re-try BC Assistant.

See Bootcamp User Interface and Build your own Windows 10 Bootcamp USB Installer .

Do you still have the OSXRESERVED partition on your Mac?

From macOS Terminal, can you post the output of

diskutil list

You have a 3TB Fusion drive. What is the year/model of your Mac? Do not post the serial number of your Mac.

2017 iMac 27

Excellent. Please remember to back up macOS, Windows and create a Windows System Restore point.

Are you getting the same IMageInstall error? What is the year/model of your Mac and macOS version?