MP 1,1-5,1 Windows suddenly not selectable as startup-disk anymore

[flyproductions]

As the title says: All of a sudden i get some strange error, trying to select my Windows-install as startup device in system prefs.

Running "sudo bless -mount /Volumes/"name of my win bootdisk" -setBoot -legacy -verbose" in terminal gets me the following error:

Sure it’s a legacy install. But selecting it to boot via system prefs worked perfectly eversince. Also selcting it to boot via bootpicker at startup still boots it without any problems.

Windows was a legacy-/DVD-install of Windows 10, now updated to Win 11. OS is High Sierra. Problems started shortly after the Win 11 update.

Any suggestions? Thanks in advance!

 

[startergo]

What is the result of diskutil list? Also you might want to install gdisk, disable SIP in recovery and run:

sudo gdisk /dev/diskX

where diskX is the disk containing Windows.

 

[startergo]

Just realized your firmware features are not correct. I don't know if you use OC, but if yes then you need to reset the firmware features according to here:

OpenCore on the Mac Pro

This guide explains how to use the excellent OpenCore boot loader to install, run, and update the latest version of macOS on the MacPro5,1, resulting in a clean, unaltered operating system just like on a supported Mac.

forums.macrumors.com

Legacy mode is bit one:

OpenCorePkg/Include/Apple/IndustryStandard/AppleFeatures.h at master · acidanthera/OpenCorePkg

OpenCore bootloader. Contribute to acidanthera/OpenCorePkg development by creating an account on GitHub.

github.com

But 0x00000014 in hex is 10100. If not reset NVRAM.
For Mac Pro 5,1 firmware features should be 0xC00C5417, which have bits 0 and 1 included:

 

[flyproductions]

If not reset NVRAM.
For Mac Pro 5,1 firmware features should be 0xC00C5417, which have bits 0 and 1 included

Thanks! The deep NVRAM-reset solved it!

And it looks somhow better now...

...with the firmware features matching your last post.

Im not using OC on this machine. But i made a build for an installer stick for some other cMP. And it looks like this has been enough to corrupt my nvram.

I did not know before how much of a hassle it is to reset nvram with 4 bongs as well as booting into recovery with some web-driver depending NV GPU like the 1080. Even had to swap the 5770 back in to get everything done. But now everything works as it should again.

Thanks alot!