Sometimes there’s just that one or two Windows software that is not available on the Mac that requires non virtualized environment. Or sometimes people are in a work environment where the IT simply doesn’t support Macs/virtualized OS. And those who need Windows but don’t want to pay extra or be bothered with virtualization.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases macOS Mojave 10.14.5 Boot Camp Update to Address iMac and Mac Mini Bug
- Thread starter MacRumors
- Start date
- Sort by reaction score
As I said before ⬇︎ ⬇︎
Agreed
Also
External devices like the ones which need a serial connection were/are notorious for not working in a VM, haven't used one for years though, maybe support got a lot better.
Apple today released a new macOS Mojave 10.14.5 Boot camp update, which is designed to address a bug that prevented the creation of a new Boot Camp partition on a iMac or Mac mini with a Fusion Drive.
The new software can be downloaded from Apple's support document accompanying the update.
The software update is available for iMac and Mac mini users, and won't be available to those who have other Mac machines.
Boot Camp is designed to allow Mac users to set up a partition to run Windows, providing access to PC-only apps and content.
Apple's Boot Camp update for macOS 10.14.5 comes about a month after the release of the macOS Mojave 10.14.5 update.
Article Link: Apple Releases macOS Mojave 10.14.5 Boot Camp Update to Address iMac and Mac Mini Bug
I have a 2012 iMac 13,2 with a 3TB Fusion Drive. When I updated to macOS Mojave, I loss my Windows Partition. I was hoping this update would address this issue but after installing the file I still can not install Boot Camp. I was wondering if anyone had any luck after this update.
Hmm.. Finally!
I tried so much with my iMac (last year, 3TB Fusion).. Deleted core storage, added, modified.. I don't know what I did, but tried almost everything. And almost any installation of Windows 10 went wrong, keep looping at startup, or just wont start.
Now I don't even try it anymore.. But with this update I want to try it again.
Is there a way to completely reset the Fusion drive? I know that there is a fix fusiondrive command. But that one didn't worked anymore..
I tried so much with my iMac (last year, 3TB Fusion).. Deleted core storage, added, modified.. I don't know what I did, but tried almost everything. And almost any installation of Windows 10 went wrong, keep looping at startup, or just wont start.
Now I don't even try it anymore.. But with this update I want to try it again.
Is there a way to completely reset the Fusion drive? I know that there is a fix fusiondrive command. But that one didn't worked anymore..
Me too. I am curious if this is thé fix for the 2012 iMac 3TB fusion issues. Anyone able to share experience or expertise?
I sure would like to see Boot Camp support booting from external drives. On my 512GB internal drive on my MacBook Pro, space is at a premium. It’s a big pain to get external boot working without Boot Camp supporting it, I’ve been through the steps.
I’d also like to see eGPU support in Boot Camp. Again, it’s possible to get it working but it’s a pain.
[doublepost=1560530474][/doublepost]
I don’t think there’s significant risk to Mac OS X. Using a VM is great, you don’t have to do all the rebooting, Windows is in more of a sandbox, you get nice integration and all that. The only downside is more memory being needed.
I’d say that Boot Camp is really only worth it if you’re gaming, or doing something that really needs all the memory your computer has.
I’d also like to see eGPU support in Boot Camp. Again, it’s possible to get it working but it’s a pain.
[doublepost=1560530474][/doublepost]
I don’t think there’s significant risk to Mac OS X. Using a VM is great, you don’t have to do all the rebooting, Windows is in more of a sandbox, you get nice integration and all that. The only downside is more memory being needed.
I’d say that Boot Camp is really only worth it if you’re gaming, or doing something that really needs all the memory your computer has.
2. Rebooting to APFS drivers from the Windows BootCamp control panel definitely does NOT work on either my iMac (2015) or MacBook Pro (2017). Neither does the control panel work great with high DPI settings. I checked numerous times that I have the latest version available.
4. Apple and Microsoft have broad patent/IP cross-licensing agreement. In fact they include NTFS driver in macOS for quite a while. It even has an experimental write support that has to be explicitly enabled but in my experience it always managed to corrupt the partition.
You want proof, I have it installed on my 2012 MacMini.
My MacMini has an SSD and a HDD, HDD contains Windows.
What is side by side, like on the same disk, fusion drive or what?
I said you can install Windows without bootcamp, that's a fact, just not that easy.
Last edited:
I have the same machine with the same drive, and I came to the comment thread specifically looking to see if anyone else had tried this; so thanks for your insights on this.
That said, I'm afraid I'm not surprised that it didn't fix the issue for 2012 iMacs. My understanding is its a rather complicated matter, in this very specific configuration, but here's my best attempt at a layman's interpretation of the situation: Going forward, the 2012 models are no longer going to be able to support Windows installations on hard drives which exceed 2TB, in part because Windows itself does not support boot volumes outside of the first 2TB of the hard drive on that generation of hardware -- and possibly in conjunction with bugs associated with the partitioning scheme required to accomplish the installation of Windows, within those constraints. So in previous versions of Bootcamp, it sliced up the hard drive so that it basically looks something like this ...
|----- MacOS Hard Drive (partition 1 of volume 1) ----- | (Windows size minus 2TB)
| -- Windows (volume 2) -- | (2TB)
| ---- MacOS Hard Drive (partition 2 of volume 1) ---- | (3TB)
... where the sizes indicated at the end of each line are the location on the disk at which that partition ends.
At the time, I thought Apple had come up with a really slick and interesting method for solving that 2TB boundary. I guess Apple has concluded that that's not so much true anymore.
iMac 2013 1.12 TB fusion. Was excited about this update. I did the incremental MacOS update to 10.14.5, then bootcamp update. Rebooted for good measure. Bootcamp can't partition drive. Says to repair in disk utility. Ran first aid on the drive. Tried bootcamp again, same problem. Nothing has improved for me since before this special bootcamp update.
Last edited:
I have a new Mac Mini 2018 with the System and Applications on the internal and the User folder on an TB3 connected SS3. I cannot install the Boot Camp Assistant Supplemental. Throws up an error. Conversely, if I just try to install the regular Boot Camp Assistant, it asks me to remove all external drives, which of course I cannot do since my User Folder is on the external TB3 drive.
Am I stuck or is there a workaround people know of? Thanks!
Am I stuck or is there a workaround people know of? Thanks!
Shouldn't the Windows drivers for your GPU support higher resolutions? What's Apple got to do with it? I've read the iMac Pro version of Boot Camp supports selecting APFS drives to boot from and there's a way to force install it. Why in the world Apple has not released that update to everyone is utterly beyond me. For such a rich company with so many resources, it always seems like they don't have enough programmers to do things that even tiny 3rd party companies manage to do...kind of ridiculous, IMO.
I just bought MacDrive. It lets me read/write HFS+ volumes (e.g. I can let KODI read my HFS+ external USB3 media drives from Windows 10 on my Mac Mini now. So far, zero issues here. It also has a beta APFS driver that is currently read only, but my APFS Mojave drive is perfectly readable from Windows 10 now with it. Everything works as a regular file system (no special programs needed to transfer files and thus KODI works, etc. fine. I think that was worth $60 to me. Apple will never bother.
Apple is cheap. They licensed SMB3 I think for one OS version and then decided to write their own code to avoid paying Microsoft a dime. It's been buggy ever since.... Here, I bought Tuxera NTFS and I can read/write NTFS and format drives as well no problem. Between the two, I have full interoperability between operating systems other than read only for APFS from Windows 10 (for now until it's out of beta; you wouldn't want a bug causing an error on the drives by releasing it too soon).
Apple isn't about solving problems these days. They're about making money and that means phones phones and more phones. They couldn't care less about Macs anymore. Jony Ive even had enough and left.
My current problem is stranger. I bought a Samsung 2TB SSD for my 2012 Mac Mini (and 16GB ram upgrade) and installed Windows 10 boot camp from El Capitan on a 400GB partition (leaving 1.6TB for OS X). I then upgraded El Capitan to Mojave. Everything seemed to be working fine (other than the lack of being able to change the startup drive from BootCamp). I then turned TRIM on in Mojave. It failed to boot. After much recovery playing around (first aid showed no errors after the first time), it somehow decided to boot OK. Everything seemed fine and write speeds were back up to over 500MB/sec here (Windows 10 had TRIM on all the time and also had those speeds). But sometimes when I reboot the computer and/or switch to OS X after using Windows 10 (which boots correct every time and in less time than OS X even), it just gives an Apple logo and no boot progress (light to my optical mouse is out and the USB3 hub....)
I boot in VERBOSE (CMD-V) mode and it goes into this weird reboot mach kernel loop (like a goto print in basic programming) and before that point is goes so fast I can't see the last thing it's trying to do (I might have to video it to find out as I know of no way to pause or slow it down). I then have to play with recovery, etc. (can't point to any single thing that works; it just eventually boots OK again; I thought it was startup selection the one time and a manual bless command another time, but neither seem reliable). So now I don't want to exit OS X as it might not come up again without headaches of trying to get it to boot. I've tried resetting PRAM, NVRAM, etc. Nothing.
After reading some more about APFS, I can't help but wonder if something somewhere is getting the "Preboot" location confused or something of that nature. Manually setting the bless file (which then just points back to the preboot location automatically) seemed to get it going the last time, but I don't know why as it seemed to point to the same place before/after, BUT the "bless --info" option (used in recovery mode mind you) said something about the XML file boot location and the blessed one didn't match the "TRUE" location. WTF!? I don't know what that means, but it sure sounded like something in there wasn't agreeing with something else on what to boot and maybe those locked up boot loops were pointing at the wrong thing and causing it to try to reboot (which didn't work for some reason and ends up in that message just flying up the screen like a print/goto loop).
Whatever is causing it, it's pretty darn irritating. I'm seriously thinking of reformatting/partitioning and restoring El Capitan from external backup. There's always a chance it has something to do with this SSD drive and it was just a coincidence that it happened when it did (turning on TRIM). I could try turning TRIM back off again, I suppose, but then write speeds would steadily drop (and Windows 10 has TRIM on and it works 100% fine with the same drive on its partition and once OS X *DOES* boot, it works fine until I reboot (no signs of errors in disk utility or anything and full write speeds, etc.) But I suppose I'd try that before restoring El Capitan. I could, of course just abandon OS X and go to Windows 10 full time (not much on OS X that isn't available in Windows 10 save Subler and Logic Pro, the latter of which I only use on my Macbook Pro). My Mini is mostly a whole house server for KODI and for email/web browsing (occasional older games that are available in Windows under Steam anyway).
I keep trying to find someone that has a clue about these sorts of things as those errors only show up in Google on Hackintosh sites for some reason. But so far, NO responses in other threads (one on mojave installs, one I made myself and somehow I doubt I'll get a response here either). Mac users don't seem to be very knowledgeable about the inner workings of OS X (I suspect the Hackintosh guys ARE super knowledgeable, but I don't know they'd want to take a shot at a real Mac. It might be worth asking them on a Hackintosh forum).
Hi.
Maybe the Mojave update messed something with the partitions when doing the APFS conversion. This is what I’d try:
- backup Windows files
- backup macOS files
- Boot macOS internet recovery....
- Completely wipe all the partitions from the SSD: leave it on 2TB o empty space
- Install macOS Mojave using internet recovery
- Then install Windows 10 using BootCamp.
- Move back the backup files
and hopefully all works correctly.
Maybe the Mojave update messed something with the partitions when doing the APFS conversion. This is what I’d try:
- backup Windows files
- backup macOS files
- Boot macOS internet recovery....
- Completely wipe all the partitions from the SSD: leave it on 2TB o empty space
- Install macOS Mojave using internet recovery
- Then install Windows 10 using BootCamp.
- Move back the backup files
and hopefully all works correctly.
I just had a wake from sleep issue where my monitor didn't come on. I had to reboot to get it to come back on (tried unplugging monitor and even using the thunderbolt/mini-display port and nothing). I don't think I've ever seen this happen on my Mini in 7 years. This only happened since installing Mojave. I had a reboot with a black screen with Windows 10 as well one time, but I think that was a known recent Windows 10 update bug.
I've just tried, and no, it hasn't worked for me either. I'll be getting a new iMac in the not too distant future, so it's not a big deal, but it's disappointing all the same.