MSFS 2020: Cessna 172 Skylane (steam gauge) flaps not moving after latest update

That symptom (indicator moves, but the actual surfaces and aerodynamics don’t) usually points to either (a) a conflicting control binding firing at the same time, or (b) something in the install/community aircraft config overriding the model/flight model after the sim update.

Here’s how I’d tackle it, step by step.

1) Rule out a binding conflict first (fastest win)

1. Load the 172 Skylane (steam gauge) on the runway in a totally “default” situation (clear weather, no failures).
2. Go into Controls Options and use the search box for “flaps”.
3. Make sure you don’t have multiple commands bound that could fight each other (common culprits are: an axis bound to flaps and buttons for flaps up/down, or duplicate devices each bound to flaps).
4. Temporarily clear every flap-related binding except one simple method (e.g. just “Flaps Decrease” / “Flaps Increase” on the keyboard).
5. Test again in external view.

2) Verify it’s not an aircraft-specific issue by testing another plane

1. Try a different default aircraft (anything with visible flaps).
2. If flaps work normally elsewhere, that narrows it down to something specific to the 172 variant or something overriding it.

3) Check for a Community folder conflict (very common after a sim update)
Even if you didn’t install a “172 mod”, you can still get odd side effects from unrelated packages.

1. Exit MSFS completely.
2. Temporarily move everything out of your Community folder to a holding folder (don’t delete—just move).
3. Start MSFS and test the 172 again.

If it works with Community empty, add your add-ons back in batches until it breaks again—then you’ve found the conflicting package.

4) If you’re on Steam: do a quick file integrity check
A partial/dirty update can leave you with weird “half-working” systems where cockpit indications still animate but the model/flight model isn’t being driven correctly.

1. Close MSFS.
2. In Steam, run “Verify integrity of game files”.
3. Re-test the 172.

5) Also worth checking: assistance/failure states
Not as likely given your description, but still worth a look:

1. Make sure you don’t have any failure enabled that could “jam” flaps.
2. If you use any kind of aircraft persistence/save-state tool, try a completely fresh load (not a saved flight).

A couple quick questions so we can narrow this down fast:

• Is this happening only on the 172 Skylane (steam gauge), or on other aircraft too?
• Do you have anything in Community that touches the C172 (mods, flight model tweaks, realism packs), or any control utilities running externally?
• Are you using a flap axis on a throttle quadrant (or only buttons)?
• What exact flap input are you using (keyboard, yoke buttons, Honeycomb/Logitech, etc.)?