It intercepts the calls macOS makes to the physical SMC and returns the expected values virtually. It creates a "fake" SMC environment in system memory that satisfies macOS's strict requirements, allowing the OS to boot on hardware that lacks Apple's proprietary chip.
This means the kext isn't loading properly. Usually caused by: fakesmc.kext
fakesmc.kext alone has no real sensors. You need ACPIMonitor.kext or HWMonitor plugins. If you see 128°C (a classic fake value), the kext is lying successfully, but no real data is feeding in. It intercepts the calls macOS makes to the
: Supports a wide range of macOS versions, from legacy 10.6 up to 15.x. FakeSMC vs. VirtualSMC FakeSMC3 with plugins - GitHub Usually caused by: fakesmc
PCs don't have an Apple SMC chip. Without it, macOS panics instantly during boot with a cryptic error: "SMC: successful init, but no SMC found."