MP 1,1-5,1 Installing Windows 10 in Legacy/BIOS mode in cMP with Boot Camp Assistant

[Sergey-Galan]

Although it detects hybrid partition it still Proposes and installs Windows UEFI:

If you choose to install Windows UEFI, do you want to make pure GTP from the hybrid? Or a ban on installing Windows UEFI on a hybrid?

I installed Windows 10 in Legacy mode and after booting got this:
View attachment 2384670

Your Disk signature failed. Something prevented Disk8 from completely disconnecting for signing.
You have this:
Volume BOOTCAMP 2 on disk8s3 mounted Build the main BCD store... Password:Install Language - en-US Loader GUID: {2d1b36ba-7fd3-488c-983c-4353bb4e7abf} Resume GUID: {4481dded-7860-4387-af33-7244fa55fb76} part - /dev/disk8s3 disk - /dev/disk8 scheme - GUID_partition_scheme scheme - FDisk_partition_scheme disksig - 00000000 Unmount of disk8 failed: at least one volume could not be unmounted Unmount was dissented by PID 292 dd: /dev/disk8: Resource busy disksig - 00000000 partoffset - 125059465216 diskbytes - 00,00,00,00,00,00,00,00,00,00,00,00,0 partbytes - 00,00,20,1e,1d,00,00,00,00,00,00,00,00,00,00,00 part - /dev/disk8s3 disk - /dev/disk8 scheme - GUID_partition_scheme scheme - FDisk_partition_scheme disksig - 00000000 Unmount of disk8 failed: at least one volume could not be unmounted Unmount was dissented by PID 292 dd: /dev/disk8: Resource busy disksig - 00000000 partoffset - 125059465216 diskbytes - 00,00,00,00,00,00,00,00,00,00,00,00,0 partbytes - 00,00,20,1e,1d,00,00,00,00,00,00,00,00,00,00,00 part - /dev/disk8s3 disk - /dev/disk8 scheme - GUID_partition_scheme scheme - FDisk_partition_scheme

It should be like this:

Volume Windows10 on disk10s1 mounted /Users/sergey/Boot Build the main BCD store... Install Language - en-US Loader GUID: {7a31eeaa-d7b5-4605-b44a-bf97683fda11} Resume GUID: {77a5f4bf-db2e-49aa-ba57-2ce95618ade6} part - /dev/disk10s1 disk - /dev/disk10 scheme - FDisk_partition_scheme disksig - 00000000 Unmount of all volumes on disk10 was successful 4+0 records in 4+0 records out 4 bytes transferred in 0.003642 secs (1098 bytes/sec) disksig - 2D5201E3 partoffset - 1048576 diskbytes - 2d,52,01,e3,00,00,00,00,00,00,00,00,00,00,00,00 partbytes - 00,00,10,00,00,00,00,00,00,00,00,00,00,00,00,00 part - /dev/disk10s1 disk - /dev/disk10 scheme - FDisk_partition_scheme disksig - 2D5201E3 partoffset - 1048576 diskbytes - 2d,52,01,e3,00,00,00,00,00,00,00,00,00,00,00,00 partbytes - 00,00,10,00,00,00,00,00,00,00,00,00,00,00,00,00 part - /dev/disk10s1 disk - /dev/disk10 scheme - FDisk_partition_scheme disksig - 2D5201E3 partoffset - 1048576 diskbytes - 2d,52,01,e3,00,00,00,00,00,00,00,00,00,00,00,00 partbytes - 00,00,10,00,00,00,00,00,00,00,00,00,00,00,00,00 part - /dev/disk10s1 disk - /dev/disk10 scheme - FDisk_partition_scheme disksig - 2D5201E3 partoffset - 1048576

 

[Sergey-Galan]

Excuse me that I do not immediately answer, I work and often turn off electricity, Russians destroyed many power plants and electric networks.

 

[Macschrauber]

Or a ban on installing Windows UEFI on a hybrid?

this would be nice to have an option to - I call it deactivate UEFI Windows ESP when installing in UEFI mode.

I do it (the ESP tools, for example mount from list and show bootloader) by renaming /EFI/BOOT/bootx64.efi to bootx64.efioff

so a Mac Pro can not boot this ESP directly without OpenCore, and so the risk, getting certificates in the nvram is lowered.

Deleting /EFI/BOOT works also. If renamed the disk can be easily set up to boot in a native UEFI machine by renaming back to bootx64.efi.

If you use bootx64.efioff my ESP tools show [Windows ESP (deactivated)]. Mount from ESP and show bootloader is part of MarintLo's OpenCore package for MacPros so it is widely spread.


If installed in Legacy mode imo no ESP should be written at all.

At least for the 2009 to 2012 Mac Pro Bootcamp also writes no UEFI ESP.

 

[Sergey-Galan]

tried again today with Windows 7 image , changed image from "en_windows_7_ultimate_with_sp1_x64_dvd_u_677332" to "de_windows_7_professional_with_sp1_x64_dvd_u_676919" and now the installation would start as normal, but stop sadly halfway through the process with error like "the starting configuration could not be actualised. please start ..."
with windows 10 image the legacy installation mode went trough flawless, very pleased.

the HDD has already MacOS partition (Mavericks) and i split the HDD in half, and formatted the latter half as FAT-32.
After i installed Win10 successfully, i re-formatted the second half of the HDD again in Mojave from NTFS to FAT-32 to prepare for a new installation of Windows 7; but Apple Boot Picker would still recognize the partition as "Windows" at startup, which i found odd.

@Sergey-Galan here are the log(s), maybe there can be found something that can hint to why the Windows 7 installation fails halfway through.


EDIt: error goes like "Windows could not update the computer's boot configuration. Installation cannot proceed".

Everything is fine with the logs. If this error (“Windows COULD Not update the Computer's Boot Configuration. Installation Cannot Proced”) appears during the first load, then I also had one until I repaired the video card, but it may have been a coincidence.

 

[Sergey-Galan]

this would be nice to have an option to - I call it deactivate UEFI Windows ESP when installing in UEFI mode.

I do it (the ESP tools, for example mount from list and show bootloader) by renaming /EFI/BOOT/bootx64.efi to bootx64.efioff

so a Mac Pro can not boot this ESP directly without OpenCore, and so the risk, getting certificates in the nvram is lowered.

Deleting /EFI/BOOT works also. If renamed the disk can be easily set up to boot in a native UEFI machine by renaming back to bootx64.efi.

If you use bootx64.efioff my ESP tools show [Windows ESP (deactivated)]. Mount from ESP and show bootloader is part of MarintLo's OpenCore package for MacPros so it is widely spread.


If installed in Legacy mode imo no ESP should be written at all.

At least for the 2009 to 2012 Mac Pro Bootcamp also writes no UEFI ESP.

When installing Windows Legacy Boot, the program does not touch ESP. When installing Install Windows Legacy Boot, do you want to change bootx64.efi at BootX64.efioff? And yes, when installing Install Windows UEFI, the program will not install BootX64.efi from Windows if there is bootx64.efi from Opencore or Clover.

 

[Macschrauber]

When installing Windows Legacy Boot, the program does not touch ESP. When installing Install Windows Legacy Boot, do you want to change bootx64.efi at BootX64.efioff? And yes, when installing Install Windows UEFI, the program will not install BootX64.efi from Windows if there is bootx64.efi from Opencore or Clover.

Legacy should not install an ESP at all, as Legacy/BIOS/csm mode dont needs an ESP afaik.

If a user is installing UEFI Windows, an option to deactivate Windows bootx64.efi would be nice. I can use my tools, but the average user would benefit from it on MacPro, if your tool does not install a bootable Windows ESP (as an option, of course).

I check the sn, btw, to detect if it's a MacPro 4,1/5,1 and give the option to deactivate a Windows ESP when one is using my "mount ESP from list and show bootloader" script.

Maybe you will opt to deactivate Windows ESP if your tool is running on a MacPro 4,1/5,1.

 

[startergo]

Or a ban on installing Windows UEFI on a hybrid?

That should be great as they are mutually exclusive.

 

[Sergey-Galan]

Legacy should not install an ESP at all, as Legacy/BIOS/csm mode dont needs an ESP afaik.

This is true, the program does nothing with there)))

If a user is installing UEFI Windows, an option to deactivate Windows bootx64.efi would be nice. I can use my tools, but the average user would benefit from it on MacPro, if your tool does not install a bootable Windows ESP (as an option, of course).

MacPro 4.1/5.1 can see /volumes/EFI/EFI/Microsoft/BOOT/BOOTMGFW.efi directly?

 

[startergo]

MacPro 4.1/5.1 can see /volumes/EFI/EFI/Microsoft/BOOT/BOOTMGFW.efi directly?

Not directly.

 

[Macschrauber]

This is true, the program does nothing with there)))

MacPro 4.1/5.1 can see /volumes/EFI/EFI/Microsoft/BOOT/BOOTMGFW.efi directly?

I guess you mean, can I boot that?

No, to boot that directly it needs /EFI/BOOT/bootx64.efi - but this is exactly what we need to avoid. Booting bootx64.efi directly signs the NVRAM with a (for our EFI 1.1 firmware) incompatible variable. What could lead to problems when other glitches in NVRAM comes in play. This is what we want and need to avoid. Because of this we have this -we-need-a-legacy-windows issue.

OpenCore starts BOOTMGFW.efi without the need of /EFI/BOOT/bootx64.efi and protects the nvram from being written from Windows ESP.

But, even if we have this OpenCore nvram protection thing, people boot UEFI Windows, or USB UEFI Windows installer sticks. And sign their bootrom with it. This can be repaired, but it needs one with deep Mac firmware knowledge. tsialex and me are the guys here what are deep into this topic. I wrote the tool and Alex did the initial investigations about the secrets of the Mac firmware.

 

[startergo]

@Sergey-Galan I have attempted a second installation and this time it succeeded. Please see the difference in the logs:

Unmount of all volumes on disk0 was successful
Windows 7 master boot record successfully written to /dev/disk0
disk0s3 was already unmounted
NTFS Windows 7 boot record successfully written to /dev/disk0s3
Volume on disk0s3 failed to mount
If the volume is damaged, try the "readOnly" option
... Complete
... Time is spent: 40m25s
... Current time: 2024-06-03 21:06:03 -0400
######################## End ########################
Disk /Volumes/CCCOMA_X64FRE_EN-US_DV9 ejected

Versus:

Unmount of disk8 failed: at least one volume could not be unmounted
Unmount was dissented by PID 292
Unable to open /dev/disk8, Resource busy
disk8s3 was already unmounted
NTFS Windows 7 boot record successfully written to /dev/disk8s3
Volume BOOTCAMP 2 on disk8s3 mounted
... Complete
... Time is spent: 41m31s
... Current time: 2024-06-03 07:45:16 -0400
######################## End ########################
Disk /Volumes/CCCOMA_X64FRE_EN-US_DV9 ejected

So the first time it failed to unmount the disk and failed to write the Master Boot Record, which have set the Windows disk unbootable.
In case the first installation does not succeed can the user repeat the installation with all files being already written to disk or the partition needs to be erased? Is there an option to slipstream the Bootcamp drivers or at least write them onto the Windows partition?
The wifi worked out of the box so I was able to install Bootcamp Assistant from Windows linked in the first post.
You may include in the script interrogation of the process which is locking the drive:

sudo lsof /dev/disk8*

 

[LookToWindward]

Hi,

I downloaded the Modified BCA but it won'r work on my MacPro3,1/El Capitan 10.11, it says it needs 10.13 to run but unfortunately 10.11 is the last version this machine will run natively (without OC).

Is there a version for 10.11 or can I patch the info.plist file in the same manner but using the 10.11 version of BCA and stand a chance that it will work?

I'm actually trying to install Windows 7 but I assume BCA doesn't care about this?

Thanks a lot
All the Best
Dave

 

[startergo]

Hi,

I downloaded the Modified DCA but it won'r work on my MacPro3,1/El Capitan 10.11, it says it needs 10.13 to run but unfortunately 10.11 is the last version this machine will run natively (without OC).

Is there a version for 10.11 or can I patch the info.plist file in the same manner but using the 10.11 version of DCA and stand a chance that it will work?

I'm actually trying to install Windows 7 but I assume DCA doesn't care about this?

Thanks a lot
All the Best
Dave

Unfortunately I haven’t tested it on anyrthing lower than HS. What you can try is to modify the plist inside the BCA the same way. @Sergey-Galan is there a way you can compile the application to work on legacy macOS 10.6+?

 

[LookToWindward]

Unfortunately I haven’t tested it on anyrthing lower than HS. What you can try is to modify the plist inside the BCA the same way. @Sergey-Galan is there a way you can compile the application to work on legacy macOS 10.6+?

There is someone, other than Apple that compile the BCA?

 

[startergo]

There is someone, other than Apple that compile the DCA?

Boot Camp Assistant is not an open source. I was talking about the application developed by a third party which can install Windows on a HDD/SSD from macOS ready to boot. This is what we are testing now. But the application does not work in EC. You can always use the Virtual box approach.

 

[LookToWindward]

But the application does not work in EC. You can always use the Virtual box approach.

Sorry but what is "EC" ?

By virtual box you mean use a VM like VMWare?

Btw, I'm trying to install windows 7 not 10, thinking that it would be easier. If 10 is easier I'll do that, but I'd rather use 7

 

[startergo]

Sorry but what is "EC" ?

El Capitan.
You need the virtual box approach

Bare Metal Windows on cMP

PART 1 of 3 This is a guide to installing Windows 10 on Classic Mac Pros without the Boot Camp Assistant. This is one of many ways to implement such a "Bare Metal" setup but is a straightforward method. This guide is for installing Legacy Windows, as opposed to UEFI Windows, but can also be...

forums.macrumors.com

 

[mrkapqa]

it seems that using an already used HDD/partition is a bit risky;

tried today again with "Legacy Boot Mode" and after using Windows 7 Iso previously with the same method (quarter-half-success) now it would no longer let me install Windows 10 on the partition with the method you provided.

It seems something must have gone wrong and the EFI partition would need repair or something, but this seems a bit risky since i have a valid HFS+ Mavericks on partition 1;

after error with windows 10 LTSC image i tried again with windows 10 22H2 which yesterday functioned beautifully to install; but today with bot images i am getting the following error:

Recovery
Your PC/Device needs to be repaired

The Boot Configuration Data file doesn’t contain valid information for an operating system.

File:\Boot\BCD
Error code: 0xc0000098

You’ll need to use recovery tools. If you don’t have any installation media (like a disc or USB device), contact your PC administrator or PC/device manufacturer.

 

[mrkapqa]

the missing drivers for Bootcamp and MacPro5,1 with Windows 10 got from here with this verhy helpful post

under point 5

Classic Mac Pro (5,1): installing Windows 10, switching between macOS Mojave & Windows without boot screen - CrystalIDEA Blog

crystalidea.com

 

[Sergey-Galan]

Booting bootx64.efi directly signs the NVRAM with a (for our EFI 1.1 firmware) incompatible variable.

/EFI/BOOT/bootx64.efi from OpenCore or Clover does not corrupt the firmware?
Ok, I'll make it possible to disable the installation of /EFI/BOOT/bootx64.efi

So the first time it failed to unmount the disk and failed to write the Master Boot Record, which have set the Windows disk unbootable.

The disk is disconnected twice, the first time when it is signed (I showed above), the second time when it makes a boot record.
I will probably make a check for the ability of the disk to turn off.

@Sergey-Galan[/USER] is there a way you can compile the application to work on legacy macOS 10.6+?

Unfortunately no.

 

[startergo]

now it would no longer let me install Windows 10 on the partition with the method you provided.

Do you have the log file for the installation?

 

[startergo]

Conditions - the system is not higher than MacOS 12 Monterey

Could you please specify the minimum macOS requirement for the application?

Edit:
Found it in the playlist:

Minimum system version 10.13

 

[Sergey-Galan]

it seems that using an already used HDD/partition is a bit risky;

The sgdisk utility makes the disk hybrid, and fdisk makes the section active. ms-sys utility makes a boot record. And the sudo dd if=/dev/random of="$disk" bs=1 count=4 seek=440 The team makes a signature for Windows.
The BCD error is random, I thought that I corrected it. In the next test version, I will correct it more radically.

 

[startergo]

The sgdisk utility makes the disk hybrid, and fdisk makes the section active

Wait, so you are saying that the user just needs to format a FAT32 partition and the tool will make the disk hybrid?

 

[Sergey-Galan]

Wait, so you are saying that the user just needs to format a FAT32 partition and the tool will make the disk hybrid?

Yes)))