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

[Macschrauber]

Tried a second time without no_automount, this time it booted Windows as well.

Also formatted the disk before in MBR, 1 partition ExFat
Seems there is a random factor, everything else was exactly same.


attach the 2 logs, one with no_automount, one without. Delete fstab before of course

 

[Sergey-Galan]

Tried a second time without no_automount, this time it booted Windows as well.

Also formatted the disk before in MBR, 1 partition ExFat
Seems there is a random factor, everything else was exactly same.


attach the 2 logs, one with no_automount, one without. Delete fstab before of course

Yes, everything is fine with the logs. But you don't need to use no_automount, since it is already in the program and is used when the disk is external. It is interesting to look at the log when the installation is unsuccessful.

 

[Macschrauber]

Yes, everything is fine with the logs. But you don't need to use no_automount, since it is already in the program and is used when the disk is external. It is interesting to look at the log when the installation is unsuccessful.

yes, I know, I bit my lips for not saving the log. Was in a hurry and did a dozen other things at the same time :-/

Edit: on Mac Pro I install on an internal disk, connected directly to the Southbridge.

 

[Macschrauber]

Windows 11 on Mac Pro 5,1 - directly installed with v6.1.6 to a 1 partition MBR Sata SSD:

BIOS-Modus Vorgängerversion means Bios-mode: legacy

diskutil list disk2
/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *126.0 GB   disk2
   1:               Windows_NTFS ⁨Windows⁩                 126.0 GB   disk2s1

 

[Sergey-Galan]

Windows 11 on Mac Pro 5,1 - directly installed with v6.1.6 to a 1 partition MBR Sata SSD:

View attachment 2389104

BIOS-Modus Vorgängerversion means Bios-mode: legacy

diskutil list disk2
/dev/disk2 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        *126.0 GB   disk2
   1:               Windows_NTFS ⁨Windows⁩                 126.0 GB   disk2s1

Windows 11 Pro - log is OK.
I can assume that the /Volumes/Windows10/Windows/Boot/PCAT folder is not always copied in full to form the bootloader. I will check in the next version. How do you like the "Deactivate Windows ESP" option, is this what you wanted for MacPro?

 

[Macschrauber]

How do you like the "Deactivate Windows ESP" option, is this what you wanted for MacPro?

Yes, exactly. Same way as I do that with my ESP tools, so it's compatible

 

[Macschrauber]

For those who wonder, what deactivate Windows ESP does:

It turns off booting directly UEFI Windows, without use of a bootloader, like OpenCore or RefindPlus.
To avoid signing the bootrom with certificates - as those two bootloaders protect the bootrom from getting certificates.




Native Apple Bootpicker, Uefi Windows is not visible, also unable to start at all

OpenCore, UEFI Windows could be selected and booted, no certificates as OC protects the bootrom

 

[startergo]

Windows update may recreate the bootx64.efi.

 

[Macschrauber]

Windows update may recreate the bootx64.efi.

Yes, indeed,
Thats why

mount ESP from list and show bootloader

Asks to deactivate (rename bootx64.efi to bootx64.efioff) when mounting a Windows ESP.
There is also a script: Check ESPs for MS certificates, what scans thru the ESPs, alarms and asks for deactivation.

 

[Macschrauber]

Did the same as #151, only difference: 1TB Sata HDD, 1 Partition ExFat, MBR, formatted before attempt.

This time it doesnt show up in BootPicker

Edit: it appears in Startup Disk, but when selected it threw an error SDErrorDomain 104

 

[Sergey-Galan]

Did the same as #151, only difference: 1TB Sata HDD, 1 Partition ExFat, MBR, formatted before attempt.

This time it doesnt show up in BootPicker

Edit: it appears in Startup Disk, but when selected it threw an error SDErrorDomain 104

In the log there is this line - Unable to open /dev/disk2, Resource busy
Therefore, the boot record did not occur.
Restart your computer and try installing Windows again.

 

[startergo]

Sounds like a device lock. Most probably by spotlight. You might want to do the disable/enable indexing during the process. Sam as for the autoremount. Plus on such an error the script should ext and say unsuccessful. There is no sense to continue.

 

[Macschrauber]

In the log there is this line - Unable to open /dev/disk2, Resource busy
Therefore, the boot record did not occur.
Restart your computer and try installing Windows again.

You can add a condition to wait a while for the disk. And try again.

Or at least tell the user to take actions to unlock the disk.

Its not about getting Windows on that disk, it worked a few times. Better than expected. And I am thankful for this tool.

Its about to improve it, to find glitches. I tried to force the error. Maybe it was the slower HDD. This could be the random part of it, wild guess, of course.

 

[Sergey-Galan]

Sounds like a device lock. Most probably by spotlight. You might want to do the disable/enable indexing during the process

It is possible to disable/enable indexing in the program, but indexing will remain disabled if the user stops the program during execution and this is a problem.

Plus on such an error the script should ext and say unsuccessful. There is no sense to continue.

I will do it

 

[Macschrauber]

It is possible to disable/enable indexing in the program, but indexing will remain disabled if the user stops the program during execution and this is a problem.

If it's bash you can do something like I do with the Dumper:

Edit: in the comment there was EXIT signal, what I handle differently

#!/bin/bash


# Set trap for SIGINT and SIGTERM signals
trap cleanup SIGINT SIGTERM

function cleanup() {

        # various code
    
    rm -f /tmp/ibiosi.bin
    rm -f /tmp/VSS_Store*.bin
    rm -f /tmp/scanvss*.log
    rm -f /tmp/Gaid*
    rm -f /tmp/Fsys*
    rm -f /tmp/nvram*.vol
    rm -f /tmp/tmpnvram.vol

    echo "Got term signal, temporary files removed."
	
    exit 1
}

# script continues
# various commands
#
#
#
#
exit 0

 

[startergo]

Tried to install Windows 11 in hybrid and UEFI modes on MacMini6,2. Got BCD error in UEFI and no boot disk in Hybrid modes.

 

[startergo]

 

[Sergey-Galan]

Tried to install Windows 11 in hybrid and UEFI modes on MacMini6,2. Got BCD error in UEFI and no boot disk in Hybrid modes.

UEFI installation - for some unknown reason the hivexsh utility did not work. If this happens again, try chmod 777 /Users/mavericksserver/Desktop/Windows Install.app/Contents/Resources/tools/bin/hivexsh
Installation hybrid - ms-sys utility, compiled on MacOS 10.13, should now work.

 

[Sergey-Galan]

View attachment 2389679

chmod 777 /Users/mavericksserver/Desktop/Windows Install.app/Contents/Resources/tools/bin/hivexsh

 

[startergo]

chmod 777 /Users/mavericksserver/Desktop/Windows Install.app/Contents/Resources/tools/bin/hivexsh

ls -l /Users/mavericksserver/Desktop/Windows\ Install.app/Contents/Resources/tools/bin/hivexsh
-rwxr-xr-x@ 1 mavericksserver  staff  40208 Jun 17  2024

original permissions 755.

ls -l /Users/mavericksserver/Desktop/Windows\ Install.app/Contents/Resources/tools/bin/
total 992
-rwxrwxrwx@ 1 mavericksserver  staff   40208 Jun 17  2024 hivexsh
-rwxr-xr-x@ 1 mavericksserver  staff   87960 Jun 17  2024 mkntfs
-rwxr-xr-x@ 1 mavericksserver  staff   72512 Jun 17  2024 ms-sys
-rwxr-xr-x@ 1 mavericksserver  staff  228932 Jun 17  2024 sgdisk
-rwxr-xr-x@ 1 mavericksserver  staff   73200 Jun 17  2024 wimlib-imagex

 

[Sergey-Galan]

Ok.
I posted the version above, does it have the same problem?

 

[startergo]

Ok.
I posted the version above, does it have the same problem?

That was from the last post. Still got the same error with hybrid MBR Windows 10 install.

 

[Sergey-Galan]

That was from the last post. Still got the same error with hybrid MBR Windows 10 install.

Is this only in Catalina? Is High Sierra doing well?

 

[Sergey-Galan]

That was from the last post. Still got the same error with hybrid MBR Windows 10 install.

I disabled
#rm "$HOME"/BCD-Windows
#rm "$HOME"/winload.txt
Can you show them to me?

 

[startergo]

Here they are.