On my MacBook Air What HappendNote: Feel free to skip this section and on to what I did that worked if you don’t want to see the process.The process that I lay out below using the terminal to create a bootable USB Drive with the Windows 10 installer on it worked. UPDATE — I had to use Windows to do it. Instead, TeamViewer Portable runs directly from a USB stick or the Cloud.Note: Here are the parts I chose for the build that this Windows 10 installer USB stick will be used for. The USB Flash drive must be formatted as exFAT.Install TeamViewer Host on an unlimited number of computers and devices. It is important to use this Mac since it will be used to identify the correct Windows drivers. All the preparation is done in macOS on the Mac that is having an issue booting Windows.Given this, I took several steps to figure out if the drive boot order or drives conflicting were a problem. A pop up saying that the installation media could not be found.Before I came to the conclusion that the installation media needed to be recreated I thought that the problem was likely related to the way that the boot devices were setup in the system’s BIOS. “Windows could not prepare the computer to boot into the next phase of installation” At this point I received one of several errors: I was able to proceed with the installation up until the point of actually installing the files to the selected drive. From there, however, the problems started.I booted Windows up, downloaded the tool freely available from Microsoft for the very purpose of creating such drives, and used the Windows 10 ISO I’d downloaded earlier to create the drive. How did I create the new boot drive that worked?I happen to have Parallels installed on my MacBook Air with a version of Windows 10 on it. None of this worked.I am fairly sure that these errors boiled down to the fact that the install.wim file had to be split up due to the 4GB file size limitation in FAT32 and the fact that OS X can’t write an NTFS drive.
On Usb Update This PostThere are two main versions of Windows 10: Home and Pro. If you have a way that has worked for you, please let me know so that I can update this post! Buying Windows 10 — Picking a versionThe first step in creating install media for Windows 10 is, of course, to buy a version of Windows 10. It was my desire to create this post and provide a solution for creating a Windows 10 installer just using OS X. The documentation for Boot Camp Assistant mentions that this option will only be present for some systems anyway.I hate to say this but the option I can think of is to use Boot Camp to install the version of Windows 10 that was purchased for this installs and use that instance to create the boot drive you need. I tried this first and it did not work for me. What can you do if you don’t have Parallels / Boot Camp installed?There are some reports that using Boot Camp Assistant will allow you to create a bootable USB drive with the installation media.You should probably only buy one of these versions of Windows if you have need of features like ReFS or enterprise level of control over desktops. The great folks at Puget Systems, however, have run some tests and shown that the version doesn’t really matter for sake of pure performance. There has been some debate that, when using a very high core count CPU like the 64 core / 128 thread Threadripper 3990x (affiliate link to Amazon), there is a need to use Windows 10 Pro for Workstations. More Versions of Windows Skip If You Chose Home or ProThere are more versions of Windows 10 called Windows 10 Pro for Workstations and Windows 10 Enterprise. I happen to be choosing Windows 10 Pro for my build. If you skipped the section above about buying Windows the installation media can be downloaded here. While this may seem scary to you don’t worry! This will only take a few easy commands and this guide will walk you through it. Creating The Install USB DriveIn this guide we’ll be using the command line in OS X to create the install drive. By “mounted” I mean we’ll figure out where OS X put the drive and how we tell it where to find it when we want to use it. In the search bar that comes up type “Terminal” and press enterThis will result in a screen that looks something like the following:With this screen up we’re going to use the command diskutil list to determine where OS X “mounted” the drive. Hold the command key (⌘) and press space or click the search button in the upper right of the screen Given that 16 GB drives are on sale, at the time of writing this, for $5 on Amazon (affiliate link) drives that are big enough can be easily found.Once you’ve plugged in the USB drive start up the terminal. First Step — Plug in a USB drive and figure out where it is mountedGiven that the installation media for Windows is a little more than 5 GB you’ll need a USB drive bigger than that. Second Step — Erase the disk and make it useable by WindowsTo do this we’re going to use the diskutil command again but with different options. In my case it is /dev/disk2 as pointed to by the arrow. Copy the /dev/disk text for the drive you find. Look for the one that is listed as both external and physical and that matches roughly the size of USB drive that you plugged in. We’ll do this by using the hdiutil command with the mount option. Third Step — Mount the Windows 10 Install Media so it can be copied to the USB driveAs mentioned before “mounting” is the process of having OS X make a hard drive or, as in this case, a file that contains the contents we want on a hard drive available to be used. When it’s done you’ll see something like the following:If you’re curious about the technical details about how we formatted the USB stick, we used the FAT32 format (specified by the MS-DOS option) and a Guid Partition Table (specified by the GPT option). A limitation of the FAT32 drive format is that it cannot hold files larger than 4 GB and the Windows installer now has a file larger than that. In my case they the folder /Volumes/CCCOMA_X64FRE_EN-US_DV9 as seen below: Fourth Step — Copy the files over to the USB driveWhile this may seem like a simple drag and drop copy this we actually need to do something a little special. Run the following command to mount this file for use:Hdiutil mount ~/Downloads/Win10_2004_English_x64.isoOnce this has run hdiutil will tell you where it put the files. If will likely be named something like Win10_2004_English_x64.iso and be located in your Downloads folder. Free slot games for macIf you don’t have it installed run the following command:More detailed instructions for installing Homebrew on OS X can be seen here. Step 2 — Install Homebrew if you don’t have itContinue to step 3 if you’ve already got Homebrew installed. As the copy starts you’ll see the files flash by as they’re moved over to the drive. If it does, click ok so that the copy can continue. Step 1: Copy everything BUT install.wim to the driveTo do this we’ll use the rsync command as follows:Rsync -vha -exclude=sources/install.wim /Volumes/CCCOMA_X64FRE_EN-US_DV9 /Volumes/WIN10This may ask you whether you want to allow Terminal to have access to a removable drive. Given this little issue we’ll have to do this copy in a couple steps. To do this type the following and press enter:Wimlib-imagex split /Volumes/CCCOMA_X64FRE_EN-US_DV9/sources/install. Type the following and press enter:Mkdir /Volumes/WIN10/sources Step 5 — Use wimlib-imagex to split up install.wim and save it to the USB driveWe’ll use part of the newly installed wimlib to handle both splitting up the install.wim file and saving it to the USB drive. To install it run the following:Brew install wimlib Step 4 — Create a new directory on the drive for the split up install.wimTo create a new directory from the command line we’ll use the mkdir utility. We’ll use it to split up the install.wim file so that we can copy it to the USB drive. This is because wimlib is a set of functionality to deal with wim files.
0 Comments
Leave a Reply. |
AuthorTiffany ArchivesCategories |