Troubleshooting

The service isn’t running

If the background service stops — crashed, or stopped manually — every fan reverts to BIOS/automatic control, and the tray shows a notification. Fanture never leaves fans in whatever state they were in when the service dies; that’s the whole point of the two-process design. Restarting the service (or just the app, which can restart it from Settings) restores whatever profile was active.

No controllable fans found

This can be entirely normal: most laptops and many prebuilt desktops don’t expose fan control to software at all, regardless of the app. It can also mean the PawnIO driver isn’t installed — check Hardware for how to tell the difference.

Stall alerts

A fan shows a “not spinning” warning — on its card on the Fans page and on its row in the tray window — while it reads 0 RPM when it should be spinning, above its calibrated start duty. The warning clears by itself once the fan spins again. It usually means the fan physically isn’t spinning: check the cable, or that it’s actually plugged into the header Fanture thinks it’s driving. Calibrating the fan first makes this warning meaningful; before that, Fanture doesn’t know what duty a fan is supposed to start at, and treats a header that never reports any RPM as empty and hides it.

Data and logs

• User settings (saved profiles, fan names, display preferences): %AppData%\Fanture\
• Service settings (fan policies, limits, calibration): %ProgramData%\Fanture\
• Crash log: %LocalAppData%\Fanture\crash.log

Export diagnostics

The Hardware page’s “Export diagnostics” button writes a file with the current sensor readings, app and service versions, driver status, and the service’s own recent log lines — everything worth attaching to a bug report in one file. It only ever writes to a location you choose; Fanture never uploads it anywhere on its own.

Still stuck?

Open an issue on the GitHub repository with what you’re seeing and, ideally, an exported diagnostics file attached.