for sake of this, let's exclude any private odin release from the discussion, & instead focus on technical details. i know odin patches kernel to load its unsigned driver which may be undesirable, but what if i am well aware of the consequence and still decide to proceed? does it work on UEFI install? coz it was advertised as hardware independent. if not, can anyone share its working principle as to why it is restricted to BIOS MBR install? *i ask this for learning purpose, please avoid solely suggesting other activation methods as a reply. EDIT: We know that Daz's Windows Loader works by modifying MBR to inject SLIC so it requires MBR harddisk partition. So it won't work in UEFI Windows with GPT partition. What I wonder is, if ODIN changes SLIC cached in RAM through boot-start driver, shouldn't it work on UEFI too? as it probably had made no assumption on underlying harddisk partition. or does the SLIC structure or position differs from BIOS to UEFI, such that the tool must be redesigned?