![]() You can also try running the driver setup in Compatibility Mode (Right click the setup exe, Properties>Compatibility> Check the box "Run this program in Compatibility mode" > Run the setup). Have you tried this method? Have you tried resetting NVRAM and resetting the SMC? Also did you unzip the WindowsSupport folder before executing the Bootcamp setup? What exact process(es) is(are) failing to install? Just to be sure, you're using the WindowsSupport files that you got from Steps 4/5 in the linked tutorial and not another Mac or a download from online, correct? The WindowsSupport files created from those steps are specific to your Mac's make/model. Correct - I grabbed them straight from Apple. ![]() It's just cosmetic and IIRC, if you go to 'System Preferences > Startup Disk', choose your Window's partition as the startup disk, and restart, then 'EFI Boot' in the boot manager should change to the same name as your Windows volume. Edit: You can also try running the driver setup in Compatibility Mode (Right click the setup exe, Properties>Compatibility> Check the box 'Run this program in Compatibility mode' > Run the setup). ![]() The 'EFI Boot' option in the boot manager has been a common occurrence for 9+ years when doing installs outside of using the typical Bootcamp Assistant method. As long as what specs your enclosure has is at least USB 3.0+, you shouldn't run into issues. ![]() Intel has restricted NVMe to Thunderbolt 3 to a few devices that are sold with SSD's and a non-removable cable. It's, at best, USB 3.1 Gen 2 since there are no NVMe to Thunderbolt 3 enclosures on the market. The enclosure you have is not a true M.2 to Thunderbolt 3.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |