Instant Pot Pressure Cooker F10 Error Code Fix

by

What This Error Means

F10 on an Instant Pot pressure cooker means a temperature sensor / runaway overheat fault. The control board thinks the pot is way hotter than it should be or can’t read the sensor correctly, so it shuts everything down.

In plain terms: the safety brain doesn’t trust the temperature reading, so it kills the heat to avoid a meltdown or fire.

Official Fix

This is the “by the book” path, straight from how the manufacturers want it handled.

  • Hit Cancel, then unplug the cooker. Let it sit at least 30 minutes so the internals actually cool down.
  • Pull out the stainless inner pot. If you ran it with very thick sauce, almost no liquid, or rice stuck to the bottom, that can spike the sensor. Scrape and wash everything clean.
  • Check the bottom of the inner pot and the heater plate inside the base. They should be clean, flat, and dry. Any burned-on food, warped metal, or moisture can trigger F10.
  • Make sure you really did put the inner pot in. Heating an empty base with no pot will throw temperature faults fast.
  • Inspect the sealing ring, float valve, and steam release valve. If steam is leaking like crazy, the cooker runs hotter than expected trying to reach pressure and the safety system can freak out.
  • Dry off any spills down the sides or into the base. If broth or starchy water has gone under the liner, let the unit air-dry overnight before you try again.
  • Reassemble everything. Add at least 1–1.5 cups of water. Run a short test on Pressure Cook / Manual for 5 minutes.
  • If it heats, pressurizes, and finishes with no F10, you’re good. If F10 comes back immediately or every time, the manual answer is: stop using it and contact Instant Pot / Instant Brands support. The temp sensor or control board is likely bad and they don’t consider it user-serviceable.

The Technician’s Trick

Here’s the off-the-record stuff techs do when a pot is out of warranty and headed for the trash anyway. If tools and mains voltage scare you, skip this.

  • Unplug it. Fully. No “it’s just off”. Cord out of the wall and out of the pot.
  • Remove the inner pot and trivet. Flip the cooker upside down on a towel.
  • Take off the bottom cover (usually a few Phillips screws). Watch for sharp edges.
  • Look for obvious damage: burned spots on the board, melted plastic, or corrosion from old spills. If it’s charred, don’t fix it—bin it.
  • Find the round metal temperature sensor disc in the middle of the heater plate. It should sit flat against the bottom of the inner pot when assembled.
  • Gently clean the face of that sensor and the mating spot on the inner pot with a bit of isopropyl alcohol on a cloth. You want clean, shiny metal-to-metal contact, not grease or carbon.
  • Make sure the little spring or bracket pushing the sensor up isn’t bent flat. If it’s lazy, gently bend it so it presses the sensor firmly against the pot bottom again.
  • If you have a meter and skills, check the thermal fuse (inline fuse near the heater). Open (no continuity) = blown safety fuse. Replace only with the same temp and amp rating, never a “stronger” one.
  • Reassemble the base, flip it back over, add 2 cups of water, and test on Pressure Cook. If F10 is gone and it comes to pressure normally, you just saved it. If the code stays, the control board itself is likely shot—usually not worth chasing unless you find a cheap donor unit.

Is It Worth Fixing? (The Financial Verdict)

  • ✅ Fix: Under 5 years old, no burn damage or melted plastic, error only started after a bad cooking session (thick sauce, scorched food), and you’re comfortable cleaning and testing.
  • ⚠️ Debatable: Mid-age pot (5–7 years), out of warranty, needs a sensor or thermal fuse but the rest is clean. Worth it if you’re handy or parts are cheap.
  • ❌ Replace: Strong burnt smell, melted underside, visible board damage, or repeated F10 even after cleaning and cooling. At that point, put the money toward a new cooker.

Parts You Might Need

As an Amazon Associate we earn from qualifying purchases.

See also

Working on other machines that like to scream in error codes? These breakdowns can help too: