Separate names with a comma.
Discussion in 'Mac Pro' started by wulai, Oct 19, 2018.
Upgrade mojave Boot camp Assistant is not available. This Mac does not support Boot Camp
Yes, we’ve known that for a fairly long time now. I guess you must have blinked
Sometimes it seems like Apple is deliberately trying to drive away customers by arbitrarily dropping support for features that have been trumpeted in the past.
All part of the "planned obsolescence" push.
Can still be done with a Windows USB or DVD installer by holding option at boot. The partitioning is the only tricky part (or better yet, use a dedicated Bootcamp hard drive).
All I can suggest is to submit a bug report for it, although I doubt they'll add that feature back in. Maybe if they provide boot screens for non-EFI cards.
I think it's very telling that Apple hasn't addressed the APFS issue in any of the last three macOS releases (all of which incorporated APFS to varying degrees). We're talking about one of the most valuable companies in the world. If they felt it was necessary to craft an APFS-compatible version of Boot Camp Control Panel they would have done it by now. The fact that they're just expecting everyone to option-boot and therefore disabling bootcamp entirely in Mojave for the cMP tells me that they're thisclose to deprecating it entirely. I bet that happens by 2020.
I've just discovered the latest Boot Camp 6.1 control panel in Windows shows APFS macOS drives. After installing the correct Boot Camp drivers for your Mac Pro you can then install the 6.1 drivers (e.g. iMac Pro).
So are the iMac Pro 6.1 drivers override the cMP drivers or they coexist?
How to install the 6.1 drivers
LOL, figures. Guess I have to eat my words yet again. Thanks for reporting this. I was waiting for 1809 to be re-released before setting up a new Win10 drive but maybe I'll just go ahead and install 1803 and test this out.
--- Post Merged, Oct 20, 2018 ---
Windows is smart enough to use the best available driver. There's no danger in installing a newer driver set as they will only update the older drivers in cases where the hardware matches.
--- Post Merged, Oct 20, 2018 ---
MisterAndrew explains here
--- Post Merged, Oct 20, 2018 ---
Yeah I think the 6.1 package just updates the core Boot Camp Sevices and adds a few extra drivers the cMP doesn’t need, but that doesn’t hurt anything.
So I tried to update my 6.0 bootcamp driver, but it complained that another version is already installed.
Installed and working well here too... I did a small writeup on it before I found one elsewhere so I won't post it. Thanks for making a thread. Good to have it working normally again.
I ran into that issue too, because at first I installed the Mac Pro 6,1 drivers which are 6.0. You have to right click on the Bootcamp.msi file and select uninstall. Then you can install the 6,1 drivers.
For some reason right click did not bring uninstall option. So I had to find the correct BootCamp.msi and uninstall through CMD thanks to @bookemdano
Nuts! I downloaded the 6.1 drivers and installed them in a Win 10 legacy-BIOS boot version. It didn't work. Everything completed (almost too fast I thought) but it said it finished installing. But the Boot Camp Manager icon did not appear in the task bar at all. And then when I tried to open the Boot Camp Manager from the Program directory it wouldn't open. It didn't complain, just nothing happened. I checked its properties and it said it was the new 6.1 version just installed a few minutes earlier. I tried reinstalling 2 more times with the same results.
I was updating from 5.x drivers and didn't get a message about another version being installed so I didn't do any uninstall. I did have to install from the command line because I did get the message that it wasn't compatible with my hardware, but that was expected. I used the workaround recommended in the other thread at: https://jeffw.net/2015/09/08/this-v...s-not-intended-for-this-computer-model-fixed/
However, I wonder if that is right? It runs bootcamp.msi from the Drivers/Apple folder instead of running BootCamp/Setup.exe which I would have normally double clicked to install the Bootcamp package. Could that be the problem, or is that what everyone else is doing? Also I'm still on BootRom 138-. Do I need 140-?
That should be OK. The only BootCamp.msi is in the drivers\Apple folder from what I remember
Yeah. And I know it loaded a new Boot Camp Manager file since the old one disappeared and the new one has the correct version number. But for some reason it doesn't work. I wonder if it needs the 140 BootROM to function, but I would still expect the icon to show up in the task bar? That feels like some sort permissions problem and I don't know enough about Windows to troubleshoot that?
Well, I am on 140 so that may have to be some sort of permissive. I was first on the version 5 drivers, then installed 6 from nMP, then I had to uninstall the boot camp service to install the 6.1
Yeah, but I can't imagine any way the firmware could affect the icon from showing up. It's 3 am here so I think I'll wait to see if anyone has an idea tomorrow, else I'll be up all night fooling around with it.
I would try uninstalling first and then install. I see this as the only difference in your installation method.
I hade to use thirdpart uninstaller to get rid of BootCamp services. I used Revo uninstaller. There is a try version that I used. Use the scan part and "select all" to get rid of all. Just a suggestion. Did a restart and then installed BootCamp 6,1.
Yes, I just got done uninstalling BootCamp services version 5 by right clicking on the BootCamp.msi file and that seemed to just delete the BootCamp Manager as was suggested above. I then installed the 6.1 version again and this time it worked. I now have the 6.1 Win Boot Manager showing up in the task bar and it identifies both of my APFS MacOS's (Mojave and HS) on separate SSDs as simply MacOS, while providing full names of the HS installs that are on HFS HD's. So I chose the first of the MacOS identified disks and it booted me back to Mojave.
The only problem I found (just a first quick look) was that my Magic Mouse was no longer working in Windows so I'll have to fix that. Probably deleted the BT Link Key somehow, or perhaps I need to roll back to the previous v5 driver. I'm in a hurry to head out so I'll fix it later.
So bottom line, I guess you have to uninstall version 5 BootCamp Services before installing version 6, even though there was no message that was necessary as there was when people went from v6 to v6.1.
I didn't have to do that. It just worked. Then on next reboot, it reinstalled the proper BT/MM driver. Just go to your device manager and let it find the proper driver. That SHOULD work. It did for me...
HaHA! Microsoft has done a rather good job of Windows obsolescence without any intentional planning. Well.. as long as you don't count all of the Dell & HP printers and accessories dropped over the years that are still working great on Mac OS.