Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Bootcamp failed to copy Windows 10 files - I've tried everything...

Hello,


I'm sorry to sound like a broken record on these forums about Bootcamp not working, but I'm at the point of having no idea what to do. I haven't used a Mac in over 20 years, but am comfortable with working on computers on both the software and hardware front. I recently obtained a early-2015 Macbook Pro Retina 13", and I've upgraded the hard drive to a 500GB Samsung 970 Evo NVMe SSD via using the Sintech adapter that was created for this particular SSD proprietary connector. I bring that up because I don't know if that has anything to do with my woes here. In order to have gotten the NVMe drive to natively work in the first place, I used an OEM Apple hard drive to update the laptop completely for all the firmware updates necessary, then installed the Samsung 970 Evo and reinstalled Mac OS. That all said, the laptop is fully up-to-date on Mojave 10.14.2 with no pending updates.


I've read so many threads here, on Reddit, Youtube videos, etc. saying which ISOs worked and which didn't. I've tried so many of them and none of them will work. Still trying to use build 1803 since many have said the newest one is problematic. Once I open Bootcamp, select the ISO, allocate the partition space (100GB), and begin the process, after the tools are downloaded, I am immediately prompted with "An error occurred while copying the Windows installation files."


I've also tried the "twocanoes" solution to no avail. I genuinely have no idea what else to try. Based on what has been asked of others in similar situations, I booted into single-user mode and ran the fsck_apfs -s -o -y /dev/rdisk1 in hopes that you see something that is wrong that I have no idea about. Any help would be greatly appreciated!

MacBook Pro Retina (2015 and later)

Posted on Jan 10, 2019 8:29 PM

Reply
Question marked as Best answer

Loner T, so your inquiry about creating my own partition got me thinking, and I was finally able to get everything working! After some trial and error, I found that a problem this system was having was creating TWO partitions and having them mount after. So I created two FAT partitions, one for the install of Windows and the other to dump the contents of the installation ISO into, as well as the bootcamp Windows support files. When I created each partition, I had to reboot the device, then create the next. I also had to go with the 1803 build, because one of the files for the 1809 build is 5GB, which exceeds FAT's 4GB limit. I tried to make the partition exFAT instead, but mac OS won't mount exFAT (at least without more trouble than it was worth). So after that, I did my install of Windows, installed all the support files, and then did driver updates (kept getting kernel security check error blue screens). Not sure if the blue screens are fixed, but it may be. Then deleted the "install" partition, and everything seems good now!


Only update left is the 1809 update that Windows is downloading, so we'll see how that goes. Thanks for checking to make sure my APFS and also getting me thinking!

Posted on Jan 11, 2019 12:01 AM

Similar questions

6 replies

Jan 10, 2019 9:21 PM in response to ShimakazeKai

Your APFS looks clean. W10 1803 (April) should work, W10 1809 is supposed to work on 10.14.2 (I have not tested Mojave.2 with W10 1809 personally).


As a test, try to create a FAT partition of the size you want Windows to be and post the output. If you are working with APFS resizeContainer, it may be a better option, because it shows much more detail than DU.


Also, in my past experience, I have seen non-Apple SSDs run into many issues installing Windows, while macOS works fine. In most cases, when the original Apple SSD is re-installed, Windows does install properly. This is your second test, if the first test runs into any issues. The Samsung EVOs are notorious for issues on Macs, but the PROs work very well.

Jan 10, 2019 9:27 PM in response to Loner T

Unfortunately I don't have the OEM drive anymore (original died and so I borrowed my friends who allowed me to backup her machine and erase it so I could get the firmware updates to make the NVMe work). I'm hoping that isn't the case, as I've read other Evo drives working, but honestly have no idea.


I can create the FAT partition; what do I run to show the results? (I'm assuming something in terminal?) Also, I'm not familiar with the APFS resizeContainer.


I'm largely Mac illiterate right now and am doing my best to scrape by with all these problems, haha.

Jan 10, 2019 9:43 PM in response to Loner T

Okay, I created a 100GB FAT partition called "WINDOWS TEST". Here were the results:


Partitioning disk “Samsung SSD 970 EVO 500GB Media” (disk0)


Running operation 1 of 2: Add “WINDOWS TEST” 100.49 GB by splitting “mac HD” (disk0s2) from 499.9 GB to 399.41 GB…

Aligning shrink delta to 100,486,279,168 bytes and targeting a new physical store size of 399,411,826,688 bytes

Determined the minimum size for the targeted physical store of this APFS Container to be 100,339,249,152 bytes

Resizing APFS Container designated by APFS Container Reference disk1

The specific APFS Physical Store being resized is disk0s2

Verifying storage system

Using live mode.

Performing fsck_apfs -n -x -l -S /dev/disk0s2

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 mac HD was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.230.6).

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 Preboot was formatted by newfs_apfs (748.77.8) and last modified by apfs_kext (945.230.6).

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.77.8) and last modified by apfs_kext (945.230.6).

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.77.8) and last modified by apfs_kext (945.230.6).

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/disk0s2 appears to be OK.

Storage system check exit code is 0.

Shrinking APFS Physical Store disk0s2 from 499,898,105,856 to 399,411,826,688 bytes

Shrinking APFS data structures

Shrinking partition

Modifying partition map

Initialized /dev/rdisk0s3 as a 93 GB case-insensitive HFS Plus volume with a 8192k journal


Mounting disk

Creating a new empty APFS Container

Unmounting Volumes

Switching disk0s3 to APFS

Creating APFS Container

Created new APFS Container disk2

Preparing to add APFS Volume to APFS Container disk2

Creating APFS Volume

Created new APFS Volume disk2s1

Mounting APFS Volume

Setting volume permissions


Running operation 2 of 2: Erase “WINDOWS TEST” (disk2s1)…

Deleting APFS Container with all of its APFS Volumes

Unmounting Volumes

Unmounting Volume “WINDOWS TEST” on disk2s1

Deleting Volumes

Deleting Container

Wiping former APFS disks

Switching content types

Unmounting disk

Erasing

512 bytes per physical sector

/dev/rdisk0s5: 195951872 sectors in 3061748 FAT32 clusters (32768 bytes/cluster)

bps=512 spc=64 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=780511232 drv=0x80 bsec=195999744 bspf=23920 rdcl=2 infs=1 bkbs=6


Mounting disk


Operation successful.


Question marked as Best answer

Jan 11, 2019 12:01 AM in response to ShimakazeKai

Loner T, so your inquiry about creating my own partition got me thinking, and I was finally able to get everything working! After some trial and error, I found that a problem this system was having was creating TWO partitions and having them mount after. So I created two FAT partitions, one for the install of Windows and the other to dump the contents of the installation ISO into, as well as the bootcamp Windows support files. When I created each partition, I had to reboot the device, then create the next. I also had to go with the 1803 build, because one of the files for the 1809 build is 5GB, which exceeds FAT's 4GB limit. I tried to make the partition exFAT instead, but mac OS won't mount exFAT (at least without more trouble than it was worth). So after that, I did my install of Windows, installed all the support files, and then did driver updates (kept getting kernel security check error blue screens). Not sure if the blue screens are fixed, but it may be. Then deleted the "install" partition, and everything seems good now!


Only update left is the 1809 update that Windows is downloading, so we'll see how that goes. Thanks for checking to make sure my APFS and also getting me thinking!

Bootcamp failed to copy Windows 10 files - I've tried everything...

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.