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.
Related Forum: macOS Mojave
Top Rated Comments
How about updating Boot Camp Control Panel in Windows to support ‘retina resolutions’, APFS to be able to select Boot partition or reboot to macOS?
How about releasing a APFS Windows driver to be able to read macOS files?
How about adding NTFS write compatibility to macOS.
Simple thing. Apple is doing nothing to solve them.
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.