I hacked the ACPI firmware on my system, linux is able to apply "my firmware" rather than use the operating system supplied firmware.

Does anyone know if windows can do the same ?

▲

jeroenhd 6 days ago | parent | next [-]

Microsoft documents replacing the ACPI table with their API: https://learn.microsoft.com/en-us/windows-hardware/drivers/b... (bottom of the page)

Unfortunately you need to disable signing for that, which will trigger anticheat in online games and makes Windows nag you about it.

Someone wrote a bootloader specifically to patch ACPI on boot in CSM mode if you're okay with reinstalling Windows on an older system that can't play certain games: https://github.com/MovAX0xDEAD/ACPI-Patcher

	▲	p_l 6 days ago \| parent [-]
		IIRC you can resign everything with your own key, but anticheat might still explode about it.

▲

phs318u 6 days ago | parent | prev [-]

This is what I was going to ask, but I assume that the ACPI.SYS driver (which wraps the ASUS ACPI BIOS implementation) is signed by Microsoft, which means "not unless you allow unsigned drivers", which I don't even know if that's possible in current Windows (my deep Windows-fu is about 20 years out of date).

	▲	mananaysiempre 6 days ago \| parent [-]
		The ACPI.SYS driver itself is not at fault here, it’s just a generic bytecode interpreter that’s the same in every Windows install. The problem lies with the bytecode—the “ACPI tables”—that the firmware of these specific devices feeds it. There is nothing physically forcing it to run the code that’s stored in the motherboard flash, though; it could, say, use a patched version instead. The equivalent function is well-supported on Linux, because Linux uses a different interpreter (the reference one from Intel, in fact) and in general manages the hardware differently enough to regularly expose bugs in the ACPI code of manufacturers whose QC pass condition is “boots Windows” (all of them) and who can’t be bothered to fix bugs not affecting Windows (almost all of them).