MP All Models BootCamp releases/updates tracking thread (MP7,1 BootCamp)

[w1z]

It also appears brigadier stopped working due to a ssl error of sorts and I badly need the drivers.

Does anyone have the latest bootcamp drivers for the imacpro?

Edit: sorted. I downloaded the BootCampESD.pkg and unpacked WindowsSupport.dmg

 

[w1z]

Just came across this and thought I'd share - A new fork of Brigadier with bug fixes and enhancements - https://github.com/corpnewt/brigadier

 

[tsialex]

Re-issued MP5,1 BootCamp version 1.0.1.1293150744, from 2015-02-09, re-signed with the new certificates, is Product-ID 041-84868.

I'll update the first post later.

 

[tsialex]

Btw, re-issued iMacPro1,1 BootCamp 041-91731.

 

[eksu]

My 'Boot Camp Control Panel' (6.1, UEFI Windows Install) wanted to update automatically, and I let it.

On the new version now, I can choose to boot between my Mojave SATA SSD and my Windows SSD, but my PCIE Catalina HD is no longer listed.

I might jump around a couple different versions and see if this gets resolved or if I can roll back.

 

[cdf]

On the new version now, I can choose to boot between my Mojave SATA SSD and my Windows SSD, but my PCIE Catalina HD is no longer listed.

I've experienced the same thing (on a CSM Windows install) and went back to 041-88815.

 

[eksu]

Anyone have a 041-88815 link or do I need to scavenge my hard drives for my old files? Does Brigadier allow you to select older versions?

 

[tommy chen]

Anyone have a 041-88815 link or do I need to scavenge my hard drives for my old files? Does Brigadier allow you to select older versions?

https://forums.macrumors.com/threads/bootcamp-releases-updates-tracking-thread.2177384/post-27272830

 

[eksu]

• Please note that Apple remove previous released versions, so you can only download the most recent one for each Mac, exception of this case is iMac Pro that we can download two BootCamps for now.

Bummer, thanks.

 

[cdf]

I think the download is still available. You can search for it in SUS Inspector.

 

[tsialex]

I think the download is still available. You can search for it in SUS Inspector.

Apple removes it from the SUCatalog and from the SU server, if it was like you are thinking the URLs from the first post still worked.

BootCamp releases are not like iOS firmwares where you had to keep the full history available for updates, just the most recent one.

 

[tsialex]

2019 MacPro BootCamp released, product-ID 041-20483, 577,9MB, version 1.0.0.0.1.1572633498.

 

[tsialex]

 

[Demigod Mac]

6.1.9 just showed up. Safe to install for a MacPro5,1?

 

[tsialex]

6.1.9 just showed up. Safe to install for a MacPro5,1?

View attachment 882485

Weirdly, both updates are not on the SUS updates list. Not by name or version.

 

[tsialex]

Apple released a new BootCamp for 2019 Mac Pro:

Original Release Date:	Version number:	ProductID:	Size:	Mac:
2020-03-18	1.0.0.0.1.1580283400	061-51424	708,5 MB	MacPro7,1

Btw, BootCamp for MacBook Air 2020 was released too, 041-84890.

 

[startergo]

I am using iMacPro1,1's 041-88815 drivers. I see all my drives:
HFS+, APFS Windows (EFI)
I used GPT Fdisk to rename the boot entries in the Boot Camp Control Panel for Windows. HFS+ volume reads correctly the boot entry too, but all APFS volumes (Catalina and Mojave) always read "Mac macOS" no matter how I set them up in GDISK. Has anybody successfully renamed an APFS boot entry?

 

[cdf]

I am using iMacPro1,1's 041-88815 drivers. I see all my drives:
HFS+, APFS Windows (EFI)
I used GPT Fdisk to rename the boot entries in the Boot Camp Control Panel for Windows. HFS+ volume reads correctly the boot entry too, but all APFS volumes (Catalina and Mojave) always read "Mac macOS" no matter how I set them up in GDISK. Has anybody successfully renamed an APFS boot entry?

I've been looking for a way to do this. However, I wouldn't be surprised if the "Mac" name is hardcoded for APFS.

 

[startergo]

I've been looking for a way to do this. However, I wouldn't be surprised if the "Mac" name is hardcoded for APFS.

I wonder where is the actual location of the bootcamp panel in Windows? This is really inconvenient as if you have multiple APFS boot entries you can't properly boot.

 

[cdf]

This is really inconvenient as if you have multiple APFS boot entries you can't properly boot.

What's more, if you have multiple MacOS installations in the same APFS container, the Bootcamp software in Windows only detects one!

 

[tsialex]

Apple released an updated BootCamp for iMac Pro today, first post table updated.

Original Release Date:	Version number:	ProductID:	Size:	Mac:
2020-04-16	1.0.0.0.1.1586398929	061-97204	695,4 MB	iMacPro1,1

 

[mrkapqa]

Hello, thanks for this thread;
had trouble installing Windows 10 Bootcamp software on a MP4,1>MP5,1; the downloaded software via Brigadier and else always complained that it must be run for Windows 7;
with the help of this guide here
https://crystalidea.com/blog/classic-mac-pro-and-windows
it finally functioned, after i found this thread here and was able to download the next newer .pkg after

BootCamp-041-55643

which seems no longer downloadable (so i just took the next on the list which gave the proper driver package aswell).

 

[Rastafabi]

Hello, thanks for this thread;
had trouble installing Windows 10 Bootcamp software on a MP4,1>MP5,1; the downloaded software via Brigadier and else always complained that it must be run for Windows 7;
with the help of this guide here
https://crystalidea.com/blog/classic-mac-pro-and-windows
it finally functioned, after i found this thread here and was able to download the next newer .pkg after

which seems no longer downloadable (so i just took the next on the list which gave the proper driver package aswell).

I usually install bootcamp completely manually these days. To do so (you would get a more current BOOTCAMPO support package via brigadier

brigadier.exe -m iMacPro1,1

If I remember correctly this should install the drivers. Incase it does not work you'd need to run brigadier with the -o flag to save the download

brigadier.exe -m iMacPro1,1 -o BOOTCAMP_DRV

which should save the installer files to a directory named BOOTCAMP_DRV within your home folder. You might also specify another directory like so:

C:\Users\[user_name]\Downloads\BOOTCAMP_DRV

Once saved you can install the BOOTCAMP.msi file using the cmd-prompt.

msiexec /install C:\path\to\BOOTCAMP.msi

the hardware related drivers need to be installed manually though. Search the downloaded directory for "driver install files (.inf I think, but just look for something the explorer calls driver setup information or similar), then install them from the explorer with a right click > install.

I hope all those information are correct as I recalled them from memory. Another tip is to install 7zip manually beforehand as brigadier might error out downloading it automatically to unpack the driver.