Ok, I've download and installed App Cleaner and Cleaned up WindowsInstaller.app. I will now re-installer 6.1.7 and try again
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Installing Windows 10 in Legacy/BIOS mode in cMP with Boot Camp Assistant
- Thread starter startergo
- WikiPost WikiPost
- Start date
-
- Tags
- windows 10 bios
- Sort by reaction score
- Status
The latest one is 6.1.8
Installing Windows 10 in Legacy/BIOS mode in cMP with Boot Camp Assistant
Failed to create main BCD store. But this time the hivexsh utility worked, but stopped without finishing its work. I don’t know what prevented it. In version 6.1.8 added a check for BCD creation.
forums.macrumors.com
I tried it again:
Booted from Mojave in Bay 1
HDD is Bay 4
Bays 2,3 empty
No USB drive connected.
It started ok but seems to have frozen at 22% 66000 of 145007.
It's been stuck like this for over 5 mins? What should I do? The installer is till responsive, I could try to save the log?
Booted from Mojave in Bay 1
HDD is Bay 4
Bays 2,3 empty
No USB drive connected.
It started ok but seems to have frozen at 22% 66000 of 145007.
It's been stuck like this for over 5 mins? What should I do? The installer is till responsive, I could try to save the log?
Trying again with 6.1.8
It has frozen again, this time at 68%, Extracting file data: 3411 of 9005
Not sure what to do? The installer in still active, I could maybe save the log, but not sure how much would it be since it has completed?
Drive bay 1 Mojave boot
Drive bay 4 HDD formatted as ExFat MBR
It has frozen again, this time at 68%, Extracting file data: 3411 of 9005
Not sure what to do? The installer in still active, I could maybe save the log, but not sure how much would it be since it has completed?
Drive bay 1 Mojave boot
Drive bay 4 HDD formatted as ExFat MBR
Last edited:
@Sergey-Galan what is this:
Code:
fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1> Partition 1 marked active.
fdisk:*1> Invalid command '2'. Try 'help'.
fdisk:*1> Writing current MBR to disk.fdisk:*1> Invalid command '2'Log for 6.1.8 Freeze attached.
This is trying installing on an internal SATA bay drive, shall I try using the USB again?
This is trying installing on an internal SATA bay drive, shall I try using the USB again?
Z2
It may be slow, but that could depend on the drive. Bad drive?
From what I can see it is working. It is extracting data and the value is changing:
Code:
Windows Install disk2s1 Extracting file data: 3334 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3339 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3344 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3349 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3353 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3358 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3363 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3368 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3373 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3377 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3382 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3387 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3392 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3396 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3401 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3406 MiB of 9005 MiB (37%) done
Windows Install disk2s1 Extracting file data: 3411 MiB of 9005 MiB (37%) doneOk, yes, probably a bad disk, I used the SSD in Bay 4 and all went well, log attached
Not sure if this is the right place, but....
I have a 5,1 running Monterey 12.7.5 oclp 1.5 and I have legacy win10 on a ssd, which I used to be able to access through the oclp boot picker (listed as legacy). Think that was a feature added relatively recently.
However now the only thing available is the macOS drive. I can sort of get to the drive by pulling everything except that drive and rebooting and choosing it blind in the stock boot picker (my rx580 has non standard firmware or requires a flash for the enablegop I did to work and Ive not done it yet)
Is there any way of getting the legacy install back to showing in the oclp boot picker? Is there an option for legacy installs somewhere that is default off ?
I have a 5,1 running Monterey 12.7.5 oclp 1.5 and I have legacy win10 on a ssd, which I used to be able to access through the oclp boot picker (listed as legacy). Think that was a feature added relatively recently.
However now the only thing available is the macOS drive. I can sort of get to the drive by pulling everything except that drive and rebooting and choosing it blind in the stock boot picker (my rx580 has non standard firmware or requires a flash for the enablegop I did to work and Ive not done it yet)
Is there any way of getting the legacy install back to showing in the oclp boot picker? Is there an option for legacy installs somewhere that is default off ?
The best place for OCLP support is the discord forum. You can create a new thread there.
Finally got past the Windoze Setup and actually in!
If you wan't me to test some other installs I can do it tomorrow if you like
If you wan't me to test some other installs I can do it tomorrow if you like
When formatting a disk in MBR, usually Start sector 2048 (nr of hidden sectors). The filter looks for the section number based on the unique number “Start sector”. Your Start sector is 2, this is not a unique number, the filter found it in two places.
Look at other reports, they all have 2048)))
Modifying .wim files has always been your friend. However, the thing I'd be more worried about is driver support for 5,1 and earlier for Windows 10. I'm fairly certain that Apple never supported those machines for Windows 10 via Boot Camp and I'm fairly sure that's because drivers for those components for Windows 10 don't exist. Windows 10 specific drivers didn't start existing in the Intel side of things until Ivy Bridge. 5,1 is pre-Sandy Bridge/E.
What bluetooth/wifi did the iMac Pro have?
Is it the same as the bluetooth/wifi we've all mostly used to upgrade our 5,1 Mac pros (94360CD if I remember correctly)?
I tried getting W10 working my 5,1 6 core machine that is in my cycling trainer pain-cave (it runs Zwift and Fulgaz). W10 mostly ran except for the bluetooth drivers not being signed properly.
I was wondering if it could be related to my non-standard bluetooth/wifi (non standard for the 5,1). I could try the iMac Pro drivers if they help.
My method for installing W10 was to use virtual box to get the install going then restart and access via the opencore boot menu.
Let's see. BCM94360CD (
https://gist.github.com/nuomi1/16133b89c2b38b7eb197
are
Also here:
github.com
PCI\VEN_14E4&DEV_43A0) is supposed to be coming from iMac late 2013 iMac14,1 , so the drivers for it according tohttps://gist.github.com/nuomi1/16133b89c2b38b7eb197
are
Also here:
GitHub - jsassu20/Apple-Airport-Broadcom-BCM4360-Windows-Drivers: Apple Airport Extreme Broadcom BCM94360CS, BCM94360CS2, BCM94360CSAX AC Wireless Card Windows 7-10 Drivers
Apple Airport Extreme Broadcom BCM94360CS, BCM94360CS2, BCM94360CSAX AC Wireless Card Windows 7-10 Drivers - jsassu20/Apple-Airport-Broadcom-BCM4360-Windows-Drivers
github.com
Last edited:
As for the BCM943602CD (
it is from the late 2015
also in
PCI\VEN_14E4&DEV_43BA)it is from the late 2015
iMac16,1 (16,2) so its drivers should be:also in
iMac18.3 and it shares the Bootcamp drivers with iMacPro:
Last edited:
Do I need to install these drivers on my 5,1 Windows 10 install?
I've tested to boot the MBR Windows 11 Sata disk on a Mac Mini 2014 external:I think there is no way to boot a legacy mbr disk from USB on a classic MacPro.
I'd be glad if someone proves me wrong
USB Sata bridge: start to boot but one liner error: no bootloader
Thunderbolt sata bridge: the disk booted completely, like it was an internal one.
I have booted MBR with:
Code:
USB 3.0 Bus:
Host Controller Driver: AppleUSBXHCIPPT
PCI Device ID: 0x1e31
PCI Revision ID: 0x0004
PCI Vendor ID: 0x8086
Product ID: 0x0301
Vendor ID: 0x0984 (Apricorn)
Version: 1.28
Serial Number: 4A3838303030373648453530
Speed: Up to 5 Gb/s
Manufacturer: Apricorn
Location ID: 0x14600000 / 5
Current Available (mA): 900
Current Required (mA): 8
Extra Operating Current (mA): 0I may try with another bridge, when it worked on your 2012 MM.
Side note: The alt-key did not worked to get the Apple boot picker when this USB controller was plugged in also. After removing and switching to Thunderbolt bridge it worked without further setup change.
While writing it: There was another difference: I selected Win11 with the startup disk control panel, as the boot picker has not worked. This box is on Mojave, no OpenCore.
Side note: The alt-key did not worked to get the Apple boot picker when this USB controller was plugged in also. After removing and switching to Thunderbolt bridge it worked without further setup change.
While writing it: There was another difference: I selected Win11 with the startup disk control panel, as the boot picker has not worked. This box is on Mojave, no OpenCore.
Windows Install 6.1.8
tested Windows 7, MBR legacy worked, but MacBook Air 2013 could not complete boot, wrote something about could not update boot data, not sure it was the book
wrote
I think that should be catched by Windows Install.
the files I needed where made (working on upgrading my show OS versions tool to include Windows versions with bios / uefi flag)
tried Windows 7 UEFI
1st time it stuck, 2nd time it locked the machine 4 seconds before stopping. No chance to get it back, to save the log, but hard shutdown. Include the log of the stucked attempt.
The install seems to have finished, I dont want to boot uefi Windows on this machine, try that later. But the files I needed were made (Software hive and the Win UEFI ESP)
I'd think about to store the log to /Library/Logs with a time stamp - to catch such situations, and to help those users what forget to store the log
tested Windows 7, MBR legacy worked, but MacBook Air 2013 could not complete boot, wrote something about could not update boot data, not sure it was the book
wrote
Code:
fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
..
Device could not be accessed exclusively.
A reboot will be needed for changes to take effect. OK? [n] Disk: /dev/disk2 geometry: 7783/255/63 [125043311 sectors]I think that should be catched by Windows Install.
the files I needed where made (working on upgrading my show OS versions tool to include Windows versions with bios / uefi flag)
tried Windows 7 UEFI
1st time it stuck, 2nd time it locked the machine 4 seconds before stopping. No chance to get it back, to save the log, but hard shutdown. Include the log of the stucked attempt.
The install seems to have finished, I dont want to boot uefi Windows on this machine, try that later. But the files I needed were made (Software hive and the Win UEFI ESP)
I'd think about to store the log to /Library/Logs with a time stamp - to catch such situations, and to help those users what forget to store the log
Are you using this driver?
github.com
Maybe it is breaking the installer?
GitHub - kasbert/OS-X-SAT-SMART-Driver: Max OS X kernel driver for providing access to external drive SMART data
Max OS X kernel driver for providing access to external drive SMART data - kasbert/OS-X-SAT-SMART-Driver
github.com