by

Keymagic.sys Error Mac Boot Camp Error

  1. Keymagic.sys Error Mac Boot Camp Error Codes
  2. Keymagic.sys Error Mac Boot Camp Error 8
  3. Keymagic.sys Error Mac Boot Camp Error 10

Intro

With macOS High Sierra Apple introduced the APFS filesystem with improved integrity protection. You can boot into Windows just fine, but when you wish to load a Boot Camp OS within a virtual machine the loader complains about a missing disk or some missing EFI elements. Eventually you get a blue Boot Manager screen with a bunch of options. According to VMware is UEFI missing an APFS driver.

This is also the case when installing an EFI based operating system directly in the VM without using Boot Camp.

Make changes to the Boot Camp Control Panel. It’s that simple! Once you are done with the above steps, you can go back to the second account and assign primary user account back to admin once again. Are you facing any other issues related to Boot Camp on your Mac or Windows machine? If you are a Mac user, you know that installing Windows 10 isn't as straightforward as many people may think and Boot Camp Assistant can be a challenge especially when creating a bootable Windows USB installation USB. How to Boot from a Windows 10 USB Installer and Open a Command Prompt Window. Restart the Mac and immediately hold down the option key until then Start Manager icons appear. Choose the external drive icon with the label EFI Boot. You should see a window similar to the image shown below. When this occurs, press the shift+F10 key combination.

To make it work you need to losen the integrity protection of your entire Mac. On some forums people just disable the protection completely, but I highly recommend to not doing that! It also protects against some nasty malware attacks on a deep system level. What I suggest to do is to only disable the protection on the filesystem.

This is not ideal either, but at least Fusion can access the Boot Camp partition while not exposing other layers to attacks. Until VMware finds a way to access Boot Camp in a secure way this is all you can do. They are working on it though:

  1. If Boot Camp Assistant says that your disk could not be partitioned. If Boot Camp Assistant stops responding or says that Boot Camp installation failed. If the Boot Camp installer doesn’t open after using Boot Camp Assistant. Install Windows 10 on your Mac with Boot Camp Assistant. Restart your Mac in macOS or Windows.
  2. Boot camp stuck on “Apple Keyboard” for over an hour. Installing boot camp on the on the new MacBook Pro. After it boots up in windows it continues installing boot camp but has been on “Apple Keyboard” for over an hour.
  3. Start up your Mac in macOS. Use the compatibility tables to make sure you have a Mac that supports the version of Windows you’re installing. If your copy of Windows came on a DVD, you might need to create a disk image of it to work with Boot Camp. Connect a 16GB or larger USB flash drive that you can erase.
  4. I'm going to show you how to windows 10 on mac os high sierra with boot camp. I did run into some boot camp issues but once fixed, the windows 10 installatio.

No APFS driver in UEFI renders the Guest OS unbootable when the Guest boot volume is using APFS.

Rest assured we are very excited about and interested in leveraging the new capabilities found in Apple’s new File System, but for now it will give you an OS that you can not boot in a Virtual Machine.

As such, during the installation, be sure to NOT check the ‘Use APFS’ checkbox, otherwise you will render the VM unbootable.

The bandage

Warning: These are not the best fixes because you are lowering the security of your system. A real fix can only be done if macOS and Fusion play nice together, keeping the app sandbox intact. But given the nature of I/O access to the BootCamp partition such high security method will be close to impossible in the current app/OS design.

In case you still want to continue, the options you have are:

  • Don’t enable the more secure APFS during the macOS upgrade when APFS is not yet applied;
  • Bypass the filesystem protection by granting full disk access to Fusion;
  • Bypass the filesystem protection by completely disabling it in the core OS.

Method 1: Full disk access for Fusion

Why is this bad? You should never allow apps full access to your entire Mac. Apps can carry malware or really bad bugs, even those from well known companies like VMware. Instead each app should be able to function perfectly within its own sandbox. Granting full disk access to an app is like giving it a key to your house and blindly trusting them, their friends (i.e. third party components) and anyone else they see fit with access to all your data. They can do anything with it, from deletion, alteration and encrypting your files for ransom all the way to uploading your stuff to the wide public world.

Thanks to Joaquin in the comments. I haven’t tested this method yet myself.

  1. Go to System Preferences > Security and Privacy
  2. Click the Privacy tab

Keymagic.sys Error Mac Boot Camp Error Codes

You may need to click the lock in the bottom-left corner and enter your password in order to make changes.

  1. On the left find Full Disk Access
  2. In the right pane find and enable the checkbox next to VMware Fusion

Method 2: Full disk access for everything

Why this one is bad is obvious. /monotype-corsiva-free-download-windows-7.html. It’s like the note on method 1, but way worse. Disabling the system integrity protection (SIP) is like removing the walls from your house. The only file system protection you will have is stupid luck.

Keymagic.sys Error Mac Boot Camp Error 8

  • Reboot into Recovery-mode, holding CMD+R until the Apple logo appears.
  • Go to Utilities menu > Terminal
  • Enter:

The mac reboots. When it is done create the Boot Camp VM. You will get an error saying you might not be able to run the VM, but it will be just fine.

Undo the change

If you wish to undo the change to re-enable the CSR setting on the file system, redo the steps above and instead of the command run this:

You can also do ‘enable’ which should enable all parts, but ‘clear’ will reset them to the OS defaults. At the moment the outcome is the same. However, macOS may change something in the future and intentionally disable a part of CSR and then ‘enable’ could mess things up a bit.

Modern EFI or legacy BIOS

When you are installing an EFI based OS to install directly in VM (non-boot camp) try a BIOS variant instead and create a custom VM with legacy BIOS enabled instead of EFI. Otherwise it may work as well, but in my trial and error the BIOS combination came out best.

If you like this article or it helped you in some way, please consider a (small) donation to keep it online for others to find.

Keymagic.sys Error Mac Boot Camp Error 10

Changelog
2017-10-19 – I restored the protection on my Mac. My intention was to run LiquidSky through Fusion which used to work great on Fusion v8, but since v10 it is lagging like crazy. So for games I now rather boot to Windows instead of using a virtual machine. Can’t wait for LiquidSky to launch their Mac app and finally be free from Windows.
2017-10-23 – Added section about EFI vs BIOS.
2017-11-03 – It’s interesting how many visitors this post alone gets. 25 50 unique views per day is not very common for my site, especially the click through rate from Google at 11.4%. Imagine how many users are struggling with this problem.
2017-11-03 – Changed undo command to ‘clear’.
2019-10-23 – Rewritten parts to include the steps from Joaquin.
2019-12-26 – Added warnings with explanations.

Related stuff