
It allows you to install Windows on an external drive without first having Windows installed on a PC or in a virtual environment. But the method we’re going to outline here is a bit different. They range from creating clones of an existing PC installation or using Microsoft IT tools for installing Windows. There are actually a few ways you can successfully install Windows on an external drive. Installing Windows on an external drive would be a great solution to the problem of available space, but as we said, Boot Camp and Windows impose a restriction on installing to an external drive.

While Boot Camp Assistant can partition your startup drive for you to make room for Windows, there are bound to be many of you who just don’t have room to spare on your startup drive to install Windows. One of the downsides to Boot Camp and the Windows installer is that it restricts you to only installing Windows on your Mac’s internal drive. It’s a nice capability that lets you select – at boot time – which operating system you wish to use: macOS or Windows. This latter suggestion advising that it "might cause more issues," such as bricking the install altogether.Boot Camp and Boot Camp Assistant allow you to install Windows on your Mac. ISO and install a clean Boot Camp version of Windows 10, version 1903 instead. Or, if you're daring, you can even try jumping up to macOS Catalina." It also suggests using Microsoft's Media Creation Tool to build a new. Lifehacker suggests, "If you're not on macOS Mojave, it might be time to try giving that a shot. While Microsoft says it is working on a resolution to the problem and gives an estimated delivery of this as "late July," there may be other options worth a try. "Updating your Apple Boot Camp Windows Support Software drivers may allow you to update to Windows 10, version 1903," it states, adding, "you may be able to check for updated Windows support software, in macOS, choose Apple menu > App Store, then install all available updates."

Microsoft offers a workaround, of sorts, to the block. Apparently the error is being caused by a "compatibility hold" that has been put in place for devices with a "MacHALDriver.sys dated Septem01:57:09 or older in Windows\system32\drivers."
