Install windows 8 mac refit

Bootcamp is actually leading me down the external device road. Lots of googling for drivers. I did manage to get everything working though. I have been trying to install windows 10 external SSD. However, there are random BSOD frequently. Any tips you can help? Many readers would appreciate an article about this topic. Good luck.

How to Install Windows 10 on Mac using Boot Camp Assistant

I ran into a series of problems getting Windows 10 installed onto my late MacBook Pro running I hope the author has actually performed this process because it is by no means as simple as what is posted here. In short, the full process is nothing short of a nightmare with Apple to blame for each of the problems along the way.

But there are some helpful, more realistic descriptions of what it takes to get everything to work elsewhere on the net. It is definitely possible to do it, but expect trouble. The hardware is great.

The drivers work really well. In fact you can just install Windows only on Apple hardware and it runs great. I am only using Windows for games, which I keep on an external drive, and for about 5GB of combined apps and documents.

How to Install Windows On Your Mac When All Else Fails - Hongkiat

Name required. Mail will not be published required. All Rights Reserved. Reproduction without explicit permission is prohibited. You will have to create it like mentioned before here to force an EFI boot of the installer. There will then be a progress bar loading files but unfortunately you will get stuck on a black screen in a few seconds To be finally able to load setup you need to flash MacPro4,1 firmware to MacPro5,1 firmware. But you will still have a different version after the upgrade flash. Apple does not seem to take great care about correct versioning with EFI standards as I understood from Rod Smith's comment here.

Install bootcamp drivers and enjoy AHCI without patches. Be sure to strip the bootmgr files from the installer disc or stick.

Bootrom MP B07 EFI 1. B03 EFI 1. B08 you could first try to continue without upgrading. Downgrading should be possible as well, definitely possible to version MP Otherwise the flash will not perform. If patch is running successfully you can see a big grey loader bar and the apple logo. Optical drives will open. See here how to easily disable SIP. Booting then will show Windows logo but will go black w o signal when login screen should appear.

The system will boot to login properly after only sec black screen without signal when using the DVI-I port instead. After successful login I could unplug and switch the port. Did not have time to investigate further. How do this? Thanks to Pavel Urusov. Sign up to join this community. This enables you to re-install rEFInd after the fact by running refind-install , should some other tool or OS wipe the ESP or should the installation go awry. In such cases you can use refind-install or install manually. In the past, the Mac's firmware was quirky enough that the Linux tools didn't always work reliably.

The matter seems to have improved with recent versions of Linux tools, but I can't guarantee success if you use Linux for this task. There is one significant issue with OS X If your setup is unusual, if your computer uses Secure Boot, or if you want to create a USB flash drive with rEFInd on it, you should read the man page for this utility.

Best 2018 Upgrade for all Macbook whites : Full install procedure Windows 7 Privet WinBook - 2018

Warning: OS X See Table 1 for details. If your ESP is not so mounted, refind-install will attempt to locate and mount an ESP, but this action is not guaranteed to work correctly. You can convert to a more conventional configuration using the mvrefind script after you've booted in EFI mode.

Prior to version 0.

Running Windows on a Mac, part 3: The complete how-to

I changed this because the default configuration for OS X If you're upgrading a working install of rEFInd to the OS X root partition, it's best to pass the --notesp option to refind-install. This option is described in more detail shortly. In either case, the details of the output differ depending on your existing configuration and how you ran the program.

Unless you see an obvious warning or error, you shouldn't be concerned about minor deviations from these examples. If you run into such a situation, or if you want to install in an unusual way, read on This option will boot the old version of rEFInd or the new one, if something went wrong and the old version continues to boot.

Before you do this, you should use rEFInd to identify the unwanted files—the filename and volume identifier appear under the icons when you highlight the option. You can then locate and delete them from within OS X. Before you delete the old files, though, you may want to copy over any changes you've made to the rEFInd configuration, icons, and other support files.

The refind-install script supports a number of options that can affect how it operates. Sometimes the refind-install script just won't do the job, or you may need to install using an OS that it doesn't support, such as Windows. In these cases, you'll have to install rEFInd the old-fashioned way, using file-copying commands and utilities to add the program to your EFI's boot loader list.

You can verify that this is the case by using the df command:. The Mac's boot process deviates a bit from EFI standards, and older versions of efibootmgr didn't always work properly on Macs. This problem seems to have gone away with more recent versions of efibootmgr , but using OS X may still be more reliable.

On the other hand, Apple's new as of OS X One of these methods is to do the job from Linux. This is an unusual configuration. If you're using it, you can proceed, making suitable adjustments to subsequent commands. Weird: A bug exists in some Lenovo computers and perhaps in some others, too that causes the firmware's boot manager to refuse to boot any boot loader that doesn't have the name Windows Boot Manager or Red Hat Enterprise Linux.

If you have such a system, you must pass one of those names in quotes rather than rEFInd to efibootmgr via its -L option. This bug was reported to Lenovo in mid-November , and by late , at least some Lenovos were mercifully free of this bug. You may also need to add options if your ESP is in some unusual location or if your system is unusual in some way. Consult the efibootmgr man page if you need help. On some systems, efibootmgr won't do what you expect.

On such systems, you may have better luck renaming the rEFInd files, as described in the Alternative Naming Options section. If you're an advanced enough user to be considering a manual rEFInd installation procedure, doing the job from the Recovery HD environment may be your best option. You can determine whether your Mac needs the x or IA32 build by typing the following command in a Mac Terminal window:.

You should also be aware of your OS X version and installation options. This report on the problem, and particularly the post by mic-marchen, suggests that the problem is related to a bug in OS X's bless utility, and particularly its --info option, that causes it to corrupt data on disks with 4 KiB sectors. These Advanced Format disks are becoming increasingly common, particularly at larger disk sizes. Therefore, I strongly recommend that you not type sudo bless --info to check the status of your installation if you have such a disk, or even if you suspect you might have such a disk.

I've seen Advanced Format disks as small as GB. The procedure for installing rEFInd on a Mac is similar to that for installing it under Linux, except that you must use the bless utility rather than efibootmgr to register the program with the firmware. To be precise, you should follow these steps:. When you reboot, your Mac should bring up the rEFInd menu, and should continue to do so thereafter. If you make changes that break this association, you can re-run the bless command if necessary, restoring the rEFInd files first.

This might be necessary after installing system updates from Apple or if you upgrade rEFInd to a newer version. This program attempts to keep rEFIt set as the default boot loader, but it also has the purpose of protecting the computer from launching the wrong OS after waking from sleep. Used in this way, rEFInd will still look for its own configuration file, refind. If you don't move the icons from the rEFInd package, your icons will continue to look like rEFIt icons, and you'll be missing the new icons for specific Linux distributions that rEFInd provides.

One final caveat: It's conceivable that rEFItBlesser is what's causing filesystem corruption for some users, so if you've been having this problem with rEFIt, it might be worth disabling this program and not using it with rEFInd.

Installing rEFInd Manually

If you want to remove rEFInd from your system, you can delete its files. The Mac will revert to booting using whatever standard boot loader it can find. Alternatively, you can use bless to bless another EFI boot loader. Warning: Windows 8 implements a fast shutdown feature that helps speed up shutdown and startup operations on a single-boot computer.

Unfortunately, this feature can cause filesystem corruption if it's used on a multi-boot computer. I've only tried it once, and it seemed fairly intuitive and easy to use, but I don't have detailed instructions on how to use it. If you want to use EasyUEFI, you'll have to use it in place of bcdedit at the end of the following procedure. One way to accomplish this goal, and to proceed forward once the ESP is accessible, is as follows:.

At this point, when you reboot, rEFInd should appear as your new default boot program.