Hello. The program does not affect macOS and OCLP when installing Windows, check, maybe you have problems with the disk. Try installing again with legacy boot, while OCLP must be excluded, and the disk on which you install must be an internal SATA (not USB). And I would like to see the log, I will be able to see whether the program installs Windows correctly.
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
@Sergey-Galan, Thanks for the answer!
yes, I will check the HDD for problems...
as I wrote above:
Windows legacy installation - not visible for OC-boot; so I immediately changed the installation option to UEFI, but apparently due to the lack of additional drivers - Win startup shows an abnormal termination and I tried to fix it with the help of the win-processor, but after winondows hung on this page and I could no longer load either winOS or MacOS (they are on different disks)
Attachments
Last edited:
First of all, many thanks to @Sergey-Galan for this great piece of software! I used it today to install the latest Windows 11 on my MacBookAir6,2, and it worked perfectly. Now I also have a Hackintosh running Sonoma alongside Windows 11.
Since your software makes it furthermore easy to back up a Windows installation, I was hoping to use it for periodic backups of my Windows 11 setup, similar to how Time Machine protects my Sonoma install. Time Machine has already saved me once when a cheap NVMe from AliExpress that was in my Mac previously died completely—so having the same kind of safety net for Windows would be amazing.
The problem I’ve run into is that my Windows partition (called System—see attached screenshot) does not appear as eligible for selection inside the Windows installer. Is there any way to make the app recognize it?
Thanks in advance!
Since your software makes it furthermore easy to back up a Windows installation, I was hoping to use it for periodic backups of my Windows 11 setup, similar to how Time Machine protects my Sonoma install. Time Machine has already saved me once when a cheap NVMe from AliExpress that was in my Mac previously died completely—so having the same kind of safety net for Windows would be amazing.
The problem I’ve run into is that my Windows partition (called System—see attached screenshot) does not appear as eligible for selection inside the Windows installer. Is there any way to make the app recognize it?
Thanks in advance!
Attachments
Hi. If you disable Tuxera and remount the "System" partition, you will see the partition in the list, and you will be able to create a backup.
If you execute the command in the terminal:
diskutil info disk4s2Note disk4s2 is the "System" partition (as in your screenshot, make a change if this is not the case).
And provide me with the list, I will see how this program renamed the format name - by default Type (Bundle): ntfs, and in the new revision I will make a change after which Tuxera will not be an obstacle.
Last edited:
Thanks for the quick reply. I did what you suggested, but still no luck—the partition does not show up in your application. I’ve attached the screenshot you requested.
Forget what I wrote, after relaunching Windows Install it is now shown. Thanks for the hint! So it was Tuxera NTFS blocking it after all.
Forget what I wrote, after relaunching Windows Install it is now shown. Thanks for the hint! So it was Tuxera NTFS blocking it after all.
Attachments
Please try the test version with the Tuxera NTFS program enabled.
I just did but unfortunately I can't select the partition while Tuxera NTFS is enabled. Attached please find the Terminal output of the NTFS disk with Tuxera NTFS on, perhaps that could help for future versions.
Attachments
Yes, I can select the Tuxera NTFS mounted drive now. Thanks!
Thanks. I'll add Tuxera NTFS recognition in the next revision.
If I’m doing the “Install Windows legacy boot” option in High Sierra, since there’s no separate “Full Disk Access” option in system preferences, is this my cue to disable SIP again? Thanks, Sergey.
Hi. When installing “Install Windows legacy boot” the disk should not be a system disk, as it should be able to be disconnected during the installation process. If necessary in High Sierra, disable SIP.
Perfect, thank you. I tried doing it without disabling that and it simply wrote zero files to the drive and claimed the process was done. I guess that’s the problem.
EDIT: All right, never mind. Same problem as all the other ways I’ve tried. Black screen, flashing cursor. No matter what version of Windows, no matter type of ISO, no matter what method. I’m done. Thanks anyway, everyone.
Last edited:
This is a long known issue of some PC GPUs, if your GPU does not provide pre-boot configuration support with the MacPro5,1, you'll need to wait until Windows Update automatically downloads the GPU drivers, could take half an hour or even more.
You'll need to be directly connected to the internet via Ethernet, without any proxies and etc, btw.
Ah, I see. I have Microsoft’s update IPs blocked on my network. No wonder it never did anything no matter how long I waited. Guess that’s it, then.
EDIT: Hang on, I haven’t even finished setup yet. It doesn’t know how to connect to any networks near me. That can’t be it.
Last edited:
Official Windows 11 installed on a Mac Pro 4.1>5.1 with OpenCore & Monterey. I installed it on a separate NVMe drive with a Sabrent adapter formatted to exFAT. After installation, Windows updates downloaded and installed. Windows works, applications install and work.
I'm having trouble creating a backup. The Windows partition is correctly mounted in Monterey, and it appears normally in Finder and in the Terminal disk utility list. The program automatically detects the partition and the Desktop/Backup folder - however, the backup doesn't start. I get a message that the partition doesn't exist and that I need to select/enter the correct partition in the program menu. But I can't change anything there; it's the only partition the program sees.
Another issue 1 The drive had a previous failed Windows installation from a USB flash drive. I force-cleaned everything on NVME, deleted the GPT table, and formatted it to exFAT.
Another issue 2 is that the partition named WINDOWS still existed during these procedures. I cleaned it in the terminal, not with Disk Utility.
Please advise what else I can check/correct to analyze why the backup isn't starting. Thanks!
Is it possible to backup to ISO with another tool and then safe restore from ISO in Windows Install?
I'm having trouble creating a backup. The Windows partition is correctly mounted in Monterey, and it appears normally in Finder and in the Terminal disk utility list. The program automatically detects the partition and the Desktop/Backup folder - however, the backup doesn't start. I get a message that the partition doesn't exist and that I need to select/enter the correct partition in the program menu. But I can't change anything there; it's the only partition the program sees.
Another issue 1 The drive had a previous failed Windows installation from a USB flash drive. I force-cleaned everything on NVME, deleted the GPT table, and formatted it to exFAT.
Another issue 2 is that the partition named WINDOWS still existed during these procedures. I cleaned it in the terminal, not with Disk Utility.
Please advise what else I can check/correct to analyze why the backup isn't starting. Thanks!
Is it possible to backup to ISO with another tool and then safe restore from ISO in Windows Install?
Last edited:
Hi.
Enter
in the terminal.
Save the output.
Enter
in the terminal.
(Windows11 is the name of your Windows volume; yours may be different.)
Save the output.
Let me look at these outputs.
Enter
Code:
diskutil listSave the output.
Enter
Code:
diskutil info Windows11(Windows11 is the name of your Windows volume; yours may be different.)
Save the output.
Let me look at these outputs.
I think so, if the path to the wim file in the ISO image is correct. But you can mount the ISO image yourself and drag the wim file itself into the program window.
Thank you @Sergey-Galan
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk2 1000.0 GB disk0s2
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI EFI 209.7 MB disk1s1
2: Microsoft Basic Data WINDOWS 1000.0 GB disk1s2
/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +1000.0 GB disk2
Physical Store disk0s2
1: APFS Volume Monterey – dane 76.2 GB disk2s1
2: APFS Volume Preboot 269.5 MB disk2s2
3: APFS Volume Recovery 1.1 GB disk2s3
4: APFS Volume VM 1.1 MB disk2s4
5: APFS Volume Monterey 15.4 GB disk2s5
6: APFS Snapshot com.apple.os.update-... 15.4 GB disk2s5s1
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *256.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_APFS Container disk4 255.9 GB disk3s2
/dev/disk4 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +255.9 GB disk4
Physical Store disk3s2
1: APFS Volume Mojave Vanilla 44.8 GB disk4s1
2: APFS Volume Preboot 24.7 MB disk4s2
3: APFS Volume Recovery 507.6 MB disk4s3
4: APFS Volume VM
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk0
1: EFI EFI 209.7 MB disk0s1
2: Apple_APFS Container disk2 1000.0 GB disk0s2
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *1.0 TB disk1
1: EFI EFI 209.7 MB disk1s1
2: Microsoft Basic Data WINDOWS 1000.0 GB disk1s2
/dev/disk2 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +1000.0 GB disk2
Physical Store disk0s2
1: APFS Volume Monterey – dane 76.2 GB disk2s1
2: APFS Volume Preboot 269.5 MB disk2s2
3: APFS Volume Recovery 1.1 GB disk2s3
4: APFS Volume VM 1.1 MB disk2s4
5: APFS Volume Monterey 15.4 GB disk2s5
6: APFS Snapshot com.apple.os.update-... 15.4 GB disk2s5s1
/dev/disk3 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *256.1 GB disk3
1: EFI EFI 209.7 MB disk3s1
2: Apple_APFS Container disk4 255.9 GB disk3s2
/dev/disk4 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +255.9 GB disk4
Physical Store disk3s2
1: APFS Volume Mojave Vanilla 44.8 GB disk4s1
2: APFS Volume Preboot 24.7 MB disk4s2
3: APFS Volume Recovery 507.6 MB disk4s3
4: APFS Volume VM
The logic is as follows:
In the program, you specified the volume name "WINDOWS," which is then passed to the executable script.
The script checks the volume name, disk number, and partition number. If the check fails, it throws the error you mentioned earlier. I don't yet know why you're getting this error.
Actually, the script was written earlier, and the program interface was developed later. That's why there are two disk checks. If you see the volume name "WINDOWS" in the program window, that means the check has passed. In the script, this is the second check, and it can be commented out, i.e., disabled. I've attached a test version with the check disabled.
If you can't create a backup, send me the log (upper left corner of the screen, File -> Save log).
In the program, you specified the volume name "WINDOWS," which is then passed to the executable script.
The script checks the volume name, disk number, and partition number. If the check fails, it throws the error you mentioned earlier. I don't yet know why you're getting this error.
Actually, the script was written earlier, and the program interface was developed later. That's why there are two disk checks. If you see the volume name "WINDOWS" in the program window, that means the check has passed. In the script, this is the second check, and it can be commented out, i.e., disabled. I've attached a test version with the check disabled.
If you can't create a backup, send me the log (upper left corner of the screen, File -> Save log).