Thx for details.this is the "boot hook" by Open Core, if you dont want it then set LauncherOption in OpenCore to Disabled.
this is this boot001 ... line in the dumper as it is sometimes hard to get it away, so I added a line if that boot hook is in the nvram variables.
This is a nice and wanted feature to survive nvram resets and to set OpenCore's default selection by the startvolume prefpane.
About the old Bootblock:
The Bootblock never gets updated by regular Firmware Updates. My theory why is to let a failsafe in the firmware chip to load the firmware rescue cd if something fails.
tbh the firmware rescue cd never worked for me. Firmware rescue is in my experience taking out the flash chip and replace it with a new flashed one with firmware and personal machine's IDs.
The only way to get the bootblock updated is by manual firmware reconstruction.
tsialex and me are afaik the two guys what can do that job. I owe my first steps into firmware investigation to him and he is my mentor ;-)
TSIALEX I know from before solutions about HW and he is TOP.
For my complication, now I just for safe over VinClone done backup of my WinDisk and NOW I dont see any of my 2 Windows drives. Its frustrated that when no change was made in setups and installations jut missed visibility under macOS (Win Boot Drive).
But my question is still same - please do you have any way how to do ability from macOS Monterey (MP5.1 unsupported with OCLP) to reboot ONLY ONCE to Windows and after reboot or shutdown again boot into macOS (?)
Due APFS problem Windows OS not sees in BootCamp panel bootdrive macOS OCLP Monterey.
Due "SDErrorDomain error 104" is unable to manually choose Windows drive to boot natively from macOS OCLP Monterey.
Due "BootBlock" in unable to reboot into different native supported macOS from macOS OCLP Monterey. Stillrebooting in macOs Monterey OCLP.
My thniking was to put in between another macOS native supported ro reboot into it where are not new locking/blocking features from AppleOS and in it to reboot into Windows. After that in Windows will be visible this native macOS for reboot again back into it without NVRAM reset and then to choose to reboot in OCLP macOS Monterey back. I know its 2step/4step stolution but I thank that it can work.
But now I see only another additioning problems and complication.
THE BEST option for silution is to implement "something as BLESS command" but 100% working in Monterey as ability for users to use old working command BLESS (once and permanet), that was perfectly suitable before thoose "security disabilities from Apple"...
And additionally ADD GOP INIT for all possible GPUs without bootscreen wich will solve 99% booting issues in this kind of way...
Last edited: