Lance, can you tell me if you look at the list of hardware and drivers in windows - does everything work correctly for you? Are there about 100 incorrect drivers for internal equipment like mine? I've been following your reviews on YouTube for many years, and I make many decisions only after carefully studying the experience of many people from the Macrumors community. I thought about it for about half a year and decided that it was time to upgrade to Mac Pro 7.1 (I bought two identical 7.1 instead of my two old 4.1/5.1.)I created with the app in the 5,1 and put it in my 2019 Mac Pro and it booted no prob which prooves the 5,1 is the problem, the app was not the issue, it's an issue with my 5,1 and maybe the latest Windows 11 build. I can still install Windows 11 using my 2022 Rufus created thumb drive on the 5,1 and get it up to date.
Regarding the first point. Legacy Windows installation is relevant for Mac Pro 4.1/5.1, old iMacs and MacBooks that do not have the OCLP bootloader installed. The firmware of these computers does not know what UEFI Windows is.1. as I expected, despite the fact that Sergey's program prepared disk for installing Legacy windows correctly, the installation process itself did not start on the Mac Pro - nowhere in the discussion did I find in which cases it is necessary to install UEFI, and in which cases Legacy. My cmp 7.1 simply did not start the installation - it does not consider this disk bootable
UEFI Class 3 devices do not have the Compatibility Support Module (CSM) needed for Legacy BIOS Boot.There is no need to install Legacy Windows for Mac Pro 7.1, but it is possible.
Thanks for the information.UEFI Class 3 devices do not have the Compatibility Support Module (CSM) needed for Legacy BIOS Boot.
UEFI Class 3+ devices are Class 3 devices that additionally include a TPM.
The T2 chip is effectively a TPM and the MP71 therefore appears to be a UEFI Class 3+ device.
In simple terms therefore, the MP71 does not support Legacy Windows.
It is possible to install such indeed, but the MP71 will not and can not boot it.
This is all inferred btw as Apple does not specifically publicly define device UEFI Classes.
I had about 100 unrecognized devices on my Mac Pro 7.1. what bootcamp gives is little things - a mouse, a keyboard and all sorts of other insignificant Apple-specific little things. Ethernet didn't work. I spent a whole week reading various forums. First, I downloaded several Intel drivers from updates - the number of errors decreased by about 60. Then I downloaded Aquantia ethernet drivers from official site. Two more errors deleted. Ethernet works. Now I have PCI Data Acquisition and Signal Processing Controller error and SM Bus Controller driver error- there are about 10 errors left
Why would you use this guide on Mac Pro 7.1? The only thing you can use from this guide is the Windows Install application to install Windows from macOS.I had about 100 unrecognized devices on my Mac Pro 7.1.
Yes, there are a lot of off-topic posts here, but unfortunately I can’t create my own topic, I’ll be banned (((Why would you use this guide on Mac Pro 7.1? The only thing you can use from this guide is the Windows Install application to install Windows from macOS.
A pre-prepared flash drive with bootcamp drivers. But the problem is that not all of his devices are updated, and when he tries to install drivers from other sources, he gets a blue screen.@Sergey-Galan is there a way to download the bootcamp drivers during the process or the user has to download them on a separate USB?
In order not to start all over again, make a backup after each attempt to install drivers; the program has this option.Controller error and SM Bus Controller driver error- there are about 10 errors left
following the official intel instructions, I launched some driver installers and got a blue screen of death
so everything is very confusing here
This is the off-topic question, and that appeared to be the only question you had.I wanted to specifically ask the experts
should I return the original BIOS of the video card instead of the one modified by syncretic?
because when I launched the AMD diagnostics - it gave an error - it wrote that the equipment is not recognized - not the original AMD
rsync -r dir1/ dir2
.I don't know if it's a topic or not, but I reverted the GPU BIOS to non-flashed, and all my errors were removedThis is the off-topic question, and that appeared to be the only question you had.
As far as the Windows Install software goes there are no specific drivers installed by that software so if some drivers don't work out of the box it is recommended to provide the Bootcamp drivers on a USB drive. Just download the drivers through the Bootcamp assistant in the macOS and copy them to a fat formatted USB drive usingrsync -r dir1/ dir2
.
@Sergey-Galan Is Windows 10 32 bit supported? After using theWininstall
Windows won't boot.
I think the wimlib utility is provided on the site for the environment in which it works.I use wimlib v1.14.4 Windows binaries (64-bit). You can try wimlib v1.14.4 Windows binaries (32-bit), but who needs it))) https://wimlib.net/
Try changing the value of "Deactivate Windows ESP" several timesBtw, v6.2.3 disk selection with High Sierra is not working correctly, someway is always disk10s10 that is selected.
I did, try the test version. Rename the file you created on the site https://schneegans.de/windows/unattend-generator/ from autounattend.xml to unattend.xml and save it to the Backup folder, which is located on the desktop by default, but you can choose another folder. When the program installs Windows, it will copy unattend.xml to the root of the partition. It worked for me. Tested on Windows11 24H2 and Windows10 LTSC.@Sergey-Galan there is a easy way to add the autounattend.xml to the Windows install? I would make the life of system admins a lot easier, if possible.
I did, try the test version. Rename the file you created on the site https://schneegans.de/windows/unattend-generator/ from autounattend.xml to unattend.xml and save it to the Backup folder, which is located on the desktop by default, but you can choose another folder. When the program installs Windows, it will copy unattend.xml to the root of the partition. It worked for me. Tested on Windows11 24H2 and Windows10 LTSC.
I can't imagine how a system administrator in an office installs Windows on Macs.
I will make it so in the release that there is no need to rename; when copying, the program will rename the file itself.Rename the file you created on the site https://schneegans.de/windows/unattend-generator/ from autounattend.xml to unattend.xml and save it to the Backup folder.
I can't imagine how a system administrator in an office installs Windows on Macs.![]()
In general, the answer file is useful, especially if you experiment. True, not everything works - I selected almost all programs for removal, but in fact they remained.
I will make it so in the release that there is no need to rename; when copying, the program will rename the file itself.
Or in the installed system you can use this - https://github.com/builtbybel/BloatboxerPerhaps will be better to use a image already cleaned/prepared by Sysprep instead?